This article provides general preparation guidance. Final service recommendations depend on the actual software, data, licensing, integrations, and operating requirements involved.
Match the server software and version
Record the exact Minecraft version and whether the server uses Vanilla, Paper, Purpur, Forge, NeoForge, Fabric, or another loader. A version mismatch can prevent the world or content stack from loading correctly.
Collect the complete world data
Include the main world and any Nether, End, dimensions, or custom world folders. Keep the level-name setting available so the migrated service points to the correct save.
Preserve the content stack
Copy plugin, mod, configuration, scripts, permissions, and dependency folders together. For modpacks, include the server pack or a reliable manifest and note any custom files that are not part of the public release.
Test before changing DNS or advertising the move
Launch the migrated copy privately, review the console, verify permissions and databases, and confirm that players can join before retiring the previous service.
Never place passwords, private tokens, recovery codes, API keys, database credentials, or license keys into a public form or unverified message.