Moving your Rust server to another hosting provider doesn't mean losing your map, player bases, blueprints, or plugins. Whether you're currently self-hosting on your PC or switching hosting providers, you can transfer your existing files without starting over.

The process involves backing up your server data, uploading it to your new Rust server, and making sure everything loads correctly.

This guide covers transferring from self-hosting to dedicated hosting, switching between providers, and migrating your server to Pine Hosting.

What Files Do You Need To Transfer A Rust Server?

Rust stores important server data inside a directory determined by your server identity.

For example, a server using the identity rustserver typically stores its files in:

server/rustserver/

The most important files include:

  • .sav files contain saved map progress, including player bases, buildings, and deployed entities.
  • .map files contain map terrain and monuments.
  • player.blueprints.*.db files store learned player blueprints.
  • Other .db files contain additional player information.
  • cfg/ contains server configurations, administrators, and bans.
  • sv.files.*.db files store player-created signs and other image data.

If you're using Oxide or Carbon, you'll also need your plugin folders, configurations, permissions, and saved data.

Copying the complete server identity directory is generally safer than transferring individual files.

What To Do Before Migrating Your Rust Server

Before transferring your Rust server, make sure you:

  • Stop your existing server before copying its files.
  • Create a complete backup of your map, player data, configurations, and plugins.
  • Record your server identity, map seed, map size, and custom map settings.
  • Confirm your new hosting plan has sufficient RAM, CPU resources, and storage.

Having reliable Rust server backups is important, especially when transferring an established community.

You should also check that your existing map is compatible with the current Rust server version.

How To Check Your Rust Map Compatibility

Rust includes a protocol version number in its .sav filenames. This number changes during forced map wipes, preventing older saves from loading on updated servers.

To check compatibility:

  1. Start your new Rust server with a default Procedural Map.
  2. Allow it to generate and save the map, then stop the server.
  3. Open server/<server.identity>/ and locate the generated .sav file.
  4. Compare its protocol version with your existing server's save.

For example:

proceduralmap.4000.12345.289.sav

Here, 4000 is the map size, 12345 is the seed, and 289 is the protocol version.

If your original save uses the same protocol version, it passes this compatibility check. If it uses an older version, the map is outdated and cannot be loaded on the updated server.

You'll need a fresh map, although blueprint progress, compatible plugin data, and configurations may still be transferable.

How To Transfer A Self-Hosted Rust Server To Dedicated Hosting

If you're currently running Rust on your own PC or VPS, you can transfer your server files directly to a dedicated hosting provider.

Step 1: Locate Your Existing Server Files

Stop your self-hosted Rust server and open its installation directory.

On Windows, your server identity directory might look like:

C:\RustServer\server\rustserver\

Copy the entire identity folder, including your map, player databases, and configurations.

Also copy your Oxide or Carbon directories if you're running a modded server.

Step 2: Prepare Your New Hosted Server

Purchase a Rust hosting plan and access your provider's game panel.

Start the server once to generate its directories, then stop it before uploading your existing files.

Configure the server identity, map seed, and map size to match your previous server. For custom maps, preserve the appropriate map configuration.

Avoid changing your Rust map seed or size, as different settings can cause a new map to generate.

Step 3: Upload Your Rust Server Files

Most hosting providers offer a File Manager or SFTP access for uploading server files.

  1. Connect to your new server using its File Manager or an SFTP client such as FileZilla.
  2. Locate the active server/<server.identity>/ directory.
  3. Back up the destination's existing files before replacing them with your saved data.
  4. Upload your original server identity files.
  5. Restore your plugin directories if applicable, and ensure the correct modding framework is installed.

Once completed, start your server and confirm that your map, bases, and player progress have transferred correctly.

How To Transfer A Rust Server Between Hosting Providers

If you're moving from one Rust hosting provider to another, the process is similar. However, you'll download your existing files through your old provider's game panel rather than accessing them directly on your computer.

Step 1: Download Your Existing Server Files

Log into your current hosting provider's game panel and stop your Rust server.

Use its File Manager or SFTP connection to download the complete server identity directory, along with any Oxide or Carbon plugin data.

Step 2: Prepare Your New Hosting Server

Log into your new hosting provider's game panel.

Make sure the server has generated its default directories and is stopped before uploading anything.

Check that your server identity, map settings, and modding framework match your previous configuration.

Step 3: Upload And Restore Your Files

Using your new provider's File Manager or SFTP connection, upload your saved Rust files into the correct directories.

Make sure you preserve the original map and player data rather than overwriting them with the destination server's newly generated files.

Start your new Rust server and verify that your map, blueprints, and plugins work correctly.

How To Transfer Your Rust Server To Pine Hosting

Whether you're moving from self-hosting or switching providers, Pine Hosting offers three ways to transfer your existing Rust server.

Our Rust hosting includes a built-in Server Transfer feature, SFTP access, and free migration assistance.

Method 1: Use Pine Hosting's Server Transfer Feature

Our Server Transfer feature allows you to migrate directly through our game panel without manually downloading and reuploading your entire server.

  1. Log into our game panel and select your Rust server.
  2. Stop the server and open the Server Transfer feature.
  3. Enter the required connection information from your previous host.
  4. Follow the interface to initiate the transfer.
  5. Once completed, verify your transferred files and start your server.

This method is particularly convenient when switching from another provider with remote file access.

Method 2: Transfer Your Rust Server Using SFTP

If you're migrating from a self-hosted machine or prefer manual transfers, you can use SFTP.

Open the Settings tab in our game panel to find your SFTP connection information.

Connect using FileZilla or WinSCP, then upload your existing map, player data, and configurations to the appropriate directories.

You can also restore your Rust server plugins and select the appropriate Oxide or Carbon framework through the Startup tab.

Once everything is uploaded, start your server and check that your progress is intact.

Method 3: Let Pine Hosting Handle Your Migration

If you'd rather not transfer your files yourself, our support team can help.

We offer free server migration for customers moving from another hosting provider.

Simply open a support ticket through our website or Discord and provide your previous host's connection details, your server files, or temporary panel access securely through support.

If you're currently self-hosting, you can also contact our team to arrange how to provide your existing server files.

Common Problems After Migrating A Rust Server

Your Server Generates A New Map

Check that your .sav files are in the correct directory and that your server identity, map seed, and size match your original configuration. An incompatible protocol version can also prevent an older save from loading.

Players Lose Their Blueprints

Verify that your player.blueprints.*.db files transferred correctly. Blueprints are stored separately from your map save.

Plugins Aren't Working

Ensure the correct Oxide or Carbon framework is installed and that your plugin configurations and saved data were transferred. Some plugins may also require updates.

Players Cannot Connect

Your server IP and port will usually change after migration. Share the new connection details and ensure your Rust server is updated to a compatible version.

Move Your Rust Server To Pine Hosting

Transferring your Rust server doesn't have to mean losing your map, player progress, or plugins. Whether you're moving from self-hosting or another provider, the right files and configuration will allow your community to continue playing.

With Rust server hosting from Pine Hosting, you get powerful hardware, an easy-to-use game panel, backups, and convenient migration tools.

Use our Server Transfer feature, upload your files through SFTP, or let our support team assist with your migration for free.