Switch to GameBridge
A migration program for operators leaving a PAM or a vendor stack, from assessment and data mapping through player import, ledger migration and parallel run to cutover and decommission. Honest about what moves, what does not, and the window it takes.
Eight steps from assessment to decommission.
The sequence is fixed; the calendar depends on player count, the incumbent's export options and how many brands move. We rehearse the cutover before it counts.
- Step 1Assessment
Inventory of the incumbent: players, wallets, bonus states, VIP tiers, content, campaigns, integrations and contracts. Output: a migration scope and a cutover approach.
- Step 2Data mapping
Every incumbent field mapped to a GameBridge field: wallet types, KYC statuses, consent flags, VIP tiers and XP, bonus states, segments. Unmappable items are listed, not assumed.
- Step 3Player import
Player records imported from a spreadsheet through the console's Excel import, with KYC status, consent and VIP tier, and verified against source counts.
- Step 4Balances and liability on the ledger
Opening balances per wallet and open bonus liability posted as ledger rows, locked funds carrying playthrough. Every migrated cent is a balanced posting.
- Step 5Reconciliation sign-off
Totals per wallet type, locked versus free balance and liability compared exact to the cent to the incumbent snapshot. Finance signs before anyone plays.
- Step 6Parallel run and soft launch
A soft-launch cohort plays on GameBridge while the incumbent serves everyone else. One wallet of record per player at any time.
- Step 7Cutover
Freeze the incumbent, post the final balance delta, switch DNS and apps, hand over the redeem queue and support, watch the ledger and Engine Diagnostics.
- Step 8Decommission
Incumbent exports archived for regulatory retention, integrations switched off, contracts closed on their notice dates.
What migrates, and what you rebuild.
What does not move is listed now, not discovered in week three.
Moves with the player
- Player records via spreadsheet import: identity, contact, registration date, KYC status, consent flags
- Wallet balances per wallet type, posted as opening ledger entries
- Open bonus liability as locked funds with playthrough, in liability reports from day one
- VIP tier and XP, adjusted with a mandatory reason and reconciled by the XP backfill
- Suppressions: bounces, complaints, SMS STOP, manual blocks, global or per brand
- Responsible-gaming states such as self-exclusion and limits
Moves as configuration
- Bonus definitions rebuilt in the bonus engine and imported as JSON, CSV or XLSX
- Segments as nightly rule definitions with import and export
- Banners and packages with JSON import, packages with a dry run first
- Campaign journeys rebuilt in the canvas and imported as JSON
- Catalog exclusions and categories with JSON import and preview
Does not move automatically
- Third-party provider game histories: they stay in the incumbent's exports for retention
- Historic campaign sends, opens and clicks: new funnels start at cutover
- Passwords: players set a new one on first login, verified by OTP over SMS or email
- KYC documents held by another vendor: status moves, documents do not
- Historic transaction rows in My Activity: opening balances carry the value, not the rows
Exports we take as standard, and what needs custom work.
Integrated means the platform has a standard path for the data. On request means custom mapping or tooling scoped in the assessment.
Statuses describe our import path, not the incumbent's willingness to export. Notice periods and export fees at the incumbent are part of the assessment.