Export overview

Exports turn persisted catalog data into a file or report for review or delivery. Available output depends on the selected export type and destination profile. Some platform templates are best-effort CSV only; API delivery is not implied. Draft or incomplete data should remain clearly labeled.

Select the correct Catalog, finish imports, review Audit and Rights findings, and confirm the recipient's field requirements. Export permission depends on Workspace role and plan.

Open Catalog → Exports at /exports. Spreadsheet Import also provides CSV and XLSX catalog export actions where enabled.

1. Choose the export purpose or destination template before selecting fields.
2. Select the tracks or catalog scope and review the count.
3. Include metadata, rights, validation, or other supported sections required by the recipient.
4. Choose CSV, XLSX, PDF, or JSON only when that option is displayed for the selected workflow.
5. Review warnings and draft status, then generate the export.
6. Download the result, inspect identifiers and column structure, and retain its execution context.

The file reflects canonical data at generation time. Later edits do not change an existing download. Export history or job status may be available for asynchronous generation.

Use a small sample for a new destination, preserve UTF-8 encoding, and avoid sending rights data without verification. Keep a record of template and generation time.

A missing format may be unsupported for that template. Empty fields usually reflect incomplete source data, not an export transformation failure.

Check permission, catalog selection, Processing Queue, and export history. Retry only after a failed job finishes. If a CSV opens incorrectly in a spreadsheet application, import it explicitly as UTF-8.

See Catalog Audit, Rights & Ownership overview, and Spreadsheet Import.