Moving a Path of Titans community server from a home PC or another host to LOW.MS does not have to mean starting from scratch. If you have been running a PoT community server yourself, all your tuned config, registered players, and every dinosaur your community has raised are sitting in a handful of folders on your current machine. Copy those folders across to your LOW.MS server in the right places and everything comes back online exactly as it was: same rules, same characters, same progression. This guide walks through where those files live on a PoT server, how to get them onto your new LOW.MS box using the File Manager or SFTP, and the small handful of settings you need to re-check once the upload is done. If you have not ordered yet, you can set up Path of Titans server hosting with us first.
Where Path of Titans Saves Live on Your Server
On any PoT community server, everything that matters sits under a single folder: PathOfTitans\Saved\. Inside that folder there are two areas you care about.
The first is Config\. LOW.MS runs Path of Titans on Windows, so on your server this is PathOfTitans\Saved\Config\WindowsServer\. That folder holds Game.ini (server name, password, rules, rates and quest settings), GameUserSettings.ini (the mod list) and Commands.ini (admin roles and who holds them). These are plain text files and they carry every tweak you have made since you first started the server. If your old server ran on Linux, the same files sit in Config/LinuxServer/ on that machine. They are the same files either way, and on LOW.MS they go into Config\WindowsServer\, because that is the only folder our servers read. The message of the day, rules and player lists (MOTD.txt, Rules.txt, Bans.txt, Mutes.txt and Whitelist.txt) sit directly in PathOfTitans\Saved\.
The second is DatabaseCache\. This is where the local database stores player data. Accounts sit under DatabaseCache\Account\ as JSON files named by Alderon ID (for example 123456789.json), and each dinosaur character is saved as a separate JSON file under DatabaseCache\Character\. If you zip up DatabaseCache\ you have a complete backup of every player and every dinosaur on the server.
If your old host was using the Alderon remote database instead of a local one, your player data is not in DatabaseCache\: it is held by Alderon, keyed to your server token. In that case you only need to carry across your config files, and you should set **Database** to Remote in **Service Settings** on your LOW.MS server. If your old server was on a local database, leave **Database** on Local, which is the default. Player data does not move between the two modes, so get this one right before your players log in.
Before You Do Anything
Stop the old server before you copy anything. PoT writes to the database files while the server is live, and a copy taken mid-write can come across with half-finished character data. Shut the old server down, wait a few seconds, then start the copy.
On the LOW.MS side, provision your Path of Titans service at control.low.ms and let the first install finish. That gives you a clean PathOfTitans\Saved\ layout to drop your files into, and it confirms the server boots on a stock config before you overwrite anything. Once it is running cleanly, stop the service from the panel. Do not upload files to a running server.
One last thing worth doing: take a Cloud Backup of the freshly installed server before you change anything. If the upload goes sideways, Cloud Restore puts you back to a known-good state in a couple of minutes.
Uploading via File Manager
For most people, the panel's File Manager is the fastest way. Open your service at control.low.ms, click File Manager, and browse to PathOfTitans\Saved\.
Upload your config files into Config\WindowsServer\ and replace the versions already there. That applies whether they came out of WindowsServer or LinuxServer on your old machine. Then upload your DatabaseCache\ folder into PathOfTitans\Saved\ the same way. File Manager will ask before overwriting existing files; say yes.
The File Manager handles zip files natively, so if you compressed Saved.zip on your old box you can upload the single archive and extract it on the server. That is usually quicker than dragging thousands of individual character JSONs across a browser upload. If that archive came from a Linux server, it will extract a Config\LinuxServer\ folder: move the files inside it into Config\WindowsServer\, or the server will carry on running the stock config.
Uploading via SFTP
For larger worlds, anything with more than a few hundred characters in the database, SFTP is the saner choice. LOW.MS exposes SFTP on port 8822. Open your service page, grab the SFTP credentials, and connect with FileZilla, WinSCP, or the sftp CLI:
sftp -P 8822 your-username@your-server-hostname
Once connected, navigate to PathOfTitans/Saved/, upload your config files into Config/WindowsServer/, and upload your DatabaseCache/ folder alongside Config/. SFTP handles interrupted transfers cleanly, so if the connection drops halfway through a 40,000-file DatabaseCache/ upload, you can resume without starting over.
Pointing the Server at Your Config
With the files in place, open PathOfTitans\Saved\Config\WindowsServer\GameUserSettings.ini in the File Manager's editor and sanity-check it. If you had mods on the old server, they belong under the [PathOfTitans.Mods] section, one EnabledMods= line per mod, using the mod.io UGC ID:
[PathOfTitans.Mods]
EnabledMods="UGC_M_DYV7XYEGX2_SK"
That section name is what our template writes and what our servers read, so make sure every mod line from your old file sits under it. PoT pulls mods from mod.io at startup, so the IDs are what matters, not any files.
Your server name and join password are written into Game.ini from Service Settings, so set them there rather than relying on the values in the file you uploaded. Your slot count comes from your plan and is passed to the server on the launch line, so a MaxPlayers value carried over from your old config does nothing.
Your authentication token does not live in the config files either. Our panel writes it into the launch script as the AG_AUTH_TOKEN environment variable every time the server starts, taking it from the Auth Token field in Service Settings. Paste in the token you generated at alderongames.com/oauth/hosting-token and save. Reuse the token your old server was running on if you still have it: generating a new token revokes every previous token on that Alderon account, which will quietly break the old server's authentication.
Gotcha: all of these files, including Bans.txt and Whitelist.txt, are flagged in our panel to be rebuilt from our template. A reinstall will do it, and saving a change in Service Settings can do it. Your Service Settings values survive that; anything you uploaded or typed in yourself does not. Once the server is running the way you want, download a copy of your config and list files and keep them somewhere local, or open a ticket and ask us to bake your settings into the template. The Path of Titans Server Settings Guide covers this in more detail.
Starting Up
Start the server from the panel and watch the Web Console for the first minute. You want to see PoT load your map, mount the database, and complete its auth handshake with Alderon. Once startup finishes, join the server with your own client and check that your character is there, your quests are in the state you left them, and any mods you had configured are loaded.
If something looks off (missing characters, the wrong map, or the server not appearing in the community list), stop the server, Cloud Restore to the clean snapshot you took, and double-check the folder paths on your upload.
A Few Things to Know
Path of Titans pulls mods from mod.io at boot, so as long as the EnabledMods= lines under [PathOfTitans.Mods] in GameUserSettings.ini are correct, your LOW.MS server will download them on the first start. You do not need to upload the mod files yourself. Expect the first boot to take a little longer than usual while they come down.
Your Alderon auth token is tied to your hosting account, not to a specific machine, so the token from your old server is valid on LOW.MS. You just need to enter it once in Service Settings because the panel does not know about your old install.
Finally, a stock map does not live in any config file on our servers, so there is no SelectedMap or ServerMap line to carry over for one. The map is the first argument on the server's launch line, and you pick it in the panel: either one of the ready-made launch lines in Commandline Manager, each of which has its map baked in (Riparia is only available that way), or the Map dropdown in Service Settings, which only takes effect on the custom launch line. The Default launch line always boots Panjura, so if the server comes up on a different map from the one you chose in the dropdown, check which launch line it is using. A community map is the exception. Its mod ID goes in [PathOfTitans.Mods], and Alderon's documentation also asks for a ServerMap=MapName line under [/Script/PathOfTitans.IGameSession] in Game.ini, using the exact map name the mod specifies. Miss either one and the server will not load it, and your existing characters may be pinned to a map that is not running. That ServerMap= line is a hand edit, so the gotcha above applies to it: keep a local copy of Game.ini once it works.
Take a fresh Cloud Backup once the server has been live for an hour or so. That becomes your new baseline.