Switching from another DAW

Take your work with you

If you already work in Logic, Ableton, FL Studio, Cubase or Pro Tools— here is exactly what carries over and what doesn't, before you move a project.
Try it on an existing projectSee pricing

Coming from

LogicAbletonFL StudioCubasePro ToolsStudio One

The honest version

What carries over, and what doesn't

No application fully opens another's project, whatever the advert says. This is the real picture.

Audio files and stems

Carries over

Drag them in. The sample rate is converted on the way if needed, and the original files are never touched.

MIDI files

Carries over

Standard MIDI in and out, with tempo and time signature. Your parts arrive as notes you can play.

Tempo and key

Carries over

Detected from the audio you brought in, or read from the MIDI file.

Channel names, order and colour

Partly

Kept when you export named stems. The colour is reassigned by instrument type.

Automation

Doesn't carry over

Fader and effect moves don't travel between applications. Export the part with the automation already printed into it.

Plug-in settings

Partly

An external plug-in keeps its preset if it is installed on both sides. The built-in effects have no counterpart.

The project file itself

Doesn't carry over

No application reliably reads another application's project format. The move is done through audio and MIDI.

Same thing, different word

Same concepts, different names

Region · Item · ClipClip
Arrangement view · PlaylistTimeline
Bounce · Render · FreezeExport · Freeze to audio
Aux · Return · FX channelBus
Rack · Insert slotEffects chain
Warp · Flex · ElasticStretch
Comping · Take folderTakes lane

Moving one song

1

Export stems from your previous software

Every channel, from bar one, with the effects printed in. Give them tidy names — the names carry over.

2

Drag the folder in

Each file lands on its own channel, aligned, at the project tempo. It takes about a minute.

3

Rebuild only what you must

Usually just the master chain and the automation you really cared about.

4

Keep the previous one installed

Nothing forces a clean break. You can run both side by side and switch when it suits you.

One consideration, honestly

If you have built a deep workflow in another application — templates, automation, specific plug-ins — you will need to rebuild part of it. Test the studio on a real project before moving your day-to-day work into it.

Test it on an existing project.

The studio opens in your browser. You can keep your previous software installed alongside it.

Open the studioDownload for PC

Also runs in the browser · Desktop version: Windows 10/11 · 64-bit · 193 MB