Migration
Move existing banking data to GKS Bank without starting two banking resources together.
Use migration when you are replacing an existing banking resource. For a new server, follow Installation instead.
Make a database backup and stop the old banking resource before importing data. Never run two resources that own the same balances.
Supported sources
| Source | Detected tables |
|---|---|
qb-banking | bank_accounts, bank_statements |
Renewed-Banking | bank_accounts_new, player_transactions |
esx_addonaccount | addon_account, addon_account_data |
Check available adapters
Run this in the server console:
gkbank importThe command lists available adapters and whether their source tables exist in the database.
Preview the migration
Run a dry run first. It reads and maps the source data without writing to GKS Bank:
gkbank import qb-bankingReplace qb-banking with the source shown by gkbank import.
Apply the migration
When the dry run looks correct, apply the import:
gkbank import qb-banking --applyImported accounts and transactions are marked as imported. The migration map prevents the same source row from being imported twice.
Verify
After the import:
- Start GKS Bank with the old banking resource stopped.
- Check player balances and shared accounts.
- Check recent transaction history.
- Check cards and inventory items if they are enabled.
- Keep the old database backup until verification is complete.