What Happens When a Blockchain Game Migrates to Another Chain?

“The game moved to another blockchain” sounds like one event. In practice it can mean several very different things — cards bridged to a new network, balances moved to a different chain than the assets, contracts redeployed while old ones freeze, or a game shut down entirely while its assets were absorbed into a wider ecosystem. In the NFT Video Games registry, a game’s current chain and its migration history are recorded separately, because the distinction matters when you’re checking whether an asset you own is still usable.

What “migration” can mean#

A blockchain game is not a single object on a chain — it’s a stack: game contracts, player-owned NFT assets, token balances, marketplace infrastructure, and off-chain gameplay systems. “Migration” can touch any subset of that stack:

• Full game migration — the game itself redeploys or re-points to a new chain and play continues there.
• Asset migration — NFTs are bridged, redeemed, or re-minted on a new chain while the game logic stays put (or is already gone).
• Token/balance migration — currency balances move to a different network, sometimes on a different chain than the NFTs.
• Partial migration — only some layers move; the rest are frozen, deprecated, or left on the old chain.
• Ecosystem migration — assets transition into a successor product or a publisher’s wider platform rather than a new chain deployment of the same game.
• Chain expansion — the game adds support for another chain without abandoning the original; this is not a migration at all, though it is often announced like one.

Why projects migrate#

The documented reasons in the registry are mundane rather than dramatic: a chain provider sunsets infrastructure (StarkEx, an Avalanche subnet), a studio consolidates onto a chain with lower fees or a bigger user base, a licensing loss forces an asset transition, a game’s entire platform collapses and it must replatform to survive, or a game relaunches under new ownership on a different network. Migration is usually infrastructure maintenance, not a verdict on a game’s health — and not a promise about it either.

What can move — and what can stay behind#

Different layers move by different mechanisms, and they don’t always move together:

• NFT assets can be bridged, redeemed for new tokens, or re-issued on the destination chain. The old-chain copies may remain valid, may be frozen, or may become inert records of what you used to own.
• Token balances typically bridge or are credited on a new chain — sometimes to a different chain than the NFTs, as Sorare’s cards→Solana / balances→Base split shows.
• Game contracts don’t “move” — new deployments go live on the destination chain and the old ones are frozen or deprecated.
• Marketplace infrastructure may shift with the assets (Blankos NFTs moved into the Polkadot-based Mythical marketplace) or disappear with the game.
• Gameplay progress — levels, inventories, progression — is the layer least likely to carry over verbatim; migrations frequently reset or re-scope it.

Game migration vs asset migration vs token migration#

The most important distinction for a player: whether the game moved, or only the assets did. A game migrating (Aavegotchi to Base) means play continues on the new network. Assets migrating without the game (F1 Delta Time’s cars into the REVV Motorsport ecosystem) means you may still hold usable items — inside a different product, not “the same game on a new chain.”

What players should verify#

When a project announces a migration, check before assuming anything moved:

• Which chain is canonical now — where new play, minting, and trading actually happen.
• Whether old-chain assets still function — usable in-game, tradeable on the old marketplace, or frozen records only.
• Whether you must act — claim, bridge, or re-register assets before a deadline, or whether the project airdropped/migrated them automatically.
• Dates — when the old chain support actually ends versus when the announcement was made.
• What exactly moved — NFTs, balances, contracts, marketplace — because the layers can split across chains.

Case studies from the registry#

Twenty-six registry records document twenty-three different shapes of “moved to another chain” — including two that stretch the phrase itself:

