01 Can you transfer your Palworld server to another hosting site?
Usually yes, if you can export the relevant files and the destination runs a compatible server. Moving an existing dedicated server is not automatically the same as converting a co-op world or switching player identity formats. Preserve the original files and match the destination’s instructions to your exact source setup.
The safe order is export, verify the archive, restore into an isolated destination, test the characters, then cancel. Do not cancel first and assume the old provider will keep files available. We found no single retention promise that applies to every Apex or BisectHosting cancellation, so ask about your service’s cutoff while it is still active.
02 Which files should you download before cancelling Apex?
Prefer a complete copy of Pal/Saved/ plus your startup configuration, build record and mod inventory. Where a panel will not export that whole tree, export the complete active world folder and the relevant configuration tree separately. Do not download just one Level.sav and assume the job is finished.
| Keep | Why it matters |
|---|---|
Pal/Saved/SaveGames/0/<WorldID>/, including Players, Level.sav, LevelMeta.sav and other files present | Preserves the world and associated player data as one consistent set. |
Pal/Saved/Config/LinuxServer/ or WindowsServer/ | Keeps the active configuration, including world-selection information. |
| Existing backup folders | Provides earlier recovery points if the latest save is already damaged. |
| Mod files or an exact reinstall manifest, startup settings and build | Helps reproduce the environment instead of guessing after cancellation. |
Apex’s world-transfer instructions ↗ identify the SaveGames/0 location and DedicatedServerName in GameUserSettings.ini. Its panel setup guide ↗ describes Backups under File Management. Use the current panel to export; if the web download cannot handle the full world, use its supported file-transfer method. Config files can contain passwords: store this archive privately.
03 How to save and export a BisectHosting Palworld server
- Tell players the maintenance time. Save through the supported server controls, then stop cleanly and wait until the process has ended.
- In the Starbase file manager, locate the active world under the panel’s Pal/Saved tree. BisectHosting’s player-save guide uses
/home/Pal/Saved/SaveGames/0; panel-relative paths may display differently. - Download the full world directory or an archive of it, plus the active Config directory. Include all world files, not only Players.
- Open the downloaded archive locally. Confirm the expected WorldID, file inventory and a plausible modification time.
- Keep one untouched source copy and a separate working copy for the destination.
The path is documented in BisectHosting’s save-repair guide ↗; its transfer guide ↗ addresses importing to BisectHosting. We are using those references to locate data, not claiming its import instructions are a universal procedure for leaving every host. If permissions prevent a complete export, ask support before ending the subscription.
04 Restore the world without creating a nested-folder mistake
Create a separate destination instance and stop it before uploading. Extract the world so its actual data sits inside SaveGames/0/<WorldID>/, not inside an additional archive-name folder. Use the destination’s matching configuration directory. Hostinger’s official import guide ↗ explains matching DedicatedServerName to the copied world folder.
Keep source and destination on compatible builds. Do not casually open a newer save in an older server, and do not replace the destination’s complete configuration with an old version’s defaults. Record any settings you intentionally carry over. If the destination generates an empty world, stop and inspect the path and selected WorldID rather than overwriting the original archive.
05 The world is right, but a player is asked to create a character
That symptom can indicate a player-identity mapping issue rather than a missing world. BisectHosting documents a cross-environment save-repair workflow; co-op-to-dedicated migration can also need a version-compatible conversion. A host-to-host copy should not automatically trigger an untested converter.
First verify the complete Players directory and correct world. If conversion is actually needed, use the destination’s current instructions, keep untouched copies and test on a duplicate. Do not upload private world archives to an unfamiliar conversion site without understanding what is sent. An account change, OS change and server-version change are separate variables; record each one so support can identify the right fix.
06 The cancellation gate: five checks before you leave
- A known base and its stored items are present.
- Each regular player can access the expected character and guild.
- Platforms that worked before, including any PS5 members, can still join.
- A new saved change survives a clean destination restart.
- The source archive remains readable on storage outside both hosting accounts.
Once all five pass, record the migration time and cancel according to the old service’s billing rules. Keep the old world copy instead of treating cancellation as a backup strategy. If the only issue is joining the destination, follow the platform connection guide before attempting destructive save repairs.