A successful game-server migration preserves the world, player progress, configuration, and the community’s ability to reconnect. Copying the largest save file is rarely a complete plan. The safest workflow is to inventory the installation, test a copy, stop changes for the final transfer, and verify the destination before retiring the source.
Use the existing server as your recovery option until the new one has passed a normal play session and produced a usable backup. Plan the overlap before canceling a subscription.
Inventory the complete server state
Record the exact game version, branch, mod or plugin versions, startup settings, world identifier, and scheduled jobs. Ask which directories contain player records, permissions, inventories, and configuration. If the installation uses a database or multiple linked instances, include those dependencies in the plan.
Use the game’s official documentation for save locations rather than relying on a generic host path. Managed panels can place files differently. For example, Pocketpair documents separate platform-specific configuration locations; transferring the wrong configuration file can leave a Palworld world running with unintended settings.
Prepare a compatible destination
Confirm that the new provider supports the game version, operating requirements, necessary ports, and required mods. Check upload limits and ask whether the panel rewrites configuration on startup. Find out whether the assigned address changes after migration or a region transfer.
Install a clean matching server and verify that it starts before adding your data. Then stop it and upload a copy using the provider’s documented process. Keep the test private so new progress cannot accumulate on two competing versions of the world.
Test the copied world with returning players
Check more than the status indicator. Connect as an ordinary player, visit familiar locations, verify inventory and ownership, and exercise important mods or permissions. Invite at least one other returning player because the administrator’s account may hide an access or identity problem.
Read startup logs and test a normal save followed by a restart. Confirm that the restarted server loads the expected progress. Measure connection quality from the group’s main regions, and verify the new backup workflow before scheduling the public switch.
Freeze play for the final transfer
Announce a maintenance window with a time zone and the new joining instructions. Stop player activity, trigger the game’s supported save process, and shut down cleanly. Take the final complete backup only after the relevant data is consistent, then copy that state to the destination.
Keep the original server stopped or otherwise unavailable for ordinary play while the destination is verified. Two writable worlds can diverge immediately, making rollback confusing. If you use a custom hostname, account for cached DNS results and keep direct connection instructions available where the game supports them.
Validate the move before retiring the old host
Run the same verification checklist you used in the rehearsal, then open the server to the community. Monitor the first normal session for missing data, connection failures, and save errors. Take and download a new backup from the destination so your recovery process no longer depends on the old account.
Keep the source data for a defined recovery period, protect it from accidental use, and document which copy is authoritative. Once the move is accepted, remove obsolete access and scheduled jobs, update community links, and cancel the old service according to its terms.
Our recommended game server hosts
Gravel Host is our #1 editorial pick. Compare these five alternatives against your game, platform, region, and resource needs; availability differs by provider.
Our first choice for your next server
Modern survival games & new releases
High-population competitive servers
Console & PC crossplay servers
Budget-conscious players
Small groups & beginners
This is an editorial order, not a benchmark score. Some alternative-provider links are affiliate links. How recommendations work.
Frequently asked questions
Can players keep playing during the final file copy?
That risks copying inconsistent data or losing progress created after the copy began. Use a maintenance window and the game’s supported save-and-shutdown process for the final transfer.
When should I cancel the previous host?
After the destination passes a representative session, save-and-restart checks, and a backup verification. Keep an overlap period that fits the value of the world and your recovery needs.
Sources & further reading
Use the original documentation for current commands, compatibility, plan details, and requirements.
Found something that needs updating? Send us a correction. Provider features and availability can change; confirm your requirements before ordering.
