A label decides to leave its distributor. The new company promises better reporting, lower fees, faster support. Somebody uploads the entire catalog on Monday and asks the old distributor to take it down on Tuesday.
By Friday, several releases have vanished. One album is back as a duplicate. A track is still on Spotify but its play count has restarted at zero. Two artists are mapped to the wrong profiles, and both distributors are claiming the same fan-uploaded videos on YouTube.
The move looked like a file transfer. Operationally it was something else entirely: a change in the active supplier of recordings, metadata, rights instructions and payment information across a dozen platforms at once.
A careful transfer can preserve a lot of a catalog's platform history. It's never guaranteed — and an ISRC on its own will not repair contradictory deliveries.
What usually survives a distributor change
Spotify officially supports track linking. When a recording is redelivered, Spotify can associate the replacement with the existing track and keep its play count. The conditions are strict: matching audio and metadata, including duration, title and artist name. You can verify linking by comparing the displayed play counts in Spotify's desktop app. Notably, Spotify's own guidance doesn't promise every replacement will link.
Distributor documentation says the same thing in the same careful way. DistroKid advises identical audio, ISRCs, titles and album information — while explicitly stating it can't guarantee streams or playlist placements survive. CD Baby tells transferring artists to wait until the replacement is live before requesting a takedown from the previous distributor.
When matching works, a recording may keep its Spotify play counts, its place in playlists containing the linked track, its connection to the existing recording, some engagement history, and continuity on the correct artist profile.
Not everything comes along. DistroKid warns that iTunes and Amazon reviews may be lost. Release-level links, product reviews, dashboards, historical earnings reports, smart links and platform-specific promo features may stay attached to the old delivery or account.
Treat continuity as something to verify platform by platform — not as a blanket promise anyone can make you.
Start with a catalog export
Don't start by downloading audio from a streaming service or rebuilding metadata from memory.
Build a catalog manifest containing, at minimum: release title; track title and version; primary and featured artists; existing artist-page identifiers; ISRC for every recording; UPC or other release identifier; original release date; label name; track order and disc number; explicit-content status; composers and contributors; territories; audio filename, duration and technical spec; artwork file; current platform links; the current distributor's internal identifier; ownership and royalty splits; YouTube Content ID status; and any active licences, exclusions or territorial restrictions.
DDEX's catalog-transfer guidance goes considerably further, recommending transfer of release identifiers, titles, artist roles and sequence, genres, dates, label information, contributors, rights controllers, publishing data and recording identifiers. That list is written for professional rights-controller transfers, but it makes the point for everyone: a catalog is not adequately represented by a folder of WAVs and a spreadsheet of ISRCs.
Keep the export outside both distributors. A dashboard should never be the only surviving record of the catalog it manages.
An ISRC identifies the recording, not the release
The ISRC belongs to the sound recording, and it should stay attached to that recording when the distributor changes. A remix, live version, instrumental or materially different master needs its own. Moving an unchanged recording does not.
The UPC identifies the release product. DDEX is explicit that an ISRC can't serve as the identifier for an album containing multiple resources.
That distinction creates a practical headache, because distributors handle it differently. TuneCore says the same UPC and ISRCs may be used when the redistributed album is identical — a changed track order or tracklist requires a different UPC. DistroKid accepts outside ISRCs but not outside UPCs for new uploads.
Here's the part worth understanding: a new UPC does not automatically require new ISRCs for unchanged recordings. It does mean the replacement may be treated as a new release package even though its tracks can still link to the existing recordings.
Record both sets of identifiers. Don't quietly overwrite one with the other in your ledger.
Matching means more than copying the title
For track linking, the new delivery has to describe the same recording.
| Field | Transfer treatment |
|---|---|
| Audio | Use the exact original master file where possible |
| ISRC | Reuse the existing code for the unchanged recording |
| Track title | Preserve spelling, punctuation and version information |
| Artist names | Preserve primary and featured-artist roles |
| Duration | Don't trim silence or export a slightly different master |
| Explicit status | Keep the classification consistent |
| Original release date | Preserve the actual original date |
| Track order | Keep it unchanged if reusing the release identifier |
| Artist mapping | Supply existing Spotify, Apple Music and other artist IDs where supported |
| Artwork | Reuse the existing approved artwork unless a change is genuinely required |
Even a "harmless" fix can break matching. Changing feat. formatting, moving a featured performer into the title, swapping in a louder master, shortening an outro — any of these can make a service see a different product or a different recording.
Which makes a distributor transfer a genuinely bad moment to rebrand the artist, redesign the artwork, revise titles and remaster the catalog all at once. Move first. Correct separately, once the catalog is stable.
Deliver the replacement before removing the original
The safer sequence is an overlap:
- Submit the catalog through the new distributor.
- Preserve the original identifiers, audio and metadata.
- Route every release to the existing artist profiles.
- Wait for the replacement to go live at each priority service.
- Verify recording links and displayed play counts.
- Check albums, artist pages and territories.
- Only then request takedown through the previous distributor.
- Keep monitoring until the old delivery disappears.
The overlap reduces the chance of a window where the recording simply isn't available. It may temporarily create two copies of the same release — when the data match, platforms can often consolidate or associate them, though processing differs by service.
TuneCore's public instructions describe requesting the old takedown while distributing the replacement; CD Baby recommends waiting until the new delivery is live. For a catalog worth protecting, the conservative rule is the better one unless both distributors are coordinating the transfer directly.
And keep the old account and payment method active through this period. Saving one month of subscription is not worth prematurely pulling a catalog that took years to build.
Verify recording by recording
Don't sign off on a 200-track migration after checking one popular single.
Build a status sheet covering every release and priority platform: replacement delivered; replacement live; correct artist page; correct release date; play count linked; playlist position retained; territories correct; old delivery removed; Content ID ownership resolved; final old-distributor statement received.
On Spotify, compare the visible count before authorising the old takedown — Spotify specifically recommends the desktop app for confirming that tracks linked.
And inspect the low-stream recordings. Your biggest track gets attention automatically. The forgotten B-side is exactly where missing metadata, wrong territories and duplicate artist pages survive unnoticed.
Royalties don't move with the files
The new distributor starts collecting only for activity covered by its delivery and rights period. The previous one may keep receiving late reports for months after its release is gone.
Keep access to historical royalty statements, transaction-level exports, invoices and tax documents, collaborator split records, recoupment balances, pending withdrawals, reserves and adjustments, and unmatched-income reports.
During the overlap, income may appear through both distributors. That isn't automatically duplicate payment — the reports may cover different service periods, territories or reporting months. Reconcile by platform, recording, territory and usage period, not by the month the cash landed in the bank.
Expect the move to cost more than the new distributor's advertised fee: overlapping subscriptions, new submission charges, staff time, metadata cleanup, support work, and delayed access to part of your earnings. There's no universal transfer price, because distributors use different subscription, per-release and commission structures.
YouTube needs its own plan
Delivery to YouTube Music and enrollment in Content ID are separate operations. A distributor may deliver an art track without administering Content ID, or offer Content ID as an optional service.
Content ID works through separately created rights-management assets and reference files that identify fan uploads, with claims governed by ownership and policy information supplied by the rights holder or its administrator. So if both distributors administer the same recording during your overlap, you can end up with conflicting claims or contradictory ownership instructions.
Before migrating, establish: which company currently controls the Content ID asset; when its reference and ownership will be released; when the new administrator should activate its claim; whether any channels or videos are allowlisted; which territorial policies apply; and whether the Official Artist Channel and art tracks stay correctly mapped.
The same warning covers social-platform monetization, neighboring-rights collection, publishing administration and sync representation. These may be bundled inside a distributor's account, but they're separate rights mandates — moving the master delivery doesn't automatically terminate or transfer them.
A hypothetical label transfer
A small label with 42 releases and four active artists wants better accounting and automated collaborator splits. Its best recording has 1.8 million Spotify plays and sits in several user playlists.
Instead of moving everything at once, it transfers three low-risk releases first. The team exports all identifiers and files, redelivers the recordings, confirms Spotify track linking, checks Apple Music artist mapping, and resolves one duplicate YouTube art track.
Only after that test does it move the rest in groups of ten. Both distributor accounts stay open for two additional reporting cycles, and the finance sheet records which distributor was active for each recording and territory in every period. Content ID moves separately, once the art-track delivery is stable.
Slower than a bulk upload, obviously. It also produces evidence that the workflow works before the catalog's most valuable recording gets anywhere near it.
Who should postpone the move
Delay if you don't have the original master files; if existing ISRCs or release dates are missing; if ownership is disputed; if the artist is changing name at the same time; if a major campaign or release is already running; if the old distributor has frozen the account over fraud or rights concerns; if nobody can reconcile overlapping royalty statements; if the new distributor can't accept existing ISRCs; or if support can't explain artist-profile routing and YouTube rights migration.
One more, stated plainly: changing distributors does not erase an artificial-streaming investigation, an ownership dispute, an unpaid recoupment balance or a contractual restriction. Trying to use a transfer to escape those tends to make the catalog harder to restore, not easier.
Where CREWPORT fits
CREWPORT's guided release workflow helps organise identifiers, contributor information, scheduling and delivery for releases managed through the platform — which is most of the work on the receiving end of a migration: keeping ISRCs intact, routing releases to the correct existing artist profiles, and validating metadata before it goes out so a replacement delivery actually describes the same recording.
What no distributor can promise, including us: whether every platform preserves historical engagement. Track linking is Spotify's decision, made on the data you supply. A migration also still requires a complete export from your previous distributor, and service-by-service verification afterwards.
Anyone telling you a transfer is guaranteed to keep your streams is describing something they don't control.
The transfer is finished when the accounting is finished
A catalog hasn't moved successfully just because the songs play.
The replacement has to sit on the correct artist pages. Spotify tracks have to link. Territories and release dates have to match. Old rights claims have to end. New reports have to begin. Late income from the previous distributor has to be collected and reconciled.
The most important document at the end isn't a new dashboard — it's the migration ledger showing what moved, when, who verified it, and which company should receive each period's revenue.
Less exciting. It's also how a label keeps its catalog intact.
FAQ
Will I lose my Spotify streams if I change distributors?
Not necessarily. Spotify supports track linking, which can associate a redelivered recording with the existing track and retain its play count — but it requires matching audio and metadata including duration, title and artist name, and Spotify doesn't guarantee every replacement links.
Do I need new ISRCs when I switch?
No. An ISRC identifies the recording, so an unchanged recording keeps its existing code. New ISRCs are for remixes, live versions, instrumentals and materially different masters.
Can I keep my UPC?
It depends on the distributor. TuneCore says the same UPC and ISRCs may be used if the album is identical, with a changed tracklist or track order requiring a new UPC. DistroKid accepts outside ISRCs but not outside UPCs for new uploads. A new UPC doesn't force new ISRCs on unchanged recordings.
Should I take my music down first?
No — deliver the replacement first, confirm it's live and linked, then request the takedown. Keep the old account and payment method active until the migration is verified.
Can I fix titles and artwork while I'm moving?
Don't. Changed durations, titles, feat. formatting or masters can prevent matching. Move the catalog unchanged, then make corrections once it's stable.
What happens to YouTube Content ID?
It's separate from delivery and needs its own plan — who controls the asset now, when ownership is released, when the new administrator activates, and which allowlists and territorial policies apply. Two administrators claiming the same recording during an overlap causes conflicts.
Why am I getting royalties from both distributors?
Usually because reports cover different service periods, territories or reporting months — not duplicate payment. Reconcile by platform, recording, territory and usage period rather than by when the cash arrived.
Move it once, and move it properly
The receiving end of a migration is mostly discipline: intact ISRCs, correct artist-profile routing, metadata that matches the original delivery field for field.
CREWPORT validates your metadata before delivery and keeps ISRCs, credits, version information and artist identity consistent across your catalog — so your replacement delivery describes the same recording your history is attached to.
Note: distributor policies on identifiers, takedowns and Content ID change, and each streaming service controls its own matching and catalog-processing rules. Confirm current requirements with both distributors before you begin, and treat platform continuity as something to verify rather than assume.
Sources
- Spotify for Artists — Re-uploading Music and Track Linking
- DDEX — Catalog Transfer Data Requirements
- DDEX — Can a Release Be Identified by an ISRC?
- CD Baby — Switching Music Distribution
- TuneCore — Switching From Another Distributor
- DistroKid — Switching Distribution Companies
- YouTube — Content ID for Music Partners
- YouTube — Music Aggregators and Preferred Distributors