How to Move a 7 Days to Die Server to a New Host
Move a 7 Days to Die server to a new host: copy Saves and GeneratedWorlds, bring serveradmin.xml, and match GameWorld and GameName in serverconfig.xml.
Updated Oct 3, 2026 · 5 min read
On this page
To move a 7 Days to Die server to a new host, stop the old server and download three things from its user data folder (~/.local/share/7DaysToDie/ on Linux, %APPDATA%\7DaysToDie\ on Windows): the save in Saves/<GameWorld>/<GameName>/, the map in GeneratedWorlds/<world name>/ if it is a random generated world, and Saves/serveradmin.xml. Upload them to the same places, copy your serverconfig.xml values, and set GameWorld and GameName to exactly the old names. Run the same game version.
What you can and cannot move
| Thing | Moves to the new server? |
|---|---|
| The world state: bases, land claims, loot containers, day count | Yes, Saves/<GameWorld>/<GameName>/ |
| Players' characters, levels, skills, inventories and map progress | Yes. They are saved on the server, in the save's Player folder |
| A random generated (RWG) map | Yes, but only with its GeneratedWorlds folder. The save alone is not enough |
Navezgane or a pregenerated map like PREGEN01 |
The map ships with the game, so only the save moves |
| Admins, bans and whitelist | Yes, serveradmin.xml |
| Server rules | Copy the values from serverconfig.xml. Since V3, most game rules are one SandboxCode |
| A save from a newer game version than the new server runs | No. Match the version, or set the new server to the same Steam branch |
What goes where
| File or folder | What it holds | Old server (Linux) | Old server (Windows) | New server |
|---|---|---|---|---|
Saves/<GameWorld>/<GameName>/ |
World changes, players, land claims | ~/.local/share/7DaysToDie/Saves/ |
%APPDATA%\7DaysToDie\Saves\ |
Same path under Saves |
GeneratedWorlds/<world name>/ |
The RWG map itself: terrain, towns, POIs | ~/.local/share/7DaysToDie/GeneratedWorlds/ |
%APPDATA%\7DaysToDie\GeneratedWorlds\ |
Same path |
Saves/serveradmin.xml |
Admins and permission levels, bans, whitelist, command permissions | Root of Saves |
Root of Saves |
Root of Saves |
serverconfig.xml |
Name, password, world, game name, slots, land claim rules, SandboxCode |
Server install folder | Server install folder | Copy the values, not the file |
Mods/ |
Modlets and overhauls | Server install folder | Server install folder | Server install folder |
If the old serverconfig.xml sets UserDataFolder or SaveGameFolder, the saves live wherever those point instead, and serveradmin.xml sits in that save folder too.

Before you start
- Save and stop. Run
saveworldin the console, then stop the server, so the last day is on disk. - Note the version. Check which game version and Steam branch the old server ran. Saves do not load on an older build.
- Copy the config values. Open the old
serverconfig.xmland noteGameWorld,GameName,WorldGenSeed,WorldGenSize,SandboxCode,ServerPassword,EACEnabledand the land claim settings. - List the mods. Every mod the world used must be on the new server, on the same version.
Step 1: Download from the old host
Use a backup download, the file manager's zip option, or SFTP with FileZilla or WinSCP. RWG maps and long running saves are large, so SFTP is the most reliable. Download the whole Saves folder and the one world folder you need from GeneratedWorlds.
Step 2: Work out the two names
Look inside Saves. The first folder level is the world, the second is the game:
Saves/
serveradmin.xml
East Nikazohi Territory/ <- GameWorld
MyServerGame/ <- GameName
Player/
Region/
For an RWG map, the GameWorld folder name matches a folder in GeneratedWorlds with the same name. For Navezgane, it is simply Navezgane.
Step 3: Upload to the new server
Stop the new server, then upload:
- The
GameWorld/GameNamefolders intoSaves, keeping both levels. - The matching world folder into
GeneratedWorlds. serveradmin.xmlinto the root ofSaves, replacing the empty one.- Your mods into
Mods.
Step 4: Point the server at the old names
This is the trap. If GameWorld is set to RWG on the new server, it does not look for your map. It generates a fresh one from the seed and size, with a new name, and starts a new save in it. Set GameWorld to the exact folder name of your uploaded map, like East Nikazohi Territory, and GameName to the exact game folder name. Spaces and capitals must match.
The second trap: launch options override serverconfig.xml. Many hosts pass the world and game name on the command line from their panel, so editing the XML does nothing. If your change does not stick, look for a panel setting instead.
Paste the old SandboxCode so difficulty, loot, XP and blood moons match, and set EACEnabled the way it was.
Step 5: Start and check
Start the server. Loading an existing world is much faster than generating one. Join, check that your character still has its level and inventory, and check a land claim. Before a big update, check the game's Steam news for notes on whether existing saves carry over.
Common problems
- Server generated a new map:
GameWorldis stillRWG, or the world folder name has a typo. Set it to the uploaded folder name. - Map is right but everything is reset:
GameNamedoes not match the save folder, so a new game started on the same map. - "World not found" or the server stops on start: the save came across without its
GeneratedWorldsfolder. - Admins have no permissions:
serveradmin.xmlwent into the game folder instead of the root ofSaves. - Players get a version mismatch: the new server runs a different version or branch from the save and the players.
- Blocks or items missing: a mod is missing or on another version.
Moving to GamezServers
On a 7 Days to Die server from GamezServers, click Backup, stop the server, and upload Saves and GeneratedWorlds into .local/share/7DaysToDie/ from the Files tab or over SFTP (login in Settings). The file manager can extract a zip or download one straight from a link. World, Save name, Sandbox code and Game version are panel settings, so set World to your map's folder name and Save name to your game folder name. The world then keeps its day count without anyone's PC. For a co-op world from your own game, see how to move a 7 Days to Die save to a dedicated server.
FAQ
Where are 7 Days to Die server saves stored?
In Saves/<GameWorld>/<GameName> inside the user data folder: ~/.local/share/7DaysToDie/ on Linux and %APPDATA%\7DaysToDie\ on Windows, unless UserDataFolder or SaveGameFolder moves them.
Will players keep their characters?
Yes. Characters are stored on the server in the save's Player folder, so they carry over with the save.
Where is serveradmin.xml?
In the root of the Saves folder, not in the server install folder or the game save.
Do I need the GeneratedWorlds folder?
Yes for random generated maps. The save only holds changes, and the map itself lives in GeneratedWorlds.
Skip the setup. Your own 7DTD server.
Then $19.99/mo. Just trying it? $5.00 for 3 days