Move Your Minecraft Server to a New Host Without Losing Your World

Introduction

Switching hosts when your Minecraft server is already live is a scary idea, and understandably so: there is a world, there are builds, inventories, sometimes months of play behind it. The fear is always the same, losing everything between the old server and the new one. In practice, a clean migration takes between thirty minutes and two hours depending on the size of the world, and nothing is lost as long as you follow the right order. This guide covers a full Minecraft server move to SERV-Minecraft hosting: what to take with you, what you should never copy, how to upload your files, and how to switch your players over without a visible outage.

One principle matters more than anything else: a Minecraft server is nothing but a folder of files. If you have that folder, you have your server. No host owns anything you cannot take with you.

What you actually need to take

Before downloading everything in bulk, know what counts. On a server of several gigabytes, half the weight is useless once it reaches the new host.

On a modded server the logic is identical with mods, config, defaultconfigs and scripts. And of course you keep your world folders.

Step 1: write down the old server's setup

Migrations almost always fail for the same reason: the new server does not run exactly what the old one ran. So note three things before touching anything.

• The exact Minecraft version, down to the patch (1.21.4 and 1.21.5 do not load a world the same way, and you never move a map down to an older version).
• The server type: Vanilla, Paper, Purpur, Spigot, Forge, Fabric, or a specific modpack with its build number.
• Your plugin or mod list, with versions. The /plugins command in game or in the console gives you the whole list in one line on a plugin server.

Those three lines fit in a text file on your desktop and will save you an hour later on.

Step 2: shut the source server down properly

Never copy a world while the server is running. Minecraft keeps chunks in memory that are not yet written to disk, and a hot copy produces an inconsistent, sometimes corrupted map, with areas rolled back by several hours.

1. Warn your players and get them disconnected.
2. In the old host's console, type save-all and wait for the write confirmation.
3. Type stop, or use the panel's stop button. Wait until the server is genuinely offline, not merely stopping.

Only from that point are your files trustworthy.

Step 3: download your files

Two methods, depending on what your current host offers.

As an archive

Most panels let you select folders, build a .zip or .tar.gz archive and download it. This is by far the fastest route: a 4 GB world comes down as a single compressed file, often half the size, instead of thousands of small .mca files sent one by one.

Over SFTP

If an archive is not possible, connect over SFTP with FileZilla or WinSCP using the credentials your host provides, and drag the folders to your disk. Expect it to take longer: the protocol opens one transfer per file, and a Minecraft world contains a great many of them.

Check the size of what you downloaded before moving on. A 30 MB world folder when the server reported 3 GB means the download stopped early.

Step 4: prepare the destination server

Order your server with the new host based on what you were actually running, not on what you hope to save. At SERV-Minecraft the four Minecraft plans are sized like this:

• Start, 8 GB RAM, 4.99 € per month: a vanilla or survival server among friends, with a few light plugins.
• Plugins, 16 GB, 8.99 € per month: a Paper or Purpur server with a real plugin list, several worlds, ten players and up.
• Modded, 24 GB, 15.99 € per month: Forge or Fabric with around a hundred mods.
• Modpack, 32 GB, 21.99 € per month: the heavy CurseForge modpacks such as All the Mods, which load thousands of recipes at boot.

Once the server is delivered, open it in the panel and go to the Version tab before uploading anything. Pick the edition and the version that match exactly what you noted in step 1, tick Format the server to start from a clean base, and run the install. You end up with a fresh server on the right version, ready to receive your data.

Mind the order: the format option deletes every existing file. You tick it now, never after uploading your map.

If your server runs a CurseForge modpack, the Modpacks tab installs it directly, which saves you from transferring several gigabytes of mods: all you will have left to upload are your worlds and your custom configs.

Step 5: upload your files

Two routes again, depending on volume.

1. From the browser. Files tab in the panel, Upload button. You drop your folders and files in, no software to install. Ideal for a reasonably sized world and a plugins folder.
2. Over SFTP. Advanced tab, SFTP access box: you will find the address, the port and the username to enter in FileZilla. Preferable for large modpacks and multi-gigabyte worlds, and because an interrupted transfer resumes where it stopped.

Keep the original structure: world at the root of the server, not inside a subfolder. A classic mistake is uploading the folder that contains world rather than world itself, after which the server generates a brand new map and ignores yours.

If a plugin used a MySQL database (LuckPerms, Essentials with remote storage, CoreProtect, an economy plugin), create your database from the Advanced tab, Database box, import your .sql export, then put the new credentials into that plugin's config. Without this step your permissions and balances start from zero even though the map is right there.

Step 6: review server.properties

