One-pass migration from Traktor collection.nml into VirtualDJ database.xml + Favorite Folders. Regular playlists plus a separate Favorite Folders (★) tree preserved end-to-end, format gotchas handled on both sides, nothing leaves your machine.
Moving from Traktor to VirtualDJ normally means an XML round-trip: export from Traktor, hope VirtualDJ parses it correctly, manually rebuild regular playlists plus a separate Favorite Folders (★) tree, 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: Paths live in three stores (main DB, M3U exports, Favorite Folders). Fix one without the other two and the library stays half-broken.
Supported today
Rekordbox · Serato DJ · VirtualDJ (incl. Favorite Folders) on Windows 10+ and macOS (Apple Silicon + Intel).
Traktor and VirtualDJ 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 VirtualDJ database.xml + Favorite Folders (Favorite Folders (the ★ tree) are filesystem-rooted shortcuts that don't fit the standard playlist model — most migration tools strip them entirely). 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 VirtualDJ's native format directly, so regular playlists plus a separate Favorite Folders (★) tree 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 regular playlists plus a separate Favorite Folders (★) tree 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 VirtualDJ receives a clean library.
Yes. Traktor and VirtualDJ libraries are both copied to timestamped backups before any write. Rollback is always one folder away.
Yes — see the VirtualDJ to Traktor guide. MLD supports every direction between supported apps.
Yes. VirtualDJ's Favorite Folders (★) are a first-class destination — MLD can write nested folders into the ★ tree if you choose that target during transfer.
Free tier covers detection and viewing. Lifetime access is $49 — $19 for the first 100 DJs.
