Launch week, worst case: the new contract is live, but one exchange still accepts the old token, a wallet shows the wrong address, and staked holders have no way to claim. That’s a split migration, and deploying the new asset doesn’t prevent it.

Our new guide starts with the question to answer before you announce any date: how will every eligible holder receive the right asset, through the right route, exactly once?

Five assumptions that split migrations

  • “The snapshot freezes the old token.” It doesn’t. A snapshot records state at a chosen point; it doesn’t stop transfers. If Alice is allocated from the snapshot and Bob can also swap the 100 OLD she sold him, the project pays twice.
  • “The explorer holder list is our distribution list.” It shows addresses, not always the people entitled to the funds. Exchanges, pools and contracts can hold tokens for many users, so a blanket airdrop can miss beneficiaries or credit the wrong recipient.
  • “A 1:1 swap keeps our price and our chart.” The ratio only sets how many new units replace eligible old units. It doesn’t guarantee price, liquidity, rankings or price history on trackers, so don’t promise your community an unchanged chart.
  • “One exchange confirmed, so the rest will follow.” A notice from one venue doesn’t establish support anywhere else. The guide’s checklist asks every exchange to confirm support, funding cutoffs, trading, accounting, reopening and exceptions in writing.
  • “If something goes wrong, we’ll roll it back.” Completed claims, burns and third-party settlements may be irreversible. A tested stop-and-recovery plan is worth more than an assumed undo button.

What’s inside the guide

  • Four scenarios with different scopes: a new contract, a move to a mainnet, a second network, or a proxy upgrade that may not require holders to move at all
  • A holder migration matrix for personal wallets, exchanges, liquidity pools, staking, vesting and bridges, with the main risk to block in each, from paying the same entitlement twice to accidentally unlocking funds that are still under vesting
  • Snapshot, eligibility and swap-ratio rules, including why the ratio has to stay separate from decimals
  • Liquidity and trading pairs as a separate workstream, because an old DEX pool doesn’t automatically become a market for the new asset
  • What to submit to CoinGecko, CoinMarketCap, wallets and explorers, and why a ticket, a logo and a live price are different milestones
  • A fill-in announcement template and anti-scam checks your holders can actually use
  • A migration register and a pre-launch checklist that ends with a stop plan

Read it before you announce a migration date, not after:

Token Migration Guide: Moving to a New Contract or Mainnet

If your migration involves a new Tokpie market or destination network, the final section lists what to bring to our team: asset identities, holder treatment, ratio, proposed schedule and test evidence.

Founders who’ve already migrated: what took longest to line up — exchanges, trackers and wallets, or LP, staking and vesting balances?