The FiveM framework landscape shifted through 2026: QBox, the community fork built on qbx_core and the ox ecosystem (ox_lib, oxmysql, ox_inventory), is now the standard recommendation for new roleplay servers, and it ships as a txAdmin recipe you can deploy in minutes. That leaves thousands of established QBCore servers asking the harder question: migrate a live city, or stay put?
Should You Migrate at All?
Honest answer first. Migrate if:
- Your server is early enough that your resource list is mostly standard qb- resources
- You are fighting QBCore bugs that QBox already fixed
- You want the ox stack's performance and actively maintained core
Stay on QBCore for now if:
- You run a large, heavily customized city with dozens of paid or custom resources
- Your scripts are deeply tied to QBCore internals rather than its public APIs
- Your city is stable and your player count is healthy, because a working city is worth more than a modern framework
A migration is a project, not an afternoon. Budget a weekend minimum and a staging server always.
What QBox's Compatibility Layer Covers
QBox ships a qb-core compatibility bridge, which is what makes migration realistic at all: most resources written against QBCore's exports keep working on qbx_core without edits. What the bridge covers well is the common export surface most shop, job, and interaction scripts use. What it cannot cover is resources that reach into QBCore's internals or rely on framework behavior that QBox deliberately changed. Every migration finds a handful of these, which is exactly what the staging phase is for.
Requirements Before You Start
- FXServer build 10731 or newer: QBox requires a current artifact, so update your server artifact first
- oxmysql 2.7 or newer: QBox standardizes on oxmysql for database access
- A full backup: database dump plus a complete copy of your resources folder and server.cfg, taken while the server is stopped so the dump is consistent
The Migration Path
- Stage it. Deploy the QBox txAdmin recipe on a second server instance (a temporary small plan works). This gives you a known-good QBox baseline to migrate onto, rather than performing surgery on your live city.
- Restore your database into staging. QBox reads QBCore's data structures for players, characters, and money through its compatibility handling. Verify a handful of real player accounts load with correct money, items, and job data before going further.
- Move resources over in groups. Start your custom and third-party resources in batches on staging, watching the console per batch. Resources that error against qbx_core go on a fix list: check whether the author ships a QBox-native version (many now do), whether the bridge just needs the resource restarted in the right order, or whether it needs a small export rename.
- Test the money paths hardest. Jobs, shops, inventories, and anything that touches player money are where silent breakage hurts most. Run each core loop of your city manually.
- Schedule the cutover. Announce a maintenance window, take a final fresh database dump from live, restore it onto the QBox instance, and swap. Keep the old QBCore instance intact and stopped for at least a week as your rollback path.
FAQ
Does migrating wipe my players' characters and money? No. Player data lives in your MySQL database, and the migration moves the database, not resets it. The risk is not data loss but resource incompatibility, which staging catches.
Do qb- scripts work on QBox? Most do, through the compatibility bridge. The exceptions are scripts that touch framework internals, and those are findable on a staging server in an evening.
Can I run QBox with my existing txAdmin? Yes, QBox is deployed and managed through txAdmin like any recipe. Our txAdmin setup guide covers the basics.
Which framework should a brand-new server pick in 2026? QBox, and our ESX vs QBCore vs QBox comparison covers why in depth.
Host It on Hardware That Keeps Up
Framework migrations are the moment servers also discover their hardware ceiling, since the ox stack's performance gains only show on a server that is not CPU-starved. FiveM hosting plans run on AMD Ryzen 9 hardware with NVMe SSD and DDoS protection on every tier, with a temporary second instance easy to add for your staging weekend.