Music Library Doctor
Playlist migration

Engine DJ → Serato DJ

One-pass migration from Engine DJ m.db into Serato crate files. %% separator encodes nested crate folders preserved end-to-end, format gotchas handled on both sides, nothing leaves your machine.

The problem

Moving from Engine DJ to Serato DJ normally means an XML round-trip: export from Engine DJ, hope Serato DJ parses it correctly, manually rebuild %% separator encodes nested crate 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: Every write must update both the main DB and each affected .crate atomically, or Serato shows ghost entries.

How Music Library Doctor does it

  1. 1 Install Music Library Doctor on the machine with Engine DJ and Serato DJ. 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 Serato DJ. MLD maps playlist groups, smart playlists, history sessions into %% separator encodes nested crate folders sensibly.
  4. 4 Choose Serato DJ as the destination. MLD writes Serato crate files natively and updates both the main DB and every .crate file in one pass.
  5. 5 Open Serato DJ — 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 Serato DJ 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 Serato crate files (Smart Crates are rule-based queries, not static lists — they have no direct equivalent in most other apps and need to be snapshotted at transfer time). 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 Serato DJ's native format directly, so %% separator encodes nested crate 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 Serato DJ 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.

Will nested %% separator encodes nested crate folders transfer correctly?

Yes. MLD reads playlist groups, smart playlists, history sessions and writes %% separator encodes nested crate folders natively so the structure survives the migration.

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

Does it back up my libraries before writing?

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

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

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