Overview

This page explains how to migrate an existing catalog from a full-service distributor to Reprtoir Distribution. The same principles may apply when migrating from one external distributor to another, but in that case you should always consult the new distributor for specific rules, as each platform may require different ingestion procedures.

When migrating to Reprtoir Distribution, the delivery licensee changes on DSPs. Because of that, all DSPs require a full redelivery and a full takedown of the previous versions. A structured migration process is essential to preserve historical data such as streams, playlists, chart positions, save counts, and artist profile continuity.

❗️
Notes on Non-Reprtoir Migrations
These guidelines apply specifically to migrations into Reprtoir Distribution. If you are migrating from one external distributor to another, the new distributor’s technical rules, validation workflow, and migration policy always take precedence.

Process Summary

Step	Action	Details
1	Deliver the full catalog through Reprtoir Distribution	Use the same ISRC and UPC values as the previous distributor. DSP matching depends primarily on these identifiers.
2	Wait 5 days	This waiting period allows DSPs to detect and match new versions. Spotify explicitly recommends this window as best practice.
3	Verify migration success	Check that the new versions are correctly matched and that artist profiles have not been duplicated.
4	Send takedown requests to the previous distributor	Only after both the 5-day window and the verification checks. Early takedowns significantly increase the risk of mismatches and duplication.
5	Apply metadata updates if needed	Once matching is confirmed, major metadata adjustments (titles, credits, versions) can safely be applied.

Technical Rules

Identifiers (UPC and ISRC)

The stability of identifiers is the most critical element in a successful migration.

UPC must remain identical to the original distributor’s delivery.
ISRC must remain identical for every Track.
DSPs use this pairing to match old and new versions.
Changing either value will create a new, unrelated product page.

Even a partial mismatch (for example same UPC but different ISRC) prevents proper version matching.

Metadata Consistency

During migration, metadata should remain strictly identical to the previous version.

Titles, Subtitles, Main Artists, Featured Artists, and contributor roles should be unchanged.
Minor typo corrections are tolerated but unnecessary changes should be avoided.
Major modifications (new versions, new featurings, different titles) must only be applied after the migration has completed and DSP matching is confirmed.

Audio and Artwork Requirements

DSP matching depends partly on waveform analysis.

Audio:

Format changes are acceptable (WAV 16-bit → FLAC 24-bit).
Audio length must remain the same.
Variations under 5 seconds are tolerated; more significant differences may cause DSPs to treat the track as a different master.
Remasters, edits, noise reduction, or normalization changes may break matching.

Artwork:

Artwork should remain identical to the previously delivered image.
Changing artwork during migration increases the risk of mismatches.

Artist IDs

Always include artist IDs for:

Spotify Artist ID
Apple Music Artist ID

Missing or incorrect Artist IDs frequently lead to duplicate artist profiles. This is one of the most common migration issues.

Platform Behavior

DSP	Migration Type	Specific Notes
Spotify	Redelivery before takedown	Matching usually within 48–72 hours. A 5-day delay and prior verification are recommended before takedown.
Apple Music / iTunes	Redelivery before takedown	Matching is usually automatic when metadata and identifiers remain identical.
Deezer	Redelivery before takedown	Very strict with titles and artist names. Even minor inconsistencies may break matching.
Amazon Music	Redelivery before takedown	Preserves historical data if UPC, ISRCs, and metadata remain consistent.
TIDAL, Qobuz, FLO, NetEase	Redelivery before takedown	Follow the same 5-day buffer and verify matching before takedown.
SoundCloud	Specific process required	Requires prior approval and a catalog report submission. Follow platform-specific steps.

Timing and Validation

DSP sync time: usually 48–72 hours.
Recommended buffer: at least 5 days after delivery before requesting takedowns.
Matching validation: confirm that the new version appears as the primary version under each Track or Album page.
Profile validation: confirm that Artist Profiles have not been duplicated or fragmented.

Takedown requests should only be sent once both the time buffer has elapsed and matching has been verified on key DSPs.

Best Practices

Migrate catalog in batches when possible.
Avoid simultaneous updates during migration (new versions, rebranding, track list changes).
Archive all original metadata, audio, artwork, and reports before starting.
Review DSP dashboards after migration to confirm proper matching and profile continuity.
If a DSP fails to match a Release, contact Reprtoir Support. Some platforms accept manual matching requests or can intervene on specific releases.

Notes on Non-Reprtoir Migrations

These guidelines primarily apply when migrating to Reprtoir Distribution. If you migrate from one external distributor to another (without involving Reprtoir Distribution), your new distributor’s rules take precedence. Always confirm with them:

identifier requirements,
migration buffers and recommended delays,
metadata constraints,
platform-specific migration procedures.