Rebuild or Migrate? A Decision Framework for Redeploying a Brazil-Built iGaming Platform

Rebuild vs migrate igaming platform

Migrate a Brazil-built iGaming platform to another regulated market when three conditions hold: you own the source code and the right to deploy it elsewhere, the Brazil-specific parts sit in modules you can replace without touching the core, and currency, identity, tax and reporting rules live in configuration rather than in code. If the first condition fails, the contract decides the path, not the architecture. If the second or third fails, the choice is between refactoring before the move and rebuilding the affected modules or the whole platform. Whatever you decide, Brazilian player data and the Brazil compliance archive stay behind, and the Brazil-only integrations are replaced. This guide sets out the three gates in order, the Brazil coupling audit, the drivers that tip a borderline case and the white-label contract clauses to read first.

Status on 17 November 2026

Item Status Source, date checked
MP 1.394/2026 In force since 25 Sep 2026. Art. 1 prohibits the exploration, offer, intermediation and advertising of fixed-odds betting lotteries, including offers from abroad. Its validity was extended by 60 days on 9 Nov 2026 (ATCN 118/2026); the Congress page lists the extended period as ending on 4 Mar 2027 Congresso Nacional, MPV 1394/2026, 17 Nov 2026; Planalto text, last read 21 Oct 2026
Congress Joint Committee designated on 30 Sep 2026 and still awaiting installation, with no rapporteur. 99 amendments were filed by 13 Oct 2026, and five were later withdrawn. Urgency regime since 9 Nov 2026. No conversion bill published Congresso Nacional, MPV 1394/2026, 17 Nov 2026
STF ADI 8027 (lead case), ADI 8024, ADI 8028 and ADI 8035 challenge the MP, with Minister Luiz Fux as rapporteur. At the request of the Prosecutor General, Fux ordered the nationwide suspension of lower-court cases on the MP’s constitutionality until the STF rules; the order is to be referred to the Plenary. No decision suspending the MP itself and no plenary date reported STF news, 9 Nov 2026; press, 9 to 10 Nov 2026

This framework assumes the Brazilian product stays closed. If the MP is suspended, lapses or is converted with changes, our operator exit guide sets out what each scenario means for the live stack, including when to hibernate it rather than decommission it. Because Art. 1 also covers offers from abroad, a redeployed platform has to keep Brazil excluded.

Market change, not product change

Redeploying keeps the product (a casino, a sportsbook, or both) and changes the market. If you are changing the product instead, for example to skill games, PvP duels, fantasy sports or a free-to-play social casino, our guide to converting a betting platform into non-wagering products covers what to reuse, adapt and remove. If you have not chosen a path yet, our overview of formats and markets after the ban compares them.

The exit guide also lists which components are reusable in a redeployment and which stay in Brazil. This guide starts from that list and answers the next question: can the reusable part move as it is, or does it have to be refactored or rebuilt first?

Five outcomes, not two

Migrating a platform means deploying the existing codebase in a new regulated market, replacing the market-specific modules and certifying the result there. Rebuilding means producing a new platform, either custom-built or from another vendor, and carrying over only what you are free to reuse: product knowledge, designs and content whose licences cover the new market. Most real decisions sit between the two.

Outcome What happens to the code What carries over Main risk Usually chosen when
Migrate The existing codebase is deployed in the new market; Brazil-specific modules are swapped through configuration and new adapters Core platform, game and feed integrations whose licences cover the new market, tooling and runbooks Brazil logic found late, during certification All three gates pass
Refactor, then migrate Brazil logic is extracted into configuration or adapters first, then the platform is deployed The same as migrate, after the refactoring The refactoring grows into a rebuild without anyone deciding it should Ownership and modularity pass; market rules are hard-coded
Rebuild selected modules A new PAM, wallet or cashier is built next to the retained modules and switched over in stages The retained modules, often the sportsbook engine or the game integrations Two architectures running side by side for longer than planned Ownership passes; one or two core modules fail the modularity test
Rebuild or re-platform A new codebase, custom or on another vendor’s platform Product knowledge, designs, and content where licences allow Certification and integrations start from zero The code is old, undocumented or inseparable, or you have no right to reuse it
Extend with the current vendor The vendor deploys its platform for you in the new market under an amended contract Brand, front end and the vendor platform Lock-in and fee terms carried into the new market White-label or turnkey contract, and the vendor supports the destination

