The challenge

Legacy that couldn't be turned off.

The operator's existing platform handled millions of monthly transactions. Maintenance windows were measured in hours of forgone GGR — a replatform with a freeze was not commercially possible. A parallel-run with manual reconciliation would have introduced reconciliation drift across multiple regulators. Either path was unacceptable.

What we did

Live cut-over, wallet-first, region-by-region.

We migrated wallet first. Both stacks read the same balance state through a thin shim that survived the entire cut-over. CRM and content followed once wallet parity was verified daily for two weeks. Each region was cut over independently — Tier-1 LATAM first, then EU regulated, then EU non-regulated — so a regression in one market couldn't propagate. The legacy stack stayed online as a read-only fallback for 30 days post-migration.

14-WEEK CUT-OVER · WALLET-FIRST · ZERO DOWNTIME W1 W4 W7 W10 W14 Wallet shim — both stacks read same balance Live throughout LATAM Tier-1 W1–W4 EU regulated W4–W9 EU non-regulated W9–W14 Legacy stack online as read fallback · 30-day soak Decommissioned W14+30 0h Player-visible downtime 100% Daily wallet-balance parity 3 Regions cut over independently 0 Regulator queries on filings
Region-by-region cut-over plan with wallet shim live throughout. Legacy stack soaked for 30 days post-migration.
Results

By the numbers.

  • 0 hours of player-visible downtime across the 14-week migration
  • 100% wallet-balance parity verified daily through cut-over
  • Cross-sell wallet enabled day-one post-migration
  • Compliance reports filed across three regulators with zero queries
The migration didn't show up in our metrics. Players didn't notice — that was the brief, and that's what we got.
Anonymous (operator-confidential) Head of Platform · Tier-1 European operator
Share LinkedIn Telegram Email