Move a Single-Player Minecraft World to a Java Server

Moving a single-player Minecraft world to a Java server lets friends share an existing project. Begin with a copy of the world and keep the original untouched until the multiplayer version has been tested.

This is a same-edition transfer. A Bedrock world is not a drop-in replacement for a Java save, and a modded world needs its compatible server stack.

Record the source environment

Note the Minecraft release, loader, mods, and datapacks used by the single-player world. Create an export or copy after leaving the world and closing the game.

Check whether the world relies on client-installed content. Server-side dependencies must be present on the destination, while client-only files may not belong there.

Prepare the destination

Set up a server using the compatible game release and software. Stop it before uploading the world. Place the complete world directory where the server expects it and configure the active world name.

Check for an extra nested folder after extraction. If the server creates a new map, stop it and inspect the selected path instead of continuing to play on the wrong save.

Verify the move

Join and inspect a recognizable build, another dimension, and your inventory. Single-player ownership and player data can need attention depending on the source and destination setup, so test before inviting everyone.

Restart the destination and confirm progress persists. Keep the source copy until the group has played a normal session without missing data.

Can I update the world during the move?

Keep the first transfer as close to the original environment as possible. Test updates separately with another backup.

See moving between hosts and Paper's migration guidance if the destination also changes server implementation.

Choose your next step

Compare EZ Game Host Minecraft hosting for your group. Choose resources for your actual world and workload, then keep a downloadable backup before changing hosts.