A conceptual data mapping document primarily records how concepts and data from a source format map into OpenUSD concepts, schemas, prims, properties, and authored scene description. NVIDIA's Learn OpenUSD Data Extraction lesson states that producing such a document is valuable because it serves as a data specification for extraction implementation, helps stakeholders set requirements and expectations, and helps developers understand which features are supported between two formats and what to expect from the extraction phase. (docs.nvidia.com)

Option D is correct because the document is specifically about translation between OpenUSD and another data representation, such as a DCC format, interchange format, or custom application model. Option A is broader than the purpose of the document; an end-to-end workflow specification may include tools, review, publishing, validation, and delivery, while conceptual mapping focuses on data correspondence. Option B is also too narrow because content structure is only one possible mapped concept. Option C is incorrect because storage requirements are not the core concern. This aligns with Data Exchange Data Extraction, Conceptual Data Mapping, Format Translation, and Converter Design.