Back to blog

How to Migrate Music Studio Software Without Losing Work

4 November 2026
How to Migrate Music Studio Software Without Losing Work

Migrating music studio software means moving three things: your project files with their media, your plugins and instruments with their authorisations, and your working habits. Do it in this order: back up everything, gather each project's media into one folder, reinstall and authorise software on the new setup, then test with real sessions before you retire the old system. This guide covers moving to a new computer and moving to a different DAW. It also covers what to do when you run a teaching studio and need your admin tools moved as well.

TL;DR

  • Keep the old computer and old DAW working until the new setup has passed real sessions.
  • Most DAW projects only link to audio. Use the DAW's collect or copy command before you move anything.
  • Plugins and authorisations are the usual failure point. Gather installers and licence details first, and check plugin formats.
  • Between different DAWs, bounced audio and MIDI are the most reliable carriers. Open formats such as DAWproject help in some cases.
  • Test old and new projects on the new system, then wait a few weeks before wiping the old machine.

Table of Contents

Two kinds of migration

People use the phrase for two jobs. They need different plans.

Same DAW, new computer. Projects open as before, but the media, plugins, drivers and licences must all arrive intact. The work is mostly logistics.

Different DAW. The project format changes. Moving a DAW usually involves a learning curve of a few weeks even for experienced users. Some plugins do not carry their settings across cleanly. Converting past work is hit-and-miss, and often means freezing tracks or exporting stems.

The steps below cover both. Where a step applies to only one, it says so.

Step 1: Take stock and back up

The old computer is the best record of what your projects depend on. Before you change anything, list the plugins, versions, formats, licences, presets, sample libraries and custom folder paths you actually use. FX Recall's migration guide recommends keeping the old system running until the new one passes real-session testing. It also recommends a full system backup or disk image, and consolidating your current projects.

A simple rule helps here. The 3-2-1 backup rule means three copies of your data, on two types of storage, with one copy off-site. In practice that is your working drive, an external SSD or hard drive, and a cloud copy.

Also collect the small things that are easy to lose:

  • Installers for every plugin and instrument, kept in one folder.
  • Licence files and registration codes.
  • Content packs and sample libraries.
  • Account logins for each vendor.

Gus's migration tips suggest saving installers in a common location, keeping licence files, using email as a registration repository, and using a notes app for registration codes. Do this as you buy software, not on the day you move.

Step 2: Gather each project's media

Most DAWs do not store audio inside the project file. The project holds instructions and links that point to audio and samples elsewhere on disk. Copying the project file alone is not a real backup. Every major DAW has a command that gathers the media into the project folder.

DAWWhat to use
Ableton LiveCollect All and Save from the File menu, then compress the folder
Studio OneCopy External Files in the Pool tab
ArdourFile > Archive to create one compressed session archive
FL StudioFile > Export > Zip looped package
Logic ProFile > Save As, with the copy audio option
GarageBandAlready self-contained

The FL Studio, Logic Pro and GarageBand entries come from Violet Recording's backup guide.

Ableton states that Live Sets are compatible across Windows and Mac. The references to audio files, Max for Live devices and plugins sit inside each .als file, while the files themselves are stored elsewhere. That is why the collect step matters.

In Studio One, you can also enable the preference that asks to copy external files when saving a song. That keeps future projects portable without extra work.

Drive formats when moving between Windows and Mac

By default, Windows and Mac use different drive formats, NTFS and HFS+, and neither system can write to the other's drives without extra software. A FAT32 drive reads and writes on both. FAT32 cannot hold a single file over 4 GB, so large audio files may not fit. Check your biggest files before you choose a drive.

Step 3: Move plugins, instruments and authorisations

This is where most migrations stall. Three things matter: format, platform and licence count.

Plugin formats

On Windows and Mac, only VST and VST3 formats are compatible across platforms. Ableton notes that when you move from Windows to Mac, or the reverse, tracks using Audio Unit (AU) plugins must be rendered first. Use Freeze and Flatten in Live 11, or Bounce in Live 12. PreSonus says the same in plain terms: if a Studio One song uses AU plugins on macOS and you open it on Windows, the VST versions do not load automatically, even if they are installed. A common format such as VST or VST3 avoids the problem.

Image-Line gives the same advice for FL Studio projects. Use the latest release on all systems, install the same plugins in the same formats (VST, VST3 or CLAP), and enable the Verify plugins scan. If the other system does not own a plugin, bounce that track to audio before you send the project.

Apple Silicon

Some third-party plugins built for Intel processors do not run natively on ARM or Apple Silicon. Image-Line suggests Rosetta mode as a temporary fix. It also notes that Apple will drop Rosetta 2 support after macOS 27, with near-total removal in macOS 28 in 2027. If you are moving to a new Mac, check each vendor for a native version before you commit.

Licences

Each Ableton Live licence includes two authorisations, which lets the registered owner authorise Live on two computers. You cannot de-authorise Live on a previous computer. If you run out, you contact Support. Other vendors have their own rules. Before you wipe the old machine, check the policy for each major plugin and deauthorise where the vendor allows it.

Step 4: Moving to a different DAW

