Romestead Move Server to Another PC: Transfer Saves and Config

Short answer: stop the old server, back up saves and config, install or copy the dedicated server on the new PC, install .NET 8 Runtime, restore the files, then test local launch before changing router UDP 8050 rules or inviting friends.

Move checklist

Tell players the server is going offline for migration.
Stop the Romestead dedicated server cleanly on the old PC.
Copy the world/save folder, config file, and any server settings into a dated backup folder.
Install the Romestead Dedicated Server on the new PC or validate files with SteamCMD App ID 4763510.
Install the .NET 8 Runtime on the new PC before testing launch.
Copy the backed-up save and config files into the matching location on the new setup.
Start the server locally and confirm the correct world loads.
Update firewall and router forwarding so UDP 8050 points to the new PC local IP.
Ask one friend to test direct connect before announcing the move is finished.

What must move

Item	Why it matters	Risk if skipped
World/save folder	Contains group progress	Server starts with a new or empty world.
Config file	Stores world name, password, port, player settings, or startup behavior	Wrong world, wrong password, or changed port.
Server files	Dedicated server executable and dependencies	Server cannot launch or uses mismatched files.
Runtime	.NET 8 Runtime may be required for startup	Server opens and exits immediately.
Port rules	Friends connect to the new machine	Old PC still receives router traffic, or no one can join.

Moving to a VPS or managed host

The same logic applies when moving from a home PC to a VPS or managed host: preserve saves, preserve config, test restore, then update join details. The difference is that a VPS needs Linux, firewall, and backup comfort, while a managed host should provide a file manager, restart button, and backup download option.

Common migration mistakes

Copying server files but forgetting saves.
Copying saves but forgetting the config that points to the world.
Changing router forwarding to the wrong local IP.
Testing with friends before confirming the world loads locally.
Deleting the old server before the new one has been tested.

Related Romestead server guides

Start with the save backup guide, use config file location to find settings, fix startup with .NET 8 Runtime, repair downloads with SteamCMD App ID 4763510, and compare hosting options if the move is really about 24/7 uptime.