← All guides
ASA Manager · Step-by-step

ASA Manager: import an existing server

Locate an existing ASA installation, review detected settings and add it without moving its saves or server files.

19 Oct 2026 · ASA Server Manager
TBB ASA Server Manager settings screen, captured from the desktop application
After import: verify the existing installation’s map, identity and settings · Actual prototype 0.7.3 interface with sample data; final build may differ.

Import adds an existing installation to the manager. It is different from installing a fresh server and different from restoring a backup. Initial import testing is still required before the first public release.

1. Prepare the source server

  1. Stop the server using its current launcher.
  2. Close that launcher or disable its automatic restart/schedule.
  3. Make a separate backup of the server’s Saved folder and launch script.
  4. Locate the installation containing ShooterGame/Binaries/Win64/ArkAscendedServer.exe.

2. Find the installation

  1. Open Servers and click Import server.
  2. Browse to the existing server installation folder, or a parent folder containing your ASA installations.
  3. If available, select its .bat or .cmd launch script so launch-only settings can be inspected.
  4. Click Find servers and select the intended installation.
  5. If starting from an INI file, use Choose INI and verify the installation resolved from it.

Game.ini and GameUserSettings.ini normally sit inside ShooterGame/Saved/Config/WindowsServer for this Windows server layout. An INI file alone may not contain the map, ports, mods and cluster launch arguments.

3. Review before importing

  1. Click Review selected server.
  2. Check the installation path, map, session name, ports, mods and any inspection notes.
  3. Correct missing details using the original launch script/configuration as your reference.
  4. Click Import reviewed server.

Step illustration

TBB ASA Server Manager settings screen, captured from the desktop application
After import: verify the existing installation’s map, identity and settings · Actual prototype 0.7.3 interface with sample data; final build may differ.

This screenshot shows the Settings page you should review after import; it is not a screenshot of the import dialog.

4. Check the result before first start

  1. Select the imported profile and inspect Settings, Mods, Network and Cluster.
  2. Confirm no second profile points at the same live installation.
  3. Keep the old launcher closed.
  4. Start through TBB and check the Console.
  5. Confirm the expected world and saves load, then stop normally.

Import leaves original files and saves in place. Starting or applying configuration later can write managed settings. Review first rather than assuming every other launcher stores settings in the same way.

5. If it finds nothing

Select the installation root rather than only a transfer folder or backup ZIP. Check that the ASA executable and directories actually exist on an accessible drive. Include the selected path and inspection notes in a private support report, with passwords removed.

Cluster folders and membership

Explore ASA Server Manager

View the project →