Upload A Save
Migrating a save is mostly a file-management task, but it becomes a world-destroying task if you rush it. Treat the transfer as a controlled deployment: confirm the right folder, keep the original untouched, and verify the world loads before anyone starts playing again.
What To Preserve
| World data | Map state, containers, safehouses, and environmental changes. |
|---|---|
| Player progression | Characters, inventories, factions, and any database-backed identity data. |
| Server config | Mod IDs, map order, and settings should match the save you are importing. |
Migration Workflow
- Back up the live server directory and the source save separately.
- Upload the save into the correct server location instead of merging files blindly into an existing world.
- Match the mod stack and map configuration before first launch.
- Start the server, join with an admin account, and inspect key bases, vehicles, and player-owned areas.
- Only reopen the world after that validation pass succeeds.
Mistakes That Cause Broken Worlds
- Importing the save while leaving an older world with the same name in place.
- Changing mod order between the original host and the destination server.
- Forgetting that character data and world data may live in different files or folders.
Verified 2026 Detail
When moving a save between hosts, branch parity matters as much as file parity. The official site still keeps the unstable beta separate from stable, so a migration should confirm branch, map stack, and workshop context together before you assume the save copy itself failed.
Current Official Note
Project Zomboid's official FAQ still treats unstable betas as a separate opt-in path from stable. If you are migrating a save, make sure the source host, destination server, and active clients are all on the same branch before you diagnose missing map data or broken characters.
Need a stable place to test changes before you touch a live world? Launch your Project Zomboid server with Supercraft.