One-pass migration from VirtualDJ database.xml + Favorite Folders into Traktor collection.nml. Folder nodes inside the collection XML preserved end-to-end, format gotchas handled on both sides, nothing leaves your machine.
Moving from VirtualDJ to Traktor normally means an XML round-trip: export from VirtualDJ, hope Traktor parses it correctly, manually rebuild folder nodes inside the collection XML, discover cues didn't translate. VirtualDJ has portable and shared install modes that put database.xml in different locations — tools that hardcode the path miss portable setups entirely. And on the destination side: Writes have to preserve every existing node (history, remix decks, samples) or Traktor refuses to load the collection.
Supported today
Rekordbox · Serato DJ · VirtualDJ (incl. Favorite Folders) on Windows 10+ and macOS (Apple Silicon + Intel).
VirtualDJ and Traktor speak completely different languages: 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) 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 VirtualDJ'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.
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 regular playlists plus a separate Favorite Folders (★) tree and writes folder nodes inside the collection XML natively so the structure survives the migration.
Run Fix Missing Tracks for VirtualDJ first. MLD scans your drives, matches moved/renamed files, and repairs links in VirtualDJ before the transfer — so Traktor receives a clean library.
Yes. VirtualDJ and Traktor libraries are both copied to timestamped backups before any write. Rollback is always one folder away.
Yes — see the Traktor to VirtualDJ guide. MLD supports every direction between supported apps.
Yes. MLD tracks VirtualDJ version compatibility and updates with each new release. See the changelog for the version matrix.
Free tier covers detection and viewing. Lifetime access is $49 — $19 for the first 100 DJs.