How to Move a Minecraft Server to a New Host
Switching Minecraft hosts is easier than it looks — your whole server is just files. This guide walks the safe way to migrate to a new host without losing your world, plugins or players: back up, transfer, reconfigure, update the address and test. Minimal downtime, nothing lost.
A Minecraft server is portable: the world, configs, plugins and player data are all files you can copy. Moving to a new host means backing them up, uploading them to the new server, matching the version, and pointing your players (or your domain) at the new IP. Done in order, you can migrate with almost no downtime and nothing lost.
Below is the safe, in-order process. Moving to us? Our Minecraft hosting has a File Manager and one-click versions/modpacks that make this quick.
What you'll need
A quick checklist before you begin — have these ready and the rest is easy.
- Access to your old server's files (File Manager or SFTP).
- A full backup: world folders, configs, plugins/mods.
- The exact server type and version you were running.
- A new host with a File Manager/SFTP to upload to.
- Your domain's DNS (if you use one) to repoint.
Migrate your Minecraft server, step by step
Back up everything on the old host
Stop the server (so files aren't mid-write) and download a full backup: the world folder(s) (world, world_nether, world_the_end), server.properties, ops.json, whitelist.json, banned-players.json, and your plugins/ or mods/ folders with their configs.
world/ world_nether/ world_the_end/ server.properties ops.json whitelist.json plugins/ (or mods/) + their config folders
Match the version & type on the new host
On the new server, install the same server type and version — Vanilla, Paper, Fabric/Forge and the exact MC version (and modpack) you were running. A version mismatch is the main thing that corrupts a migrated world, so get this right first.
Upload your files
Stop the new server, then upload your world folders and configs via the host's File Manager or SFTP, overwriting the fresh defaults. Put plugins/mods into plugins/ or mods/ exactly as they were.
Reconfigure & set RAM
Check server.properties carried over (gamemode, difficulty, view-distance), and set the new plan's RAM. If you use Aikar's flags, apply them on the new host too. Start the server and watch the console for any missing-plugin or version errors.
Update the address (IP or DNS)
Your new server has a new IP/port. If players connect by IP, share the new one. If you use a domain or an SRV record, update the DNS to point at the new host — then it's a seamless change for players who use the domain.
A / SRV record -> new server IP:port
Test, then cancel the old server
Join, check the world, plugins, permissions and player data all loaded, and have a friend test too. Only once you've confirmed everything works should you cancel the old host — keep its backup for a few days just in case.
No world lost, minimal downtime
Always stop before copying
Copying a running world can grab half-written files and corrupt the save. Stop the server on both ends before you back up or upload.
Match the version exactly
The #1 cause of a broken migration is a version/type mismatch. Install the same Paper/Fabric/Forge and MC version on the new host before uploading the world.
Use a domain so switches are painless
If players connect via a domain/SRV record, future host moves are just a DNS change — no one has to learn a new IP. Set one up now if you haven't.
Keep the old backup a few days
Don't cancel the old host the instant it works. Keep its backup for a few days in case something surfaces later.
Common problems & fixes
Hit a snag? These are the issues people run into most — and how to solve them.
The migrated world won't load or is corrupted
Almost always a version/type mismatch. Install the exact same server type (Paper/Fabric/Forge) and MC version on the new host, then re-upload the world.
Plugins throw errors on the new server
Either the version differs or a config didn't copy. Match the version and make sure each plugin's config folder came across too.
Players can't find the new server
They're using the old IP. Share the new IP, or update your domain/SRV DNS record to the new server.
Permissions or ops were lost
ops.json, whitelist.json and your permissions plugin's data didn't transfer. Copy those files from the old backup.
Skip the setup — host it with ESAGAMES
Moving your Minecraft server to us? Our Minecraft hosting has a File Manager, SFTP and one-click versions/modpacks to make migration quick — with DDoS protection and backups, on a low-latency Frankfurt network.
Frequently asked questions
Will I lose my world if I move Minecraft hosts?
No, if you do it in order: stop the server, back up the world folders and configs, install the same version on the new host, upload the files, and test before cancelling the old one. The world is just files — copied correctly, nothing is lost.
How do I transfer my Minecraft world to a new server?
Stop the old server, download the world folder(s) (world, world_nether, world_the_end) plus server.properties and your plugins/mods, then upload them to the new host (matching the version) via File Manager or SFTP, overwriting the defaults.
Do my plugins and mods carry over when I switch hosts?
Yes — copy the plugins/ or mods/ folder and their config folders to the new server. Make sure the new host runs the same server type and version so the plugins/mods load correctly.
How do I avoid downtime when migrating a Minecraft server?
Set up and test the new server fully before switching. If players use a domain/SRV record, the cutover is just a DNS change. Do the final world copy during a quiet period so little play is missed.
What's the most common mistake when moving a Minecraft server?
A version or server-type mismatch — uploading a Paper world onto a Vanilla server, or a different MC version. Always install the exact same type and version on the new host first, then upload the world.
Do players need a new IP after I migrate?
If they connect by IP, yes — share the new one. If you use a domain or SRV record, just update the DNS to the new server and players who use the domain won't notice the change.
Keep reading
Minecraft is a trademark of Mojang Studios / Microsoft. ESAGAMES is an independent hosting provider, not affiliated with or endorsed by Mojang or Microsoft.
