Aternos is a good start: free, no setup, and for a small group that is enough for a long time. At some point the idle shutdown, the queue at peak times or the missing own address starts to bother you. Moving to your own server at game-serverhosting is not a restart – your world comes along. This guide walks through the migration wizard step by step and says honestly what does not come along automatically.
What changes after the move
| Point | Aternos | game-serverhosting |
|---|---|---|
| Uptime | Shuts down when idle, restart via the web UI | Runs permanently for as long as your contract runs – no sleep mode |
| Start and provisioning | A start queue is possible when capacity is full | Provisioning after payment; installation and available capacity determine the wait |
| Address | Assigned Aternos address | Your own subdomain with a live availability check |
| Bedrock cross-play | Manually via plugin | Geyser and Floodgate on supported Paper stacks; not suitable for every modpack |
| Ads | Yes | None |
| Cost | Free | Monthly plan depending on memory, paid via Stripe or credit balance |
The price depends on the memory you choose; the wizard shows it in step 5 before payment.
Preparation: what the world ZIP contains – and what it does not
The ZIP from the Aternos worlds overview contains the world folder: regions, player data, level data. It usually does not contain:
- the server settings (
server.properties), such as difficulty, view distance, PvP, - the operator list, the whitelist and banned players,
- plugins or mods as files.
The migration wizard detects plugins and mods when they are inside the archive and lists them in the detection step. Whatever it does not find you re-add in the panel after the move – the plugin manager of your new server installs the common plugins with one click. So write down what runs on your Aternos server before exporting.
Important: Stop the Aternos server before downloading the world. This prevents further progress on the old server after your export.
The migration in six steps
1. Download your world from Aternos
Open the worlds overview of your Aternos server and download the active world as a ZIP. With several worlds (Overworld, Nether, End as separate folders) download all of them; the wizard detects each one.
2. Open the migration wizard
Use the Aternos entry link. Game (Minecraft Java) and import method (upload) are then preselected. You need an account for the order; you can create it inside the flow, also via Google or Discord login.
3. Upload the archive
Select the ZIP. Wait until the upload has completed. The wizard shows the limit for a direct upload; larger worlds can alternatively be handed over via SFTP or a download link.
4. Check the detection
After the upload the wizard analyses the archive: edition, Minecraft version, server software (Vanilla, Paper, Fabric, Forge …) and any plugins or mods found. It sorts the extensions it finds into importable, convertible and unsupported. Whatever is unsupported will not run on the new server and needs a replacement – better to know now than after paying.
5. Configure the server and pay
Set server software (such as Paper or Fabric), memory, server name and subdomain. The wizard suggests the memory from the detection – 4 GB for Minecraft Java, more with many mods or players; you can adjust it. Pay via Stripe or from your credit balance. The server is then provisioned automatically and the world applied – large worlds and installations can take longer.
6. Confirm the takeover
As soon as the server is running, the wizard checks that a join is possible and shows “Ready for takeover”. Connect, look around, then confirm the takeover. Only then does the migration count as complete. Your Aternos server stays unchanged until then – so you always have a way back.
After the move
- Share the address: Java players connect via your subdomain. Bedrock players (mobile, console, Windows edition) use the same subdomain with the Bedrock port shown in your panel –
19132is only the Geyser default, not automatically your assignment. For a supported Paper stack, check the Geyser/Floodgate status in the panel. Java modpacks are not automatically compatible with Bedrock. Details: Set up Bedrock cross-play. - Re-enter settings: Operators, whitelist and server properties are re-entered in the panel.
- Reinstall plugins: Whatever the detection did not find, you install through the plugin manager.
- Create a backup: Create a backup after the first successful start – also keep the original world ZIP and the Aternos copy until you have checked the migration.
Frequently asked questions
Can I move more worlds later? Yes. The guide Upload & switch a Minecraft world shows how to upload or switch a world on an existing server.
What happens to my Aternos server? Nothing. The migration only reads the archive you upload. Deleting or keeping it is your call.
What if the detection marks a plugin as unsupported? It is not applied. Look for a current version or an alternative in the plugin manager – the server starts without the plugin too.
Sources and review date
Reviewed on 8 September 2026. Aternos documents the world download, the start queue and the different Nether and End directory layouts. Check these dimension folders when changing server software. Our import steps describe the current migration wizard; detection does not replace joining and checking the world yourself.
Ready? Open the migration wizard.