ARTICLE VIDEO

Migrating Data from Cakewalk "SONAR": Cubase

Music Production TroubleshootingPublished 2017.12.28Updated 2026.07.17
Read article ↓

With Cakewalk ending development of SONAR, users need to migrate to other DAWs. This article explains a practical way to migrate projects made in SONAR to Cubase. It details the process of exporting audio tracks as an OMF file and MIDI tracks as a MIDI file, then importing each into Cubase. It also covers points to watch out for when migrating, such as preventing garbled track names, handling Region FX and rebuilding mixer settings, so you can switch DAWs smoothly.

With SONAR's development ending, users will effectively have to consider moving to another DAW sooner or later.
Here we'll introduce a simple way to migrate a SONAR project file, the song file you made in SONAR, to a Cubase project file.

Here, we'll assume a typical song project file in SONAR containing a mix of

  • audio tracks
  • MIDI tracks (including synth tracks and instrument tracks)

.

First, in the SONAR project file, export
audio tracks as an OMF file
MIDI tracks as a MIDI file
in these two formats,
then import each into a Cubase project file.

Here are things to watch out for in advance when exporting.

  • If track names use double-byte characters such as Japanese, they may become garbled when exported, so change them to track names using only alphabet characters at this point.
  • In SONAR, audio clips with Region FX clips applied, such as Melodyne, aren't exported to OMF, so remove the Region FX clips or render them.
  • SONAR's OMF doesn't include automation, including volume, pan and effects. You'll need to bounce the tracks or set these up again in Cubase after migrating.
  • MIDI files generally contain performance data and basic MIDI controller information (volume, pan, expression and so on). They don't include instrument or sound data, so you'll need to set these up again in Cubase after migrating.
  • Console (mixer) data basically can't be migrated. Either remix from scratch in the Cubase project, or note down information about plug-ins you can use in both and apply them.

Exporting MIDI track data

First, to migrate the data in the MIDI tracks from the SONAR project file, export it as a Standard MIDI File (SMF).

From the menu bar, select "File" → "Save As."

Under file type, select MIDI file format 1 and click Save.
For the difference between format 0 and 1, see here.

Dialogs appear cautioning you about copyright and noting that audio data isn't included, but you can select "Yes" for all of them. Continuing on saves the MIDI file.

Exporting audio track data

Next, to migrate the audio track data, export it as an OMF file.

From the menu bar, select "File" → "Export" → "OMF."

For the file type, select version 2.
Set the checkboxes at the bottom like this, then click "Save."

The OMF file is exported.
For more about OMF files, see here.

Importing the MIDI track data

Import the two files exported from SONAR into Cubase.
It's best to import the MIDI file first.

The MIDI file contains tempo information, so importing it first saves you from having to set the tempo after importing the OMF file.

From Cubase's menu bar, select "File" → "Import" → "MIDI File."

If you already have a project file open, you'll be asked whether to create a new project. Select "Create" here. If you import a MIDI file into an existing project, the tempo information isn't applied.

Select the MIDI file you exported earlier and click "Open."

A new project file opens with the MIDI track data imported.
The track information for the audio tracks is also imported here, creating empty MIDI tracks with just track names and no data. Delete them.

Also, for what were instrument tracks or synth tracks in SONAR, both a MIDI track containing the actual MIDI data and an empty MIDI track with no data are created. Delete these unnecessary tracks too.

Set up the sound for each MIDI track again in Cubase.
If the instrument can be used in both SONAR and Cubase, such as a VST instrument,
you can also assign the same instrument and sound as in SONAR.

Importing the audio track data

Next, import the OMF file containing the audio track data.

From Cubase's menu bar, select "File" → "Import" → "OMF."

Select the OMF file you exported earlier and click "Open."

Here you need to import the OMF file additionally into the existing project, so select "No."

The import options appear, so check all tracks, select the advanced settings at the bottom right and click "OK."

The audio tracks and the audio data they contain have been imported.
Change the track order and so on as needed.

The MIDI data and audio data should now be largely migrated, so continue with mixing work including effects to complete the data migration.

Mastering Cubase

We've also prepared 125 articles across Cubase for beginners and advanced users, so please make use of them if you buy it.

Cubase 9.5 new features explained 1

Cubase 9.5 new features explained 2

Cubase tutorial articles

Frequently asked questions

Q1. When migrating from SONAR to Cubase, can I carry over my original mixing settings?

Console data basically can't be migrated. Automation such as volume, pan and effects needs to be set up again in Cubase. We recommend noting down information about plug-ins you use in both.

Q2. Can I migrate instrument and sound information along with the MIDI file?

MIDI files contain only performance data and basic controller information, not instrument or sound data. You'll need to assign instruments and set up sounds again in Cubase.

Q3. What should I do if my track names use Japanese?

Double-byte characters such as Japanese may become garbled on export, so it's important to change track names to alphabet characters only beforehand.

Q4. Why isn't Region FX reflected when exporting to OMF?

SONAR's OMF format doesn't support Region FX clips, so you need to remove the FX or render them in advance.