Update a legacy QBCore installation

There is no universal qb-core v2 branch or tagged migration that can safely transform every customized server. Treat each repository, database change, and integration as a separate migration boundary.

Procedure

1. Record current remotes, branches, commits, and uncommitted changes.
2. Clone current upstream repositories into a separate staging directory.
3. Compare manifests, configs, shared data, SQL files, exports, and events.
4. Port customizations deliberately instead of copying the new source over production.
5. Apply only SQL changes found in the relevant upstream repository and reviewed for your schema.
6. Test character load/save, money, jobs, inventory, vehicles, housing, and permissions.
7. Deploy repository by repository with a rollback point after each unit.

Do not run generic ALTER TABLE statements or clone a branch merely because a third-party guide labels it “v2”.

See breaking-change review and resource updates.