Direct answer

Transfer a stopped, consistent copy of the entire world and each dimension, then configure the destination to load those files with matching software and world settings.

Recommended procedure

  1. Write down Minecraft version, server fork, installed plugins/mods and level-name on both machines.
  2. On the source, run save-all flush then stop; copy the world, all dimension folders and necessary plugins to a verifiable archive.
  3. Install compatible software at the destination without generating over the migrated save. Stop the destination before replacing any newly generated placeholder world.
  4. Upload the data, set ownership and level-name, then start with the public endpoint closed for testing.

What to do next

Check associated user data, UUID handling, plugin databases, permission groups and per-world configs. Migrate proxy settings separately from world data.

How to verify the result

Compare the old and new spawn, inventory, Nether/End portals and several previously visited bases before opening to players.

Version and compatibility notes

A downgrade to an older Minecraft data version is not a safe rollback. Moving between Vanilla and Paper may require dimension directory conversions described by the Paper migration guide.

Official references

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000