How Do I Confirm My Release Migrated Successfully?

✅ What a Successful Migration Looks Like

The easiest way to confirm a successful migration is to check for duplicate releases on DSPs.

After your migration is processed, you should see:

• Your original release (from your previous distributor)
• A duplicate release delivered by EngineEars

Both versions should be:

• Identical in track titles
• Using the same ISRCs
• Matching metadata (artist name, release title, etc.)
• Reflecting the same streaming data (on supported platforms like Spotify)

This duplication is intentional and part of the migration process.

🔍 Why Duplicate Releases Matter

The duplicate allows you to safely confirm that:

• Your music has been properly delivered by EngineEars
• All metadata and assets match the original
• Your streaming history is preserved (where supported)

This ensures there’s no disruption to your catalog before removing your old version.

🚨 When You’re Ready: Submit a Takedown

Once you’ve confirmed that:

• The EngineEars version is live
• Everything matches your original release

You can go ahead and request a takedown from your previous distributor.

This will leave only the EngineEars version live moving forward.

⚠️ If Something Looks Off

If your release was not migrated properly, one of the following may happen:

• It gets flagged for copyright conflicts

If that happens, don’t worry, our team will reach out if we need anything from you (like verification or additional details) to resolve it.

💡 Pro Tip

Always avoid making any metadata changes (like artist name) during migration. Wait until after everything is successfully mapped and confirmed before making updates.

If you’re unsure whether your release migrated correctly, feel free to reach out or join Office Hours and we can review it with you in real time.