Move an Aternos server to Minestrator or NitroServ

Prepare before moving your Aternos server

Record the game edition, exact version, server software and release, mods or plugins, and important settings. Keep exact names and numbers; “modded server” is not enough to recreate the environment.

This guide primarily covers Minecraft Java to Minecraft Java. For Bedrock, keep a compatible Bedrock server. Uploading files does not automatically convert a Java world into Bedrock format.

Choose a maintenance window with no players online. Explain that progress made on the old server after the final backup will not automatically appear on the new one.

1. Download the Aternos world

Stop the server and use the download option on the Worlds page. Follow the official Aternos world download instructions.

Keep the original archive on your computer. Extract a copy to check that files are present and readable. A world export does not guarantee that every server configuration, plugin or other data file is included.

Aternos does not provide full FTP access; its file access documentation explains the restrictions. Separately record or retrieve the settings you can access. If your software manages multiple worlds, check each one before treating the backup as complete.

2. Choose a compatible destination

The new server must support the same game version and loader. For a modpack, use the same server pack release. Check storage for the world, software and backups, as well as the host's import and restoration process.

Compare Minestrator and NitroServ and review the Minecraft server budget guide. Keep the old server until the new installation has passed testing.

3. Prepare the software and import a copy

1. Install the matching software release on the destination. For a modpack, use the author's server archive and instructions.
2. Complete an initial startup if the installation procedure requires it, then stop the server before replacing world files.
3. Back up any destination test world so you do not overwrite useful data.
4. Upload your world copy through the host's import tool or file access. Avoid an accidentally nested folder: the server needs files at the expected directory level.
5. Check the configured world name, including level-name when the software uses server.properties, and restore compatible settings.
6. Reinstall required mods, plugins and dependencies from their official sources. They are not necessarily included in the world archive.

Folder layouts may differ between Vanilla, Paper and modded servers. Follow the instructions for your software and host rather than guessing how dimension folders should be renamed.

4. Test before moving players

If inventories appear missing, check authentication settings and player identity before moving files. Changing authentication mode during migration can change how data is associated with accounts.

5. Switch the address and keep a rollback option

After testing, stop progress on the old server. If players returned there after the initial export, make a final backup and repeat the import. Then share the new address and exact modpack release with your group.

Keep the initial archive and old configuration until several sessions have worked on the destination. If migration fails, return to the intact old setup rather than experimenting on your only remaining copy.

Aternos migration FAQ