How to Move a Satisfactory Server to a New Host

To move a Satisfactory server to a new host, stop the old server and download your newest .sav from FactoryGame/Saved/SaveGames/server/ plus the session's blueprint folder from SaveGames/blueprints/<session name>/. On a Linux server both live under ~/.config/Epic/FactoryGame/Saved/SaveGames/. Upload the save to the same folder on the new server and the blueprint folder to blueprints, with the folder name unchanged. Claim the new server, then load the save from Server Manager > Manage Saves. Both servers must run the same game version and branch.

What you can and cannot move

What goes where

A Windows server run as a service keeps the same folders under %WINDIR%\ServiceProfiles\NetworkService\AppData\Local\FactoryGame\. The Satisfactory wiki's dedicated server page lists every variant.

Before you start

• Save and stop the old server. In Server Manager, open Manage Saves and make a manual save, or wait for the autosave, then stop the server. Downloading from a running server can give you a save that is a few minutes behind.
• Match the version and branch. If the old server ran Experimental, the new one must too. A save made on a newer build will not load on an older server.
• List your mods. Note every mod and its version. Install the same set on the new server before loading the save, or modded buildings and items disappear.

Step 1: Download everything from the old host

Every host offers at least one way out: the panel's backup download, the file manager's zip option, or SFTP with FileZilla or WinSCP. The quickest in game route is Server Manager itself: in Manage Saves, select the save and download it to your PC.

Server Manager does not download blueprints, so use the file manager or SFTP for the blueprints folder.

Step 2: Pick the right save

Saves are named after the session, with _autosave_0 to _autosave_2 or a timestamp on the end. Sort by Date modified and take the newest one for your session. If the old server had several sessions, only take the one you are moving and its matching blueprint folder.

Step 3: Copy the blueprints, named exactly

This is the step almost every move guide forgets. Blueprints are not stored in the .sav. Each session has its own folder in SaveGames/blueprints/, named after the session, holding pairs of .sbp (the design) and .sbpcfg (icon and description) files.

On the new server, upload the folder into SaveGames/blueprints/ with the same name as the session in your save. If the folder name differs by even a capital letter, the blueprint menu shows up empty. Copy both files of every pair. The blueprints folder may not exist on a fresh server until someone makes a blueprint, so create it if needed.

Step 4: Upload the save and claim the server

1. Stop the new server and upload the .sav into SaveGames/server/.
2. Start the server.
3. In Satisfactory, open Server Manager, add the new address and claim it with a server name and admin password if it is not claimed yet.
4. Open Manage Saves, select your save and click Load Game.

If you would rather not use the file upload, Server Manager can do it: Manage Saves > Upload Save sends a save from your PC's %LOCALAPPDATA%\FactoryGame\Saved\SaveGames\<id>\ folder, so put the downloaded file there first.

Step 5: Set the server settings again

Because ServerSettings.<port>.sav stays behind, the new server starts with default settings. In Server Manager, set the join password, Auto Pause, Autosave on Disconnect and the session the server loads after a restart. Loading the save from Manage Saves normally sets that last one for you.

You can copy ServerSettings.<port>.sav too, but the port in its name must match the new server's port, and it brings the old admin password with it. Starting fresh is simpler.

Common problems

• Blueprint menu is empty: the blueprint folder is missing, sits in the wrong place, or its name does not match the session name exactly.
• Save does not appear in Manage Saves: it is in the wrong folder, picked up a double extension like .sav.txt, or was uploaded while the server ran. Stop, fix, start.
• "Save is from a newer version": the new server is on an older build or a different branch. Update it.
• Server starts a new world after a restart: the loaded session is not set as the one to load. Load your save again from Manage Saves.
• Cannot log in as admin: you copied the old ServerSettings file, so the old admin password applies. Use it, or delete that file and claim the server again.
• Missing buildings: a mod is missing on the new server.

Moving to GamezServers

On a Satisfactory server from GamezServers, the server is claimed on first start with the Admin password shown in Settings, so sign in to Server Manager with that. Click Backup, stop the server, and upload your .sav to .config/Epic/FactoryGame/Saved/SaveGames/server/ and your blueprint folder to .config/Epic/FactoryGame/Saved/SaveGames/blueprints/ from the Files tab or over SFTP. The file manager can extract a zip or download one straight from a link. Set the game branch to match your old server, and your factory keeps running without anyone's PC. For a save from your own game, see how to upload a Satisfactory save to a dedicated server.

FAQ

Where are Satisfactory dedicated server saves stored?

In ~/.config/Epic/FactoryGame/Saved/SaveGames/server/ on Linux, and %LOCALAPPDATA%\FactoryGame\Saved\SaveGames\server\ on Windows.

Are blueprints saved in the .sav file?

No. They are separate .sbp and .sbpcfg files in SaveGames/blueprints/<session name>/, so copy that folder too.

Will my friends keep their characters and inventories?

Yes. Player inventories and positions are stored in the save, so everyone picks up where they left off.

Do I need to claim the new server?

Yes. Claim it in Server Manager with a name and admin password, then load your save from Manage Saves.