Conan Exiles Enhanced: migrate a Legacy server

Confirm the group can move together

Check the edition used by every player. Funcom requires matching client and server versions; Enhanced availability on Steam does not mean every other platform runs that edition.

For Steam players remaining on Legacy, the official FAQ describes selecting Conan Exiles Legacy in the game's version and beta options. That selection must match the destination server. Do not move a mixed-platform group before checking everyone's available path.

Identify transferable world data

Exiled Lands has documented progression transfer covering characters and structures. The FAQ identifies the Legacy dedicated-server file as ConanSandbox/Saved/game.db.

Siptah needs a separate decision: its structures do not transfer in the same way. Enhanced does not provide a separate private Siptah map server as before; its setup uses an Exiled Lands server. Siptah content still requires the DLC. Do not promise an identical transfer of an old Siptah base.

Prepare a copy for conversion

Stop the source and archive all of ConanSandbox/Saved, configuration, mod files and load order. For Legacy Siptah, retain dlc_siptah.db as part of that archive. Preserve the environment and versions required for recovery.

Prepare a separate Enhanced-compatible destination. Follow Funcom's conversion procedure or the provider's confirmed workflow for your world. Do not improvise database renames. Converted files are distinct, and their format is not a straightforward downgrade to Legacy.

Validate before switching players

Check characters, clans, bases, storage and access rights. Test Enhanced-compatible mods at the intended versions, then complete a save-and-restart cycle. Have owners inspect important locations.

If conversion fails, retain originals and logs. Recovery uses the preserved Legacy backup with a compatible Legacy environment, rather than loading an Enhanced save directly into the old server.

Frequently asked questions