FL Studio Pro
Workflow

Move FL Studio to a New Computer Without Breaking Projects

By Eric Norris Published Sep 23, 2026 12 min read

Quick answer

Install FL Studio fresh, unlock products on the About panel, then copy the actual User data folder shown in Options > File settings. Export active projects as zipped loop packages, reinstall matching plugin formats and keep the old computer until control projects pass.

FL Studio project transfer from an old computer to a new music production workstation

Install FL Studio fresh on the new computer, sign in on the About panel and click Unlock products, then check Options > File settings on the old computer and copy its actual User data folder; Documents/Image-Line is the default, not a guaranteed location. Export active projects as zipped loop packages. Reinstall each third-party plugin from its vendor in the same format, add your sample libraries as Browser search folders and open a few control projects. Keep the old computer as it is until those projects play with every sample and plugin in place.

Treat the move as a dependency transfer. FL Studio, the license, project files, recorded audio, sample libraries, plugin files, plugin licenses and personal presets live in different places, and the move works once each one is reconnected on the new system. The program folder is the one part you do not copy: install FL Studio fresh and move the data around it.

FL Studio transfer map for the application license projects samples plugins and presets
Separate the move into six parts. FL Studio and plugins are installed again, while projects, audio, libraries and personal data are copied and reconnected.

What to copy and what to install again

Install FL Studio itself fresh on the new computer from the latest installer, then copy the data that belongs to you. Third-party plugins follow the same split: install them again from each vendor, and copy only their presets and libraries where the vendor supports a move.

What to copy and what to install on the new computer
Part of the setupTransfer methodFailure to avoid
FL Studio applicationDownload and install the latest releaseCopying the old program folder and its broken paths
Image-Line licenseSign in on the About panel and click Unlock productsAssuming a copied program is already registered
ProjectsExport a zipped loop package or copy the project folderMoving the FLP and leaving its audio behind
User data folderCopy the actual User data folder shown in Options > File settings; Documents/Image-Line is the defaultPlacing it in a cloud-synced folder
Sample librariesCopy the library and add its folder to the BrowserRenaming folders without reconnecting them
Third-party pluginsInstall the same format and version from each vendorLoading a different format, version or name
Plugin databaseComes along inside the User data folderExpecting it to install the plugins

Keeping these jobs separate also gives you a clean rollback. If a project opens with missing audio, you know to look at its package and library paths. If a plugin is missing, you can check the format, scan path and license without copying unrelated FL Studio files again.

Inventory the old computer before moving files

Begin with a short inventory while the old system still works. Write down the FL Studio version from HELP > About, the User data folder, every Browser extra search folder, the plugin scan paths, the audio interface and driver, and any custom Plugin database folders. I keep projects and samples out of the program folder on macOS, because the Updating manual warns that an update deletes personal files left in the Package Contents folder under Finder > Applications > FL Studio.app > Content. Move anything stored there before you reinstall, and keep the list next to the transfer drive.

Next, pick control projects that cover the whole setup: one recent song, one older song, one with recorded audio, one with external sample packs and one built on important third-party instruments and effects. These become the test set on the new computer, since one short beat that opens fine says little for a large archive.

Make a second copy of irreplaceable project data before you reorganize anything. The site guides on FL Studio autosave and backups and FL Cloud project backup explain recovery options, but keep the migration copy separate from your routine backup rotation.

Install and unlock FL Studio on the new computer

Download the latest FL Studio installer for the new operating system and run a normal installation. Image-Line allows one personal license on multiple computers and operating systems when the licensed owner is the only user, so the old installation can stay in place while you set up its replacement.

Image-Line's answer on moving the program to a new computer says its software can be installed several times for personal use, so the new computer does not need a second license. Install FL Studio for your own account rather than All users, which keeps the license with one person. Companies, organizations and schools need a multiple license version.

Open FL Studio, go to the About panel, enter your Image-Line account email and password and click Unlock products, which registers every Image-Line product on the account, not only FL Studio. For an offline computer, the installation and update instructions describe a registration key file: log in to your Image-Line account on a computer with internet access, save FLRegkey.reg to portable media, copy it over and open it through Unlock with file on the About panel. Check that the expected edition and the Image-Line plugins show as registered before you bring in large projects.

I install the same release or a newer one before opening a single project, because a project saved in a newer version will not open in an older one. A project from the latest beta may need that beta to become the new release before it can open in the release version. Keep its working beta environment and an untouched project copy meanwhile. With several versions installed side by side, an old shortcut can start the older one, so open FL Studio from the Windows Start menu or Finder > Applications. The feature limits of Fruity Edition can also block projects made in a higher edition. Our FL Studio installation guide covers the installer steps.

Transfer projects with their audio, not just the FLP

An FLP keeps the project data but not the samples used in it, as Image-Line's project-format documentation points out. A project can arrive looking complete while its Audio Clips and Sampler Channels still point to files on the old disk.

