Server operations
Move a FiveM server to another VPS
Migrate FXServer artifacts, txData, server resources and framework databases without losing accounts, permissions or player progress.
Moving only server.cfg is not a full server migration. The panel's admin records and moderation data live in txData; framework player progress commonly lives in a separate SQL database.
Inventory before the move
| Component | Verify / preserve |
|---|---|
| FXServer | Artifact type and build; OS/runtime requirements |
| txAdmin | Complete txData, including admin data and any required logs |
| Game data | server.cfg, included CFG files, custom resources and assets |
| Framework | Consistent SQL dump, DB users/privileges and compatible dependencies |
| External | DNS, Cfx Portal key, webhooks, secrets and third-party integrations |
Migration workflow
- Announce a maintenance window. Stop or pause joins so files and SQL snapshots remain consistent.
- Record current versions, active ports, folder layout and credentials in a private inventory.
- Stop processes writing to
txDataand server-data folders, or take a storage-level consistent snapshot. - Copy these three data sets separately: complete txData, server data/resources and a consistent framework database backup.
- Transfer them over a trusted encrypted channel, not via public file shares. Check file ownership and access rights at the destination.
- Install a compatible FXServer artifact on the destination; point
TXHOST_DATA_PATHto the restored txData location. Do not accidentally create a new blank admin database. - Restore SQL into the destination database; change the server-side connection to the new DB host without publishing the password.
- Test the destination on private/temporary ports with no production DNS change.
- Verify web admin login, permissions, server startup, test character persistence, resource loading and backups.
- Cut over DNS/firewall routes and monitor both server logs and player reports. Retain a rollback copy until validated.
Verify backup integrity
On Linux, you can record a checksum for a finished backup archive and compare it after transfer:
sha256sum /secure-backups/fivem-snapshot.tar.gzThis verifies transfer integrity, not whether the archive or database contents are consistent. Test restoring to a private environment before deleting the old server.
Avoid common losses
playersDB.jsonexport does not contain all txData, resources or SQL character data.- Multiple txAdmin instances must not write to the same txData directory.
- Container
localhostand remote DB hostnames differ; verify from the process network. - Rollback may need to restore both files and database state. Prevent both old and new servers from writing simultaneously.
See Backups & updates, v8 environment migration and port setup.
Source: txAdmin master backup implementation.