When to Remove a Release From Your Old Distributor

The removal gate is a live replacement, not a dashboard label

Request removal from the old distributor only after the replacement is live on the stores that matter for the release. The facts for this cluster call out Spotify, Apple Music, and Amazon Music as separate checks. Open each destination yourself, confirm the artist, title, version, and audio are the intended release, and save the URLs and check date in your release log.

Before you press send on the removal request, confirm four things in your own records:

• The replacement page is live on Spotify, Apple Music, and Amazon Music, checked one store at a time.
• The new delivery uses the original ISRCs and UPC, with the same audio file and matching release metadata.
• The old distributor's Content ID state is recorded, including whether its registration has been de-registered.
• The old dashboard reports and sales data are exported, and you know which account will receive the remaining reports.

Use the overlap as a control, not a promise

The commonly cited 48-to-72-hour overlap means keeping the old release live for a short period after the new delivery appears. Practitioners recommend it so a DSP has time to see the duplicate deliveries. The facts sheet is clear about the limit: this is convention, not a documented Spotify guarantee.

Spotify's track-linking process looks at more than the ISRC. The cited distributor and label-service sources identify the artist name, track title, audio fingerprint, and duration as matching signals too. Use the identical audio file and preserve the release details. A new master, changed duration, or altered styling gives the platform a harder matching problem.

Once the replacement is live and the overlap has done its job, request removal through the old distributor. The exact form and processing time belong to that provider. Keep the request confirmation in the same record as the store URLs. If you want the stream-preservation risks in full, read the guide to switching without losing Spotify streams.

The royalty tail stays with the old account

A removal request changes where the release is delivered. It does not move old distributor reports into the new dashboard. The old distributor continues collecting for streams that happened while its delivery was live, up to the point of removal. Leave that account open while those reports work through the reporting cycle.

The cluster facts put distribution royalty reporting at roughly two to four months from stream to payment, after the DSP and distributor processing windows. Publishing royalties use separate organisations and schedules. Treat the dates as a monitoring window, not a promise from every provider. Check the old account for final statements before you close it.

For the statement work after the handoff, the distributor royalty statement guide is the useful next read.

Content ID has its own offboarding order

Store removal and YouTube Content ID are related release operations, but they are not the same switch. If the old distributor registered the recording with Content ID, de-register that old registration first. Confirm that it is gone before the new distributor creates a replacement registration. Two active registrations for one recording can create an ownership conflict and restrict or block monetization.

Write the Content ID confirmation into the release log. Do not rely on a plan name or a support ticket being open. The cited Symphonic and CD Baby help material describes the conflict and the old-off, new-on order. If your distributor does not offer Content ID, mark that field not applicable rather than inventing a second task.

Record the handoff before you request removal →

A release log makes the final decision auditable

A small record is enough. Capture the release identifiers, the replacement URLs, the date each store was checked, the removal request number, the Content ID state, and the date you will check the old account for its final reports. This is useful when a release has several tracks because one missing destination can hide inside an otherwise successful catalog transfer.

The artist and release in that record are invented for the example. The fields are the point: they show what you checked and when, without claiming that a platform will merge or preserve anything automatically.

Primary references for this guide include Spotify for Artists on getting music onto Spotify, ISO 3901:2019, the IFPI ISRC Handbook, and CONNECT Music Licensing's ISRC guidance. The overlap recommendation comes from the facts sheet's cited practitioner material, including Ari's Take, and is not presented as Spotify policy.