Game Server Migration Checklist: Move Without Split Worlds

A game server migration should preserve progress and leave one clear live destination. The biggest avoidable mistake is letting players continue on both old and new copies during the move.

Plan the cutover before copying data.

Inventory the service

Record the game build, extensions, configuration, saves, and external data stores. Include scheduled jobs and integrations such as community bots or custom domains.

Check the source provider's export options and retention policy before canceling. Keep control of your own backup throughout the move.

Rehearse the destination

Restore a copy using a compatible software stack. Test joining, important world locations, representative player data, and a restart.

Use separate credentials or isolated databases where appropriate so the rehearsal cannot modify production state.

Document the exact transfer steps that worked. A rehearsal reduces the amount of improvisation during downtime.

Perform the final cutover

Announce maintenance, stop writes on the source, and export the final consistent state. Import it, repeat the acceptance checks, and then share the new connection details.

Keep the old instance offline and retain its archive until the destination has completed normal play. Update domain records and scheduled jobs deliberately.

Should a migration include a game update?

Separating them makes diagnosis easier. First prove the move, then test an update with a new recovery point.

Use the game-specific Minecraft transfer guide or Palworld migration checklist.

Choose your next step

Compare EZ Game Host plans against your game, expected workload, and backup needs. Start with a plan you can measure, and revisit it after a representative busy session.