Move a Game Server: From Any Host to game-serverhosting

You can move your game server from many hosts to game-serverhosting by transferring the existing server files via direct SFTP import, file upload, or backup URL. The key is to identify the relevant worlds, mods, plugins, configurations, and possible database dependencies before the import and then check the result cleanly afterward.

Requirements Before the Migration

Before starting the import, you should briefly inventory your old server. Write down the game, server version, used modloaders or plugin systems, and important configuration files. For Minecraft, these can include server.properties, world folders, plugin folders, and mod files. For ARK, Valheim, CS2, or Rust, the relevant files are located in different directories depending on the server structure.

Always create a backup at the old provider before moving files. If your game keeps running while copying, world or database files can become inconsistent. For the cleanest possible result, stop the old server shortly before the final export or run a second, final import during a maintenance window after a test import.

As an FTP/SFTP client, you can use FileZilla, for example; the official project page is documentation at filezilla-project.org. Use such tools only with login details from the dashboard of your previous host.

The Three Import Methods

Method 1: Direct SFTP Import

Direct SFTP import makes sense if your previous host supports SFTP. game-serverhosting can then fetch the data directly from the old server without you having to download it locally first.

You need:

• SFTP host, meaning IP address or domain
• SFTP port, often 22 or host-specific
• Username
• Password
• the correct path to the server directory

Start the import via /migrate and then check on the target server whether the expected folders were transferred. This method is especially suitable if your server contains many files or larger worlds. However, it does not replace checking game versions and mod compatibility.

Method 2: File Upload

File upload also works if the old provider does not offer SFTP access. You download the server folder via FTP or SFTP, package it locally as ZIP or TAR.GZ, and then upload the archive in the migration wizard.

Step by step:

1. Connect to your old server, for example via FileZilla.
2. Download the complete game folder.
3. Check whether world folders, plugins, mods, and configurations are included.
4. Compress the data as ZIP and check the upload limit currently shown in the import dialog.
5. Upload the archive via /migrate.

This method is robust because you can check the files locally. Make sure you do not back up temporary cache files instead of the actual world or save data.

Method 3: URL Import

URL import is suitable if your previous host offers a direct download URL for backups, for example for a .tar.gz archive. You enter the URL in the migration wizard instead of manually downloading and re-uploading the file.

It is important that the URL is reachable for the import and really points to the complete backup. If the link expires after a short time, you should start the import immediately after creating the URL.

Finding SFTP Login Details: Host Overview

For specific providers, you can find separate guides for the migration from G-Portal to game-serverhosting, the switch from Nitrado to game-serverhosting, and the migration from ZAP-Hosting to game-serverhosting.

What Is Typically Imported?

Files that are contained in your server directory or backup can be imported. These often include world data, player profiles, inventories, plugins, mods, and configuration files such as server.properties or game.ini. Database data is only transferred if it exists as files, for example with SQLite.

External MySQL databases, host-specific panel settings, operating system configurations, and login details outside the server folder are not imported automatically. If your server uses external services, document them before the move and set them up again separately.

If you need more control over individual files, the guide for SFTP access on the game server will help you. For Minecraft, the guide for the Minecraft EULA and first server start is also relevant.

Check the Result

Start the new server only after the import is complete. Then open the logs and check whether missing mods, wrong versions, or damaged configuration files are reported. After that, connect in-game and check the world state, inventory, permissions, plugin commands, and important server rules.

For modified servers, the server version should match the previous installation. If you migrate and update at the same time, you mix two sources of errors. Better: first import without changes, test, and only then perform updates.

Troubleshooting

The Import Stops

Check the host, port, username, password, and path. For file uploads, check whether the archive is readable and below the stated limit. For URL imports, the link must be directly reachable.

Files Are Missing After the Import

Compare the old server folder with the new file system. Often only a subfolder was backed up, or the actual save path was located somewhere else.

The Server Does Not Start

Read the current log file first. Typical causes are missing mods, incompatible plugins, wrong Java or game versions, or configuration values that do not fit the new startup command.

Players See an Old World State

Then an older backup was probably imported, or the old server continued running during export. Stop the old server, create a fresh backup, and import again.

Checks, Limits, and a Safe Way Back

The guide “Move a Game Server: From Any Host to game-serverhosting” applies to the server type described in the article and the version state visible at the time of checking. Menu names, available versions, mod or plugin compatibility, and required resources may differ after updates. Therefore, do not transfer values unchecked to another game, loader, or server version.

Before making changes to the world, game state, configuration, or extensions, create a backup of the affected files. Then change only one related step and check it with the same client and server version you want to play with later.

A successful single test is not a performance or availability guarantee. World size, mods, plugins, player count, network path, and simultaneous load can change the result. Document the version, change, and test result so you can understand later deviations.

FAQ

Does the Import Cost Anything?

Before starting, check in the import dialog whether the import is still offered without additional costs. You pay game-serverhosting for the new server plan; check the terms shown in the order process each time.

How Long Does the Migration Take?

The duration depends on the amount of data, number of files, connection, and import method. Small archives transfer faster than large modified servers with many individual files.

Does My Old Server Keep Running During the Import?

Technically, it can keep running, but for consistent data you should stop it before the final export. Otherwise, world or save files can be changed during copying.

What Should I Do if My Old Host Does Not Offer SFTP?

Use file upload. Download the data via FTP or file manager, create a ZIP or TAR.GZ archive, and import it via /migrate.

Are External Databases Transferred?

No, external MySQL databases and similar services are not imported automatically. Only file-based data contained in the backup can be transferred.