Step 1
Inventory the old server
Capture the current software, plugins or mods, Java version, startup flags, scheduled jobs, world name, and backup status.
Migration guide
A good Minecraft migration is mostly about sequencing: capture the files, match the software stack, test on the new host before DNS or announcements change, and keep one clean rollback point.
The biggest migration mistakes are usually operational, not technical. Worlds are copied without plugin folders. Startup flags are forgotten. The Java version changes silently. DNS is flipped before the new instance is tested. The safest path is to treat migration as a short controlled handoff rather than a one-click move.
Start by documenting the current server: software stack, Java version, plugin or mod list, world size, scheduled tasks, backups, and any startup flags that are not part of the default install. Then create a fresh server on the destination host that matches those requirements before you move files. Only when the new instance boots cleanly and the world loads properly should you plan the final cutover.
Step 1
Capture the current software, plugins or mods, Java version, startup flags, scheduled jobs, world name, and backup status.
Step 2
Create the new instance, match the stack, upload files, and confirm the world loads before anyone new joins it.
Step 3
Change the join path only after the new server survives a final test and a fresh backup exists from the old host.
What Usually Breaks
Best Next Step
Next step
Once the migration checklist is clear, the Minecraft page gives you the cleanest path into the right tier and the secure client portal.
Secure checkout
Orders are completed in the secure client portal operated by IllusionCloud FZ-LLC. The portal opens in a new tab so you can return to this page while you compare plans.
The portal is part of the same operating company and will open in a new tab.