A project does not convert cleanly. Plan for what each format can carry.

Bounced audio is the most reliable carrier. Sound on Sound describes bouncing each audio and virtual instrument track as a continuous audio file. Every file starts at the same point, such as bar 1, beat 1. Imported into the new DAW, the tracks line up.

MIDI carries notes, not sounds. A MIDI file holds standard MIDI information only. It does not hold virtual instruments or audio. Export it alongside your bounced stems so you can re-voice parts in the new DAW.

DAWproject carries more. DAWproject is an open, DAW-agnostic format started by Bitwig. Studio One 6.5 added support in late 2023, and Bitwig Studio followed. Reaper is not formally supported, but a community-built converter exists. According to Gearnews, the format takes MIDI notes, audio clips, fades, volume, pan, time warping, markers and mixer automation. It also stores the full state of loaded plugins. The same article notes limits. Some DAW features cannot be translated, and you need the same third-party plugins installed on the destination DAW.

A practical export set for each project:

  1. A full-length bounce of each track from the same start point.
  2. A MIDI file for each instrument part.
  3. A stereo mixdown for reference.
  4. A text note of tempo, key, time signature and plugin settings you cannot export.

For your most important work, keep the original project and the old DAW installed. You will want them for revisions.

Step 5: Test before you retire anything

Verify the move with real sessions. FX Recall's guide suggests opening recent and older projects, checking that plugins and libraries load, playing through instruments and samplers, and verifying automation, sidechains and routing. Compare plugin inventories between the two systems.

If you moved to a new Windows machine, check for audio dropouts. Pete Gardner at Sound on Sound recommends a DPC latency check after migration using Resplendence's LatencyMon. He notes that the older DPC Latency Checker has behaved erratically since Windows 8. A common source of spikes is Ndis.sys, linked to networking drivers, antivirus or auto-updating software.

Then wait. Gus suggests producing on the new machine for a few weeks. After that, open a spread of old projects, the oldest, the newest, the median and some in between. This shows whether anything has been forgotten. Only then wipe the old computer.

A migration plan you can follow

  1. Pick a quiet period with no deadlines. Production Expert advises making time for the move during a quiet spell.
  2. Back up using 3-2-1 and create a disk image of the old system.
  3. List plugins, versions, formats and licences.
  4. Collect media for every active project.
  5. Install and authorise software on the new setup.
  6. Move one non-critical project first.
  7. Build templates and map shortcuts to match your old setup where possible.
  8. Test, then wait, then retire the old system.

The same source advises starting small with one non-mission-critical project, keeping the old DAW installed as a fallback, and building templates early.

Fresh install or system migration

A new music PC has different hardware, so a fresh installation is usually preferable. Gardner notes the BIOS and OS settings will differ. He also notes that a system migration, by moving the drive, can save a lot of time when reinstalling everything would take too long and deadlines are tight. Pick the fresh install when you have time. Pick the drive transfer when you do not.

Moving the teaching side of your studio

Moving the teaching side of your studio

A music teacher or studio owner often has a second set of files: student lists, lesson notes, repertoire records, schedules and sheet music. These need the same care as projects. Export what you can in common formats, keep a backup copy, and move one group of students first.

Our view on this is below.

Our perspective

We build Stormusi for teachers, studios and ensembles, and we are educators ourselves. In our experience, the hardest part of changing tools is not the data. It is the time a teacher loses while two systems run side by side.

We design our products to reduce that overlap. Each product is separate, so you can start with one that covers your most urgent job, such as classroom tools, studio management, ensemble organisation or sheet music creation. All products use one login.

We do not charge per student. You pay for the products you use, so a growing roster does not change your bill, and bundling several products brings a discount. That makes a gradual move easier to budget: add a product when you are ready for it.

Stormusi

Where Stormusi fits

If your migration includes the teaching side of your work, Stormusi offers separate products for it. Stormusi Composer supports sheet music creation using AI. Stormusi Classroom provides classroom tools for music teachers, including a repertoire tracker and a weekly planner.

Stormusi

Studio management for private tutors and schools, and ensemble scheduling and repertoire management for bands and choirs, are part of the same suite. Several products have free tier options. To see the full range, visit Stormusi.

FAQ

Can I open a project from one DAW directly in another?

Usually not. Project formats are specific to each DAW. The most dependable route is to export bounced audio from each track, plus MIDI files. Some DAWs support DAWproject, which carries more information, but both DAWs need to support it and the same plugins must be installed.

Why do my plugins not load on the new computer?

The most common causes are a different plugin format, a missing installer or an unauthorised licence. AU plugins do not load on Windows, and VST and VST3 are the formats that work across platforms. On Apple Silicon, some older plugins also need a native version. Check the format, the version and the authorisation for each one.

How many computers can I authorise?

It depends on the vendor. Ableton Live, for example, includes two authorisations per licence and does not allow de-authorisation on a previous computer. Check each vendor's authorisation page before you plan the move.

How long should I keep the old computer?

Keep it until the new setup has passed real sessions and you have produced on it for a few weeks. Open a sample of old and new projects first. If everything loads and plays correctly, wipe the old machine.

Sources

Recommended