
Move Rust plugin settings and player data to another server
Configuration controls how a plugin behaves. Data records what already happened, such as a player's reward balance. A successful startup on a new host only proves the plugin could load.
Choose what the move is supposed to carry
For a faithful move, list the plugin build, required libraries, settings, language files and stored data that your players need. Read the publisher's storage instructions. Data might live in a named subfolder or an external database.
For example, Better Chat keeps the chat group definitions in oxide/data/BetterChat.json and its messages under oxide/lang. If the goal is to preserve the existing chat format, write down the title and message color of a test player. If the goal also includes keeping the same people in the same groups, include the framework's group and membership data.
Copy after writes finish
Stop the source server cleanly so the plugin can finish saving. Move the documented files or database backup to the corresponding locations on the stopped destination. Keep the originals. Verify that the destination uses its own copy of storage before both servers can run at once.
On the destination, use the same supported plugin release. Give your test player the expected group if memberships were intentionally left behind, then send a message. If their title or color changed, check the chat group definitions. If the definitions are present, check the player's group membership.