How to Move a Release to a New Distributor Without Losing Streams
Migrate a music release with identical audio and metadata, controlled overlap, mapping and track-link checks, financial closeout, rollback evidence, and no preservation promises.
The short answer
To improve the chance that platforms link a migrated release, deliver the identical audio and matching metadata through the new distributor, preserve the ISRC and original release facts, verify the correct artist profiles, allow a controlled overlap where permitted, and remove the old delivery only after the new one is live and correctly linked. No distributor can guarantee preserved streams, playlists, reviews, links, libraries, recommendations, or uninterrupted availability.
Three things to know
- 01
Export catalogue, contracts, assets, identifiers, metadata, statements, links, profile IDs, and balances before changing anything.
- 02
Use identical audio and matching release facts, then verify linking and availability platform by platform before the old takedown.
- 03
Close financial, rights, split, tax, Content ID, support, and access obligations with the old and new providers separately.
What belongs in a distributor migration control sheet?
One record should show catalogue identity, delivery state, financial closeout, and removal authority.
- 01
Source archive
Preserve exact audio, hashes, durations, artwork, metadata, identifiers, profile IDs, contracts, licences, links, and screenshots.
- 02
New delivery
Record provider, submission, matching fields, artist IDs, stores, territories, references, approvals, rejects, and live URLs.
- 03
Link verification
Compare profiles, audio, metadata, ISRCs, durations, counts where visible, playlists, libraries, reviews, and unresolved uncertainty.
- 04
Old removal
Define contract authority, required green checks, takedown scope, reference, timing, monitoring, duplicates, gaps, escalation, and rollback options.
- 05
Financial closeout
Track statements, lags, reserves, balances, taxes, splits, recoupment, disputes, account access, Content ID, and final contacts.
What should be exported before a distributor migration?
Export the exact delivered master files, durations, artwork, titles, version labels, artist roles, artist profile identifiers, ISRCs, UPCs, original release dates, label, copyright lines, credits, language, explicit flags, territories, store selections, lyrics, splits, licences, platform URLs, playlist evidence, statements, transaction history, unpaid balances, tax records, support cases, and takedown terms. Preserve file hashes and screenshots. If the old provider disappears or access ends, this archive becomes the migration source of truth.
How identical should the new delivery be?
For a catalogue transfer rather than a new version, use the same audio file and duration and match song titles, album title, version information, primary and featured artists, ISRCs, original release date, credits, explicit status, and other material metadata. Supply exact artist IDs where supported. Spotify says track-linking relies on matching audio and metadata, including duration, title, and artist name. Do not remaster, trim silence, change roles, revise titles, or bundle unrelated corrections into the migration.
Should the old and new deliveries overlap?
A controlled brief overlap can reduce gap risk when provider and platform rules permit it. DistroKid's own migration instructions allow an overlap and advise uploading before requesting the old removal. Do not copy that timing blindly to another provider. Confirm both contracts, fees, exclusivity, duplicate-delivery handling, ownership, release dates, and takedown processing. Define the evidence that authorizes removal: new version live, correct artist mapping, expected track link, required territories, audio, metadata, and campaign destinations verified.
How should platform linking be verified?
Compare the old and new release and track URLs, play counts where visible, artist profile, ISRC, duration, credits, audio, availability, and playlist context. Spotify says matching play counts in its desktop app indicate tracks have linked. Record screenshots before, during, and after migration. Other services use different signals and may not expose linking. Do not assume a shared ISRC alone proves the catalogue entity, user libraries, reviews, playlists, links, or recommendations transferred.
When should the old delivery be removed?
Remove it only after the new distributor confirms delivery, each priority platform is live and correct, observable linking is verified, required territories work, campaign links are safe, the old contract permits removal, and a rollback or escalation plan exists. Submit one controlled takedown and preserve its reference and scope. Avoid removing the old version because one store is ready while others are still processing. Monitor until duplicate and old listings resolve without creating a catalogue gap.
How should royalties and splits be closed out?
Record the final usage periods, reporting lag, reserves, thresholds, tax forms, currency, splits, collaborator invitations, recoupment, adjustments, disputes, and payment contacts under the old provider. Keep the account accessible until final statements and corrections arrive. Configure new splits independently and confirm they match agreements. A migration does not move unpaid royalties, contractual rights, publishing administration, neighbouring-rights registrations, Content ID mandates, or accounting history unless the relevant parties explicitly support that transfer.
What should happen if linking fails?
Do not immediately take down and re-upload again. Freeze changes, compare the exact audio and metadata, identify which platform and territory failed, preserve both URLs and delivery references, and open coordinated cases with the new distributor and platform where available. Ask for track-link or catalogue-merge review without promising an outcome. If the old delivery remains live and contracts allow, keep continuity while the case is reviewed. Document any accepted loss before proceeding with an irreversible takedown.
What supports this controlled migration?
Practical notes
- Spotify says matching audio and metadata can enable track-linking and provides a visible play-count check for successful linking.
- DistroKid recommends identical audio, titles, album title, ISRCs, and other metadata while explicitly refusing to guarantee preserved counts or playlist placement.
Source notes
- Spotify for Artists: Re-uploading music, accessed July 18, 2026.
- DistroKid Help Center: Switching from a Different Distribution Company to DistroKid, accessed July 18, 2026.
Frequently asked questions
- Does using the same ISRC guarantee preserved streams?
- No. Matching identifiers, audio, metadata, and profiles improve the evidence, but platforms control linking and no outcome is guaranteed.
- Can two distributors deliver the same release briefly?
- Some migration workflows allow controlled overlap, but both provider contracts, platform behavior, fees, exclusivity, and duplicate rules must be checked.
- Should an artist remaster during a distributor switch?
- Treat a materially changed master as a separate version. Combining remastering with migration reduces matching evidence and complicates diagnosis.
- Will playlist placements and reviews move automatically?
- They may not. DistroKid explicitly disclaims guarantees for counts and playlists and notes some store reviews can be lost.
- When can the old distributor account be closed?
- After contractual obligations, final statements, reserves, taxes, splits, support cases, takedowns, balances, and evidence exports are safely resolved.