01Specification
Casino migration & integration
Move a running casino without losing players, balances or history. Two kinds of work. A full casino migration brings players, balances, KYC states and history from your current platform to ours in a planned cut-over; our implementation takes 10–16 weeks, and PSP re-contracting sets the calendar date. A technical integration adds a PSP, KYC provider, game studio, CRM or data feed to a platform that is already live.
- Full migration in 10–16 weeks, our implementation time
- Dry-run import reconciled to the cent before any cut-over
- Old platform kept intact until hypercare ends
- REST API, webhooks and sandbox for your team
Index → What moves · Migration plan · Integrations · API access · Turnkey
02What moves
What moves with you, and what has to be re-done.
Migrating an existing casino, parts list. Honest answer first: most data migrates cleanly, contracts do not. Here is the split we work from.
| Item | What | How it moves | Status |
|---|---|---|---|
| MIG-01 | Players | Accounts, profiles, contact preferences, limits and self-exclusions. | Moves |
| MIG-02 | Balances | Real money per currency, reconciled against the source platform at cut-over. | Moves |
| MIG-03 | KYC states | Verification level, documents on file where the provider allows transfer, risk flags. | Moves |
| MIG-04 | Bonus history | Active bonuses with remaining wagering, historical bonus records for compliance. | Moves |
| MIG-05 | Affiliate data | Affiliate accounts, player attribution, commission state. | Moves |
| MIG-06 | Game history references | Transaction ledger and round references for audit and regulator reporting. | Moves |
| MIG-07 | PSP contracts | Between you and the PSP; usually re-signed or amended for the new platform. We start this on day one because it is the usual critical path. | Re-signed |
| MIG-08 | Passwords | Hashes rarely transfer between platforms. Players reset on first login; we handle the messaging. | Reset |
| MIG-09 | Stored card tokens | Belong to the old PSP integration. Players re-enter a card on first deposit unless the same PSP is kept. | Re-entered |
| MIG-10 | Game studio agreements | Move to the new licence and aggregator; content lists are re-confirmed per market. | Re-confirmed |
| MIG-11 | Front-end | Rebuilt on our themes or your design; we do not port old templates. | Rebuilt |
03Migration plan
Five stages, one cut-over weekend. The dry run is the stage that matters.
Migration plan, 10–16 weeks. If the import reconciles on the dry run, the real cut-over is a repeat with a maintenance page in front of it. Our implementation time is 10–16 weeks; PSP re-contracting is signed by third parties and usually sets the calendar date.
Platform1 / your workThird-party contracts: PSPs, studios, licence holder. They set the calendar date
- Weeks 1–3
Audit and mapping
Export from the source platform. Every table and field mapped to its target, with the gaps and transformations listed in writing.
- Weeks 2–6
Parallel environment
Your new platform configured and running next to the old one: brand, content, PSPs, KYC, bonus rules. Nothing on the old platform changes yet.
- Weeks 6–10
Dry-run import
Full import into staging. Balances reconciled to the cent, bonus states checked, sample players walked through login, deposit and withdrawal.
- Cut-over weekend
Cut-over
Old platform frozen, final delta imported, reconciliation signed off, redirects and DNS switched. Maintenance window agreed in advance, usually a few hours in low-traffic time.
- Three to four weeks after
Hypercare
Engineers on the channel daily, source data kept for comparison, any edge case fixed from the ledger rather than by hand.
04Technical integration
Integrations we add to a running platform.
Scoped individually, usually in days rather than weeks when the provider has a documented API. Built, tested in sandbox, released in an agreed maintenance window.
Payment providers
Card acquirers, open banking, e-wallets, local methods and crypto gateways, added to cascading routing per market.
KYC providers
Document and liveness checks, PEP and sanctions screening, mapped to the platform's KYC states and limits.
Game studios
Direct studio integrations or new aggregators, with lobby placement, per-market enablement and round-level reporting.
CRM and ESP
Segment sync, event streams and triggered campaigns to your email, SMS and push providers.
Affiliate software
Postbacks and player attribution to your existing affiliate platform, or the built-in tracking if you have none.
BI exports
Scheduled exports or direct connectors to your warehouse and dashboards; regulator report formats where required.
Sportsbook feed
Third-party sportsbook integrated with the shared wallet, bonuses and reporting.
Custom modules
Anything with an API and a clear specification. Scoped and quoted after a short discovery.
05API access for operators
Your data and your platform, reachable from your own tools.
Operators are not locked into the back office. The same API the front-end uses is available to your team, with documentation and a sandbox to build against.
What you get on every deployment
- REST API for players, wallets, transactions, bonuses, games and reporting, with token-based auth and per-key permissions
- Webhooks for registration, deposit, withdrawal, KYC change, bonus and game events, with signed payloads and retries
- Sandbox environment with test players, test PSPs and demo game content, separate from production
Documentation and ownership
- Documentation with request and response examples, rate limits and a changelog; breaking changes announced in advance
- Turnkey deployments additionally get database and infrastructure access in your own cloud or data centre
- Role-based keys so an agency or BI vendor sees reporting without touching payments or player data
06Risks and controls
What goes wrong in migrations, and the control for each.
Risks and how we handle them. Each control is written into the migration plan, so it is checked off rather than remembered.
Data loss
Source export kept read-only and retained through hypercare. Every import reconciled against the source: player counts, balance totals per currency, open bonuses. No cut-over without a signed reconciliation.
Downtime window
Agreed in writing, scheduled for your lowest-traffic hours. Rehearsed on the dry run so the real window is a known duration. Rollback plan: the old platform stays intact until hypercare ends.
Player re-verification
KYC level and documents transfer where the provider and your licence allow. Where they do not, only the affected segment is asked to re-verify, with messaging prepared before cut-over and withdrawals not blocked unnecessarily.
SEO continuity
Full URL inventory from the old site, one-to-one 301 redirects shipped at cut-over, titles and meta preserved on equivalent pages, sitemap resubmitted, crawl errors monitored during hypercare.
Payment gaps
PSP re-signing started on day one. Where a PSP cannot be ready for cut-over, an alternative is live for the gap and the original is added when its contract clears.
Scope creep
A front-end redesign or new markets can run in parallel, but they are a separate line in the plan with their own dates, so the migration itself stays measurable.
07Questions
What operators ask before moving.
Migration questions. Bring a sample export to the call and we can give you a more exact answer.
Book a 30-minute callHow long does a casino migration take?
Will players notice the migration?
Can we keep our PSP and KYC providers?
Do we get API access to our own platform?
What happens to our search rankings?
08Get a quote
Migration
Dated plan
Send us a sample export and we will map it.
A short discovery to see your current platform, then a dated migration plan with the cut-over window, what will need re-signing and a fixed price for the migration itself.
- Reply within one business day, from an engineer
- Field-by-field mapping after a sample export
- Dated plan with the PSP re-contracting on it
- NDA on request, no newsletters