
Rehearse an Oxide-to-Carbon migration before switching live
Make the first Carbon boot on a copy you can discard. Carbon documents a one-time migration, so use a fresh copy of the original if you need to repeat that first-boot test.
Write down what the new server must preserve
Record one consequential example of each kind of state. A rewards balance for a test player proves more about plugin data than a list of files. One staff action and the same action denied to a regular player give you a check on permissions.
Copy the stopped installation, including its world, framework files, plugin settings and state. Give the rehearsal its own ports and storage. Point plugins at test databases and disable live notifications and automated jobs before the first boot.
Follow Carbon’s prerequisites on the copy. Turn off any tool that reinstalls Oxide and restore the Rust files Oxide patched. Keep the old oxide folder on the copy for Carbon to import, and keep an untouched backup of the whole pre-switch setup.
Check the migrated paths and the scheduled jobs
After the test boot, check that old Oxide config files reached Carbon's configs folder and that the plugin, data, language and permissions material is present. Inspect the extension list if any plugin needs a DLL. Then run the player and staff checks from your notes.
Open the jobs you already run from outside the game. A job that calls an Oxide-prefixed command needs a Carbon equivalent or an intentionally configured alias. Test a harmless read first. Schedule the live move only after the rehearsal gives you the same answers where it counts.