This article provides general preparation guidance. Final service recommendations depend on the actual software, data, licensing, integrations, and operating requirements involved.
Create a clean copy of the server data
Collect the server-data directory, resource folders, server configuration files, permission configuration, and any framework-specific files. Remove temporary caches and do not include unrelated backups inside the migration archive.
Export the database safely
Create a current SQL export and verify that it can be opened before the move. Record the database name and required character set, but never place live passwords or private connection strings inside a public quote request.
Document external dependencies
List Discord bots, webhooks, APIs, Tebex connections, license systems, voice resources, and any scripts that require IP changes or domain updates.
Remember the Cfx.re player-slot rule
Hosting resources can be sized around your expected population, but the actual player-slot limit is controlled by the active Cfx.re subscription or license connected to the server.
Never place passwords, private tokens, recovery codes, API keys, database credentials, or license keys into a public form or unverified message.