Skip to content
Rust guide

Migrate a Rust server

Move a Rust community without gambling wipe progress. Copy cold files, verify plugins, then cut traffic.

Updated September 2026Vendor-neutralNo fake benchmarks
Back up the instance and stop the server before changing configuration, mods or wipe scripts.

Inventory first

Note server identity name, map/seed/size, ports, RCON password, Oxide/Carbon presence, and any custom assemblies. Export a plugin list.

Cold copy

Stop the old server. Archive the identity folder, framework data directories, and config files. Transfer with SFTP or similar. Keep the old archive untouched as rollback.

Bring up the new host

Install matching Rust dedicated server build. Restore files into the expected paths. Install the same plugin framework version family you tested. Do not mix random plugin DLLs from different eras without a staging test.

Config pass

Update IP binds, ports, and any absolute paths. Confirm RCON. Start once with a temporary name if you want a quiet test.

Cutover

Point DNS or share the new IP. Keep the old server offline (not both writable). Watch joins and console errors for the first peak.

Rollback

If the new host fails, stop it and restore the old archive to the previous machine. That only works if you kept a cold copy.

Related: Migration wizard · Rust hosting

Plan calculator · Migration wizard · Free trial

Prefer managed hosting in Germany?

Monolith runs game servers on a verified Ryzen 9 9950X production node with panel, SFTP and scheduled backups.

View Rust hosting
Already used Monolith?

Share an honest review to help other server owners.

Review us on Trustpilot

Still stuck after the guide?

These walkthroughs are written to help you succeed on your own. If something still blocks you, open a billing ticket and we will help from there.