
Switching Minecraft server hosts or moving your server to a new region does not mean starting over from scratch. By transferring your world folders, configuration files, and databases properly, you can move to a new provider while keeping player inventories, builds, and settings intact.
Before shutting down your current server, make sure your new host is ready to run your setup. If you are still comparing providers or looking for a specific location, you can use the plan finder on hosting.9minecraft.net to compare plans, locations, features, and prices converted to USD per month.
Check that your new plan has enough memory for your loaded chunks, player count, mods, and plugins. You can check your requirements with the RAM calculator at /tools/ram-calculator/. You also need to configure the new server environment to match your exact server software and version:
Never copy files while the server is running, as active chunk writes can corrupt your world data. Follow these steps on your old host:
save-all in the server console to force all world data and player inventories to write to the disk..zip or .tar.gz) of your server directory using your host's file manager or backup panel. Downloading a single archive is much faster and more reliable than downloading thousands of individual region files over SFTP.If any of your plugins (such as economy, permissions, or logging tools) use an external MySQL or MariaDB database rather than local flat files, export a .sql dump from your old host's database panel as well.
If you want an exact clone of your server, transfer almost everything from your root directory. Make sure your archive includes:
world folder (DIM-1 for the Nether and DIM1 for the End). For Paper, Spigot, and Purpur servers, dimensions are split into three separate folders: world, world_nether, and world_the_end. Player inventories and Ender chests live inside the playerdata subfolder of the main world.plugins or mods directory, plus the config folder so you do not lose your custom settings.server.properties, bukkit.yml, spigot.yml, and your config/paper-global.yml or paper-world-defaults.yml files.ops.json (which stores operator permission levels 1 to 4), whitelist.json, banned-players.json, and banned-ips.json.server-icon.png file (which must be 64x64 pixels).You can leave behind old crash reports, the logs folder, and old backup archives to keep the transfer size small.
Make sure the new server is stopped before uploading your files. Connect to your new host via an SFTP client or use the control panel's web file manager to upload your compressed archive to the root directory, then unarchive it.
If you are migrating to a self-managed VPS or dedicated server instead of a shared host, you will also need to handle the startup environment yourself. You can use our start script generator (which includes Aikar flags for Paper servers) or the Docker compose generator to set up your service. Before starting the server for the first time on a fresh machine, make sure eula.txt exists and contains eula=true.
If you exported a MySQL database in Step 2, create a new database on your new host, import the .sql file, and update the database host, username, and password inside the relevant plugin configuration files.
When moving between providers, your assigned IP address and port will almost always change. Open server.properties on the new host and check these settings:
server-ip= to blank (or the specific IP required by your new host) and update server-port to match the port assigned by the new panel. By default, Java Edition listens on TCP port 25565, while Bedrock Dedicated Server uses UDP port 19132 (19133 for IPv6).If you are upgrading to Minecraft 26.3 during the migration, note the standard server.properties defaults: view-distance=10, simulation-distance=10, max-players=20, online-mode=true, white-list=true, spawn-protection=16, pause-when-empty-seconds=60, and difficulty=easy. Notice that white-list defaults to true in 26.3, so either disable it for a public server or manage your allowed players with the whitelist generator. You can also rebuild a clean configuration using the server.properties generator.
Start the server on your new host and watch the console output carefully. Verify that the world loads without region errors and that all plugins or mods enable cleanly. Join the server using the new IP address and port to check that your inventory, spawn point, and operator permissions work as expected.
You can also verify that your server is reachable from the outside using our server status checker. If you use a custom domain name, update your DNS A record (and SRV record if your port is not the default 25565) to point to the new IP and port. Keep your old server files as a local backup for a few days until you are certain everything on the new host is running smoothly.
Yes. Your buildings, terrain, and player inventories are saved inside your world folders (including the playerdata subfolder). As long as you stop the server with save-all, download the complete world folders, and upload them to the new host running a compatible Minecraft version, nothing will be lost.
Yes. Standard Minecraft server files are portable across providers. Whether you are moving between shared hosts, a VPS, or a home server using a tunnel like playit.gg, you can download your files via SFTP or a panel backup and upload them to the new host.
Yes. Moving a server to a new geographic region works the exact same way as migrating between hosts. If your current provider offers the target location, their support team or control panel may let you transfer the instance directly; otherwise, you can download a backup of your server files and upload them to a new server plan in your chosen location.
This usually happens for one of two reasons: either the world folder name in server.properties (level-name) does not match the name of the folder you uploaded, causing the server to generate a brand-new world, or online-mode was changed between true and false, which changes the UUIDs used to match players to their files in the playerdata folder.