One-pass migration from VirtualDJ database.xml + Favorite Folders 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 VirtualDJ to Engine DJ normally means an XML round-trip: export from VirtualDJ, hope Engine DJ parses it correctly, manually rebuild playlist groups, smart playlists, history sessions, 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: 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).
VirtualDJ and Engine DJ 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 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 VirtualDJ'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 regular playlists plus a separate Favorite Folders (★) tree and writes playlist groups, smart playlists, history sessions 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 Engine DJ receives a clean library.
Yes. VirtualDJ 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 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.
