You can usually switch music distributors without resetting a recording’s stream count, but no distributor can guarantee that every store will link the replacement delivery. The safest process is to reuse the original ISRC, deliver the identical audio with matching metadata, keep the old version live until the replacement is visible, and verify the link before requesting a takedown.
What Can Carry Over?
An ISRC identifies a particular sound recording. Changing the company that delivers an unchanged recording does not make it a new recording, so the original ISRC should normally travel with it. Stores also compare the audio and metadata when deciding whether two deliveries represent the same track.
Successful track linking can preserve visible play counts, saves, and playlist associations. It is still a matching process controlled by each digital service provider, not a guaranteed transfer of account data between distributors. A new master, different duration, changed artist credit, or new ISRC can cause a store to treat the upload as a separate recording.
The UPC identifies the release rather than an individual track. Save and reuse the original UPC when the new distributor permits it, but prioritize the correct ISRC on every track and an exact metadata match across the release.
What to Save Before You Transfer
Export the information while you still have full access to the old distributor. Create one row per release and keep a separate row for every track on an album or EP.
- Original WAV files or the exact masters used for the live release
- ISRC for every track
- UPC for each single, EP, or album
- Primary and featured artist credits exactly as delivered
- Track, release, and version titles, including punctuation
- Original release date, track order, explicit-content status, and territories
- Cover artwork and complete songwriter, producer, and contributor credits
- Store URLs, Spotify URIs, analytics exports, royalty statements, and split records
- Details of any active YouTube Content ID or social-platform rights claims
Do not use the migration to quietly replace a master or rename a version. A remaster, remix, edit, or materially different recording needs its own identifier and should be handled as a new release.
The Safest Transfer Order
1. Confirm the new distributor accepts existing codes
Check the upload workflow before cancelling anything. Make sure it allows you to enter an existing ISRC and, if needed, an existing UPC. Ask support how it handles catalog transfers, YouTube Content ID, and territory restrictions. If the service automatically assigns new codes, resolve that before submitting the release.
2. Recreate the release without creative changes
Upload the same master and artwork. Enter the original ISRC for each track, use the original release date, and copy the artist names, titles, versions, contributor roles, territories, and track order from your catalog export. Select any option that marks the music as previously released or transferred.
3. Submit while the old delivery remains live
Do not request the old takedown first. The overlap gives stores both deliveries at the same time and makes it possible to confirm whether they have linked. Delivery and review times vary by distributor and store, so plan the move away from an important release date or active campaign.
4. Verify the replacement at your priority stores
Wait until the new distributor reports the release as delivered, then inspect Spotify, Apple Music, YouTube Music, and any store that materially affects your audience or income. Compare the visible recording, artist profile, play count where available, release date, and playlist presence.
5. Remove the old delivery only after verification
Once the replacement is live and linked, request the takedown through the old distributor. Keep screenshots, ticket numbers, delivery dates, and store links. If the releases appear separately or the replacement begins with no history, pause the takedown and ask the new distributor to investigate the mismatch.
How to Verify Track Linking
The cleanest signal is that the replacement appears as the same recording rather than a second standalone version. On Spotify, compare the visible play count and check whether playlists still point to the track. On other services, confirm the correct artist page, release date, artwork, and catalog position.
If a duplicate appears, compare these fields first:
- ISRC on the old and new deliveries
- Audio file and track duration
- Primary and featured artist formatting
- Track and release titles, including version labels
- Original release date and track order
Send both store links and the expected ISRC to the new distributor’s support team. The distributor is normally the party that can escalate delivery corrections to the store.
Platform-Specific Risks
YouTube Content ID needs separate coordination. Two administrators claiming the same recording can create ownership conflicts or delay monetization. Ask the old distributor when it will release its claim and ask the new distributor when its claim will begin. Do not assume that a store takedown automatically ends every rights-management service.
TikTok, Instagram, Facebook, and other short-form platforms may update on different schedules from audio streaming stores. Check sounds and rights claims separately rather than treating a successful Spotify link as proof that the entire migration is complete.
Collaborator splits also do not transfer automatically. Recreate them in the new dashboard and tell collaborators when the paying entity changes.
What to Check After the Takedown
Keep the old account accessible until all outstanding statements and payouts have arrived. Royalties already reported through the old delivery stay with the old distributor’s accounting system; they are not moved into the new dashboard.
After the takedown has propagated:
- Confirm that one correct version remains at every priority store
- Recheck stream counts, playlist placements, artist-page mapping, and release dates
- Update smart links, website embeds, ad destinations, and social profiles
- Confirm collaborator splits and payout details in the new account
- Monitor Content ID and social-platform claims for conflicts
- Save the final old-distributor statements and all migration correspondence
A careful transfer reduces the risk of lost continuity, but the practical rule is simple: preserve the recording identifiers and data, overlap the deliveries, verify first, and remove the old version last.