How to Transfer a Rust Server

Transferring a Rust server is useful if you’re changing hosting providers, moving to a new machine, or backing up your server with all player data, world saves, and configuration.

You can transfer your server using the Importer Tool, which offers a fast, automated transfer for moving to Cybrancee, or the Manual Mode via FTP/SFTP, which gives full control and works for any host.

Using the Cybrancee Importer Tool


1. Log In to Your Panel


2. Select the ‘Importer’ Tab

Cybrancee panel showing the Rust startup page with the importer tab outlined

3. Fill in the Import Settings

Fill in the fields with the FTP credentials from your source server.

  • Host: Enter the FTP host of your source server.
  • Port: Use the default/automatic port.
  • Username: FTP username of your source server.
  • Password: FTP password of your source server.
  • Source: Keep as / (do not change) if you want to import the entire server. If you only want to import specific folders or files, adjust this path to point to the folder containing the data you want to transfer.
  • Destination: Keep as / (do not change) to import everything into the root of your new server. If you’re only importing certain folders, you can change this to a specific directory on the destination server.
  • Mode: SFTP by default.

Test and Import:

1. Select the ‘Test’ button to verify the connection.
2. Once successful, select the ‘Import’ button to start transferring your source server.

Cybrancee import tab page with import setting form outlined

5. Confirm the Import

In the confirmation popup, select whether you want to wipe server files (recommended for a full installation of the source server). Then select the ‘Import’ button to proceed.

Cybrancee Importer tab page showing confirm import popup with 'Enable Wipe' and 'Import' buttons outlined

6. Start Your Server

Once the import is complete, start your Rust server and monitor the console to ensure everything loaded correctly.

Cybrancee panel Rust server controls, start button outlined

Manual Mode (via FTP/SFTP)


1. Prepare the Source Server

Before transferring, make sure your current server is ready:

Stop the server to ensure all files are saved and there’s no active writing.

Backup all files in your Rust server directory, including:

  • server folder
  • cfg folder (server configuration files)
  • oxide plugins (if installed)
  • Any custom maps or assets

Having a complete backup ensures that nothing is lost during the transfer.


2. Create a Backup

Before transferring, make sure you have a complete backup of your server — this is the data you’ll be moving to the new server.

If you’re not sure how to create a backup, see our guide How to Backup and Restore Your Rust Server.


3. Download the Backup

Once your backup is ready, download it to your local computer.

cybrancee backup tab with download button outlined

4. Connect via FTP/SFTP to the New Server

Use an FTP client like FileZilla to connect to your server.

If you need help setting up FTP, see our guide How to Connect to Pterodactyl Via SFTP.

FileZilla with connection details outlined

5. Upload Files to the New Server

  • Extract the downloaded backup file on your computer.
  • Upload all files and folders from your backup, maintaining the same folder structure.
  • Verify that all files, especially world saves (.sav) and configuration files, uploaded successfully.

Make sure the folder structure matches the original backup, as this is critical for the server to function correctly.


Option 1: Upload the Entire Backup

If you want to keep a full copy of your server exactly as it was:

  • Upload the entire backup folder to the root directory / on your new server via FTP.
  • This is the safest way to retain all data but can take longer depending on the size of your backup.
server connected via ftp with server root outlined

This method is the safest way to retain all data, but it can take longer depending on the size of your backup.


Option 2: Upload Only the Essential Folders

If you prefer a faster transfer and only need the critical data:

Upload the following folders and files to the new server:

  • World save files in server/rust (only required if you want to keep your current map).
    .map or .sav files.
  • Player data files in server/rust (only required if you want to keep player progress).
    Player Data .db files
    Player Blueprints player.blueprints files
  • Custom Emoji files located in server/rust, if you have custom emojis.
rust backup with sereveremoji folder and files outlined
  • cfg folder with configuration files from server/rust/cfg .
    server.cfg
    users.cfg
    bans.cfg
rust backup with cfg folder outlined
rust backup with files in cfg folder outlines
  • Plugins: oxide folder
rust backup with oxide folder outlined
  • Custom maps or assets you’ve added.

You can skip temporary files, old logs, or outdated backup snapshots to save time and space.

Tip: Make sure all essential files are correctly uploaded and maintain the original folder structure. This ensures your Rust server loads correctly on the new host.


6. Start the New Server

Start the Rust server and monitor the console for errors.

  • If you transferred the map and player data, check that everything is correct. The server should load the world, player data, and player blueprints as expected.
  • If you didn’t transfer the map or player data, check that the server has generated a new world correctly and that no previous player data has been carried over.
  • Ensure admins and moderators have been loaded properly from the users.cfg file.
  • Confirm that the settings from server.cfg are applied correctly.
  • Check that all plugins have loaded correctly by entering .plugins in the console (if you have any installed).
  • Make sure all server functionality is operating as intended.

Test connections and gameplay to confirm the transfer was successful.

Cybrancee panel Rust server controls, start button outlined

Rust Server Hosting

Starts at $11.99

External link icon

Was this article helpful?
Please Share Your Feedback
How Can We Improve This Article?
Table of Contents