Music Library Doctor
Playlist migration

djay Pro → Traktor

One-pass migration from djay Pro JSON library into Traktor collection.nml. Folder nodes inside the collection XML preserved end-to-end, format gotchas handled on both sides, nothing leaves your machine.

The problem

Moving from djay Pro to Traktor normally means an XML round-trip: export from djay Pro, hope Traktor parses it correctly, manually rebuild folder nodes inside the collection XML, discover cues didn't translate. djay Pro syncs library data through iCloud on Mac, which means the canonical library may live in a hidden iCloud Drive folder rather than the local app support folder. And on the destination side: Writes have to preserve every existing node (history, remix decks, samples) or Traktor refuses to load the collection.

How Music Library Doctor does it

  1. 1 Install Music Library Doctor on the machine with djay Pro and Traktor. MLD detects both libraries automatically.
  2. 2 MLD opens djay Pro JSON library directly without needing djay Pro to be running.
  3. 3 Select the djay Pro playlists or folders you want in Traktor. MLD maps playlists and collections into folder nodes inside the collection XML sensibly.
  4. 4 Choose Traktor as the destination. MLD writes Traktor collection.nml natively.
  5. 5 Open Traktor — playlists are already there with hierarchy intact, paths pointing at the right files.

Supported today

Rekordbox · Serato DJ · VirtualDJ (incl. Favorite Folders) on Windows 10+ and macOS (Apple Silicon + Intel).

Why native integration matters

djay Pro and Traktor speak completely different languages: djay Pro JSON library (djay Pro integrates tightly with Apple Music and Spotify streams alongside local files — tracks that came from a stream have no portable file path) versus Traktor collection.nml (Traktor stores stripe/waveform data per track in a separate analysis folder — moving tracks without the analysis files loses visual previews). XML export-import is the usual bridge — and it's lossy on both ends. MLD treats both formats as first-class, reads djay Pro's structure natively, and writes Traktor's native format directly, so folder nodes inside the collection XML survives and the target app doesn't re-import anything. A timestamped backup of each app's library is taken before any write.

Frequently asked questions

Do I need to install djay Pro and Traktor on the same machine?

Yes. MLD reads both libraries locally, so both apps (or at least their library files) must be accessible on the same computer. Nothing uploads anywhere — all scanning is local.

Will nested folder nodes inside the collection XML transfer correctly?

Yes. MLD reads playlists and collections and writes folder nodes inside the collection XML natively so the structure survives the migration.

What if my music files moved after I built the djay Pro library?

Run Fix Missing Tracks for djay Pro first. MLD scans your drives, matches moved/renamed files, and repairs links in djay Pro before the transfer — so Traktor receives a clean library.

Does it back up my libraries before writing?

Yes. djay Pro and Traktor libraries are both copied to timestamped backups before any write. Rollback is always one folder away.

Can I go the other way, Traktor back to djay Pro?

Yes — see the Traktor to djay Pro guide. MLD supports every direction between supported apps.

Does this work with the latest djay Pro version?

Yes. MLD tracks djay Pro version compatibility and updates with each new release. See the changelog for the version matrix.

Get your library in shape in minutes

Free tier covers detection and viewing. Lifetime access is $49 — $19 for the first 100 DJs.

Related guides