Importing & Migration

PalCommand can adopt an install you already have, and can migrate a co-op world onto a dedicated server. These are two different flows.

Importing an existing PalServer install

From the Dashboard, click Import. The dialog has a drop zone (“Click to choose a server folder”) and an Install path field with a Browse picker beside it. Either one opens the same native folder picker. Point it at an existing PalServer install directory; PalCommand adopts it in place and keeps its existing settings. Nothing is downloaded and nothing is reinstalled. An optional Name field overrides the name PalCommand would otherwise take from the folder.

Click Import. On success you get a report: how many settings were adopted from the existing install, any settings PalCommand had to force (for example, to avoid a port collision with another managed server), and warnings worth reading before you start it. If the import fails, the error shows as-is and the form stays open so you can fix the path and try again.

Migrating a co-op save to a dedicated server

Co-op saves that carry a WorldOption.sav file silently override the dedicated server’s PalWorldSettings.ini values. If PalCommand detects one on a server’s Settings tab, it shows a banner: “Your settings edits are being ignored. WorldOption.sav overrides this file”, with a Repair button (only enabled while the server is stopped).

To bring a co-op world onto a dedicated server, open the target server’s card overflow menu and choose Migrate co-op save… (only available while that server is stopped). The wizard has three steps:

1. Source: pick from co-op saves PalCommand found automatically, or enter a save directory manually if yours isn’t in the default location.
2. Preflight: a read-only plan: file count, size, and what will happen. If the co-op host’s character carries Palworld’s unfixed host-GUID bug (the host’s save migrates as a fixed placeholder ID, and logging in before it’s fixed can silently delete the host’s Pals), a warning panel explains it, links two known-working community tools, and requires an “I understand” toggle before Migrate is enabled. PalCommand does not rewrite save data itself to fix this. It flags it and gets out of the way.
3. Report: what actually happened: files copied, whether a WorldOption.sav was found and removed, and where the previous world (if any existed at the target) was backed up to.