Migrating from v3 to v4
Move your existing garages into the v4 admin panel
v4 saves garage locations in the database. Import your v3 locations once, then manage them through /garageadmin.
Back up and replace the files
Stop jg-advancedgarages and back up the resource and your database. Replace the resource with the v4 files, keeping the folder name jg-advancedgarages.
Check the v4 dependencies before starting the new version.
Prepare your config
Use the new config/config.lua and copy over your settings. Replace these location tables with your v3 versions, keeping their garage names unchanged:
Config.GarageLocationsConfig.JobGarageLocationsConfig.GangGarageLocationsConfig.ImpoundLocations
Copy any customised interior, marker, blip and garage settings too. The importer uses these when creating locations.
Update the database
Keep Config.AutoRunSQL = true to apply the database updates when v4 starts. If you run SQL manually, run the new install/run-qb.sql (QBCore/Qbox) or install/run-esx.sql (ESX) in your server's database first.
Fully restart your server. Resolve any SQL errors before importing locations.
Import your garages
Open /garageadmin as an admin and click Import. Choose All sources to import your current config and old private garages, including their members.
Click Preview, check the locations and resolve any errors, then click Import. Existing garage IDs are skipped, so importing again won't overwrite them.
Check access and vehicles
Test opening, storing and retrieving vehicles at your imported garages and impounds. Check job and gang restrictions. Imported private-garage users have Member access; assign Owner where players should manage membership.
Imported garages have unlimited parking until you set a limit. Make future location changes in the Admin Panel.
For new housing or third-party integrations, use the server registration exports.
Last updated 18 September 2026