Game Server Migration Guide

How to move an existing game world

A successful migration preserves more than the map. Saves, player profiles, server versions, settings, and compatible mods may all need to match.

Before you copy anything

  1. Stop the original server cleanly and make a complete backup.
  2. Record the exact game, server version, edition, or branch.
  3. Record the world name, save name, and any platform-specific identifiers.
  4. List every mod and confirm whether it is server-side or also required by players.
  5. Keep the original server untouched until the dedicated server has been tested.

Files normally involved

  • World or map files: the generated or downloaded world data used by the server.
  • Game save: world-state data such as structures, inventories, progression, and active entities.
  • Player data: profiles, ownership information, and player progression associated with the save.
  • Server configuration: settings such as player limit, difficulty, game name, and world selection.
  • Mods: compatible server-side files required by the existing world.

The exact locations depend on whether the old server ran on Windows, Linux, a hosting panel, or another provider. Do not assume that copying only the visible world folder will preserve every player’s progress.

Testing the migrated server

  1. Start the dedicated server and confirm it loads the intended world without generating a new one.
  2. Join with a known player account and verify the correct character, location, inventory, and ownership.
  3. Check important bases, containers, vehicles, and landmarks.
  4. Review the console for missing-mod or world-loading errors.
  5. Create a fresh backup only after the migrated world passes testing.

Explore supported game hosting →

Migration Assistance

Want Astro Hosting to help?

Tell us where the current world is hosted, its version, and whether it uses mods.