Move without rebuilding the business

In most cases yes, and the assessment comes first. What matters is what your current provider will export, in what format, and what your contract permits.

Player identities, balances, bonus states, verification history and transaction records each need a defined destination on the platform, and some of them need decisions from you about how history is represented. We would rather tell you early that something cannot move cleanly than discover it during a cutover weekend.

Balances migrate as balances, with real, bonus and locked amounts kept apart rather than merged into one figure, because merging them destroys the terms attached to the bonus part.

Active bonuses need a decision from you: carry the remaining wagering requirement across, settle it before the move, or honour it manually. Each option has a player communication attached. We plan that before the cutover, and the ledger records the migration itself so the opening position is auditable.

Not automatically, but it depends on what you can bring with you. If your existing verification records can be exported with enough evidence attached, they can be represented in the player's compliance tier on the platform.

Where the evidence is thin or the format cannot be reconciled, the honest answer is that some players will need to be verified again. It is better to know which ones before the move than to find out at their first withdrawal.

Four things. A description of your current stack and which parts you intend to keep. A sample of the data you can export, or at least the schema. Your contractual position with the incumbent, including notice and extraction rights. And your licence and market footprint, because that decides what is possible rather than what is convenient.

With those we can tell you what moves cleanly, what needs rebuilding, and roughly how long it takes.

On the Turnkey Platform route you keep your own payment relationships, because you hold the licence and the operation. On White Label, payments run through the orchestration that sits under our licence, which is part of what the route provides.

If you have an existing provider you need to keep, raise it in discovery. The answer depends on the route, the market and the provider, and we would rather scope it properly than agree in principle and renegotiate later.

In the deployment your brand runs on, hosted through our infrastructure partner CloudWalker. On a dedicated deployment that is your own environment, and where it sits is a decision we take with you rather than a default we apply, because residency is often driven by your licence and your target markets.

On shared deployments, brands remain separated at the identity and account level. If residency is a hard requirement, bring it to discovery early, because it shapes the deployment plan.