Migration Guide

This guide helps you migrate from other scripts, making the transition as smooth and compatible as possible.

---

Migration Type Key

Built-In Migration

• Automatically supported with no SQL changes, code changes, or manual setup required.

Minor Migration Required

• Requires a simple command, SQL query, or small code change. All required queries or code are provided. Usually completed in minutes.

Moderate Migration Required

• Requires provided SQL queries and some code changes across a few files. Usually completed in 5–15 minutes.

Major Migration Required

• Requires multiple SQL queries and larger code changes across several files. Usually takes 1+ hours.

---

Supported Mechanic Migrations

See which mechanic scripts can be migrated to cd_mechanic while keeping existing vehicle progress and saved data where possible.

Script Name	Migration Type	Notes
esx_mechanicjob	Built-In Migration
jg_mechanic	Minor Migration Required	A single chat command is used to run the database migration.
qb-mechanicjob	Built-In Migration

---

Migration Data Comparison

This table shows what important data can usually be kept when moving to our mechanic system.

Key

✅ Migrated / Reused

• Existing data can be migrated or reused

❌ Reconfigure

• Existing data cannot be migrated or reused, but can be reconfigured again

⚠️ Not Used

• Your old mechanic script does not have this feature

Data

esx_mechanicjob

jg_mechanic

qb-mechanicjob

GTA performance upgrades	✅	✅	✅
Cosmetic upgrades	✅	✅	✅
Vehicle paint	✅	✅	✅
Engine / body health	✅	✅	✅
Registered inventory items	✅	✅	✅
job inventory/stash item contents	✅	✅	✅
Jobs	✅	✅	✅
Society account	✅	✅	✅
Advanced upgrades	⚠️	✅	⚠️
Advanced tuning	⚠️	✅	⚠️
Degradable / service parts	⚠️	✅	⚠️
Nitrous	⚠️	✅	⚠️
Stancer	⚠️	✅	⚠️
Player run business locations	❌	❌	❌
LS Customs locations	❌	❌	❌