Coming from another framework

01What Nova takes over

Nova is built on QBox and already provides the foundation of a city: the framework, the inventory, the phone, targeting, the in-game admin panel, kept up to date by us. A migration is therefore not about carrying your whole old server over, but about taking back what is yours: your unique scripts, their data, and the setup of your city.

On the server page, answer "Migrate from ESX, QBCore or other" to the question of the "Is my city ready?" list: the steps and suggested articles adapt. To compare frameworks before you start, read ESX vs QBCore vs QBox; for the details of the move, migrating from ESX or QBCore to QBox.

02Your QBCore and QBox scripts

A script written for QBox finds the core it expects. Many scripts written for QBCore go through the QBox compatibility bridge, on by default: it is the "Enable QB Bridge" setting of the Configuration screen, "QBox Framework" section. Leave it on as long as one of your scripts needs it.

Upload the scripts into resources/[client] from the Files screen, enable them in the "Resources" card, restart, then test them one by one in game. Most recent scripts load ox_lib: in their fxmanifest, the @ox_lib/init.lua line must be replaced with @nova_lib/shared/lib_init.lua (adding your own scripts covers the rest).

03Your ESX and alt:V scripts

A script written for ESX will not work without being adapted: its calls to the framework do not exist under QBox. Nova does not convert scripts; expect to rewrite the part that talks to the framework, while the script's own logic often carries over.

An alt:V server does not carry over as is: the FiveM API is different, and the layer that talks to the game gets rewritten. The guide migrate from alt:V to FiveM says what carries over, what gets rewritten, and in which order to go about it.

04What not to import

Import neither a whole framework nor its base resources: inventory, phone, targeting, HUD, character management. Nova already provides them, and two versions of the same resource get in each other's way even under different names. A folder named like a Nova framework resource cannot be enabled: the "Resources" card puts it under "To fix".

05Your data

Characters, inventories and vehicles are not converted automatically: Nova's database does not have the same shape as ESX's or QBCore's, and your players create their character again. Tell your community before opening.

Your own scripts' data does carry over. Export only their tables from the old server, then import the .sql file into the primary database: Databases, "Manage", then "Import a .sql file". It is the one read by scripts that go through oxmysql, as most do.

A full export of the old database will be refused: the file is read in full before running, and a single statement that names a Nova framework table (players, users, player_vehicles…) means nothing is applied. Once the import has started, the first statement in error stops it, and the ones before it stay applied. The file is limited to 10 MB and 50,000 statements; split a large export, and take a backup first (databases).

06Your city, and when something blocks you

Jobs, economy, items, properties and permissions are recreated in game with /admin, without touching a file; the guide configure a FiveM server in game tours it. If something blocks you, open a request from the server page: it attaches the server's status, and tell support you are migrating and from which framework.