Your old server.properties contains values that belonged to the old host. Three lines to check before the first boot, from the panel's file editor or the Settings tab:

server-ip=
server-port=25565
level-name=world
online-mode=true

• server-ip must stay empty. An old IP address left here simply prevents the server from starting.
• server-port is managed by the panel, do not force it to a value carried over from the old host.
• level-name must match the exact name of your world folder. If your map is called survival2026, write survival2026, otherwise the server creates an empty world named world and your players will think everything is gone.

Think about your plugins too: any config holding an IP address, a port or a hostname (BungeeCord or Velocity proxy, dynmap, voting plugins, Discord webhooks) needs the new values.

Step 7: start up and verify

Start the server from the Console tab and actually read the lines scrolling by on that first boot. That is where everything is decided.

[Server thread/INFO]: Preparing level "survival2026"
[Server thread/INFO]: Loaded 428 advancements
[Server thread/INFO]: Done (18.412s)! For help, type "help"

The world name in quotes must be yours. If you read Preparing level "world" while your map is called something else, stop immediately and fix level-name: every minute of play on a fresh world adds cleanup work.

Then log in with your own account and look around: your spawn point, a chest you know, your operator rights, a plugin or two. Then ask a regular player to check from their side. Two pairs of eyes are better than one on a server that has just moved.

While you are there, enable the Backups option on your server page and create a first backup from the Backups tab, Create a backup button. That gives you a restore point dated the day of the move.

Step 8: switch the connection address

Your server now has a new address. Two possible situations.

You used the address supplied by the old host. Share the new one with your players, on your Discord and in the server description. Leave the old server switched off but not deleted for a few days, so everyone has time to move across.

You had your own domain name. That is the comfortable case: change the record at your registrar and your players see nothing. Point your A record at the new IP, and if your server does not listen on port 25565, add an SRV record so the address works without typing a port:

_minecraft._tcp.play.mydomain.com.  SRV  0 5 25567 mc.mydomain.com.

Allow up to a few hours for DNS propagation. Keep the old server stopped during that time, never running in parallel: two live servers with the same audience guarantees that some players will make progress on the map you are about to throw away.

Only cancel the subscription with the old host once your backups are verified and your players are back. A few euros of overlap cost less than a lost map.

The mistakes we see most often

• Copying while the server runs. Result: missing chunks, empty chests, rollbacks. Always save-all then stop.
• Changing version along the way. Moving host and upgrading are two separate operations. Transfer identically, check everything works, then update, with a backup at hand.
• Forgetting plugin configs. The whole plugins folder moves, not just the .jar files. Otherwise you restart with default settings on thirty plugins.
• Switching from Forge to Fabric or the other way round. Mods are not interchangeable. If you take the opportunity to change loader, our guide on installing Forge or Fabric explains what works with what.
• Undersizing the destination plan. A server using 10 GB of RAM will not fit in an 8 GB plan. If you want headroom without moving up a tier, our fifteen optimisation tips should be applied after the move, not during.

Frequently asked questions

Will I lose my map when changing host?

No, as long as you copy your world folders while the server is stopped. The map is simply a set of files you take as they are. The losses people report almost always come from a copy made with the server running, or from a level-name that does not match the folder uploaded.

How long does a migration take?

From thirty minutes for a small survival server to two hours for a modpack with a multi-gigabyte world. Most of the time goes into downloading and re-uploading files, not into configuration.

Do players keep their inventories and ranks?

Yes. Inventories and experience live in world/playerdata, ranks in your permissions plugin folder or in its MySQL database. Transfer both and your players find their exact situation again. Just make sure the authentication mode (online-mode) stays the same, since it changes how players are identified.

Can I move a Bedrock server the same way?

Yes, the logic is identical, with the Bedrock world folders and the server.properties specific to that edition. If you also want Java and Bedrock players together, our guide on Geyser and cross-play covers the setup.

Should I warn players in advance?

Yes, at least the day before. Announce a maintenance window, do your migration inside it, and share the new address as soon as the server is verified. A server that vanishes without explanation loses more players than two announced hours of downtime.

What if I get stuck halfway?

SERV-Minecraft support assists with migrations. Open a ticket from the panel with your version, your server type and the step that blocks you: this is an operation we handle regularly, and most issues are solved in a few messages.

In short

Shut down cleanly, grab the right folders, install the same version on the destination server, upload your files, fix level-name and server-ip, watch the console on first boot, then switch the address. Seven points, and a server that picks up exactly where it left off. If you are instead starting a server from scratch, our guide on creating a Minecraft server takes it from the top, and our Minecraft plans start at 4.99 € per month with no commitment.