Build a recording-level manifest
List each existing recording’s exact audio version, ISRC, title and version suffix, primary and featured artists, explicit flag and platform track links. Keep a separate release-level row for the UPC, release date, cover, territory and store links. Follow the receiving distributor’s rules on product identifiers; an ISRC is a recording identifier, not an album barcode.
- Check each artist mapping before signing off a replacement release, especially artists with common or shared names.
- Exclude recordings outside the rights being moved and log any territory that is still contractually restricted.
Use a parallel verification window
For a fictional three-track EP, the new delivery shows three tracks, but Track 2 has a different audio duration and is not linked to the original Spotify count in the desktop app. Stop the old takedown. Compare the delivered file and naming to the manifest and raise the discrepancy with the new provider. Do not reuse an identifier for a different recording to try to force linkage.
After delivery, verify each agreed service and territory, then schedule the old takedown once the provider confirms the correct sequence. Save both sets of delivery receipts and calendar the last statement from the outgoing provider. Historical collections, corrections or late activity can still arrive there after the store switch.
Primary sources
- Spotify for Artists: re-uploading musicSpotify explains when an identical recording and metadata may link its play counts.
- DistroKid: switching distribution companiesProvider-specific migration checks, including existing ISRCs and sequence.
Common questions
Does using the old ISRC guarantee that play counts follow the track?
No. Verify the matched recording on each priority service. Spotify’s guidance also calls for the same audio and metadata.
Learn this properly
The interactive lessons on this topic, with sourced figures and live simulators: