Snapshot first
Back up resource files, configuration and database before changing a production stack.
NOTWEN / MIGRATION CENTER
MOVE IN LAYERS.
NOT ALL AT ONCE.
Keep the framework that already runs your server. Introduce the Notwen boundary, verify one resource at a time and preserve a rollback path before replacing anything.
01 / SOURCE STACK
What are you migrating from?
Select the framework boundary that currently owns player and server state.
02 / TARGET
Progressive adoption
Keep the source framework running while compatible Notwen resources are introduced behind a stable integration boundary.
SAFE MIGRATION
The rules stay the same on every framework.
Most migration failures come from replacing too much at once or losing the original dependency order.
One boundary at a time
Introduce one resource, verify its dependencies and test its events before removing the previous implementation.
Framework before bridge
Your existing framework must start before anything that adapts its state into the Notwen boundary.
Use explicit release states
Do not put roadmap or pre-release Notwen resources into a production ensure list just because documentation exists.
Keep rollback simple
Retain the old resource disabled but recoverable until the replacement has survived real server testing.
Validate after every change
Check console errors, resource start order and player flows before moving to the next system.
CFX REFERENCE
Use the platform commands, not assumptions.
Cfx documents ensure as starting a stopped resource or restarting an already-started one. Resources live under the server's resources directory and require a manifest such as fxmanifest.lua.