How to Move a Rust Server to a New Host
Fed up with a laggy or attack-prone Rust host? Switching is straightforward — your server is files. This guide covers migrating a Rust server to a new host without losing your map, blueprints, players or plugins, ideally timed around a wipe for a clean cutover.
A Rust server's state — the map save, player and blueprint data, your server.cfg, and your Oxide/uMod or Carbon plugins with their configs — all live in files you can copy. Move them to a new host, match the Rust version, update the IP, and you're running. Many admins simply migrate on wipe day, which sidesteps carrying the map over entirely.
Below is the process. Moving to us? Our Rust hosting runs fast dedicated cores with Layer-4 DDoS protection and one-click wipes — often the reason people switch.
What you'll need
A quick checklist before you begin — have these ready and the rest is easy.
- Access to the old server's files (File Manager or SFTP).
- A backup: server.cfg, identity/save folder, oxide/carbon folder.
- The same Rust version and modding framework on the new host.
- A new host with fast CPU and DDoS protection (why most switch).
- The new IP:port to share with your community.
Migrate your Rust server, step by step
Decide: carry the map or migrate on wipe
The easiest Rust migration is on wipe day — you don't need the old map, just your configs and plugins. If you want to keep the current map and progress, you'll copy the save too. Pick this first; it shapes the rest.
Back up from the old host
Stop the server, then download your server.cfg, the identity/save folder (the map, player and blueprint data under server/<identity>/), and your oxide/ or carbon/ folder (plugins + config + data + lang).
server.cfg server// (map + player + blueprint data) oxide/ (or carbon/) plugins, config, data, lang
Match the version & framework
On the new host, install Rust and the same modding framework (Oxide/uMod or Carbon) you were running. A framework or version mismatch is the main cause of plugins failing after a move, so line this up before uploading.
Upload your files
Stop the new server, then upload server.cfg, the identity/save folder (only if keeping the map) and your oxide/carbon folder over the defaults, via File Manager or SFTP. Keep the same identity name so the save is found.
Update the connect IP
The new server has a new IP:port. Share it with your community (client.connect IP:port via F1), update it on your Discord/website and any server-list listing, and set your server.cfg hostname if it changed.
client.connect:28015
Test, then cancel the old host
Start the new server, confirm the map/blueprints, plugins and player data loaded, and have someone connect. Only cancel the old host once confirmed — keep its backup until after the next wipe.
Clean cutover, nothing lost
Migrate on wipe day if you can
The simplest Rust move is at a wipe — you only carry configs and plugins, not the map. Time the switch to your wipe schedule for a clean cutover.
Match Oxide/Carbon exactly
Plugins break if the framework differs. Install the same Oxide/uMod or Carbon version on the new host before uploading your oxide/carbon folder.
Stop before copying the save
A running server writes to the save constantly. Stop it on both ends before backing up or uploading, or the map data can corrupt.
Switching for DDoS? Confirm protection
Many admins move because their old host got attacked. Make sure the new host includes Layer-4 protection — for Rust it's essential, not optional.
Common problems & fixes
Hit a snag? These are the issues people run into most — and how to solve them.
The map didn't carry over
The identity/save folder wasn't copied, or the identity name differs. Copy server/
Plugins error after the move
Framework/version mismatch. Match Oxide/uMod or Carbon and the Rust build, then re-upload the oxide/carbon folder.
Players can't connect
They're on the old IP. Share the new IP:port and update your Discord/website and server listing.
I switched because of DDoS but it happened again
The new host needs real Layer-4 protection. Confirm it's included — for Rust, protection is essential.
Skip the setup — host it with ESAGAMES
Switching your Rust server to us? Our Rust hosting runs fast dedicated cores with Layer-4 DDoS protection, one-click wipes and easy file access — Frankfurt, and our support helps you migrate.
Frequently asked questions
Can I move my Rust server to a new host without losing the map?
Yes — stop the server, copy the identity/save folder (map, player and blueprint data), your server.cfg and your oxide/carbon folder, then upload them to the new host running the same version and framework. Keep the same identity name so the save is found. Many admins instead migrate on wipe day and skip carrying the map.
How do I transfer my Rust plugins to a new host?
Copy the whole oxide/ (or carbon/) folder — plugins, config, data and lang — to the new server, and make sure it runs the same framework (Oxide/uMod or Carbon) and Rust version so the plugins load.
When is the best time to migrate a Rust server?
On wipe day. You don't need to carry the old map — just your server.cfg and plugins — so it's the cleanest, lowest-risk time to switch hosts.
Will my players keep their blueprints and progress after moving hosts?
If you copy the identity/save folder (which holds player and blueprint data) and keep the same identity name, yes. If you migrate on a wipe, everything resets anyway, so it doesn't matter.
Why did my Rust plugins stop working after migrating?
Almost always a framework or version mismatch. Install the same Oxide/uMod or Carbon version and the same Rust build on the new host, then re-upload your oxide/carbon folder.
How do players connect after I move the Rust server?
Share the new IP:port — they can use client.connect
Keep reading
Rust is a trademark of Facepunch Studios. ESAGAMES is an independent hosting provider, not affiliated with or endorsed by Facepunch.
