Should you migrate your FiveM server to Enhanced now? The checklist
One question decides everything: does your server depend on paid protected resources? Here's the full checklist before you move anything.
FiveM for GTA 5 Enhanced has been in early access since 21 July 2026. Ever since, the same question has been circling every owner’s Discord: do we migrate now, or wait?
The honest answer isn’t “it depends how motivated you are”. It depends on one single disqualifying criterion, then on a series of concrete checks. Here’s the checklist, in the order you should run it.
Step 0: the question that settles everything
Does your server depend on paid resources protected by Asset Escrow?
If yes: don’t go. That’s not an opinion, it’s a technical constraint. Asset Escrow — the system that protects and distributes paid resources — isn’t available on Enhanced during early access. Right now, your purchased resources have literally nowhere to go. This isn’t a conversion problem or an effort problem: there’s nothing to convert them into.
Cfx.re says as much itself: most production servers should wait for that feature before migrating. When the platform’s own maintainers explicitly tell you to hold, you hold.
If you’re standalone — your codebase is yours, in Lua or JS, with no escrowed dependencies — then migrating is reasonable right now, and the rest of this checklist is for you.
Step 1: inventory your resources, honestly
Open your resources folder and sort every single resource into one of four buckets:
| Category | Migration | Detail |
|---|---|---|
| Scripts you wrote | Easy | Lua/JS generally carry over |
| Free third-party, open source | Medium | Depends on whether it’s maintained |
| 3D assets (vehicles, MLOs, clothing) | Real work | Goes through Alchemist |
| Paid escrowed resources | Blocking | Nothing to do but wait |
The classic mistake is doing this inventory from memory. Do it file by file. On a three-year-old server there are often two or three forgotten escrowed resources, installed by a developer who left, that nobody remembers are protected — and they’re enough to block the whole move.
Step 2: scripts
This is the good news. Scripts are rarely the blocker. Most of what you wrote in Lua works, and on the C# side the move from Mono to .NET is a step forward, not a regression.
What still needs checking:
- natives you call directly, especially anything touching rendering, graphical effects and pause menus — that’s where generational differences show up;
- unmaintained third-party resources. A brilliant script abandoned in 2023 won’t be ported by anyone. You inherit the work;
- shared dependencies (frameworks, utility libraries): check how far along they are on Enhanced before planning anything. Your timeline is your slowest dependency’s timeline, not yours.
Step 3: 3D assets
This is where the actual work lives. Gen8 formats aren’t readable as-is by the Enhanced client, and Cfx.re publishes an official tool for it: Alchemist.
Worth knowing before you start: it runs on Windows 11 only, handles five formats (.ydr, .ydd, .yft, .ytd, .ypt), and doesn’t touch .ymap, .ytyp, .ybn (collisions) or .ycd (animations). On a complex MLO it will convert the models and textures, not the whole package.
The full walkthrough, CLI parameters and pitfalls are in our dedicated guide: converting Legacy assets to Enhanced with Alchemist.
The question to ask yourself here isn’t technical, it’s strategic: how many of your assets actually deserve to be converted? Plenty of servers are dragging along packs installed years ago that three players use. A migration is the best opportunity you’ll ever get to cut dead content. Converting less means testing less and breaking less.
Step 4: your player base and your community
Two checks that technical checklists always forget.
Where are your players? Migrating isn’t just changing your platform: it means asking every one of your players to own GTA V Enhanced and to have a machine that runs it properly. Poll your Discord before, not after. A technically flawless migration that locks a third of your population out is a failed migration, however good the work was.
How much bug tolerance does your community have? Early access means exactly what it says: things break, fixes land, behaviours change between builds. A competitive, young, curious community absorbs that easily. A long-standing RP community, settled into its habits, with characters and an economy two years in the making, absorbs it far less well. Be clear-eyed about which of the two you run.
Step 5: the order of operations
If you’ve cleared the previous steps, here’s how to proceed. It comes down to one principle: never a cold switch.
- Stand up a parallel test server. A second instance, a different port, your production server untouched. This is non-negotiable, and it’s the step half of all owners skip and later regret.
- Boot it empty, with the bare minimum. First you want to see an Enhanced server that starts cleanly.
- Add your own scripts, in blocks. Clean console after each addition before moving to the next.
- Convert and add assets in batches: vehicles, then clothing, then MLOs. When something breaks, you know which batch to look at.
- Test in game, not in the console. A converted texture can load without error and render black.
- Run a session with real players. Recruit a handful of volunteers from your community. They’ll find in one evening what you’d have missed in a month.
- Measure performance under load with
resmon— the full method is in our guide on why your FiveM server lags. - Keep your Legacy instance running through the transition. Your way back should stay one click away.
The decision, in three lines
- Dependent on escrowed resources → wait. There’s no clever workaround.
- Standalone, playful community, keen to experiment → go, on a parallel test server.
- Large established RP server, low bug tolerance → prepare, convert, test, but don’t switch yet.
Either way, Enhanced is the future baseline. The work you do today on a test server isn’t wasted: it’s a head start. To place the two versions side by side, see our Legacy or Enhanced comparison and our reference page FiveM Enhanced: everything you need to know.
There’s one scenario this checklist doesn’t apply to at all: the server with nothing to migrate. That’s where we sit with Chased — a single standalone resource written for Enhanced from day one, with no Gen8 asset debt and no escrow dependency. The game fits in one sentence: 1v1 hunter-versus-hunted duels in a randomly drawn shared car, where everything comes down to driving. No inventory to sort, no conversion to plan — and that’s exactly why we built it this way.