Music Library Doctor
Playlist migration

Engine DJ → Rekordbox

One-pass migration from Engine DJ m.db into encrypted master.db. Nested playlist folders preserved end-to-end, format gotchas handled on both sides, nothing leaves your machine.

The problem

Moving from Engine DJ to Rekordbox normally means an XML round-trip: export from Engine DJ, hope Rekordbox parses it correctly, manually rebuild nested playlist folders, 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 require atomic transactions, and Rekordbox must be closed or it will overwrite your edits when it next saves.

How Music Library Doctor does it

  1. 1 Install Music Library Doctor on the machine with Engine DJ and Rekordbox. 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 Rekordbox. MLD maps playlist groups, smart playlists, history sessions into nested playlist folders sensibly.
  4. 4 Choose Rekordbox as the destination. MLD writes encrypted master.db natively — encrypted master.db included.
  5. 5 Open Rekordbox — 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 Rekordbox 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 encrypted master.db (Rekordbox stores rich metadata (cues, beatgrids, hot cues, colored playlists) but XML export drops nested folder structure and is lossy on cue points). 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 Rekordbox's native format directly, so nested playlist folders 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 Rekordbox 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.

Does it work with encrypted Rekordbox 6+ master.db files?

Yes. MLD supports Rekordbox's encrypted database key format, so you don't have to downgrade or export anything to read or write playlists.

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 Rekordbox receives a clean library.

Does it back up my libraries before writing?

Yes. Engine DJ and Rekordbox libraries are both copied to timestamped backups before any write. Rollback is always one folder away.

Can I go the other way, Rekordbox back to Engine DJ?

Yes — see the Rekordbox 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