Migration Guides - QBCore Guide for FiveM

Introduction

This tutorial turns Migration Guides 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: Quick Navigation

In this step, you will apply the quick navigation concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.

Step 2: 🔄 Version Upgrades

In this step, you will apply the 🔄 version upgrades concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.

Step 3: 🚚 Framework Migration

In this step, you will apply the 🚚 framework migration concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.

Step 4: 🛠️ Migration Tools

In this step, you will apply the 🛠️ migration tools concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.

Step 5: Migration Planning

In this step, you will apply the migration planning concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.

Step 6: 1. Backup Everything

In this step, you will apply the 1. backup everything concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.

Step 7: 2. Review Changes

In this step, you will apply the 2. review changes concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.

Step 8: 3. Test Environment

In this step, you will apply the 3. test environment concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.

Code Example

-- Example: QBCore callback pattern
local QBCore = exports['qb-core']:GetCoreObject()

QBCore.Functions.CreateCallback('tutorials:getPlayerJob', function(source, cb)
  local Player = QBCore.Functions.GetPlayer(source)
  if not Player then return cb(nil) end

  cb({
    job = Player.PlayerData.job.name,
    grade = Player.PlayerData.job.grade and Player.PlayerData.job.grade.level or 0,
  })
end)

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.