We are your new 5-Star Hosting Company. At least according to ★ Trustpilot

Check out our current game server offerings.

All servers come with a 24-Hour Trial, Free Backups, and 40Gbps DDoS Protection included!

Use code SAVE15 to take 15% OFF Your First Invoice with ChicagoServers! Limited Time!
Guide

How to Move Your Game Server to a New Host Without Losing Progress

By the ChicagoServers team · Updated · 8 min read

To move a game server, write down exactly what the old one runs (game version, mods, launch settings, ports), set up the same version on the new host, stop the old server, copy the world, configs and mods across, test, and only then tell players the new address. Most migrations fail on a mismatch: a different game version, a missing mod, or a world name that no longer matches the config.

This guide gives you the checklist, the version and port pitfalls, and a downtime plan that keeps your community from drifting away during the move.

Quick answer
  • Inventory first: game and version, mod list with versions, launch parameters, ports, world name, admin lists.
  • Install the same game version and mod set on the new server before you copy any data, and test with a copy of the world.
  • Expect a new IP and possibly different ports. A domain name with a low TTL makes the switch painless.
  • Do a final backup with the old server stopped so nobody plays on a world you've already copied. Keep the old server alive briefly as a fallback.
  • Announce the date, the downtime window and the new address ahead of time.
On this page
  1. Step 1: Inventory what you're moving
  2. Step 2: Match versions before you copy anything
  3. Step 3: Copy the data
  4. How to do this on a ChicagoServers server
  5. Step 4: Handle the new IP address and ports
  6. Step 5: Plan the downtime and the announcement
  7. A short checklist to print
  8. Frequently asked questions

Step 1: Inventory what you're moving

Most of what makes a server yours isn't the world file. Before touching anything, write down:

  • Game and exact version (and Java version, mod loader version or framework version where relevant).
  • Every mod or plugin with its version, plus its config and data folders. Keep the original download links too.
  • Launch parameters and startup settings: world name, server name, ports, max players, any custom flags. On ChicagoServers these map to fields on the Startup tab, so note each value.
  • Config files and who edited them: server.properties on Minecraft, serverconfig.xml on 7 Days to Die, and so on.
  • Admin, whitelist, ban and permission data, because those are usually separate files from the world.
  • Anything tied to the old address: server-list entries, Discord bots, status pages, domain records, API allow-lists.

If you've lost track of some of this, open the old server's file manager and read it. The mod folder and the launch settings tell you most of the story.

Step 2: Match versions before you copy anything

Game saves generally move forward, not backward. If your old server is on an older version than what the new host installs by default, the new server may silently upgrade the world on first load, and you can't undo that. Rules that avoid trouble:

  • Install the same game version on the new host first. Upgrade later, on purpose, after a backup. On ChicagoServers, Steam games have a Branch button on the update bar for older or experimental versions, and some games have a version field on the Startup tab (Terraria, tModLoader, BeamMP).
  • Match the mod loader and every mod version. A mod that was updated since your world was last loaded may change data formats.
  • Check the runtime too. Recent Minecraft server builds need a new Java release, so make sure the new server's Java matches the server jar. On ChicagoServers, the Mods tab for Minecraft changes the server software, version and Java. PaperMC's install notes cover Java 25, and you can confirm the requirement for your exact version on their downloads page.
  • Remember Minecraft's 26.1 world-layout change. Paper now stores dimensions under world/dimensions/minecraft/, and the upgrade is one-way, so your first load of an old world on a new version should happen on a copy.

Step 3: Copy the data

  1. Back up the old server

    Take a full backup and keep it somewhere that isn't either server. If you're unsure which files matter, copy the entire server directory.

  2. Do a trial run on the new host

    Upload the backup to the new server (see the panel steps below) and start it with no announcement. Confirm the world loads, mods run, and admins and permissions work. This is the point where a trial or a money-back window is useful.

  3. Fix anything that doesn't load

    Compare the Console output with the old server's. Usual suspects are a world name that doesn't match the config, a missing mod, or a version difference. The Troubleshoot tab lists failed starts and crashes with the likely cause.

  4. Freeze the old server and do the final copy

    On cut-over day, announce the downtime, stop the old server, take a fresh backup and upload it to the new host, replacing the trial data. This guarantees that no one plays on a world you've already copied.

  5. Start the new server and test

    Join yourself first. Then have one admin and one regular player connect before you announce that it's live.

Copy methods: the Files tab in the panel works for small files and folders, and SFTP is faster for big worlds. Use the Host, Port and Username from the blue SFTP bar, your panel password, and set the client's protocol to SFTP (plain FTP will not connect).

