Before you start
You must administer the world, have access to its files and know the server and client versions. Allow storage for both the original and a working copy. Reading this article does not trigger an update or transfer on your service.
Record versions before scheduling the move
Record the build shown in server logs, where the world came from and the client versions. The 1.0 release and 21 October hotfix 1.0.0.3 are game announcements, not evidence that a host has installed them. Review recent notes and external tools before arranging downtime with the group. A newer client connecting successfully is not a substitute for checking the server build.
Create a consistent copy and retain the original
Tell players when the session ends and stop writes before copying the world. Identify the actual files through your configuration rather than assume one universal path. Keep the world and its settings together, labelled with a date and source version. Download an independent copy and check that the files are present and readable. Use a duplicate for the migration, leaving the original untouched.
Understand what conversion does and does not promise
Keen’s launch FAQ provides for conversion of Early Access saves to a more efficient format. That does not establish that an older executable can read a converted file. Hotfix 1.0.0.3 addresses particular migration and multiplayer loading problems. It does not guarantee recovery of every world, so a pre-conversion backup remains essential even after a successful first load.
Inspect the world before inviting everyone back
Load the copy and review errors without repeatedly interrupting the process. Join with an administrator using a compatible client. Inspect your base, important constructions, world features and relevant progress. Perform a normal stop and restart to check persistence. Review tools and mods separately: one successful connection does not validate every extension or prove that every area of a large world is intact.
Separate persistence, resources and platform support
A persistent world is available while the server runs and is reachable, without relying on one player’s PC. Large builds and Sparkworks can change CPU, memory and save-size demands. Observe the real workload rather than infer a guaranteed player count from RAM. The 13 October FAQ excludes crossplay at launch; do not plan a shared PC/PS5 server without a subsequent official confirmation.
Keep a documented recovery path
Do not replace the original with the converted world. Retain useful logs, the time and the build that produced the error. Where rollback is possible, restore a compatible executable and the matching pre-conversion files together. Replacing only part of the data can create an inconsistent state. Give support the relevant versions and symptoms without passwords or unnecessary personal information.
For your situation
| Situation | Next check |
|---|---|
| Continuing an Early Access world | Retain an independent original and test a duplicate against the confirmed target build. |
| Conversion fails | Keep the initial copy and logs; review the hotfix covering the symptom before another attempt. |
| Your group includes PC and PS5 | Do not assume crossplay. Check for a newer official announcement after the launch FAQ. |
Official sources
These documents describe the relevant protocols and software. Your service terms and configuration still need to be checked.