Switch Music Distributors: Protect Your Release History

Moving your catalog can put years of release history at risk if you remove the old delivery too soon. To switch music distributors safely, preserve the original recordings and identifiers, then coordinate the handover.

However, matching files doesn’t guarantee that streams, playlists, reviews, or analytics will carry across. Your best protection is a documented transfer, with clear timing and checks on every platform.

Start by separating the records you control from the platform data you can’t guarantee.

Understand What Can Survive a Distributor Switch

Recordings and identifiers can travel with you

An ISRC identifies a particular sound recording. Changing distributors doesn’t, by itself, create a new recording, so the same unchanged master should retain its existing ISRC.

A UPC or EAN identifies the release package, such as a single, EP, or album. Keep it separate from track-level codes. Whether you can reuse that package identifier depends on the release and the receiving distributor’s procedures.

Your release title, artist name, version labels, artwork, and original release date also belong in the transfer record. Together, these details help services recognize the replacement delivery.

Performance history isn’t part of the audio file

Public play counts and playlist connections depend on how each platform matches the incoming delivery. Meanwhile, the old distributor’s sales statements and analytics usually remain separate records.

Release history and performance data may therefore fail to transfer even when the audio and metadata match. Reviews, saved-library connections, and other platform-specific information may also change.

DistroKid says services, especially Spotify, may try to maintain counts or playlists. CD Baby also warns that retention isn’t guaranteed. Treat matching as a risk-reduction measure, never a promise that every historical connection will survive.

Build a Master Catalog Before You Upload

Record the details of every release and track

Create one approved spreadsheet before entering information into the new distributor. For each release, record its title, UPC or EAN, track order, original date, territories, and current distributor.

For every track, save the ISRC beside the exact title, artist names, version label, duration, audio filename, and master owner. Include contributor credits, explicit-content settings, and copyright lines.

Also save existing artist-profile links and public release links. These give support teams a reference when a delivery lands on the wrong page.

TuneCore’s identifier instructions explain where existing codes can be entered. Check your receiving distributor’s equivalent process before uploading.

Archive the evidence behind the catalog

Download metadata exports, royalty statements, delivery confirmations, and screenshots before cancelling anything. Save the original masters and artwork alongside contracts, split sheets, sample clearances, and cover-song permissions.

Possessing an audio file doesn’t establish ownership or permission to distribute it. Check whether your agreements cover the intended territories, formats, and new delivery arrangement.

Hold disputed recordings for review rather than including them in a bulk transfer. An old physical-release licence may not cover worldwide streaming.

Finally, back up the archive in more than one place. Your old account could become inaccessible after closure, even though you still need its records.

Match the Audio and Metadata Exactly

Use the same master, not a replacement version

A distributor migration is a poor time to introduce a remix, radio edit, new vocal, or different master. Deliver the original approved audio whenever you’re transferring the existing recording.

Don’t replace a missing master with audio downloaded from a streaming service. Recover the source file from your archive, engineer, label, or former distributor where available.

A materially different recording may need a separate ISRC. TuneCore’s release-change guidance allows previous ISRCs for tracks that remain exactly the same.

If you’re unsure whether a change creates a different version, confirm the identifier treatment before delivery.

Keep names, versions, and dates consistent

Match track titles, release titles, artist names, featured-artist roles, version labels, and original release dates. Preserve spelling, punctuation, accents, and spacing.

For example, “Mark Leigh” and “MarkLeigh” aren’t identical metadata strings. Likewise, switching between “Radio Edit” and “Original Mix” creates conflicting version information.

Check track order, artwork, credits, language, and explicit flags too. Distinguish the original release date from any scheduling field used for the new delivery.

If an existing field is wrong, ask how to correct it without disrupting the transfer. Combining migration with a rebrand or catalog revision makes problems harder to trace.

Confirm the Transfer Terms Before You Switch Music Distributors

Ask the receiving distributor whether it accepts existing ISRCs, supports existing UPCs, and can deliver to your current artist profiles. Find out whether catalog imports need manual review.

For an unchanged album, TuneCore permits reuse of its UPC. However, adding, removing, or reordering tracks changes the package and affects that treatment. Don’t assume every distributor follows the same workflow.

