Ship

Installing on your server

Unzip the folder into resources, install the dependencies the preview named, replace the old resource and ensure the new one.

Download the zip

Download at the top right of a Framework Converter result saves the converted resource as one zip, named after the resource and the target, for example esx_shops-qbcore.zip.

The header of a finished conversion: esx_shops, ESX to QBCore, 9 files, and the Download button on the right.

Unlike the upload, the zip holds the resource folder itself. The esx_shops run unpacks like this:

esx_shops/CONVERSION_REPORT.md
esx_shops/LICENSE
esx_shops/README.md
esx_shops/client/main.lua
esx_shops/config.lua
esx_shops/fxmanifest.lua
esx_shops/locales/de.lua
esx_shops/locales/en.lua
esx_shops/locales/fr.lua
esx_shops/server/main.lua

For a large resource the browser builds the zip before the save dialog opens, which can take several seconds. Click Download once and wait.

Install the resource

1
Take out the old version
The converted folder has the same name as the original. Stop the old resource and move its folder out of resources, or keep a backup elsewhere. Two folders with one name cannot both run.
2
Unzip into resources
Unzip so the resource folder lands in your resources, for example resources/[local]/esx_shops. fxmanifest.lua must sit directly in that folder.
3
Check the start order in server.cfg
The folder name is unchanged, so the existing ensure line still works. It must come after the framework and the resources the converted version needs:
```
ensure qb-core
ensure qb-inventory
ensure qb-menu

ensure esx_shops
```

Note

The resource keeps its name and its event names, such as esx_shops:buyItem. Other resources that trigger those events keep working. Rename the folder only if you also update everything that refers to it.

New dependencies

A converted resource often needs resources the original did not. The preview lists them under Resources you will need, and the new fxmanifest.lua declares them:

dependencies {
    'qb-core',
    'qb-inventory',
    'qb-menu',
}

Install every listed resource and start it before the converted one.
Search the converted files for exports[. Every name in there is a resource that has to run on your server, including helpers such as an input dialog that the manifest may not list.
On Qbox and ox_core targets, ox_lib and ox_inventory are the usual additions.

Database, items and locales

The code changes framework; your server data does not change with it. Check these three:

Items. Item names stay the same, so each item must exist in the item list of the target, for example qb-core/shared/items.lua on QBCore or ox_inventory/data/items.lua on Qbox and ox_core.
Money accounts. Frameworks name accounts differently. ESX money became QBCore cash in the esx_shops run. The decisions in the report list each account mapping.
SQL files. They are carried over as they are. If they create or change tables of the old framework, adapt them to the target's tables before importing.
Locales. Locale files are rewritten, so your own edits to them are replaced. Keep a copy of edited locales and carry your text over.

Start and test it

Start it on a test server first. Restart the server, or load it from the server console:

refresh
ensure esx_shops

Server console or txAdmin: errors from server files and missing dependencies.
F8 console in game: errors from client files.
Every feature once: each command, menu, purchase and job action the resource has. The checks cannot run these for you.

When something fails, open the result again and read the findings for that file, then see Errors on the server.