For: QBCore servers moving to Qbox  |  Includes: PDF guide, Windows and Python scanners, server check resource  |  Code: Open source  |  Version: 1.0.0 (checked against the Qbox docs for qbx_core 1.24.1)

Qbox Migration Kit: Move from QBCore to Qbox for FiveM

Tools that check your server for you, plus a companion guide. The Qbox team's official migration guide is free at docs.qbox.re/migrating and this kit follows it step by step.

What you get

• GZ Qbox Scan (Windows PowerShell, no install; Python version for Linux): reads your resources folder and sorts every resource into Replace, OK, Test carefully, Config, Port or Ask author, with the file and line of every finding.
• GZ Qbox Check (server resource): type qboxcheck in the console to check your FiveM server build, MariaDB version, table collations, QBCore resources that must not run next to Qbox, missing columns, orphaned vehicles, garages Qbox does not have, and whether every job converted.
• PDF guide: the official steps in order, with where each tool fits, a one-page checklist and a rollback plan.
• Sources: every step is linked to the official Qbox page it comes from.

Read-only

Nothing in the kit changes your files or database. You run the official SQL yourself, on a copy.

Scope

QBCore to Qbox. ESX code is flagged by the scanner, but there is no ESX data converter: moving from ESX is a manual port.

Tested

Both scanners gave identical results on a 112-resource QBCore 1.3.0 test server. The server check runs cleanly on QBCore 1.3.0 with MariaDB 12.2.

Support

Join our Discord for updates and support.