FiveM & GTA RPMigrating a FiveM server from Legacy to Enhanced
FiveM Legacy to Enhanced migration checklist: resource inventory, escrow scripts, stream_enhanced, recompiling C# for .NET, ESX and QBCore frameworks, assets and voice.
Porting a FiveM server from Legacy to Enhanced is not an artifact update: the server binary changes, the runtime moves from Mono to .NET, and part of your resources has to be adapted. This checklist walks the migration resource by resource, in the order problems actually show up.
⚙️ Requirements
- An Enhanced test server, separate from production - see running your server on the GTA V Enhanced build
- A full backup of your resources and a dump of your MySQL database
- The list of your paid scripts and the stores they came from
- Console access to the server, to read loading errors
Enhanced is in early access. Until your resource inventory is validated on a test instance, keep your players on Legacy: one critical resource that fails to load means an RP server standing still.
⚙️ 1. Take inventory of your resources
Before anything else, sort your resources folder into four piles:
| Resource type | State on Enhanced |
|---|---|
| Open Lua | Works, except Legacy-specific natives |
| Key-value data (KVP) | Must be migrated |
| C# / .NET | Must be recompiled |
| Encrypted (Tebex escrow) | Does not load today |
| Assets (vehicles, MLOs, clothing) | Must be converted |
This inventory, not your server's power, is what decides whether the migration is feasible now.
⚙️ 2. Encrypted scripts: the blocker
Asset Escrow is not implemented on Enhanced. In practice, a protected resource bought on Tebex cannot be decrypted and refuses to start, whatever server it runs on.
Three ways out, in order of preference:
- Ask the seller for an Enhanced-compatible version, or an open version for existing buyers
- Replace the script with an open-source equivalent, where one exists
- Wait for escrow to land on Enhanced, keeping production on Legacy
Count the encrypted resources your gameplay cannot do without. If that number goes past two or three, the migration is not ripe for your server, and no configuration will change that.
⚙️ 3. Lua: what actually needs checking
Contrary to what you often read, there is no lua54 to declare. The Cfx.re documentation is explicit: the setting is deprecated and, since June 2025, every Lua script already runs on 5.4. A standard manifest is enough:
fx_version 'cerulean'
game 'gta5'
client_script 'client.lua'
server_script 'server.lua'
The real work is elsewhere: scripts calling natives removed on Enhanced, or touching engine graphical elements, fail at load time or mid-session. Add your resources one by one, console open, and deal with the errors as they come.
⚙️ 4. C#: recompile for .NET
The runtime moved from Mono to .NET. A C# resource compiled for Legacy will not load on Enhanced: you need the source project, an updated target framework and updated Cfx.re references, then a rebuild.
Recompiling requires the .NET SDK on your development machine. If you do not have the sources of a purchased C# script, you are in the same position as with escrow: only the author can ship a compatible version.
⚙️ 5. Frameworks: ESX, QBCore, QBox
None of the three is plug-and-play on Enhanced; all need a ported version. Before porting your server, check the state of your framework's repository, and start from a clean install of the ported framework into which you reinject your in-house resources - rather than converting a two-year-old Legacy install.
If you are still weighing which base to build on, the ESX and QBCore comparison still holds: the framework choice does not change with Enhanced.
The database connection itself does not move - see connecting MySQL with oxmysql.
⚙️ 6. Custom assets
Add-on vehicles, MLOs and clothing must be converted for the Enhanced engine: files built for GTA V Legacy are not guaranteed to display correctly, and an unconverted asset can crash players' clients rather than simply not showing up.
One precise point not to miss: a resource streaming its files from a stream folder must use stream_enhanced on Enhanced. Mechanical work, but forgetting it silently makes your assets disappear.
Handle them last, once the server is stable with your scripts: a server that starts without its MLOs is still playable, the reverse is not true.
⚙️ 7. Voice: Mumble is deprecated
Enhanced ships a new voice system that replaces Mumble, driven by server-side natives (CreateVoiceChannel, AddPlayerToVoiceChannel, SetPlayerMutedInVoiceChannel…). Mumble natives still work, routed through that new system, but they are deprecated and will be removed. To buy time, setr sv_mumble true keeps Mumble compatibility while you port your voice resource. Test it with several players connected at once, not alone on the server.
⚙️ 8. Test in parallel, switch afterwards
The right sequence, in order:
1. Enhanced test instance, empty server
2. Ported framework, no in-house resource yet
3. In-house Lua resources, one by one, console open
4. Recompiled C# resources
5. Converted assets
6. Load test with real players
7. Production switch, during off-peak hours
Each step is validated in the console: one resource added, one restart, zero errors. Adding ten resources at once means losing track of the one blocking startup.
✅ Conclusion
The migration comes down to a single number: how many encrypted resources your server cannot do without. The rest - stream_enhanced, .NET rebuilds, assets - is mechanical work you can do alongside production. Pick up the technical context in FiveM Enhanced: running your server on the GTA V Enhanced build.
At LordHosting, Legacy and Enhanced are available on every FiveM plan: you can keep your RP server in production and spin up a porting instance without changing plan.
