Can You Move One Release to a New Music Distributor?

Set the boundary before you upload

Write down the exact release that is moving, its tracklist, the old distributor, the new distributor, and the releases that will stay where they are. Ask the new provider whether its upload form accepts a single release with existing identifiers. Read the old provider's retention and takedown terms too. The split is only useful if the remaining catalog stays covered.

A distributor's support team should be able to answer three practical questions before you start: can you submit one title without moving the rest, can you enter the release's existing codes, and what happens to the old delivery after you request removal? Save those answers with the release record.

Keep the release identity intact

Spotify directs independent artists to an approved distributor or label for delivery. The release identity then has two useful layers: an ISRC identifies each sound recording, while a UPC identifies the release as a whole. That is why a partial move needs the selected title's release record and the codes for each track, rather than a fresh set made during upload.

The official IFPI ISRC Handbook and CONNECT Music Licensing's ISRC guidance describe the recording code as tied to the recording, not to the distributor account. The facts sheet also cites ISO 3901:2019 for the standard. If the new provider wants to assign a new ISRC to an unchanged recording, stop and ask why before accepting it.

Carry over the original audio file and the release details that help a DSP match the delivery: artist name, track title, version, featured-artist formatting, duration, artwork, explicit status, and release date. A changed master or changed metadata makes a clean match harder. For the code relationship itself, see the UPC versus ISRC guide.

Run the one-release transfer in order

The safest sequence is a short handoff with a clear stop point at every stage:

1. Export the selected release's ISRCs, UPC, track titles, artist styling, version fields, artwork, explicit status, original release date, sales reports, and available analytics from the old dashboard.
2. Check the selected release's YouTube Content ID state. If the old distributor registered it, de-register that registration before a new provider creates another one.
3. Upload only the selected release to the new distributor. Enter the original codes and use the same audio file and matching release metadata.
4. When the replacement delivery appears, keep the old release live for the short overlap commonly recommended by distributors and practitioners. Forty-eight to seventy-two hours is a convention from the cited practitioner material, not a DSP guarantee.
5. Open the replacement page on Spotify, Apple Music, and Amazon Music. Check the artist, title, version, artwork, and audio one store at a time. Save each URL and the date checked.
6. Request removal of the selected release from the old distributor. Do not request account closure or a catalog-wide takedown. Save the request number and confirmation.
7. Leave the old account open while its remaining reports and payment cycles clear. Its dashboard history does not become part of the new distributor's analytics.

If you need the removal gate in more detail, read when to remove the old release. It covers the evidence to collect before the request and the royalty tail afterward.

The rest of the catalog needs its own record

A partial move creates two operating contexts. The selected release is being delivered by the new provider. The releases you leave behind still depend on the old provider's plan, store-retention terms, support channel, and reporting history. Keep a short inventory showing which provider owns delivery for each release and where its reports live.

DSP-native analytics and distributor analytics are different records. Spotify for Artists and Apple Music for Artists can retain their own artist-side history, while provider dashboards and sales reports may not transfer. Export the old reports before you lose access, then keep checking the old account for streams that happened before the selected release was removed.

The broader risks are collected in what breaks during a distributor transfer and the account-retention guide covers what to check before stopping payment.

Record the selected release before you upload it →

A partial-catalog record should look like this

Keep the release boundary visible in the same record as the store checks. That makes it harder to remove the wrong title or assume that a successful album move also moved the rest of your catalog.

The useful detail is the boundary. The record names the one release that moved, the releases that did not, and the evidence for the removal request. If any of those fields is missing, pause before you touch the old delivery.

Pause when the handoff cannot be verified

Do not force a partial move when the new distributor cannot accept the original release data, the old account's retention terms are unclear, or the replacement page is missing on a store you rely on. Fix the evidence gap first. A new ISRC, a changed master, or an unresolved Content ID registration can turn one release operation into a separate catalog repair.

The primary references for this guide are Spotify for Artists on getting music onto Spotify, the ISO 3901:2019 standard, the IFPI ISRC Handbook, and CONNECT Music Licensing's ISRC guidance. The overlap, Content ID, analytics, and reporting cautions follow the practitioner and help sources named in the switching-distributors facts sheet. None of those sources promises that a DSP will merge or preserve every result automatically.