• Sorare — split migration. Per its official help center, Sorare migrated its cards to Solana and ETH balances to Base (October 2025); the legacy StarkEx rollup was frozen in June 2026 per L2BEAT. One product, three chains, and the assets didn’t all land in the same place.
• DeFi Kingdoms — infrastructure migration, game continues. Its DFK Chain subnet retired on August 28, 2026 with assets migrating to Avalanche C-Chain and an SDK provided for third-party developers; the game itself stayed live throughout.
• Aavegotchi — full ecosystem move. The project completed its Polygon → Base migration on July 25, 2025; the Geist L3 it briefly operated was wound down earlier that year.
• Undead Blocks — relaunch, not a simple move. After fading on Ethereum/Immutable, the game relaunched on Avalanche in July 2025 under new operation (Blackhole as first DEX partner), with the UNDEAD token bridged across. A relaunch is a different event from a migration even when it looks similar.
• Blankos Block Party — chain history vs. lifecycle. Originally on Mythical’s EOSIO-based chain, its NFTs migrated to Polkadot/Mythos in 2024 — while the PC game itself was sunset in December 2023. The canonical chain changed even though the game no longer runs.
• F1 Delta Time → REVV ecosystem — asset transition after shutdown. The game ceased operations March 16, 2022 after the F1 license lapsed; its assets were transitioned into the wider REVV Motorsport ecosystem (where REVV Racing runs today). This is not a game that migrated — it’s a game that ended while its assets found a new home.
• MetalCore — migration completed, game still paused. The game finished moving from Immutable zkEVM to Solana on December 17, 2024 — a real, shipped migration — then took its servers and Discord offline on March 25, 2025 “for important changes” and has not returned. The clearest counterexample to “a migrated game is a healthy game.”
• Ember Sword — three migrations, still shut down. Across seven years of development the game’s assets moved Polygon → Immutable X → Mantle before Bright Star Studios ceased operations in May 2025. The chain kept changing; the funding problem didn’t. Repeat migrations are not, by themselves, evidence of progress.
• Crypto Unicorns — the wholesale move. In June 2024 the project migrated its entire stack — roughly 250 smart contracts — from Polygon to the Xai L3 on Arbitrum, relaunching with a native marketplace and social-login wallets. One of the largest single game migrations documented, and its XAI grant ended early just four months later: even a technically clean migration doesn’t guarantee runway.
• Calamity, Zeeverse, Realms of Alurya — the forced migration. When Treasure DAO collapsed in April 2025 — killing its chain and terminating partner publishing deals without notice — its games had weeks to replatform or die. Calamity and Zeeverse landed on Ronin and are still running; Realms of Alurya completed the migration inside a week, shipped its Hunt & Mint event, then went on indefinite hiatus anyway when the funding didn’t return. Three games, one forced migration, three different outcomes — the clearest evidence that migration is what a game does to survive, not proof that it did.
• BLOCKLORDS — consolidation onto a dedicated chain, then the end anyway. In mid-2025 MetaKing consolidated heroes and progress from Base, Polygon and Immutable onto its own LORDCHAIN, retiring legacy-chain support after the migration window. A year later the game closed anyway, when the studio pivoted to an AI product: the consolidation gave it one home, not a future.
• Honeyland — the de-NFT, a migration away from chain. Under new ownership the game went offline April 1, 2026 for a full rework in which Generation bees, queens and eggs leave the chain entirely — holders deposit NFTs and receive in-game versions back via a manual ‘Migration Machine’, while only Genesis assets, passes and land stay on-chain. The only registry record of a migration whose destination is no blockchain at all.
• Benji Bananas — breach-forced token replacement, then a pass migration and a takeover. After a market-maker wallet breach stole ~20% of supply in 2023, Animoca replaced PRIMATE with BENJI 1:1; the membership pass later migrated to Base as TYBENG, and in October 2024 the pass/token layer was handed to community governance while Animoca kept operating the game. Three different events players all call “migration.”
• CryptoKitties — the vertical-integration migration. After the game that congested Ethereum in 2017, Dapper Labs built its own chain and moved its flagship to it — the 2025 Flow relaunch (Telegram game, Meowcoins) runs on infrastructure the same studio operates. The only case where a game migrated onto its publisher’s own chain and thrived.
• CryptoBlades — migration as survival tactic, twice. After the 2021 SKILL collapse on BNB Chain, the project bridged players and ~15,000 NFTs to SKALE from five chains (October 2024) for gas-free play — a documented working migration whose game is now `unknown`, adding another data point that a shipped migration is not a health signal.
• Plant vs Undead — the multi-chain sprawl. After its 2021 BSC boom and a formal “temporary break” pause in October 2024, it came back running simultaneous Year-seasons on opBNB and a Solana deployment (sPVU) in early 2025 — not one migration but the game existing on multiple chains at once, then going quiet everywhere.
• MIR4 — mainnet migration absorbed mid-service. In August 2026 the game completed the WEMIX PLAY mainnet migration after the WEMIX$ theft — rebasing DRACO/HYDRA swap pools from WEMIX$ to USDC.e — with players’ XDRACO items carried forward. A chain-level infrastructure migration the game survived without closing.
• ICE Poker — migration into a successor, no chain change. An April 2024 governance vote ended ICE Poker’s earn loop and moved the same Polygon wearable NFTs into its Poker Arcade successor — the “migration” was a product transition where the assets, not the game, continued.
• My Crypto Heroes — the end-of-life chain rebuild. Japan’s longest-lived NFT game ended its eight-year multi-chain service (Ethereum + Polygon + Oasys MCH Verse) on September 7, 2026 with a Polygon rebuild announced and wallet re-registration already open for heroes, extensions, land and soul NFTs — the rare case where the migration IS the succession plan.
• Light Nite — sidechain to L1. The earliest earn-shooter migrated its NFT economy from Liquid — a Bitcoin sidechain — to Solana in March 2022 as “Light Nite X”, keeping the sats-rewards Legacy build alive alongside it. The registry’s only documented migration off a Bitcoin sidechain.
• Wolf Game — the collector-acquisition migration. The 2021 phenomenon hopped Ethereum → Blast → a Solana token — then Pixel Vault wound down in July 2025 and collector Seedphrase bought the IP outright that September; the ecosystem is now resetting onto Abstract (June 2026). The only case where the migration is the ownership change itself — a community member becoming the publisher and carrying the game across.
• Era7 — the migration-as-euthanasia. The BNB Chain TCG closed its live version on September 30, 2023 to relaunch on GasZero’s zero-fee testnet — player data explicitly did not transfer — and the successor build is now dead too. The only documented case where a chain move functioned as the game’s ending: a migration that was really a quiet shutdown.
• Tiny Colony — the voluntary scale migration. The ant-colony management sim left Solana for Immutable X in January 2023 — a deliberate, pressure-free move for scalability and Ethereum-ecosystem reach, announced as a partnership with holders’ assets promised unchanged. The cleanest case in the set: migration as growth, not rescue.

How the NFT Video Games registry records migrations#

Each record carries a canonical chain plus a chain_detail field for exactly this nuance — “Solana (cards) + Base (balances)” for Sorare, “DFK Chain sunset → Avalanche C-Chain” for DeFi Kingdoms. Migration history is captured in the evidence notes rather than hidden by a single chain label, and every record links the dated sources behind the claim. See how we verify blockchain games for the methodology, and the registry index for every tracked record.

What a migration does not prove#

A migration is evidence of activity, not quality. A game moving to a new chain tells you nothing about whether it is playable, whether it is maintained, or whether its assets are worth anything — those are separate questions with separate evidence. Chain affiliation, like migration history, is context rather than a verdict.

A short checklist#

When you read that a game “migrated”:

• Identify which layer moved — game, assets, balances, or marketplace.
• Check whether the old chain is frozen, deprecated, or still usable.
• Confirm whether the project requires any action from asset holders, and by when.
• Distinguish a continuing game on new infrastructure from a relaunch, a successor product, or an asset-absorption after shutdown.
• Look for dated, first-party evidence — not the announcement headline, but what actually shipped.

Verified September 22, 2026 · Sources: official migration announcements per linked registry record · how we verify · the verified registry