Out of legacy. Onto modern infrastructure.
In 30 days.
The four-week playbook for operators escaping SoftSwiss, EveryMatrix, BetConstruct, Digitain, or SOFTGAMINGS. Player set, wallet balances, KYC tier history, bonus ledger, and CRM segments preserved to the cent. No vendor lock-in. No GGR rev-share. No per-brand fees.
Four weeks. Four checkpoints.
Migrations don't fail because the new platform is slow. They fail because the cutover loses data, breaks compliance, or surprises players. The playbook is structured so the cutover is the smallest event of the four weeks — the work is in the parallel testing before it.
- Week 101
Data export + parallel infrastructure stand-up
We export your full operator state from the legacy vendor under their contractual data-portability terms (player accounts, wallet ledgers, KYC documents + tier history, bonus ledger, CRM segments, transaction history). nuke.ai stands up your tenant in parallel — separate database, separate cache, separate game-launch tokens. Your existing brand stays live and serving players the whole time.
Player set imported. Wallet balances reconciled to the cent. KYC tiers preserved.
- Week 202
Configuration + jurisdiction mirror
Compliance Config Center is populated from your existing jurisdictional posture — license parameters, deposit/loss limits, self-exclusion list (including GAMSTOP sync for UK operators), KYC tier triggers, geo-blocking, bonus restrictions, tax-reporting cadence. Payment-processor relationships are wired in (you keep your existing PSP contracts — we don't force a switch). Game catalog selection is migrated; titles you lose are flagged so you can pre-communicate to players.
Jurisdiction templates configured. PSP relationships re-wired. Game catalog parity.
- Week 303
Parallel testing + shadow traffic
Your existing platform stays primary. nuke.ai mirrors a percentage of live traffic in shadow mode — every bet, every deposit, every withdrawal is replayed against the new tenant and compared to the legacy result. Discrepancies (rounding, RNG seed drift, bonus-eligibility logic) surface here, not in production. CRM campaigns run in dry-run mode against the new segments.
Shadow traffic parity confirmed. Discrepancy log resolved. Go/no-go decision made.
- Week 404
Cutover + legacy decommission
DNS flips. Players hit nuke.ai. Their wallets, bonuses, VIP status, KYC tier, and self-exclusion state are exactly where they left them on the legacy platform — by design, the cutover is invisible to the player. Legacy vendor receives the contractual termination notice. nuke.ai operates the platform; your team operates the brand.
Live on nuke.ai. Legacy vendor in 90-day decommission window. Full audit log exported.
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? The answer is no. Specifically:
- Player accounts
- Every player ID, email, registration date, login history, and account state migrates 1:1. Self-excluded players remain self-excluded. Closed accounts remain closed.
- Wallet balances
- Reconciled to the cent across fiat and crypto rails. Pending withdrawals are completed on the legacy platform before cutover; new withdrawals route through nuke.ai.
- KYC tier history
- Every uploaded document, every verification timestamp, every tier-upgrade audit log. New PSPs / KYC vendors don't trigger re-verification — the existing tier carries over.
- Bonus ledger
- Active bonuses, pending-wagering states, free-spin balances, and historical bonus utilization. Wagering-progress math is replayed in Week 3 shadow testing to confirm parity.
- CRM segments
- Behavioral segments, VIP designations, churn-risk scores, communication preferences, opt-in/opt-out flags. The Customer Value Hub picks up the segmentation history on Day 1.
- Transaction history
- Full deposit/withdrawal/bet history exported as an immutable archive. Available to operators for tax reporting, regulator audits, and player disputes for the full statutory retention period.
- Compliance state
- Self-exclusion (incl. GAMSTOP), deposit limits, loss limits, cooling-off, behavioral-risk flags — all preserved per player. No re-onboarding, no re-acknowledgment of T&Cs unless mandated by jurisdiction.
- Game catalog
- Titles you actively serve are mapped to the nuke.ai Game Aggregator. Lost titles (rare) are flagged in Week 2; players are pre-notified through CRM before cutover.
Fixed fee compounds in your favor.
Legacy vendors price as a percentage of GGR. As you scale, your vendor scales with you — eight cents of every dollar above the baseline leaves your P&L. nuke.ai prices as a fixed platform fee that scales with brand count and MAU, not revenue. The crossover point is where the migration pays for itself.
| Scenario | Legacy (rev-share) | nuke.ai (fixed) |
|---|---|---|
| Single brand · $500K/mo GGR · 5K MAU | 8% GGR rev-share = ~$40K/mo + setup | Fixed enterprise platform fee (Launch Calculator estimate) Inflection at ~$500K GGR — beyond it, rev-share grows; fixed fee doesn't. |
| Multi-brand · $5M/mo GGR · 100K MAU | 8% GGR rev-share = ~$400K/mo + per-brand setup fees + managed-services markup | Fixed platform fee scales with brand count + MAU, not GGR Typically $3M–$7M saved over 36 months — exact figure from the Launch Calculator. |
| Enterprise · $50M+/mo GGR · 500K+ MAU | Rev-share + per-brand fees + custom-development markup; tens of millions over 36 months | Fixed enterprise contract; AI automation removes 20-50% of ops headcount Eight-figure savings over 36 months is typical; operational efficiency dominates the math. |
*Illustrative scenarios. Your exact monthly cost is generated by the Launch Calculator from your specific configuration. Legacy rev-share figures assume an 8% blended rate, which is industry-typical for multi-brand enterprise contracts.
Migrating from a specific vendor?
Each legacy vendor has its own contractual quirks and technical integration shape. The playbook is the same; the early-week details are vendor-specific.
From SoftSwiss
Full matrix →SoftSwiss agreements typically include a notice period (90 days standard) and a data-export clause that requires a written request through their compliance desk. Don't fire off the termination notice before the export request is acknowledged — the contractual sequencing matters.
Wallet-balance migration from SoftSwiss is straightforward (they export to CSV reliably). Bonus-ledger migration requires reconciliation of pending-wagering states — we run that in Week 3 shadow testing.
From EveryMatrix
Full matrix →EveryMatrix modular contracts mean you may be migrating off only part of their stack (e.g. casino but keeping their sportsbook engine OddsMatrix integration). The /compare/everymatrix page documents which engines integrate cleanly with nuke.ai's headless layer.
If you've been on EveryMatrix's managed-services tier, expect a 1-week handoff window where their ops team transfers operational runbooks. We schedule this between Week 2 and Week 3 of the playbook.
From BetConstruct
Full matrix →BetConstruct contracts often span retail + online; if you only operate online, the migration is single-track. Operators with retail terminals on SpringBME hardware need a longer parallel-operation window — coordinate with your retail-ops team early in Week 1.
SpringBME bookmaker engine integrates with nuke.ai's platform layer through standard webhook contracts; if you want to keep BetConstruct's sportsbook depth while moving casino + CRM + compliance to nuke.ai, that hybrid configuration is supported.
From Digitain
Full matrix →Digitain's sportsbook-first contracts often have GGR rev-share tied specifically to sports-betting revenue. If you're moving the casino vertical to nuke.ai but keeping Digitain's sportsbook, the rev-share scope shrinks — model the new contract terms before negotiating renewal.
Digitain's native odds engine integrates with nuke.ai's platform layer through webhook contracts. Casino-only migrations complete in the standard 30-day window; full-stack migrations (casino + sportsbook to nuke.ai's aggregator-mediated model) take ~45 days.
From SOFTGAMINGS
Full matrix →SOFTGAMINGS' turnkey-and-white-label dual model means migration scope depends on which you're on. White-label operators don't own the license; migration here means re-acquiring (or buying through) a license alongside the platform move. Turnkey operators own their license and the migration is single-track.
Game-catalog parity is the main migration concern — SOFTGAMINGS aggregates a larger raw catalog (13,000+ titles claimed); nuke.ai's 5,000+ catalog covers the high-conversion subset most operators actively serve. Lost titles are identified in Week 2 and pre-communicated to players.
Operating on a vendor not listed here? The playbook applies — the shape of the data export changes, the contract clauses change, but the four-week sequence is the same. 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
- Mitigated by parallel-operation through Week 3 — the legacy platform stays primary until shadow-traffic parity is confirmed. If the export is incomplete or incorrect, you find out before cutover, not after.
- Player confusion at cutover
- Cutover is invisible — same domain, same login, same wallet balance, same VIP status. We pre-coordinate a maintenance window in the lowest-traffic hour of your largest market and complete the DNS flip in under 5 minutes.
- Regulatory non-acceptance of the new platform
- We coordinate with your compliance team to file the platform-change notification with your regulator(s) during Week 2 — before any production change happens. Most jurisdictions require notification, not pre-approval; the timing matters.
- Bonus-wagering math drift
- Wagering-progress calculations are replayed in Week 3 shadow testing across every active bonus. Discrepancies (typically 4-decimal rounding) are caught and reconciled before cutover. We pay out any rounding-induced delta to the player.
- Cold-start CRM (no campaigns running in the new system)
- Customer Value Hub is pre-loaded with your existing segments during Week 2. Day-1 campaigns continue running without manual reconstruction. Behavioral-segment scoring picks up from the legacy state.
- Legacy vendor obstruction at exit
- Most legacy contracts have a data-portability clause that is contractually enforceable. We've worked with operators through enforcement when the vendor stalls. The 90-day decommission window gives the legacy vendor adequate time to comply.
Ready to scope your migration?
30-minute call with the migration desk. Walk through your current stack, your contract timeline, and the data shape we'll be importing. Live demo of the platform in the same call.