A sixth state, holding the Brazilian stack in hibernation while the legal position settles, is covered in the exit guide. It can run in parallel with any of the five.

The decision tree: three gates, in this order

Before the first gate, you need a destination with a licence route and a business case. Without one, the platform question is premature, because the destination’s technical standard, payment methods and reporting format decide how much of the Brazil-specific layer has to be rebuilt.

The gates run in a fixed order because each one can end the analysis. Ownership comes first because it is a question of rights, and no amount of good architecture overrides it. Modularity comes second because it decides whether replacing the Brazil-specific parts touches the core. Configuration comes last because it decides whether the replacement is mostly configuration or mostly code.

Gate Question If yes If no Evidence to check
1. Ownership and rights Do you own the source code, or hold a licence that allows you to modify, host and deploy it in the new market? Do the licences for third-party components (game content, sports data, PAM or KYC modules) cover that market? Go to gate 2 White-label or turnkey without code rights: the contract decides (extend with the vendor, negotiate an exit, or rebuild). Owned code with third-party gaps: list the components to relicense or replace, then go to gate 2 Repository access, IP and licence clauses, escrow terms, third-party licence schedules
2. Modularity Can the Brazil-specific parts (cashier, identity checks, reporting, tax) be replaced without changing the wallet, the bonus engine or the game integrations? Go to gate 3 Coupling concentrated in one or two components: rebuild selected modules. Coupling running through the core: rebuild or re-platform Service map, dependency graph, the places where wallet and bonus logic call Brazil-specific code
3. Rules and configuration Are currency, identity documents, tax, limits and reporting formats held as configuration or market adapters, rather than hard-coded in services or the database schema? Migrate: build the adapters, configure the market, certify Hard-coded logic that can be extracted: refactor, then migrate. Logic that cannot be extracted safely: rebuild the affected modules Schema review for BRL and CPF fields, a code search for market constants, an inventory of reporting jobs

Reading the tree

Passing all three gates makes migration predictable, not free. Licensing, certification and payment onboarding still start again in the destination. What the gates remove is the risk of discovering halfway through that the platform cannot move.

A failure at gate 1 is not an engineering problem. If you do not hold the rights to the code, refactoring it is not your decision to make. The white-label section below lists the clauses that decide what is possible.

Answer gates 2 and 3 from the code, not from memory. Teams that built a platform for one market tend to underestimate how far that market reaches into it. A code search for the Brazil-specific identifiers listed in the next section is a quicker and more reliable first test than an architecture workshop.

OmiSoft’s custom casino software development includes migrating iGaming platforms from legacy or closed systems to infrastructure the operator controls, covering player accounts, balances, transaction history and integrations, with controlled cutover planning. The client receives the source code and project documentation for the software delivered, and there is no platform revenue share.

The Brazil coupling audit

Gates 2 and 3 come down to one question: where does Brazil live in your platform? The audit lists the Brazil-specific elements of a platform built for the former authorised market, where each one sits when the platform is easy to move, the signals that point to a rebuild, and what replaces it in a new market.

Brazil-specific element Easy to move if it sits in Rebuild signal What replaces it in the new market
Currency (BRL) and rounding A currency code per account or per tenant, with amounts stored in minor units BRL assumed in schema columns, reports or bonus maths The destination currency or currencies, set per market
Identity and KYC (CPF checks, Brazilian KYC providers) A provider-agnostic KYC interface, with document types in configuration CPF used as a primary or unique key, or checks coded into registration and withdrawal flows The destination’s identity documents, KYC provider and age checks
Cashier (Pix and Brazilian payment providers) A payment abstraction layer with one adapter per provider Pix flows coded into deposit and withdrawal services, or wallet states tied to Pix callbacks Payment methods and providers accepted by the destination regulator and its acquirers
Regulatory reporting (Sigap) An event stream or ledger from which any report can be generated Report-specific tables and jobs that the wallet or settlement logic depends on The destination’s reporting format or real-time monitoring connection
Responsible-gambling rules Limits, cooling-off and exclusion rules held as configuration, with an adapter for the exclusion register Brazil-specific limits coded into the wallet, or exclusion checks wired to a single register The destination’s mandated limits and self-exclusion register
Tax and revenue allocation A rules or finance service that calculates per market Brazilian percentages coded into settlement or finance exports The destination’s tax base, rates and filings
Domains, geolocation and localisation Market configuration per brand Brazil-only routing and Portuguese content hard-wired into the front end The destination’s domain, geofencing and language rules
Certification evidence Change records and test evidence kept with the code Evidence held only by the lab or a former vendor A new certification against the destination’s technical standard
Brazilian player data Not part of any migration n/a A new player base acquired under the destination’s rules

