Guide · 15 November 2026

Casino platform migration: how to move an online casino without losing players

Most platform conversations do not start from zero. They start because the reports cannot be trusted, because a market needs a payment method the current supplier will not add, or because every bonus campaign needs a developer. Moving a live casino is harder than launching a new one, but it is a project with a known shape. This guide describes it.

Key points

  • A migration is decided by the quality of the data you are leaving behind, not by the platform you are moving to.
  • Accounts, balances, bonus liabilities, verification status, responsible gambling settings and history all have to move, and each needs its own check.
  • Four stages cover the work: audit, mapping, parallel run and cutover with a rollback plan.
  • Your current contract decides what you may export and in what format. Read it before setting a date.

What has to move

DataWhat to check
Player accounts and loginsWhether players keep their login or have to set a new password, and how duplicates are handled
BalancesCash and bonus balances at the moment of cutover, reconciled to the cent on both sides
Bonus liabilitiesOpen bonuses and wagering progress, so that nobody loses an offer halfway through
Verification statusWhether completed identity checks can be carried over under your licence, and where the documents are held
Responsible gambling settingsDeposit limits, time-outs and self-exclusions. These must arrive intact on day one
HistoryTransactions and game rounds, for disputes, reporting and regulator requests
Payment detailsAsk each payment provider whether stored details can be transferred or must be entered again

The row most often forgotten is responsible gambling. A self-excluded player who can log in after the move is a regulatory incident, not a bug. Our guide to responsible gambling tools lists what the platform has to hold, and the KYC and AML guide covers verification.

The four stages

  • Audit. What data exists, in what state, and what the current contract lets you take. Most surprises live here.
  • Mapping. Accounts, balances, bonus liabilities, verification status and history mapped field by field, then run against a copy.
  • Parallel run. Both systems reconcile to the same day before anything is switched. The numbers match or the date moves.
  • Cutover. One window, a rollback plan and a support rota. Players keep their balances, history and logins.

Content is the easier part. If the games come through a game aggregator, the same studios are available on the new platform, subject to certification in each market, and the lobby can be rebuilt before the switch.

What decides the timeline

Four things, in this order. The first is data quality: duplicates, missing fields and balances that do not reconcile have to be fixed before they can be moved. The second is the contract with the supplier you are leaving, which sets the notice period, the export format and what happens to balances. The third is payment provider approval, because providers assess the operator and the new set-up. The fourth is studio certification in each market you serve.

Anyone who promises a date before seeing an export is guessing. A realistic plan is written after the audit.

Mistakes that lose players

  • Switching on the busiest day of the week or during a major tournament.
  • Having no rollback plan, so that a failed check leaves no way back.
  • Starting new bonus campaigns in the week before the move.
  • Telling players late. A short notice in advance, a clear message on the day and a visible support channel prevent most complaints.
  • Treating the lobby as an afterthought. Players notice a missing favourite game before they notice anything else.

The casino platform page describes how we run a migration, and the questions to ask a provider include the exit terms worth agreeing before you sign with anyone.

Frequently asked questions

It depends on the quality of the data, the exit terms of the current contract, payment provider approvals and studio certification in your markets. A date given before the audit is a guess.
Yes, when the migration is done properly. Accounts, balances, bonus liabilities and history are mapped and moved, and the two systems are reconciled before the switch.
Usually. If the content comes through an aggregator, the same studios are available on the new platform, subject to certification in each market.
The notice period, which data you may export and in what format, and what happens to player balances. If those points are missing, raise them before you set a migration date.

Planning a move to a new platform

IGP migrates live casinos to its platform through audit, mapping, a parallel run and a cutover with a rollback plan. Tell us what you run today and we will say what the move involves.

See the casino platform →