[FAQ]

Hey,

My band is planning to switch to a new music distributor, but we’re really worried about losing our stream counts and playlist placements on Spotify. We have a few tracks that have gained some decent traction, and it would be a huge setback if all that data got reset to zero.

I’ve read that the key is to re-upload the music with the exact same metadata: ISRC codes, audio files, artwork, artist names, and release dates. The part I’m not clear on is the timing of everything. Do you issue a takedown from the old distributor first, or do you upload to the new one while the old release is still live?

I’m looking for a reliable, step-by-step process from anyone who has successfully managed this transition. We want to be as careful as possible to ensure a seamless switch.

Any help is appreciated.

[Jeff Bullas]

This is a high-stakes process, but it can be done safely if you’re meticulous.

Short Answer: To switch distributors, you must upload your tracks to the new service using the exact same audio files and text-based metadata, especially the ISRC. Crucially, you must only issue a takedown from your old distributor after the new version is live on Spotify.

Let’s walk through the correct sequence to ensure your audio and text data align perfectly.

First, you must gather the original assets, which includes the exact same audio file and all of its original text-based metadata; the most critical piece of data is the ISRC code for each track. Second, upload this content to your new distributor, ensuring every single field—track title, artist name, and original release date—is an identical match to the first release. Third, and this is the most important step, you must wait until the new upload is live on Spotify before you request a takedown from your old distributor. Rushing this and taking the old version down first is the primary reason artists lose their stream counts. If the audio content and metadata are identical, Spotify’s system will correctly map the new upload to the existing track history.

Cheers,

Jeff

[Author]

Posts