Migrate an ARK Ascended Save and Create a Cluster

Prepare source and target

Put source and target on the same ASA build. Record internal map name, startup line, INI files, ordered mod list and versions. Block joins, force a save through administration, then fully stop the source.

Archive ShooterGame/Saved/, especially SavedArks/, which holds the map save, .arkprofile player profiles and .arktribe tribe files. Preserve configuration and mods too. Download the archive away from both machines and inspect it before copying.

Migrate an ASA world

Build a cluster across maps

Each instance needs its own map, world directory and unique game/peer/query/RCON ports. Instances instead share a writable transfer directory and the same cluster identifier.

Add to each startup line:

-clusterid=MY_CLUSTER -ClusterDirOverride="D:\ARK-Cluster"

The wiki also recommends reviewing -NoTransferFromFiltering and the seven GameUserSettings upload/download controls: survivors, items and dinos can each be allowed or blocked. Do not expose the cluster directory publicly; its data can affect the server economy.

Use a separate save directory per instance, for example through AltSaveDirectoryName, while noting that ASA retains a directory/map structure. Document which process owns each map.

Validate transfers and roll back safely

On failure, stop both instances before restoring. Return map, profiles and tribes from the same timestamp, plus cluster data if a transfer was in progress. A partial rollback can duplicate or lose a survivor.

The ASA setup guide covers base ports. For modded worlds, use the ARK mod troubleshooting guide.

Frequently asked questions