# How to Move an Existing Modded Minecraft World to a New Host There's always a reason people end up needing to move a modded server to a new host — outgrowing the current plan, chasing better pricing, dealing with a provider whose support has gone downhill, or just wanting better hardware. Whatever the reason, moving an established world with weeks or months of progress is a different challenge than starting fresh, and getting it wrong can mean losing that progress entirely. Here's how to do it without anything breaking. ## Why This Is Riskier Than It Sounds Moving a modded world isn't just copying a folder from one place to another, even though that's technically most of what happens. The risk comes from everything that needs to match exactly on the new host: the same mod versions, the same Forge or Fabric build, the same configs, and often the same server software version. Miss any of these, and the world can fail to load, crash repeatedly, or in worse cases, generate corrupted data if it partially loads with mismatched mods. ## Step One: Document Your Exact Current Setup Before Touching Anything Before starting the migration, write down (or export, if your current host's panel supports it) the precise details of your current setup: - The exact Forge or Fabric version in use - The exact Minecraft version - A complete list of installed mods with their specific versions — not just names, since mod updates can introduce compatibility issues even within what seems like "the same mod" - Any server-level configs that aren't part of the mods folder itself (server.properties, ops list, whitelist, etc.) This documentation step is the single most commonly skipped part of a migration, and it's the reason a lot of migrations end up with confusing crashes that take hours to diagnose — usually because a mod version silently differs between old and new setups. ## Step Two: Take a Full, Verified Backup First Regardless of how confident you are in the migration process, take a complete backup of the current world, mods folder, and configs before starting anything, and actually verify it's complete and uncorrupted before proceeding. This backup is your safety net if anything goes wrong mid-migration — without it, a failed migration can mean losing the world entirely rather than just losing some time troubleshooting. ## Step Three: Set Up the New Server With an Identical Configuration Rather than starting the new server and adding mods as you go, set it up to exactly mirror the old configuration first: 1. Install the same Forge or Fabric version on the new host 2. Install the exact same mod versions — using your documentation from step one, not just re-downloading "the latest version" of each mod, which can introduce version mismatches 3. Copy over the same config files rather than letting mods regenerate default configs, since custom settings (especially ones affecting world generation or balance) can matter for consistency This step matters more than it might seem — even small version differences in a single mod between old and new setups are a common cause of crashes after migration, since mods aren't always backward or forward compatible even across seemingly minor version bumps. ## Step Four: Transfer the World Data With the new server configured identically, the actual world transfer is usually straightforward: - Stop the old server completely before copying data, to avoid transferring a world file that's still being actively written to - Copy the world save folder to the new server's world directory - Avoid starting the new server until the full transfer is complete and verified Depending on your old and new hosts, this transfer might happen via direct file transfer between hosts, downloading and re-uploading through each panel's file manager, or FTP/SFTP — the specific method matters less than making sure the transfer completes fully before attempting to start the new server. ## Step Five: Test Before Announcing It's Ready Once the new server starts successfully, don't immediately tell your group it's ready — test it yourself first. Walk through your base, check that machines and mod-specific systems are functioning normally, and watch the console for any warnings or errors that didn't appear on the old server. Catching an issue during this quiet testing period is far less stressful than discovering it once your whole group has logged in expecting things to work. ## Common Migration Problems and What They Usually Mean **World loads but immediately crashes.** Almost always a mod version mismatch — double-check your documented list against what's actually installed on the new server. **World loads but specific machines or structures are missing or broken.** Often points to a config difference, particularly with mods that store important data (like ID mappings) in configs rather than purely in the world save. **Server starts fine but players can't connect.** This is typically unrelated to the world data itself and comes down to new host networking configuration — port settings, firewall rules, or DNS if you're using a custom domain. ## Should You Start Fresh Instead? Sometimes migration complexity is a good moment to honestly ask whether starting a new world actually makes more sense — particularly if the modpack itself is also being updated significantly as part of the move, since combining "new host" and "new modpack version" migrations at the same time compounds the risk considerably. If a fresh start is acceptable to your group, it removes most of the risk described above entirely. ## Where to Look for Detailed Hosting Setup Once You've Migrated Once the migration is complete, it's worth revisiting whether the new host's plan is actually sized correctly for your modpack's real demands, rather than just matching your old setup's specs by default. For a more detailed breakdown of properly sizing hosting to a specific modpack, along with configuration guidance that pairs well with a fresh setup post-migration, there's a thorough guide here: [modded server migration and hosting guide](https://techprim.com/guide-to-modded-minecraft-server-hosting/), which goes further into the practical sizing and setup than a migration walkthrough alone can cover. ## The Bottom Line Migrating a modded Minecraft world safely comes down to matching the new server's configuration exactly to the old one before touching the world data itself, backing up thoroughly beforehand, and testing carefully before announcing it's ready. The process takes more care than starting fresh, but for a world your group has invested real time into, it's almost always worth the extra diligence rather than risking that progress on a rushed transfer.