--- title: "Move a Minecraft Server to a New Host Safely | ZCS" description: "A migration checklist for moving Minecraft hosting providers while preserving world saves, plugin databases, permissions and a reliable rollback." url: "https://www.zcraftstudios.com/blog/minecraft-server-move-host-without-losing-world" updated: "2026-10-20T07:16:50.972429+00:00" source: "ZCraft Studios" --- > Site index for AI agents: https://www.zcraftstudios.com/llms.txt (full reference: https://www.zcraftstudios.com/llms-full.txt). Every page is available as Markdown by adding `.md` to its URL or sending `Accept: text/markdown`. 1. [Home](https://www.zcraftstudios.com/) 2. [Blog](https://www.zcraftstudios.com/blog) 3. Move a Minecraft Server to a New Host Safely [ All posts](https://www.zcraftstudios.com/blog) # Move a Minecraft Server to a New Host Safely ZCraft StudiosOct 15, 2026Updated Oct 20, 2026 A migration checklist for moving Minecraft hosting providers while preserving world saves, plugin databases, permissions and a reliable rollback. ## In this guide - [Start with a complete inventory](#start-with-a-complete-inventory) - [Decide what needs to move](#decide-what-needs-to-move) - [Take a recoverable source snapshot](#take-a-recoverable-source-snapshot) - [Create a matching destination](#create-a-matching-destination) - [Run a pre-cutover test](#run-a-pre-cutover-test) - [Plan the DNS switch](#plan-the-dns-switch) - [Rollback and data consistency](#rollback-and-data-consistency) - [Migration verification](#migration-verification) - [Related guides](#related-guides) ## How to Move a Minecraft Server to Another Host Without Losing Players or Worlds ## Start with a complete inventory A host migration is not simply moving a `world` folder. Your server may depend on separate dimension folders, plugin databases, a proxy, domain records and external resource packs. Document the currently running Minecraft version, Java runtime, server build, startup flags and installed plugin versions. Record the active world name from `server.properties`. ## Decide what needs to move | Component | Why it must be reviewed | | --- | --- | | World and dimensions | Buildings, exploration, metadata and player state | | Plugins and configuration | Claims, economy, warps, permissions and integrations | | External databases | Persistent information may not live in the file manager | | EULA and server configuration | Access rules, port, distance and gameplay settings | | Resource packs and maps | External URLs, map tiles and asset distribution | | DNS and proxy routing | Players must land on the new host after cutover | ## Take a recoverable source snapshot Announce maintenance and stop the old instance cleanly before copying a consistent snapshot. Export plugin databases using a supported backup method and coordinate their snapshot with world files. Keep the source backup unmodified. Avoid uploading private credentials into public file-sharing services. A file archive without the correct database can restore terrain while losing ranks or claims. ## Create a matching destination Select the same compatible game software and Java runtime on the new host first. Upload the copy and restore any databases under appropriately scoped credentials. Use a separate test endpoint. Check storage permissions and plugin configuration for hardcoded database hosts, URLs, absolute paths or addresses tied to the previous provider. ## Run a pre-cutover test Join as a normal player and check inventory, permissions, claims, shops, worlds and important NPCs. Then join as a moderator and confirm moderation tools can perform the intended actions. Restart and verify persistence. Take notes on any specific difference; don't use production as the first place you discover an incompatibility. ## Plan the DNS switch If you have a custom domain, lower its TTL ahead of the planned move where practical, update the relevant A or SRV records when the new endpoint is ready, and allow for cached resolvers. Don't leave old and new instances accepting writable player activity simultaneously: progress can diverge. Keep the old instance offline or clearly in maintenance mode during cutover. ## Rollback and data consistency Define rollback criteria before switching: failed joins, missing inventory, broken authentication or unresponsive key systems. Restoring world files while leaving a newer database in place can corrupt assumptions about player state. Restore a coordinated pair of snapshots instead. Keep both original host files and export archives until the new environment has passed a realistic use period. ## Migration verification - \[ \] Two or more normal player accounts can join through the public address - \[ \] Staff commands are restricted correctly - \[ \] World, Nether and End match expected state - \[ \] Economy, claims and permissions persist through restart - \[ \] Backups succeed on the new host - \[ \] Old hosting no longer accepts unintended player activity - \[ \] Staff know the rollback procedure ## Related guides - [Minecraft Server Files Explained](https://www.zcraftstudios.com/blog/minecraft-server-files-folders-explained) - [Database-Backed Player Data](https://www.zcraftstudios.com/blog/mysql-cross-server-player-data) - [Backup Strategy](https://www.zcraftstudios.com/blog/minecraft-server-backup-strategy) - [Custom Domain and SRV Records](https://www.zcraftstudios.com/blog/minecraft-server-dns-srv-record-guide) ## Continue reading - [Update Minecraft Plugins Safely: A Step-by-Step Checklist](https://www.zcraftstudios.com/blog/minecraft-server-plugin-update-checklist) - [New Player Onboarding: Build a Server Tutorial Flow](https://www.zcraftstudios.com/blog/new-player-onboarding-tutorial-setup) - [Choosing a Minecraft Server Host: Shared, VPS, or Dedicated](https://www.zcraftstudios.com/blog/choosing-minecraft-server-host) [ Previous guide Minecraft Inventory Missing After Update or Migration](https://www.zcraftstudios.com/blog/minecraft-server-join-but-inventory-gone)[ Next guide Minecraft Server Domain Setup: A and SRV Records](https://www.zcraftstudios.com/blog/minecraft-server-dns-srv-record-guide)