How to Migrate Your Rust Server to a New Host Without Losing Data

Switching Rust hosting providers doesn't mean starting over. Your world, player data, blueprints, and plugin configurations can all be transferred. Here's the process.

What to Transfer

Essential Files

• server/RustDedicated_Data/ - Server binaries (usually freshly installed on new host)
• Map file: *.sav and *.sav.1 (your world save)
• *.map file (procedural or custom map data)
• *.db files (player blueprints and data)
• cfg/ directory (server configuration)

Oxide/uMod Files

• oxide/config/ - All plugin configurations
• oxide/data/ - Plugin data files (economy balances, homes, warps)
• oxide/plugins/ - All plugin .cs files
• oxide/lang/ - Custom language files

Other Important Files

• server.cfg or startup parameters
• Ban lists
• Whitelist

Migration Steps

Step 1: Prepare

1. Announce maintenance to your community
2. Ensure a fresh backup exists
3. Note your current startup parameters

Step 2: Download from Old Host

1. Connect via FTP to your current server
2. Download the entire server directory (or at minimum, the files listed above)
3. Verify file integrity - check that .sav files aren't truncated

Step 3: Set Up New Host

1. Install Rust Dedicated Server on the new host
2. Install Oxide if needed
3. Verify the server starts cleanly with default settings

Step 4: Upload to New Host

1. Stop the server on the new host
2. Upload your saved files to the matching directories:
   • World saves go to the server root
   • Oxide files go to oxide/
   • Configs go to their respective locations
3. Upload your server.cfg

Step 5: Configure Startup

Set your startup parameters to match the old server:

• Same world size
• Same seed (or point to your custom map)
• Same Oxide flags
• Same networking settings

Step 6: Test

1. Start the server
2. Connect as admin
3. Verify:
   • World loads correctly (buildings exist)
   • Player blueprints are intact
   • Plugin configurations work
   • Economy balances are correct
   • Homes and warps work

Step 7: DNS/Announcement

1. Update your connection info
2. Announce the new IP to your community
3. Update server lists
4. Monitor for issues in the first 24 hours

Timing the Switch

Best time: During a scheduled wipe. Migrate between the old server going down and the new one going up. Players won't notice the hosting change behind a fresh wipe.

Mid-wipe migration: Possible but riskier. Any data corruption during transfer affects the live world. Test thoroughly before announcing.

Common Problems

Players lost their blueprints: The *.db files weren't transferred correctly. Check that player database files exist and aren't empty.

Plugin data missing: The oxide/data/ directory wasn't fully transferred. Re-download and upload.

Map looks different: The server is generating a new procedural map instead of loading your save. Verify server.levelurl or seed matches, and that .sav files are in the correct location.

Performance is different: Different hardware performs differently. If you're migrating to Space-Node, the Ryzen 9 7950X3D should provide better performance than most alternatives.

Avoid Common Mistakes

• Don't run both servers simultaneously with the same map - this can cause player data conflicts
• Don't skip testing - 10 minutes of verification prevents hours of community complaints
• Keep old server files for 30 days - in case something was missed during transfer
• Communicate clearly - players are surprisingly understanding about migrations when given advance notice