Overview

This procedure applies when your organization uses its own DSP licensing agreements and delivers content through Direct-to-DSP Delivery.

In this configuration, the licensee does not change. Because of that, the migration process varies significantly depending on each DSP’s internal policies.

Some DSPs handle partner changes internally with no redelivery needed. Others require full redelivery, takedown coordination, or specific pre-approval steps (e.g., SoundCloud).

This page summarizes the behaviors commonly observed across major DSPs and outlines the best practices for preserving stream counts, playlist positions, and artist profile continuity.

❗️
Notes on Non-Standard DSP Migrations
These guidelines apply specifically when migrating to Reprtoir’s Direct-to-DSP Delivery channel. If you migrate between external distributors or change partners outside of your own DSP agreements, the migration rules and ingestion policies enforced by each DSP or distributor always take precedence.

Process Summary

Step	Action	Details
1	Confirm DSP requirements	Each DSP applies its own migration policy. Pre-validation is mandatory.
2	Deliver the new catalog if required	Use identical ISRC and UPC codes. Keep all metadata strictly aligned with existing data.
3	Verify migration success	Confirm matching before any takedown action is considered.
4	Coordinate takedown (if applicable)	Some DSPs require takedown before, others after redelivery.
5	Validate continuity	Ensure streams, playlists, and profiles remain attached to the same IDs.

Platform Behavior

DSP Type	Migration Requirement	Details
Automatic migration (no takedown or redelivery)	Amazon Music, Apple Music, Deezer, Facebook, Pandora, KKBOX, Boomplay, etc.	DSP handles partner switch internally using ISRC/UPC matching.
Full redelivery before takedown	Spotify, TIDAL, Qobuz, FLO, NetEase	Deliver new versions first, wait ±5 days, confirm matching, then takedown.
Full redelivery without takedown	7Digital, TikTok	New delivery overwrites the previous one.
Takedown before redelivery	AWA	Legacy catalog must be removed before delivering the new versions.
Specific manual process	SoundCloud	Requires form + catalog inventory before approval.

Technical Rules

These rules are identical to the migration rules used for Reprtoir Distribution:

Identifiers

ISRC and UPC must remain strictly identical.
DSP mapping relies on the ISRC–UPC pairing.
Changing identifiers creates new products in catalog.

Metadata

Metadata should remain identical during migration.
Minor typo corrections are tolerated.
Major editorial changes should only be applied after migration is completed and verified.

Audio and Artwork

Audio variations are allowed only within acceptable tolerance (±5 seconds).
Remasters or significant edits may break matching.
Artwork should remain identical to the previously delivered file.

Artist IDs

Spotify Artist ID and Apple Music Artist ID must always be supplied.
Missing IDs risk generating duplicate artist pages.

Timing and Validation

DSP sync times typically range from 1 to 5 days, depending on the platform.
Always verify that each new version attaches correctly to the existing artist profile.
Confirm that track-level statistics, playlists, and releases remain intact.
If a mismatch occurs, contact the DSP directly. Some platforms can merge entries manually.

Best Practices

Validate each DSP’s migration protocol before initiating the process.
Migrate in batches when possible to control risk.
Maintain a complete and accurate catalog mapping (ISRC ↔ UPC ↔ Release).
Monitor analytics and reporting closely for several days after each migration step.
Delay any major metadata updates until the migration is fully confirmed.
Keep historical assets easily accessible in case DSP verification teams request them.