Music Library Doctor
Playlist migration

djay Pro → Mixxx

One-pass migration from djay Pro JSON library into Mixxx mixxxdb. Crates and folder-based browsing preserved end-to-end, format gotchas handled on both sides, nothing leaves your machine.

The problem

Moving from djay Pro to Mixxx normally means an XML round-trip: export from djay Pro, hope Mixxx parses it correctly, manually rebuild crates and folder-based browsing, discover cues didn't translate. djay Pro syncs library data through iCloud on Mac, which means the canonical library may live in a hidden iCloud Drive folder rather than the local app support folder. And on the destination side: Mixxx supports its own crate format that doesn't map 1:1 with playlists — writers have to choose which model is the target.

How Music Library Doctor does it

  1. 1 Install Music Library Doctor on the machine with djay Pro and Mixxx. MLD detects both libraries automatically.
  2. 2 MLD opens djay Pro JSON library directly without needing djay Pro to be running.
  3. 3 Select the djay Pro playlists or folders you want in Mixxx. MLD maps playlists and collections into crates and folder-based browsing sensibly.
  4. 4 Choose Mixxx as the destination. MLD writes Mixxx mixxxdb natively.
  5. 5 Open Mixxx — 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

djay Pro and Mixxx speak completely different languages: djay Pro JSON library (djay Pro integrates tightly with Apple Music and Spotify streams alongside local files — tracks that came from a stream have no portable file path) versus Mixxx mixxxdb (Mixxx is open source and free, so it's often the destination for DJs leaving paid apps — but the migration tooling around it is thin). XML export-import is the usual bridge — and it's lossy on both ends. MLD treats both formats as first-class, reads djay Pro's structure natively, and writes Mixxx's native format directly, so crates and folder-based browsing 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 djay Pro and Mixxx 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 crates and folder-based browsing transfer correctly?

Yes. MLD reads playlists and collections and writes crates and folder-based browsing natively so the structure survives the migration.

What if my music files moved after I built the djay Pro library?

Run Fix Missing Tracks for djay Pro first. MLD scans your drives, matches moved/renamed files, and repairs links in djay Pro before the transfer — so Mixxx receives a clean library.

Does it back up my libraries before writing?

Yes. djay Pro and Mixxx libraries are both copied to timestamped backups before any write. Rollback is always one folder away.

Can I go the other way, Mixxx back to djay Pro?

Yes — see the Mixxx to djay Pro guide. MLD supports every direction between supported apps.

Does this work with the latest djay Pro version?

Yes. MLD tracks djay Pro 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