Read the old agreement too. Confirm notice periods, renewal dates, takedown charges, account-closure rules, and access to unpaid balances. Distribution cancellation and account closure may be separate actions.

Get takedown timing in writing. Ask when the request will reach stores, whether you can remove individual releases, and how to confirm completion.

Procedures differ. DistroKid’s guidance suggests uploading through the new distributor, then removing the old delivery the next day. CD Baby advises waiting until the replacement is live. TuneCore’s transfer guidance acknowledges possible overlap or a gap.

Use your providers’ current instructions to agree on a coordinated plan. None of these procedures guarantees a store-by-store completion date.

Deliver the Replacement and Control the Overlap

Temporary overlap can help services recognize a replacement, but unmanaged duplicate listings can confuse listeners. Aim for one continuing public release once the handover finishes.

Unless your receiving distributor gives clear written instructions otherwise, keep the old delivery available until you’ve verified the replacement. Don’t rely only on an “approved” message in the upload dashboard.

Follow the agreed sequence:

1. Submit the unchanged audio and metadata through the new distributor, including the existing ISRCs.
2. Confirm delivery and inspect the replacement on each service covered by the transfer.
3. Request removal of the old distributor’s delivery at the agreed point.
4. Recheck the catalog after stores process the takedown, then resolve gaps or duplicate listings.

Make the takedown request specific. Identify the release, UPC, and old distributor’s delivery rather than asking vaguely to “remove my music.”

For a large catalog, consider transferring a small batch first. This helps expose profile-mapping or metadata problems before they affect every release.

Also avoid scheduling the move during an important campaign if possible. A temporary listing problem is harder to manage while listeners are following newly published links.

Check Every Platform After Delivery

Verify the listing, profile, and availability

Spotify working correctly doesn’t prove that Apple Music, Amazon Music, Deezer, or TIDAL received the catalog correctly. Review each destination included in your delivery.

Open the release from the artist page and test playback. Compare the title, artwork, version, duration, track order, explicit flag, and displayed date with your master record.

Check artist mapping carefully, especially when another performer uses a similar name. Featured artists should also connect to the intended profiles where the service supports that mapping.

Review territorial availability too. A release can appear in one country while remaining unavailable elsewhere, so compare delivery settings with your licensed territories.

Investigate missing history and duplicate releases

Look for separate copies of the same release, changed public counts, broken playlist entries, or links that now point to unavailable tracks. Save screenshots showing the problem and the date checked.

A matching ISRC helps identify the recording, but it doesn’t prove that the platform has linked both deliveries. Ask the new distributor to investigate rather than repeatedly re-uploading.

Give support the artist name, release title, UPC, track ISRCs, old and new store links, and delivery dates. Include the exact discrepancy.

After the old delivery disappears, check again. Some problems only become visible once the temporary overlap ends. Don’t close the support ticket merely because one platform looks correct.

Reconcile Royalties Before Closing the Old Account

A catalog transfer doesn’t move money already held by the previous distributor. Keep access to statements and outstanding payouts until you’ve reconciled them.

Compare reports using ISRC, service, territory, and usage period. Payment dates alone can mislead because reporting and payment often happen later than the listening activity.

A statement arriving after takedown may cover earlier streams. Check the usage period before treating it as evidence of an active duplicate delivery.

Confirm tax and payment details in the new account. Recreate collaborator splits where required, and check whether those settings apply to the transferred catalog. A split-payment tool doesn’t replace the underlying agreement.

Also ask whether YouTube Content ID or other rights-management services need a separate handover. Leaving overlapping claims active can create disputes even when streaming-store delivery is correct.

Keep the final old-account export alongside the first new-account statement. That creates a clear boundary for later royalty enquiries.

Retain your own catalog chronology as well. If a platform changes a displayed date or loses historical analytics, your records should still show what you released, when, and through whom.

Protect the Catalog Beyond the Handover

You can switch music distributors with less risk by preserving the exact masters, identifiers, metadata, and supporting records. Platform history still depends on each service’s matching and retention procedures.

Keep the old delivery available until the agreed handover point, then verify every destination after removal. Your catalog archive remains the reliable record, even when a platform’s public history changes.