A clear path from your current platform.

Plan your migration

Start with the dependencies, not a promised deadline. Agree the data scope, integrations, validation and cutover plan before committing to a launch date.

1. Stage 1

   01

   Data export + parallel infrastructure stand-up

   Agree the export fields, permissions, retention duties and integration inventory with your current provider. Test sample imports in an isolated environment while the existing platform remains authoritative.

   ✓Export scope agreed. Sample data and reconciliation criteria reviewed.

2. Stage 2

   02

   Configuration + jurisdiction mirror

   Map licensing requirements, player-protection settings, payment providers and game availability. Confirm which contracts and integrations can transfer and which need new approval.

   ✓Configuration reviewed by the operator. Integration gaps and approvals recorded.

3. Stage 3

   03

   Parallel testing + shadow traffic

   Validate balances, bonus progress, access and reporting with controlled test data. Keep test activity isolated from real payments and bets; resolve exceptions before the go/no-go review.

   ✓Reconciliation signed off. Exceptions resolved or explicitly accepted. Rollback rehearsed.

4. Stage 4

   04

   Cutover + legacy decommission

   Execute the agreed cutover and communication plan after approval. Monitor the new environment, retain the agreed rollback route, and close the old service only when contractual and retention duties allow.

   ✓Cutover approved. Monitoring and archival ownership assigned. Exit timing agreed.

What survives the cutover.

Every operator's deepest migration anxiety is the same: am I going to lose my players, my data, or my compliance state? Protecting them starts with an agreed inventory and documented checks:

Player accounts

Map identifiers, account states and access methods. Check duplicate records and password-transfer constraints; keep self-excluded and closed accounts restricted.

Wallet balances

Reconcile balances by currency and ledger precision. Agree how pending withdrawals, unsettled transactions and refunds will be handled before switching.

KYC tier history

Review document-transfer rights, validity, retention and the receiving provider’s acceptance criteria. Additional verification may be required.

Bonus ledger

Test active bonuses, wagering progress and free spins against the agreed rules. Resolve differences before approving the cutover.

CRM segments

Map segments and communication preferences. Preserve consent and suppression flags; validate permitted uses before campaigns resume.

Transaction history

Define the historical data to import or archive, access controls and retention periods. Verify that audit, dispute and reporting needs are covered.

Compliance state

Verify self-exclusions, limits, cooling-off periods and risk flags. Confirm regulator, provider and operator requirements before enabling player activity.

Game catalog

Check availability by title, territory, provider and contract. Record gaps and tell affected players about material changes before cutover.

Migrating from a specific vendor?

Use this checklist with each vendor. Your signed agreements and validated interfaces determine what can move, what stays, and when.

Using another vendor? Scope and timing depend on your contracts, available exports and retained services. Email the migration desk with your current vendor and we'll scope it.

What could go wrong (and what we do about it).

Data loss at the export step

Keep the current system authoritative until exported records and balances are reconciled and signed off. Test backups and rollback before cutover.

Player confusion at cutover

Agree a maintenance window, explain any changes to players, and test login, wallet and domain continuity. Confirm cutover timing and a rollback decision point in the migration plan.

Regulatory non-acceptance of the new platform

Have your licensing and compliance advisers confirm required notifications, approvals and testing before production changes. Requirements depend on the jurisdiction and deployment.

Bonus-wagering math drift

Replay active bonus states and reconcile calculation differences before cutover. Agree how discrepancies will be resolved; do not assume rounding policies transfer unchanged.

Cold-start CRM (no campaigns running in the new system)

Map segments, campaign rules, consent and responsible-gambling exclusions. Test eligibility before enabling messages; do not automatically reactivate every historical campaign.

Legacy vendor obstruction at exit

Review exit and data-export rights with counsel, agree responsibilities with the current provider and plan for delays. A migration plan cannot guarantee another party’s cooperation.