Skip to main content

Upload an existing Minecraft Java world

Move an existing Minecraft Java world to CloudExa through File Manager or SFTP. This guide covers a move between compatible Java server installations. Bedrock worlds and modded-to-Paper conversions need a different process.

Check the source before uploading

Record the Minecraft version, server software and world name on the original server. Use a compatible destination, preferably the same software and version for the first start. Opening a world in a newer version can change its data; loading it in an older version can fail or damage it. Keep an untouched original copy.

Stop the source server before making the final copy. Copy the complete world and its dimension data, not just the region files. Include any extra worlds that your plugins manage. Older Paper/Spigot setups may have separate folders such as world_nether and world_the_end; other versions use a different layout. Keep the source structure intact and consult the Paper migration instructions if you change software or version.

Prepare your CloudExa server

  1. Open the destination at the game panel. Confirm the server name and address.
  2. Create a backup of the current destination files. Stop the destination server and wait for its console to finish saving.
  3. Check free disk space. An uploaded archive and its extracted contents need space at the same time. A download on your computer is safer than relying on a second copy inside the same server quota.

Upload the files

  1. Open File Manager. Choose Upload to send files or a folder from your computer. For large transfers, use the address and username shown under Settings → SFTP Details in an SFTP client.
  2. If you upload an archive, open its menu and choose Unarchive. Check the result before starting the server.
  3. Find level.dat in the world directory. Avoid an extra nesting level such as MyWorld/MyWorld/level.dat.
  4. Open server.properties and set level-name to the correct world folder name, including letter case. Save the file. Plugins that manage several worlds can have their own configuration too.
  5. Start the server. Watch the console for errors before inviting players back.

Check the result

Join and visit a known build. Check inventories, player positions, the Nether and the End. If you moved the whole server, also verify permissions, whitelist and plugin data. Preserve the original copy until these checks pass.

If you see a new or incomplete world

Stop the server rather than continuing to play. Check the world folder name, level-name, archive nesting and dimension folders. If the console reports an unsupported version or missing mod data, return to your untouched copy and ask support about the correct migration path. Do not delete folders to make the error disappear.