How to do this on a ChicagoServers server

  1. Match the version

    Open your server in the panel. On Steam games use the update bar at the top of the page (Update now, Validate, and Branch where the game has other versions). On Minecraft use the Mods tab for server software, version and Java.

  2. Set the startup values

    On the Startup tab, fill in the fields you wrote down in your inventory (server name, world name, passwords, game options), click Save startup, then Restart. Ports are assigned by the panel; you do not set them.

  3. Upload your world, configs and mods

    On the Files tab, go to the folder, click Upload (or drag files or folders onto the page). For a .zip, right-click it and choose Extract here, then delete the .zip. For big uploads use SFTP. Stop the server before replacing its world or a file the game rewrites at shutdown.

  4. Apply config changes on the Configs tab

    For games with config files on the Configs tab, pick the file, edit it in the Settings view or as Text, click Save, then Restart. The name, passwords, ports and player slots are written from the Startup tab and your plan at every start, so values for those in an old config file will not carry over.

  5. Take a first backup on the new server

    Once it loads cleanly, open the Backups tab, choose World and settings or Whole server, and click Back up now. Set up Automatic backups while you are there.

Step 4: Handle the new IP address and ports

A new host almost always means a new IP address, and sometimes a new port. Players who saved the old address in their server list will see a dead server until they update it. Check your game's default ports, and use the exact IP and port shown in your new control panel:

GameDefault port(s)Source note (self-hosted settings; the panel handles these for you)
Minecraft Java25565 TCPSet by server-port in server.properties
Valheim2456 and 2457 UDP (base port plus one); 2456-2458 is commonly listedBase port set by -port
Rust28015 UDP game, plus a TCP RCON port you set (commonly 28016)+server.port and +rcon.port
7 Days to Die26900 TCP and UDP, plus the next few UDP ports up (26901-26902, and some guides also list 26903)ServerPort in serverconfig.xml

On ChicagoServers the ports are assigned by the panel, so you do not set them by hand. They are listed under Network on the Startup tab, and the address at the top of the server page is what players use. If a plugin needs another port, reserve one under Extra ports on the same tab; the panel opens nothing on it, the game or plugin uses it.

Use a domain name if you can. A record like play.example.com pointing at your server lets you change the IP later without telling anyone. Two practical points: lower the record's TTL (for example to 300 seconds) a day or two before the move so the change spreads quickly, and remember that a plain A record has no port. Minecraft Java supports SRV records (_minecraft._tcp) so players can leave the port off; the SRV target must point at an A record, not at a CNAME. Many other games don't support SRV, so players there still need to enter the port.

Step 5: Plan the downtime and the announcement

For a small server, the real downtime is the time needed to stop, copy and restart, often well under an hour. The part that costs players is confusion, so plan communication as carefully as the copy.

  • A week ahead: post the date, the expected downtime window and a short reason (better ping, more capacity). Pick an hour when the fewest people play.
  • A day or two ahead: lower DNS TTLs if you're using a domain.
  • On the day: post when the old server goes down, then when the new one is up, with the address in the same message.
  • After: leave the old server running for a few days if you can, with its name or message of the day pointing to the new address. In Minecraft that is the motd line, and in Valheim it is the server name. Ask players to stop connecting to the old one so progress doesn't fork.
  • Update the places that still list the old address: your Discord, website, server-list sites, bots and status pages.

After the move, watch the server for a day. Check the new server's CPU, Memory and Players at the top of the page at your peak hours, and the Analytics tab, to see whether it is keeping up.

A short checklist to print

  1. Old server inventoried (version, mods, launch settings, ports, admin data).
  2. Same version and mod set installed on the new host.
  3. Full backup taken and stored off both servers.
  4. Trial load of the world on the new host passed.
  5. Downtime announced with date, window and new address.
  6. Old server stopped, final backup taken, uploaded and verified.
  7. Admin and one regular player joined successfully.
  8. Address updated everywhere (DNS, Discord, server lists, bots).
  9. Old server left up briefly with a pointer to the new address, then retired.

Frequently asked questions

How long does it take to move a game server?

The copy itself is usually minutes to an hour, depending on world size and your upload speed. Allow extra time the first time to fix version or mod mismatches, which is why a trial load before announcing is worth doing.

Will my players need to change anything?

They will if the IP address or port changes. Using a domain name that you repoint (and, for Minecraft Java, an SRV record) means most players don't have to update anything.

Can I move a world to a different game version while migrating?

Avoid it. Move on the same version, confirm everything works, take a backup, and upgrade as a separate step. Many saves can't be downgraded after an upgrade.

Do mods and plugins move with the world?

No. Mods, plugins and their configs live in separate folders, so copy them across and install the same versions. Admin lists, whitelists and permissions are usually separate files from the world, too.

We are your new 5-Star Hosting Company. At least according to ★ Trustpilot

Check out our current game server offerings.

All servers come with a 24-Hour Trial, Free Backups, and 40Gbps DDoS Protection included!

We offer quality support, a detailed knowledgebase, video tutorials on most topics, and even live support in case you prefer a live human.

Use code SAVE15 to take 15% OFF Your First Invoice with ChicagoServers! Limited Time!