How to Switch Distributors Without Losing Spotify Streams or Playlist Placement
Keep your original ISRCs and audio file, upload through the new distributor, then leave the old release live for 48 to 72 hours so Spotify's track-linking can merge the two. Linking matches on ISRC, artist name, title, duration, and audio. It's never guaranteed, and Spotify can't fix it manually.
Switching distributors is the part of an artist's career where streams go to zero by accident. Not because the move is risky in theory, but because one wrong setting tells Spotify your song is brand new. This page is about the mechanic that decides whether you keep your numbers: Spotify's track-linking. What has to match, why the overlap window matters, and what to do when it doesn't work.
I'll be straight about which parts are documented and which parts are practitioner convention, because Spotify doesn't publish most of this and a lot of guides state guesses as fact.
What does Spotify's track-linking actually do when you switch distributors?
Track-linking is the algorithm Spotify uses to recognize that a new delivery is the same recording you already had live. When it works, Spotify combines the stream counts of the old and new versions and shows them on one linked track, so your history, your playlist spots, and your algorithmic standing carry over instead of resetting. The signals it matches on are ISRC, artist name, track title, audio fingerprint, and track duration, per Label Engine and Symphonic.
Here's the producer-side way to think about it. Spotify isn't tracking your song as a concept. It's tracking a specific recording, identified mostly by its ISRC, the 12-character code that's permanently tied to that recording and doesn't change when ownership or distribution changes hands, per CONNECT Music Licensing. When your new distributor delivers a file carrying the same ISRC and the same audio, Spotify has a strong reason to treat it as the same track. When it delivers a fresh ISRC, Spotify has every reason to treat it as a debut. Same audio, same title, doesn't matter. A new ISRC reads as a new recording, streams reset to zero, and the playlist slots are gone, per Ari's Take.
That's the whole game. The transfer doesn't lose your streams. A new identifier does.
What metadata has to match exactly for the streams to merge?
All five matching signals need to line up, and the two that trip people up are the ones they don't control by typing carefully: the ISRC and the audio file. The hard numbers, pulled straight from the matching mechanic:
matching signals (ISRC, artist name, track title, audio fingerprint, duration)
ISRC per recording, the anchor that has to carry over unchanged
overlap window, practitioner convention
of stream history survives if a new ISRC gets assigned
ISRC. This is the load-bearing one. Export every per-track ISRC from your old distributor's dashboard before you start, and enter those exact codes in the new upload. Some distributors auto-assign fresh ISRCs by default unless you explicitly paste in the originals, per eMastered. If you skip this step, the platform decides for you, and the default is usually wrong for a transfer.
The audio file. Upload the identical master. Not a re-export, not a new bounce, not a remaster, unless the track length comes out exactly the same to the millisecond, per Label Engine. Track duration is one of the five signals, and audio fingerprinting reads the waveform itself. A re-render that shifts the length or the encoding can break the match even when the ISRC is right.
Artist name and track title. Match the styling exactly. DJ Sabre and DJ SABRE and DJ Sabre with a trailing space are three different strings to a matcher. Same goes for featured-artist formatting and version titles like Radio Edit. This artist name is a constructed example, not a real one.
Track-linking is never 100% guaranteed, and Spotify cannot perform a manual link request. Both Label Engine and Symphonic state this directly.
That last line is the part nobody wants to hear. There's no support ticket that forces a link. You either give the algorithm everything it needs to recognize the recording, or you don't. So get the inputs perfect, because they're the only lever you have.
Why does the 48 to 72 hour overlap window matter, and is it real?
The overlap window is the practice of keeping your old release live for two to three days after the new delivery goes active, so Spotify's systems can see both versions at once, detect the duplicate, and consolidate the streams, saves, and playlist placements onto the linked track, per Ari's Take. If you take the old one down first and the new one isn't recognized yet, there's a gap where the recording effectively vanishes and the link has nothing to attach to.
Now the honest caveat, because this is where a lot of guides overstate things. The 48 to 72 hour figure is practitioner convention, not a Spotify rule. Spotify's own documentation does not confirm that specific window and does not promise that an overlap guarantees consolidation. The reason the number gets repeated is that it works in practice often enough that distributors recommend it, not because Spotify published it. I'd follow the convention, because the downside of an extra two days of overlap is basically nothing, but don't treat it as a merge that's promised to fire.
Dashboard analytics never transfer
One thing that does not carry over no matter how clean the link is: your distributor's dashboard analytics. Those never transfer between providers, so export every report from the old dashboard before you close the account. Your Spotify for Artists data is separate and survives independently, because it lives with Spotify, not your distributor, per Absolute Label Services.
The order that keeps the window intact: upload to the new distributor with original codes, wait for it to go live, confirm it on Spotify, and only then remove the old release. Reverse that order and you've created the gap yourself.
What do you do if track-linking fails anyway?
First, confirm it actually failed. A link can take time to appear, and Spotify doesn't notify you when it fires, so give it a few days past your overlap window before you worry. If the new version shows your full historical stream count and your playlist placements held, it worked. If you're staring at a track that reads zero streams next to your old one, the link didn't catch.
If it failed, here's how the two outcomes compare, so you know what you're looking at:
| Link held | Link failed | |
|---|---|---|
| Stream count | Combined onto one track | New track reading zero |
| Playlist placement | Retained | Lost |
| ISRC state | Original ISRC delivered | A new ISRC was likely assigned |
| What you can still do | Nothing, you're done | Redeliver with the correct ISRC and hope it catches next pass |
The most common cause is a new ISRC slipped in by the new distributor. Check the ISRC on the new delivery against your exported list. If it's different, that's your problem, and the fix is to redeliver the recording with the original code. The second most common cause is the audio: a re-exported or slightly different master that fingerprints as a separate recording. Redeliver the original file.
Be realistic about the ceiling here. Because Spotify can't manually link tracks and won't guarantee the algorithm re-merges after a botched delivery, a clean redelivery is your best shot, not a sure thing. This is exactly why the original codes and the exact audio matter so much going in. There's no reliable undo. The sibling guide on what actually breaks during a distributor transfer goes deep on the full inventory of what can break beyond Spotify, including new-UPC release-page breaks, YouTube Content ID ownership conflicts, and the royalty payment lag while accounts overlap.
Putting it together
Keeping your Spotify streams through a switch comes down to feeding the matcher exactly what it needs. Export and reuse your original ISRCs, deliver the identical audio file, match your artist name and title styling, and overlap the old and new releases for a couple of days before you take anything down. Do that and you've done everything in your control. Whether the link fires is the algorithm's call, and there's no manual override, so the discipline is getting the inputs right the first time.
If you're about to start the upload and want a checklist that catches the codes and metadata before they cost you, run it track by track before you deliver.
Frequently asked questions
Will I lose my Spotify streams if I switch distributors?+
Not if the new distributor delivers the same ISRC and the identical audio file. Spotify's track-linking recognizes the recording and combines the stream counts onto one track. You lose your streams when a new ISRC gets assigned, because Spotify then treats it as a brand-new song and resets the count to zero. The single biggest thing in your control is exporting your original ISRCs and entering them on the new upload.
How long should I keep my old release live when switching?+
The common recommendation is 48 to 72 hours of overlap, keeping the old release live for two to three days after the new delivery goes active so Spotify can detect the duplicate and consolidate. That figure is practitioner convention, not something Spotify publishes or guarantees. The downside of overlapping a little longer is nothing, so follow it, but don't treat consolidation as promised. Always confirm the new delivery is live before removing the old one.
Can Spotify manually link my old and new track if it doesn't merge?+
No. Spotify cannot perform manual link requests, and track-linking is never 100 percent guaranteed. There's no support ticket that forces a merge. If the link fails, check whether a new ISRC or a different audio file caused it, then redeliver the recording with the original ISRC and the exact original master. A clean redelivery is your best shot at the algorithm re-merging, not a guaranteed fix.
Does keeping the same ISRC keep my playlist placements?+
It's the main thing that protects them, but it isn't the only requirement. Track-linking matches on ISRC, artist name, track title, audio fingerprint, and duration together. The original ISRC plus the identical audio gives the algorithm a strong reason to treat the delivery as the same recording and carry the placements over. A new UPC at the release level can still break the catalog page in some cases even when the ISRC is preserved, which the breakage guide covers in detail.
What if I already re-exported my audio file for the new distributor?+
Re-export it from the original master, or pull the exact file you delivered the first time. Track duration is one of the five matching signals and the audio fingerprint reads the waveform itself, so a fresh bounce or a remaster that changes the length can read as a separate recording even with the right ISRC. Match the original file as closely as you can before you deliver. If you've already delivered a different file and the link failed, redelivering the original audio is the fix to try.

Keep reading
Pillar guide
How to Choose and Switch Your
To switch distributors without losing streams, reuse your original ISRC and UPC codes, upload the identical audio, keep the old release live for a couple of days so Spotify can link the versions, de-register YouTube Content ID before re-registering, and leave the old account open until royalties clear.
Related guide
What Actually Breaks During a Distributor
Three things break.
Related guide
How to Transfer Your Full Catalog
Export every ISRC and UPC, de-register Content ID with your old distributor, upload to the new one using the original codes, then keep both deliveries live for 48 to 72 hours so DSPs consolidate.
Free tool · no signup
Switch distributors without losing streams
Get a sequenced migration checklist that preserves your ISRCs, royalty records, and release availability so nothing breaks when you move your catalog.