Back Up and Migrate a Project Zomboid World Safely

Create a restorable backup

Schedule downtime and ask every player to disconnect. Trigger a save through the console if your tooling exposes it, then stop gracefully and wait for the process to exit. Copying a live world can combine a newer player database with older map cells.

At minimum, preserve:

• Zomboid/Saves/Multiplayer/ and the directory named after the profile;
• Zomboid/Server/ with the INI, SandboxVars.lua and spawn regions;
• world-linked player databases and data;
• logs needed for diagnosis;
• the ordered WorkshopItems/Mods lists and manually installed extensions.

Archiving the entire Zomboid directory is safer. Record -servername, the Build 42 branch and exact build, launch options and ports. Open the archive to verify it and leave one copy untouched.

Move to the destination

1. Install the same branch and version on the new server and run it once to create paths.
2. Stop the clean server and keep its generated directory as a rollback point.
3. Transfer the archive in binary mode and restore it under the operating-system account that runs the service.
4. Correct ownership and permissions, then reproduce -servername. If the profile name changes, rename every associated path and file coherently.
5. Reinstall the same Workshop items and dependencies. Do not update, add and remove mods during the move.
6. Reproduce ports and firewall rules, or change both configuration and launch command deliberately.

A Build 41-to-42 transition is not an ordinary same-version move. Keep the world on a compatible branch and follow The Indie Stone's migration instructions against a copy.

Test before reopening

Start the destination while leaving the source untouched. Read the log through full world load, then join with an administrator and a normal player. Check the world, characters, inventories, vehicles, safehouses, factions, time, mods and sandbox rules. Move or build something, stop, restart and verify that the change persists.

Test from outside the LAN. If the address changed, publish it only after validation. Keep the old server stopped but intact for several days and define the point at which rollback is no longer needed.

Common failures and rollback

A fresh world usually means -servername does not match the restored directory or the service runs as another user. Missing characters with the correct map point to an incomplete database copy. A post-migration connection failure can be a build or mod mismatch; it does not immediately prove save corruption.

On failure, stop the destination, retain its logs, restore the untouched archive and repeat one change at a time. For a destination with imports and exports, compare Project Zomboid hosts.