Spreadsheet Data Hub

Spreadsheet Import

Map, validate, review, and explicitly persist CSV or XLSX track metadata.

7 min read
7 min read
Last reviewed 2026-08-03
Last reviewed 2026-08-03
Beginner
Beginner

Overview

Spreadsheet Data Hub converts mapped CSV or XLSX rows into proposed Catalog actions. Validate Data parses, normalizes, matches, and reports issues without writing tracks. Persistence begins only after an authorized user selects the explicit Import N Tracks action.

Before you begin

Select the destination Workspace and Catalog. Prepare a file under the displayed size limit with one header row and one track per data row. Keep identifiers such as ISRC, ISWC, IPI, and CAE in dedicated columns where possible.

Where to find it

Open Catalog → Spreadsheet Data Hub at /data-hub.

Step-by-step instructions

  1. Select the Workspace and destination Catalog.
  2. Upload a CSV or XLSX file.
  3. For an Excel workbook, select the worksheet containing Tracks.
  4. Map each source header to the appropriate CatalogIQOS field and ignore irrelevant columns.
  5. Select Create new tracks, Update matched tracks, Create unmatched and update matches, or Validate without importing.
  6. Select Validate Data and review rows ready, warnings, blockers, matches, and proposed actions.
  7. Review non-blocking warnings and correct blockers before continuing.
  8. Select Import N Tracks or the create/update count shown by the primary action.
  9. Wait for the persisted import result showing created, updated, skipped, warning, and failed counts.
  10. Select View N Imported Tracks to open only the records stored by that execution.

What happens next

Successful track IDs are recorded on the import execution. Catalog counts and relevant views are refreshed. Saving a Mapping Profile is optional and stores mapping preferences, not track data.

Best practices

Validate a representative batch, inspect match confidence before updates, and use create-only mode when existing records must remain untouched.

Common problems

Warnings such as missing ISWC or publisher IPI/CAE do not block import. Invalid required titles or identifiers can block rows. Seeing “Validation complete” does not mean tracks exist yet.

Troubleshooting

If imported tracks are absent, verify that the import action—not only validation—completed and use the execution-scoped View Imported Tracks link. Revalidate when the snapshot becomes stale or the target Catalog changes.

Related articles

Read Resolve validation errors and duplicates, Create your first Catalog, and Catalog Audit.