Each element that sits in the rebuild column adds work. If several of them sit in the wallet, the settlement logic or the database schema at the same time, gate 2 has effectively failed, even if the platform is described as modular.

Drivers that tip a borderline case

Some platforms pass the gates on paper and still make a poor migration candidate. The drivers below do not decide the outcome on their own, but they shift a borderline case one way or the other.

Driver Points to migrate Points to rebuild How to check
Third-party licences Game content, data feeds and PAM modules licensed for the new market, or extendable to it Licences tied to Brazil or to a vendor’s platform Licence schedules; written confirmation from each provider
Data model Multi-tenant, multi-currency schema with market keys Single-tenant schema built around one market Schema review
Tests and delivery pipeline Automated tests around the wallet and settlement, repeatable deployments Manual releases, few tests around money flows CI history and test reports
Documentation and change control Architecture diagrams, change logs, past certification evidence Knowledge held by a few people or by a former vendor Document inventory
Team continuity The engineers who built the core are available The core’s authors have left without a handover Staffing plan
Support status of the stack Supported runtimes, frameworks and databases End-of-life components that a new certification would have to cover Dependency audit
Product fit with the destination The destination’s market wants the verticals the platform runs The destination needs a vertical the platform lacks, such as a sportsbook-first market for a casino-only stack Destination short-list
Sportsbook layer Odds feeds, trading and risk rules behind integration interfaces Feed and trading logic built only for Brazilian competitions and markets Feed contracts and integration code

For sportsbook stacks, assess the odds feed, trading and risk layer as a separate module. Our sportsbook software development work covers real-time odds feed integration and risk management modules, and our iGaming software development services cover the migration and modernisation of legacy platforms across PAM, wallets, payments and KYC.

White-label and turnkey platforms: a contract friction checklist

On a white-label or turnkey platform, the contract answers the code question. Contracts differ, so the only reliable answer comes from reading yours. The table lists the clauses to read first, why each matters for the decision and what to ask the vendor. It describes contract topics, not their legal effect: your counsel decides what each clause means in your case.

Clause area What to look for Why it matters for the decision What to ask the vendor
Territory and licensed markets Whether the contract names Brazil, a list of markets or specific domains Decides whether the new market needs an amendment Written confirmation of supported destinations and the terms for adding one
Source code and IP Any rights you hold in the code, your customisations or the front end; escrow arrangements and release triggers Without code rights, the options are to extend with the vendor or to rebuild Escrow terms; ownership of work commissioned for you
Data control, export and archive access Who controls player, transaction and audit data; export formats; access after termination The Brazil archive has to stay intact and accessible for the retention period, whatever you do next Archive access for the full retention period, the export format and support for continued reporting
Fees after Brazil closes Minimum monthly fees, revenue-share floors, fees for inactive brands Continuing Brazil fees change the cost of every path How the Brazil brand is treated after closure
Termination and change of law Termination rights, notice periods, any clause on regulatory change Decides when and how you can leave The vendor’s position on that clause, in writing, for your counsel
Exclusivity and non-compete Restrictions on using other platforms or building your own Can limit a rebuild or a second platform during the term Scope and duration of the restriction
Third-party contracts held by the vendor PSPs, KYC providers, game aggregators and data feeds contracted in the vendor’s name You may have to sign these yourself for the new market A list of integrations and who holds each contract
Certificates and approvals Whether certificates and lab reports were issued for the vendor’s system Certification does not follow you if it belongs to the vendor’s system Which evidence the vendor will release to a new lab or regulator
Exit assistance Transition support, knowledge transfer, handover of configuration and content Affects how a rebuild or a move to another vendor is staffed The scope of exit support and its cost basis

From the answers, three paths are realistic: extend with the vendor under an amended contract, move to a platform you control by rebuilding or re-platforming, or combine the two, staying with the vendor in the first new market while your own platform is built. None of them moves the Brazilian player base. The data clauses matter because the Brazil archive has to remain accessible, not because the data can follow you to the next brand.

