How to · Traktor Pro

Transfer your library to Engine DJ in Traktor Pro.

Traktor and Engine DJ use completely different database formats. Here is how to move your collection across, either manually or by letting Vibes handle the import and export for you.

Discover Vibes

First 500 licenses at $49. Be the first to know when we launch.

Vibes library view showing a Traktor collection ready for Engine DJ export

Vibes reads your Traktor NML and writes playlists directly into the Engine DJ database.

Transfer your library to Engine DJ in Traktor Pro, step by step.

Traktor stores its library in an NML file while Engine DJ uses its own database format. Engine DJ Desktop does include a native Traktor NML importer (present since Engine Prime 1.2 and continued through Engine DJ 4.x and 5.0), but real-world results are inconsistent: playlists sometimes import empty, hot cue transfer is unreliable, and BPM grids may need correction. For a complete, reliable transfer, a third-party bridge tool such as Lexicon or MIXO is the more dependable path.

Locate your Traktor NML file

Open Traktor Pro 4 and go to Preferences, then File Management. Under the Directories section, check the Root Dir field to see the path to your Traktor root folder. The collection NML file (collection.nml) lives inside that folder. On macOS the default is Documents/Native Instruments/Traktor 4.x.x and on Windows it is Documents/Native Instruments/Traktor 4.x.x. Note this path before closing Traktor.

Confirm all audio files are accessible

Engine DJ must be able to read the same audio files Traktor references. Make sure your music folder is on a drive that will be connected when you use Engine DJ. If any tracks show as missing in Traktor, relocate them before proceeding so the file paths are correct.

Use Engine DJ's native Traktor importer

Open Engine DJ Desktop (version 4.x or later) and look for the Traktor import option, which may appear as part of an Import Assistant workflow in newer versions. Point it to your collection.nml file. Engine DJ will attempt to import your tracks and playlists. Note that results are inconsistent: playlists sometimes arrive empty, hot cue transfer is unreliable, and BPM grids may be incorrect and need manual correction. Auto-analysis will run on any tracks that need it.

Verify and repair imported data, or use a third-party bridge

After import, check whether your playlists populated correctly and whether hot cues transferred. Engine DJ supports hot cues only (no memory cues). If playlists are empty or cue data is missing, the most reliable fix is to use a dedicated bridge tool such as Lexicon or MIXO, which give more consistent results for playlist structure, hot cues, and beat grids when moving from Traktor to Engine DJ.

The catch

Engine DJ does include a native Traktor NML importer, but its reliability is inconsistent in practice: playlists can import empty, hot cue transfer is not guaranteed, and BPM grids may need manual correction. For a complete transfer of playlist structure and cue points, a third-party tool such as Lexicon or MIXO is the more dependable option.

Mood

Euphoric

Melancholic

Mysterious

Energy

Aggressive

Peaceful

Rave

Function

Afterhours

Club

Home

The faster way

Import your NML. Export to Engine DJ. Keep your organization.

Vibes reads your Traktor NML directly, preserving your playlists and letting you layer on vibe tags for energy and mood. It then writes everything into the Engine DJ database in one export, no manual rebuilding.

See how it works

Import your Traktor NML: Vibes parses your full collection including playlists and metadata from Traktor Pro 4.

Tag by feel in Vibe Sort: assign energy, mood, and role vibes to your tracks one by one, then let Auto-Tag suggest tags for the rest based on your own taste.

Export directly to Engine DJ m.db: Vibes writes your playlists, vibe-tagged crates, and Combinations straight into the Engine DJ database, including BPM, key, and hot cue points.

Arrive organized: Engine DJ receives a playlist per vibe plus your Sets, so your prep carries over instead of starting over.

Organize in Vibes, export to Traktor Pro.

Your playlists, tags, ratings, and cue points travel back to the gear you play on, so nothing you do in Vibes is locked away.

Track 001

Artist A

128

Afterhours

Mysterious

Introspective

Track 002

Artist B

124

Cozy Floor

Peaceful

Home

Track 003

Artist C

132

Rave

Aggressive

Festival

Build & Release

Playlists

Vibes

Mood

Aggressive

Euphoric

Melancholic

Mysterious

Peaceful

Playful

Tense

Function

Arrangement

Sets

Club Night 12/28

NYE Closing Set

Rooftop 01/04

Frequently asked questions

The honest answers, including the trade-offs.

Vibes replaces the manual rebuilding work, not Traktor itself. You keep using Traktor Pro to perform and record. Vibes handles the library prep layer: it reads your NML, lets you organize by feel, and exports a fully structured collection into Engine DJ so you do not have to rebuild playlists or re-set cues by hand.

Not through the native route, since Engine DJ has no Traktor NML importer. When you use Vibes, it can export cue points to Engine DJ as hot cues during the export step, so your prep work carries over without re-cueing every track.

No. Engine DJ uses hot cues only and has no memory cue concept. Any cue points transferred into Engine DJ, whether via Vibes or another method, will land as hot cues.

Methodology