Catalog Migration — Reprtoir Distribution
Overview
This procedure applies when a client’s catalog is delivered to DSPs through Reprtoir Distribution. In this scenario, the licensee changes on the DSP side. Because of that, all DSPs require a full takedown and redelivery of the catalog.
The objective is to ensure that the new deliveries correctly replace the old ones while preserving as much historical data (streams, playlists, and profiles) as possible.
Process Summary
| Step | Action | Details |
|---|---|---|
| 1 | Deliver the full catalog through Reprtoir | Use the same ISRC and UPC codes as in the original deliveries. |
| 2 | Wait 5 days before takedown | This delay allows DSPs to sync old and new versions. Spotify recommends this period, and it is considered best practice across all platforms. |
| 3 | Send takedown requests to the previous distributor | Only after the 5-day window has passed. |
| 4 | Verify migration success | Check that the new versions appear correctly linked and that artist profiles remain consistent. |
| 5 | Apply metadata updates if needed | Once the new versions are live and confirmed, major metadata corrections (titles, credits, etc.) can be submitted. |
Technical Rules
Identifiers
- Both ISRC and UPC must remain identical.
- DSPs use this pairing to match old and new versions.
- Changing either identifier will create a new product entry.
Metadata
- Keep all metadata fields identical during migration.
- Minor typo fixes are tolerated.
- Major changes (new titles, additional artists) should only be made after migration.
Audio and Artwork
- Audio format differences (e.g., 16-bit WAV → 24-bit FLAC) are acceptable.
- Audio length must remain the same.
- Variations under 5 seconds are tolerated.
- Longer differences (remasters, edits) may break matching.
- Artwork should remain identical to the previous delivery file.
Artist IDs
- Always include artist IDs for Spotify and Apple Music.
- Missing IDs can cause new versions to appear under duplicate artist profiles.
Platform Behavior
| DSP | Migration Type | Specific Notes |
|---|---|---|
| Spotify | Full redelivery before takedown | Syncs within 48–72h; 5 days recommended before takedown. |
| Apple Music / iTunes | Full redelivery before takedown | Matching usually automatic if ISRC and UPC remain the same. |
| Deezer | Full redelivery before takedown | Strict on metadata consistency (titles, artist names). |
| Amazon Music | Full redelivery before takedown | Preserves historical data if identifiers and metadata are identical. |
| TIDAL / Qobuz / FLO / NetEase | Full redelivery before takedown | Same 5-day rule applies. |
| SoundCloud | Specific process required | Form + catalog report must be sent and approved before migration. |
Timing and Validation
- DSP sync time: 48–72 hours on average.
- Recommended takedown delay: 5 days after delivery.
- Validation: Verify that each track is linked to the original profile and that streaming continuity is preserved.
Best Practices
- Plan migrations in small batches when possible.
- Keep original files archived and accessible during the migration period.
- Monitor reports closely after the transition for any mismatches.
- Contact Reprtoir Support if a DSP does not automatically match a release — some platforms can perform manual synchronization upon request.
Updated about 18 hours ago