One-pass migration from Traktor collection.nml into Engine DJ m.db. Playlist groups, smart playlists, history sessions preserved end-to-end, format gotchas handled on both sides, nothing leaves your machine.
Moving from Traktor to Engine DJ normally means an XML round-trip: export from Traktor, hope Engine DJ parses it correctly, manually rebuild playlist groups, smart playlists, history sessions, 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: Engine DJ expects matching analysis files (.dat) next to each track for performance — pure path writes without analysis miss waveforms and cues.
Supported today
Rekordbox · Serato DJ · VirtualDJ (incl. Favorite Folders) on Windows 10+ and macOS (Apple Silicon + Intel).
Traktor and Engine DJ 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 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). 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 Engine DJ's native format directly, so playlist groups, smart playlists, history sessions survives and the target app doesn't re-import anything. A timestamped backup of each app's library is taken before any write.
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.
Yes. MLD reads folder nodes inside the collection XML and writes playlist groups, smart playlists, history sessions natively so the structure survives the migration.
Run Fix Missing Tracks for Traktor first. MLD scans your drives, matches moved/renamed files, and repairs links in Traktor before the transfer — so Engine DJ receives a clean library.
Yes. Traktor and Engine DJ libraries are both copied to timestamped backups before any write. Rollback is always one folder away.
Yes — see the Engine DJ to Traktor guide. MLD supports every direction between supported apps.
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.
Free tier covers detection and viewing. Lifetime access is $49 — $19 for the first 100 DJs.
