How to Migrate an ASA Server from Windows to Linux

Before shutting anything down, record every server’s map, friendly name, install path, game port, query port, RCON port, cluster ID, cluster directory, mod list, custom launch arguments, backup path and scheduled tasks.

Announce the maintenance window, stop automated restarts and updates, save the world, and cleanly stop every server that shares the same cluster data. Confirm that no ASA or SteamCMD process is still writing to the source.

Create a current AASM backup for each map and a separate copy of the shared cluster directory. Keep the existing Windows installation unchanged as the rollback source.

Copy the server’s root folder — the directory that contains ShooterGame and the Steam application files — to a dedicated writable directory on the Linux SSD. Use an external drive, a trusted network share or an authenticated transfer tool.

For a source already mounted on Linux, an example copy is:

For a cluster, also copy the shared cluster directory and repeat the server-root copy for every map.

The Linux desktop user running AASM must be able to read and write the migrated server tree. Check ownership and available storage before importing:

Linux paths are case-sensitive. If a custom script or configuration refers to a path with different capitalization, correct it. Do not run AASM as root to compensate for an incorrectly owned server directory.

Install the native Linux build by following the Linux installation guide. AASM’s own Linux data is stored under ~/.local/share/aasm.

From the dashboard select Add New Server, choose Import Existing Server, enter a clear server name, and browse to the migrated server root. Select the directory containing ShooterGame, not the ShooterGame or Saved subdirectory itself.

Complete the import and confirm that AASM reads the expected map, ports and INI settings. Importing should point AASM at the copied files; it should not require a new world.

Review backup destinations, cluster directories, SFTP keys, certificate paths, custom scripts and any launch arguments that contain a Windows drive letter or backslash path. Select valid Linux destinations through AASM.

Leave automatic starts, updates, restarts and backup schedules disabled until manual tests are complete. For clusters, verify that every imported map uses the same cluster ID and the same migrated cluster directory.

Use AASM’s update/verify operation so SteamCMD can check the migrated dedicated-server files. Allow its console window to finish. Recheck available disk space after verification because SteamCMD may need temporary working room.

Compare the copied save and configuration files with the migration backup. At minimum, confirm the expected files exist under ShooterGame/Saved and the correct Game.ini and GameUserSettings.ini are present.

Start a single non-cluster map first, or one map from the cluster while all other copies remain stopped. Wait for AASM to report the server as ready, then connect with a known player.

Confirm the expected map, character, tribe, structures, inventory, mods and configuration. Test RCON, a clean stop and restart, and one manual backup. For a cluster, bring up the remaining maps one at a time and perform a controlled transfer test only after each map is healthy.

After manual validation, re-enable backup, restart and update schedules in stages. Watch the first scheduled cycle and confirm it produces a usable backup and returns the server to a ready state.

Keep the stopped Windows server and pre-migration backups intact until the Linux installation has completed multiple normal operating and backup cycles. If rollback is required, stop Linux first; never resume both copies.