How to Convert a Singleplayer Modpack World to Server

Why Convert Your Singleplayer World?

You have been playing a modpack in singleplayer for weeks, built an elaborate base, progressed through questlines, and now your friends want to join. Starting over on a fresh server world feels wasteful. The good news: you can convert singleplayer modpack server files and keep everything intact. The process requires care, but it is entirely doable.

The key challenge when you convert singleplayer modpack server worlds is making sure every mod, config, and world data file lines up perfectly between your local instance and the server. Mismatches cause missing blocks, broken machines, or outright crashes.

Step 1: Match Your Mod Versions Exactly

Before touching any world files, ensure the server runs the exact same modpack version as your singleplayer instance. Every mod jar must match. Even minor version differences in mods like Create, Mekanism, or Applied Energistics can change internal block IDs and corrupt your world data.

Download the server pack for your modpack from CurseForge or the pack's official source. If no server pack exists, copy the mods and config folders from your client instance, then remove any client-only mods (shader mods, minimap renderers, HUD mods).

Step 2: Copy the World Folder

Your singleplayer world lives in .minecraft/saves/YourWorldName/. To convert singleplayer modpack server worlds, copy the entire world folder to your server directory and rename it to match the level-name value in server.properties (usually world).

Important folder structure details:

• The Overworld data sits in the root of the world folder.
• The Nether is in DIM-1/ and The End in DIM1/.
• Modded dimensions (Twilight Forest, The Aether, etc.) have their own DIM folders or are stored under the world root.
• Copy all of these, skipping none.

For the general world import process, our singleplayer import guide covers the vanilla side in detail.

Step 3: Handle Mod-Specific Data

When you convert singleplayer modpack server data, some mods store data outside the standard world folder. FTB Quests saves progress in world/ftbquests/, while mods like FTB Teams and Game Stages store player data in separate directories. Check for any mod-specific data folders in your singleplayer instance and copy those to the server as well.

Player data files (in world/playerdata/) from singleplayer use your offline UUID. On a server with online-mode enabled, your UUID will be different. This means your inventory, ender chest, and quest progress may not carry over automatically. To fix this, rename your playerdata file from your offline UUID to your online UUID, or temporarily set online-mode=false for the first join.

Step 4: Test and Verify

Start the server and join. Walk through your base and check that all blocks, machines, and stored items are intact. Open any quest book to verify progression. If blocks appear as "missing" purple/black placeholders, a mod is not loaded correctly. Check the server log for mod loading errors and compare your mod list against the singleplayer instance.

After verifying everything works, convert singleplayer modpack server settings to online-mode if you changed it, and invite your friends.

Host your modpack on Astroworld Hosting, NVMe SSDs, full panel access, 24/7 support.