Move Between Palworld Hosts: A Cutover Checklist

Moving a Palworld dedicated server between hosts should preserve world and player progress while creating one clear destination for future play. Keep the old and new instances from becoming competing live worlds.

This checklist covers a dedicated-server move. A local co-op conversion can involve additional character-mapping work.

Prepare the export

Record the source build, server environment, configuration, and mods. Confirm you can download the complete save, not only one world file.

Stop the source cleanly before the final export. Keep an untouched archive and verify that it opens before changing the destination.

For path and transfer distinctions, follow EZ Game Host's world-transfer guide.

Match the destination

Install a compatible build and supported mod environment. Upload the complete data to the destination's documented location, then point the instance at the intended world.

Do not assume the first directory in a file browser is the active save. Use configuration, timestamps, and recognizable world data together to identify it.

Validate before reopening

Check several characters, guild membership, bases, storage, and progress. Restart the destination and verify a small new change persists.

Keep the source stopped. Share the new connection details only after the test succeeds, and retain the old export until a normal play session is complete.

Can I upgrade the game during migration?

Keeping versions stable makes the transfer easier to verify. Plan an update as a separate backed-up change.

Use the official server documentation for current operational requirements and safe updates for the later upgrade.

Choose your next step

Compare EZ Game Host Palworld hosting for your group. Choose resources for your actual world and workload, then keep a downloadable backup before changing hosts.