I export active projects as zipped loop packages, because the package carries the samples from Sampler Channels and Audio Clips and opens straight from the FL Studio File menu without extracting. Choose File > Export > Zipped loop package, keep the ZIP intact on the transfer drive and open it from a local folder on the new computer. A ZIP packed by hand has to be extracted before the FLP inside opens. The Zipped loop package guide shows when this format beats a loose project folder.

FL Studio File menu exporting a Zipped loop package with the project and used audio
Use a Zipped loop package for active projects that depend on Audio Clips and Sampler Channel files. It keeps those assets beside the FLP during the move.

One limit applies. Samples loaded inside third-party plugins, such as samplers, stay out of the package unless the plugin saves sample data in its preset, the way DirectWave does with Monolithic save mode on. Move those libraries as separate items and check them inside each plugin.

Keep every project data folder attached to its project

If a project uses a project data folder, copy that folder together with the FLP. Recordings made to disk and dragged sample data are saved there, but samples loaded from the Browser or another location remain at their source unless you collect them. Use a zipped loop package or the documented Copy used samples to the project folder option for those files, and handle third-party instrument libraries separately. Image-Line lists a project moved out of its folder, or sent without it, as a cause of missing samples.

FL Studio can also gather the samples into a readable folder. The Project Settings manual describes the Copy used samples to the project folder option, which copies factory and other samples into the project folder, much like a zipped loop package. Choose it over a ZIP for projects that still collect new recordings and renders.

Keep the folder names and the hierarchy inside it as they are during the first move, and reorganize only after the project opens cleanly on the new computer. Our guide to changing an FL Studio project folder covers that later cleanup and keeps it out of the migration.

Restore User data and external sample libraries

Open Options > File settings on both computers and compare the User data folder and the Browser extra search folders. Copy the old computer’s actual User data folder after installing FL Studio; its default is Documents/Image-Line, but a custom location must be copied from where it really lives. Image-Line’s User data folder instructions identify it as the save location for recordings, projects and the Plugin database with favorites. Copy external project and sample folders separately. A Plugin database with your own folders comes along, but it does not install the plugins its entries point to.

Copy external sample libraries to a stable folder on the new system, then add each library root to the Browser. The File Search and Browser settings manual covers these paths. The new location does not have to match the old one, as long as FL Studio can see it through the Browser extra search folders. With a large archive, move the libraries first and add them as search folders before opening projects. A missing-samples pop-up can still appear on the first open, and FL Studio then searches those folders for the files.

FL Studio Files and folders settings with User data and Browser sample library paths
Match the User data location and add stable library roots as Browser extra search folders. Keep the list narrow so file searches remain useful.

Do not leave a whole drive as a permanent search folder. Image-Line offers it as a way to collect samples scattered across an old drive, and locating samples in large folders takes longer. Once a missing sample turns up, add its library folder and remove the drive path. The sample-pack setup guide gives a cleaner long-term Browser layout.

I keep the User data folder off cloud-synced folders, because Image-Line warns that iCloud, OneDrive, Dropbox and Google Drive can lock files, move them or delay writes, which can cause crashes. The User data files belong on a local drive, and the same advice covers removable and network drives. A cloud icon next to a project does not prove that every file it needs is stored on the computer.

Reinstall third-party plugins and their licenses

Install each important plugin with its own installer, using the build for the new operating system, and restore its license through the vendor account, license manager or hardware key. Image-Line strongly recommends the plugin installer and its default install location. The FL Studio registration does not activate third-party products.

Plugin identity matters as much as the product name. Image-Line's project-sharing answer says a missing plugin should be checked for the same format, version and name, and asks for identical formats, VST, VST3 or CLAP, scanned with Verify plugins enabled. Check the format first when a project reports a plugin as missing.

Open the Plugin Manager through Options > File settings > Manage plugins, confirm the scan folders, enable Verify plugins, then click Find installed plugins. I scan with Verify plugins on, because a fast scan finds plugins only by the file name, while Verify plugins gathers a unique identification code that still matches after a file is renamed. Select Rescan previously verified plugins only when you need to recheck an already verified plugin after a change; it works with Verify plugins enabled. Leave it off to scan new plugins without replacing previous verified results. The official plugin-installation manual explains formats and scanning, our plugin installation guide covers the full setup and the plugin-not-showing checklist helps when a scan runs but the plugin is still absent.

Native Access and similar managers deserve their own pass, since they handle plugin files and large libraries. Our Native Access setup guide covers that path. Move vendor libraries inside the vendor manager instead of dragging folders around until the plugin loses track of them.

Account for Windows-to-Mac and Mac-to-Windows differences

A move on the same platform keeps plugin formats and many library paths the same. A platform switch adds format choices. AU is a macOS-only format, so a Windows computer cannot load it, while VST, VST3 and CLAP exist on both systems and each plugin still needs the build for the new system. FL Studio projects themselves open on Windows and macOS alike.

