Music Library Doctor
Playlist migration

Engine DJ → Traktor

One-pass migration from Engine DJ m.db 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 Engine DJ to Traktor normally means an XML round-trip: export from Engine DJ, hope Traktor parses it correctly, manually rebuild folder nodes inside the collection XML, discover cues didn't translate. Engine DJ versions 2.x and 3.x changed the schema — tools written for one version often miss data on the other. 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 Engine DJ and Traktor. MLD detects both libraries automatically.
  2. 2 MLD opens Engine DJ m.db directly without needing Engine DJ to be running.
  3. 3 Select the Engine DJ playlists or folders you want in Traktor. MLD maps playlist groups, smart playlists, history sessions 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

Engine DJ and Traktor speak completely different languages: Engine DJ m.db (Engine DJ libraries live on the player USB/SSD itself as a per-drive Engine Library folder, not just on the home machine) 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 Engine DJ'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 Engine DJ 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 playlist groups, smart playlists, history sessions 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 Engine DJ library?

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

Does it back up my libraries before writing?

Yes. Engine DJ 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 Engine DJ?

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

Does this work with the latest Engine DJ version?

Yes. MLD tracks Engine DJ 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