Music Library Doctor
Playlist migration

Traktor → Rekordbox

One-pass migration from Traktor collection.nml into encrypted master.db. Nested playlist folders preserved end-to-end, format gotchas handled on both sides, nothing leaves your machine.

The problem

Moving from Traktor to Rekordbox normally means an XML round-trip: export from Traktor, hope Rekordbox parses it correctly, manually rebuild nested playlist folders, discover cues didn't translate. Traktor's NML schema mixes playlist data, history, and remix sets — parsers that don't understand the full schema lose data on round-trip. And on the destination side: Writes require atomic transactions, and Rekordbox must be closed or it will overwrite your edits when it next saves.

How Music Library Doctor does it

  1. 1 Install Music Library Doctor on the machine with Traktor and Rekordbox. MLD detects both libraries automatically.
  2. 2 MLD opens Traktor collection.nml directly without needing Traktor to be running.
  3. 3 Select the Traktor playlists or folders you want in Rekordbox. MLD maps folder nodes inside the collection XML into nested playlist folders sensibly.
  4. 4 Choose Rekordbox as the destination. MLD writes encrypted master.db natively — encrypted master.db included.
  5. 5 Open Rekordbox — 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

Traktor and Rekordbox speak completely different languages: Traktor collection.nml (Traktor stores stripe/waveform data per track in a separate analysis folder — moving tracks without the analysis files loses visual previews) versus encrypted master.db (Rekordbox stores rich metadata (cues, beatgrids, hot cues, colored playlists) but XML export drops nested folder structure and is lossy on cue points). XML export-import is the usual bridge — and it's lossy on both ends. MLD treats both formats as first-class, reads Traktor's structure natively, and writes Rekordbox's native format directly, so nested playlist folders 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 Traktor and Rekordbox 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.

Does it work with encrypted Rekordbox 6+ master.db files?

Yes. MLD supports Rekordbox's encrypted database key format, so you don't have to downgrade or export anything to read or write playlists.

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

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

Does it back up my libraries before writing?

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

Can I go the other way, Rekordbox back to Traktor?

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

What about Traktor stripe/waveform data?

Traktor stripe/waveform data lives in a separate analysis folder. MLD moves those alongside the playlist transfer so visual previews survive in the target app where the format allows.

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