Before a switch from Windows to macOS or back, list the projects that depend on AU, Intel-only or discontinued plugins. I render AU and Intel-only parts to audio before a platform switch, because AU stays on macOS and Image-Line calls Rosetta mode a temporary solution. Save presets where the plugin allows it. Audio does not replace the editable project, but it keeps the musical result when no matching build exists.

Apple Silicon adds another variable. FL Studio runs there in one of two modes, native Apple Silicon or Rosetta 2, and VST plugins built for Intel processors run inside a process bridge. A plugin that crashes natively can run in Rosetta mode while you wait for a native build. The Apple Silicon plugin guide covers the FL Studio side of that decision.

Open control projects and inspect the full signal path

Validation begins once files and plugins are in place. Open the control projects you chose during the inventory and wait for FL Studio to finish locating files. Read every missing-file or missing-plugin message. Press play from several points, solo important tracks, and compare obvious arrangement markers with the old system.

FL Studio control project check across the Playlist Channel Rack Mixer plugins and audio output
Use several known projects to check arrangement, samples, plugins, Mixer routing and audio output. One easy project cannot represent the whole archive.

Listen past the master output. Confirm that instruments load their intended presets, effects sit in the expected Mixer slots, automation targets still respond, sends and sidechains remain connected, and the project sample rate and audio device are correct. A silent track can come from routing or a vendor license as easily as from a missing WAV file.

Save a migrated copy under a new name instead of overwriting the original during the first review. If missing samples appear, follow the missing-samples recovery guide. If a project opens but the Browser or presets feel empty, compare the User data and Plugin database locations before changing the project.

Fix missing samples and plugins without hiding the cause

For a missing sample, search the old system or the transfer drive for the exact file name, restore the library that holds it and add the library root to the Browser extra search folders. FL Studio searches the folder the project was loaded from, then its sample folder, then every Browser folder you added. Do not swap in a different sample to clear the warning. The project plays, but it is no longer the same arrangement.

For a missing plugin, check the exact format the project used, the installed build, the scan path, Plugin Manager status and the vendor license. If the original plugin no longer runs on the new system, open the project on the old computer and render the affected part while that environment is still around.

When a project depends on many discontinued plugins, keep a system image or the old computer as a playback machine. A clean new workstation and a preserved old one can sit side by side, and the migration does not have to force every old project into the new plugin set.

Erase the old computer only after the migration passes

I keep the old computer untouched until the control projects pass, because Image-Line says there is no need to uninstall or deregister the software until you dispose of the device. Do not wipe, sell or reuse it until the new one opens every control project, finds its audio, loads its important plugins, passes the routing checks and saves a separate migrated copy. The transfer drive and the backup should also hold the source projects apart from the old machine.

Migration checklist with projects, samples, plugins and routing checked, backups still pending, and a reminder to keep the old system
Keep the old system available until projects, audio, plugins, routing and independent backups all pass. A single failed dependency means the move is still in progress.

Once the checks pass and the old computer is ready to leave your hands, remove its Image-Line license. On Windows, Image-Line provides a file and Knowledgebase instructions for removing the registry keys. Archive the inventory and note the projects that still need the old setup. That record turns a future missing plugin into a known compatibility limit.

The move is finished when the new computer reproduces your work without leaning on the old disk. A fresh install, packaged projects, stable library paths, vendor-installed plugins and a full control-project check make that result repeatable.

Moving FL Studio FAQ

Can one FL Studio license run on two computers?

Yes. One personal license covers several computers on Windows and macOS as long as you are the only person using FL Studio. Companies, organizations and schools need a multiple license version.

Do you need to remove the license from the old computer?

No, not while you still own and control it. Removal matters once you dispose of the device, and on Windows a Knowledgebase file removes the registry keys.

Can you copy the FL Studio program folder to the new computer?

Install FL Studio fresh from the latest installer instead. On the old computer, open Options > File settings and copy the actual User data folder after installation; Documents/Image-Line is only its default location. Transfer external project and sample folders too, or collect each project’s used samples in a zipped loop package.

Why will a project not open on the new computer?

A project saved in a newer version will not open in an older one, and a project from the latest beta may not open in the release version until that beta becomes the new release. Keep the working beta environment and a project backup. Check the version in HELP > About and start FL Studio from the Start menu or Finder > Applications.

Why are plugins missing after the move?

The plugin needs the same format, version and name as on the old computer. Install it with its own installer, then scan in the Plugin Manager with Verify plugins on.

How do you fix missing samples after moving FL Studio?

Copy the sample libraries over and add them as Browser extra search folders in Options > File settings, or export the project as a zipped loop package from File > Export on the old computer.

Can the User data folder live in OneDrive or iCloud?

No. Image-Line wants the User data files on a local drive, since cloud-synced folders can lock files, move them or delay writes and cause crashes.

Eric Norris
Eric Norris Nashville-based FL Studio producer and editor focused on practical workflow, mixer routing, troubleshooting, sampling and native Image-Line tools.
Explore all Workflow guides