QBCore v1 to v2 Migration Guide - QBCore Guide for FiveM
Introduction
This tutorial turns QBCore v1 to v2 Migration Guide into a clean, developer-friendly guide for QBCore/FiveM. You will follow a step-by-step flow, copy the relevant code patterns, and learn the “why” behind the setup.
Requirements
- QBCore installed and running on a dev server
- Basic Lua knowledge and comfort reading FiveM patterns
- A test workflow for iterating safely (dev server, not production)
- Optional: a code editor with Lua/FiveM helpers (VS Code recommended)
Step-by-Step Guide
Step 1: Pre-Migration Checklist
In this step, you will apply the pre-migration checklist concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.
Step 2: Major Changes in v2
In this step, you will apply the major changes in v2 concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.
Step 3: Framework Architecture Changes
In this step, you will apply the framework architecture changes concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.
Step 4: Resource Structure Changes
In this step, you will apply the resource structure changes concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.
Step 5: Step-by-Step Migration Process
In this step, you will apply the step-by-step migration process concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.
Step 6: Phase 1: Preparation
In this step, you will apply the phase 1: preparation concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.
Step 7: Phase 2: Test Environment Setup
In this step, you will apply the phase 2: test environment setup concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.
Step 8: Phase 3: Database Migration
In this step, you will apply the phase 3: database migration concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.
Code Example
local Player = QBCore.Functions.GetPlayer(source)
local playerData = Player.PlayerData
local job = playerData.job.name
local money = playerData.money['cash']Tips & Best Practices
- Keep authority on the server: validate inputs before money/database operations.
- Start with one resource/module at a time, then refactor after you verify it works.
- Use callbacks for request/response flows and events for push/UX updates.
- When you run loops, avoid freezes: always yield with Wait() (client/server) and cache hot values.