Catalog Migration

To ensure a smooth and successful migration from your current distributor/aggregator, we require the following:

1. Full Release & Track Metadata

All metadata must match exactly to preserve streaming history and avoid relinking issues on DSPs.

Track-Level Metadata

• ISRC

• Track title + version

• Primary & featured artists

• Track duration

• Genres

• Lyrics language

• Parental advisory (Clean/Explicit)

• Original release date

Release-Level Metadata

• UPC

• Track count

• Release language

• Original release date

• Label name

Even small inconsistencies can prevent track linking on platforms like Spotify.

2. Content & Licensing Checks

If your music is delivered to:

• TikTok

• Snap

• YouTube Content ID

• Facebook Audio Library

• Facebook Rights Manager

Ensure:

• Content is fully original or

• Properly cleared/licensed

Unlicensed or reused content may trigger fingerprint rejections.

3. Takedown & Transfer Handling

Do not issue a takedown before speaking to us. Different distributors handle migrations differently, and early takedowns can permanently break track linking.

4. Create Your Releases on Rapture

Inside the Rapture platform:

• Recreate the release

• Enter the same UPC, ISRCs, original dates, and full metadata

• Distribute the release

Once you've distributed, our team will verify and begin redelivery to all DSPs.

How to Confirm Linking

1. Search for your release on Spotify

• If your migration was successful, you should see two versions (old + new).
• Use the dropdown under track duration → switch between versions.
  
  
  

2. Verify Play Counts

If play counts match, linking was successful — you may proceed with takedowns. If they don’t match, send us:

• The ISRC(s)

• Spotify Track URI(s)

If you have a large catalog, focus on top-performing tracks.

Note: Spotify does not offer a bulk verification method.

DSPs That Do Not Support Play Count Linking

• iHeartRadio

• iMusica

• KKBOX

• Nuuday

• YouTube Art Track