When rebuilding wins even with owned code

Owning the code makes migration possible. It does not make it the better option. A rebuild, in full or module by module, is usually the stronger choice when:

  • the coupling audit finds Brazil logic in the wallet, the database schema and the bonus engine at the same time;
  • the stack includes end-of-life components that a new certification would have to cover;
  • nobody who built the core is available, and the documentation is thin;
  • the destination needs a different product mix, such as sportsbook-first or multi-brand operation, that the platform was not built for;
  • you plan several markets, and a single-tenant design would have to be copied for each one.

A partial rebuild does not have to stop the platform. Building the new core next to the retained modules and moving functions over one at a time, the approach Martin Fowler describes as the strangler fig pattern, keeps the working parts in use while the replacements are built and tested.

What neither path changes

  • Brazilian player data stays in Brazil. Player records, balances, transaction history and CRM lists remain in the Brazil compliance archive for the retention period. They are not imported into the new market, and the new brand acquires players under the destination’s own rules. The exit guide covers the retention obligations.
  • Certification starts again. Certificates and lab reports issued for Brazil stay with Brazil. Expect the destination regulator to require certification against its own technical standard. Good documentation and test evidence make that work more predictable; they do not replace it.
  • The licence comes first. The platform is assessed as part of a licence application, or through a licensed partner, in the destination. Engineering readiness does not shorten that process.
  • Payment partners assess the new business themselves. Describe the product and its money flows accurately, and let each acquirer and payment institution make its own assessment.
  • The Brazil compliance layer keeps running. Archive access and reporting continue whatever happens to the live stack, so keep them on infrastructure that does not depend on the redeployed platform.

From decision to plan

  1. Short-list destinations from regulator sources. Record each one’s licence route, technical standard, payment requirements and reporting format.
  2. Confirm rights. Code ownership, third-party licences and, on white-label platforms, the clauses in the checklist above.
  3. Run the coupling audit on the codebase. Search for every Brazil-specific element and record where it sits.
  4. Record the decision. Write down the outcome, the gate that decided it and the open risks, so the decision can be revisited if the destination or the Brazilian legal position changes.
  5. Plan the move. Map the data model for the new market, plan reconciliation and cutover, and agree the certification scope with the lab.
  6. Separate Brazil from the new deployment from day one. No job, report or CRM trigger in the new market reads from the Brazil archive.

You also may like

FAQ

Frequently asked questions

Should we rebuild or migrate our iGaming platform after leaving Brazil?

Migrate when you own the source code and the right to deploy it elsewhere, the Brazil-specific parts can be replaced without changing the core, and market rules are configuration rather than code. If you lack code rights, the contract decides the path. If the platform fails the modularity or configuration test, refactor before moving or rebuild the affected modules or the whole platform.

Can a white-label platform be migrated to another market?

Not without rights to the code. On a white-label or turnkey platform, the realistic options are to extend with the vendor under an amended contract, to move to a platform you control by rebuilding or re-platforming, or to combine the two. The territory, IP, data, fee, termination and exclusivity clauses decide which is possible; review them with your counsel.

Can we move our Brazilian players to the new market?

No. Player records, balances, transaction history and CRM lists stay in the Brazil compliance archive for the retention period. The redeployed platform starts with players acquired under the destination's own rules, and it has to keep Brazil excluded, because MP 1.394/2026 also covers offers made from abroad.

Do Brazilian certifications carry over to a new market?

No. Certificates and lab reports issued for Brazil stay with Brazil, and the destination regulator will expect certification against its own technical standard. Documentation, change records and test evidence from the Brazilian certification make the new work more predictable.

Which Brazil-specific components have to be replaced in any migration?

Typically the BRL currency handling, CPF-based identity checks and Brazilian KYC providers, the Pix cashier, Sigap reporting, Brazil-specific responsible-gambling rules and exclusion checks, tax and allocation calculations, and Brazil-only domains and localisation. How much work that takes depends on whether they sit in configuration and adapters or in the core code and schema.

Is a partial rebuild an option?

Yes. If one or two core modules, such as the wallet or the cashier, fail the modularity test, they can be rebuilt next to the retained modules and switched over in stages. This keeps the working parts in use while the replacements are built and tested.