Menu
  Log out
 

Migrate a Sons of the Forest Save to a Dedicated Server

Sons of the Forest Guide • Updated Aug 29, 2026

Migrating a Sons of the Forest Save to a Dedicated Server

A save migration is a file operation, not a new server setting. The client-hosted world and dedicated server use different data directories, and the official guide does not promise that every player or companion state will transfer cleanly. Preserve both copies and test before making the server canonical.

Before you begin: make two independent copies of the source save. Do not overwrite the only client save or the only server copy while experimenting.

1. Stop and identify the source

For a Windows client-hosted world, look below:

C:\Users\<user>\AppData\LocalLow\Endnight\SonsOfTheForest\Saves\<SteamID64>\

Find the multiplayer save by its slot and modification time. The exact client layout can vary with platform and Proton; do not assume a Linux path from another installation.

2. Identify the destination

The official dedicated-server data path is normally:

C:\Users\<user>\AppData\LocalLow\Endnight\SonsOfTheForestDS\

If the server is launched with -userdatapath, use that directory instead. On a managed host, ask for the mounted user-data path and use the file manager or supported upload flow.

3. Transfer a copy

  1. Stop the dedicated server.
  2. Back up its current SonsOfTheForestDS directory.
  3. Copy the source world into the destination using the provider's documented save/slot layout.
  4. Keep the destination's generated dedicatedserver.cfg and adjust only the documented SaveSlot/SaveMode values for the intended world.
  5. Do not copy a made-up SaveIndex, ServerSettings.ini, or RCON section.

4. Test the migrated world

  • Start with a private password and the intended save slot.
  • Confirm the world, base, story state, and expected player state.
  • Join from outside the host network and reconnect after a save.
  • Keep the source and pre-migration copies until the group completes a session.

What may not transfer

Do not promise that every client inventory, companion state, or progression detail maps between a peer-to-peer save and the dedicated-server build. If a state is missing, preserve the source, inspect logs and build compatibility, and contact the provider before editing binary or generated save files.

If the world loads empty

  1. Stop the server and preserve the current destination directory.
  2. Check the active -userdatapath, save slot, and SaveMode.
  3. Compare folder names and modification times against the source backup.
  4. Restore the last known-good destination copy and test again.

Related guides

Want help keeping the source and destination backed up? Host Sons of the Forest with Supercraft.

Tired of fighting this issue every patch?

Run a managed Sons of the Forest server with us. We handle the patches, mod-version pinning, save backups, and DDoS protection. Set up in minutes, multiple datacenter regions, no contract.

See Sons of the Forest hosting plans →
← Back to Sons of the Forest Guides
Top