How to Move an ARK Server to a New Host
Moving an ARK server — tames, structures, characters and all — to a new host is just a careful file copy. This guide covers migrating without losing your save or cluster, matching ASA/ASE and mods, and cutting over with minimal downtime.
An ARK server's world lives in its save folder (the .ark map save plus player/tribe data under Saved/SavedArks/), configured by GameUserSettings.ini and Game.ini, with your mod IDs. Copy those to a new host, match Survival Ascended vs Evolved and the same mods, update the IP, and your dinos and bases come with you. Clusters need the same steps per map plus the shared cluster data.
Below is the process. Moving to us? Our ARK hosting (ASA & ASE) dedicates the RAM ARK needs with mod and cluster support — often the reason people leave an underpowered host.
What you'll need
A quick checklist before you begin — have these ready and the rest is easy.
- Access to the old server's files (File Manager or SFTP).
- A backup: SavedArks folder, GameUserSettings.ini, Game.ini.
- Your mod IDs and whether it's ASA or ASE.
- A new host running the same game with enough RAM.
- The shared cluster directory too, if you run a cluster.
Migrate your ARK server, step by step
Back up the save & configs
Stop the server, then download the SavedArks folder (the .ark map save, plus player .arkprofile and tribe files), and your GameUserSettings.ini and Game.ini. This is your whole world and its rates.
Saved/SavedArks/ (map .ark + .arkprofile + tribe data) GameUserSettings.ini Game.ini
Note your mods (and ASA vs ASE)
List your mod IDs (Workshop for ASE, CurseForge for ASA) and confirm whether you're on Survival Ascended (app 2430930) or Survival Evolved (376030). The new host must run the same one — a save from one won't load on the other.
Install the same version & mods on the new host
Set up ARK (ASA or ASE to match), add the same mod IDs so they download, and let it generate the default config once. A mod or version mismatch is the top cause of a save failing to load.
Upload the save & configs
Stop the new server, then upload your SavedArks folder and both .ini files over the defaults via File Manager or SFTP. Keep the map name the same so the save is loaded.
Update the IP (and cluster data if any)
The new server has a new IP:port. Share it with players. Running a cluster? Repeat the save/config copy for each map and copy the shared cluster directory so cross-server transfers keep working.
Test, then cancel the old host
Start the server, confirm the map, tames, structures, characters and rates all loaded, and have someone connect. Only cancel the old host once confirmed — keep the backup for several days (ARK saves are precious).
Tames and bases intact
ASA and ASE saves aren't interchangeable
A Survival Ascended save won't load on Evolved (or vice versa). Match the exact game on the new host before uploading.
Stop before copying the save
ARK writes to the save on a timer. Stop the server on both ends before backing up or uploading so you don't grab a half-written .ark.
Clusters = per-map + shared data
For a cluster, migrate each map's save/config and copy the shared cluster directory, so character and dino transfers keep working.
Keep the backup for days
ARK saves represent a lot of hours. Don't delete the old host or backup until you're certain everything transferred.
Common problems & fixes
Hit a snag? These are the issues people run into most — and how to solve them.
The save won't load on the new host
Version/mod mismatch or a changed map name. Match ASA/ASE and the exact mods, keep the map name, and re-upload SavedArks.
My cluster transfers stopped working
The shared cluster directory didn't come across, or the maps point at different directories. Copy it and point every map at the same one.
Tames or structures are missing
The SavedArks folder was incomplete. Re-copy the whole folder (map .ark plus .arkprofile and tribe files) from the old backup.
I moved because of lag and it's still slow
ARK needs a lot of RAM and a strong core. Make sure the new plan actually dedicates 12-16 GB+ and a fast CPU — see our ARK cost guide to size it.
Skip the setup — host it with ESAGAMES
Moving your ARK server to us? Our ARK hosting (ASA & ASE) dedicates the RAM and CPU ARK needs, with mod and cluster support, File access and DDoS protection — and support that helps you migrate.
Frequently asked questions
Can I move my ARK server to a new host without losing my tames?
Yes. Stop the server, copy the SavedArks folder (map save, player .arkprofile and tribe data) plus GameUserSettings.ini and Game.ini, install the same game (ASA or ASE) and mods on the new host, and upload the save. Your tames, structures and characters come with it.
How do I transfer an ARK save to a new server?
Download the SavedArks folder and your two .ini files from the old host with the server stopped, then upload them to the new host running the same version and mods, keeping the map name the same so the save loads.
Can I move an ASE save to an ASA server (or vice versa)?
No — Survival Ascended and Survival Evolved saves aren't interchangeable. You must migrate to the same game the save came from. Match ASA or ASE on the new host before uploading.
How do I migrate an ARK cluster?
Do the save/config copy for each map in the cluster, and also copy the shared cluster directory (the cross-server transfer data). Give each map its ports on the new host and point them at the same cluster directory.
Why won't my ARK save load after migrating?
Usually a version or mod mismatch, or the map name changed. Match ASA/ASE and the exact mod IDs, keep the same map name, and re-upload the SavedArks folder.
Do players need anything after I move the ARK server?
Just the new IP:port to connect. Their characters live in the save you migrated, so once they join the new address, everything is as they left it.
Keep reading
ARK: Survival Ascended and ARK: Survival Evolved are trademarks of Studio Wildcard. ESAGAMES is an independent hosting provider, not affiliated with or endorsed by Studio Wildcard.
