How to migrate tokens after a rebrand? (Swap Guide)

Understanding Token Migration Mechanics

1. Token migration following a rebrand is not a simple name change—it involves a deliberate, on-chain transfer from an old contract address to a new one. This process requires users to interact with a designated migration smart contract deployed by the project team.

2. The migration window is strictly time-bound. Once the cutoff block height or timestamp passes, the old tokens become permanently non-migratable and may lose all utility or liquidity support.

3. Users must hold their legacy tokens in a self-custodied wallet—exchanges rarely handle migrations automatically, and centralized platforms often delist the old token before or during the swap period.

4. Gas fees on the target chain are mandatory for every migration step. Failure to account for fluctuating ETH or BNB costs can cause transaction reverts or stuck approvals.

5. A valid migration signature or proof-of-hold verification may be required. Some protocols issue claimable Merkle proofs based on snapshot balances taken days or weeks prior to launch.

Wallet Preparation Checklist

1. Verify that your wallet supports the chain where the new token resides. If migrating from ERC-20 to BEP-20, you must have BNB in your wallet for gas—not ETH.

2. Ensure your wallet has approved the legacy token’s contract to spend your balance on the migration interface. Unapproved tokens will fail the swap even if funds are present.

3. Back up your seed phrase before initiating any interaction. Malicious clones of official migration sites are common during rebrands—always verify the domain and contract addresses via official Discord announcements and GitHub repositories.

4. Disable browser extensions like MetaMask pop-up blockers or ad filters when using the migration dApp. These can suppress critical confirmation modals and lead to accidental loss.

5. Confirm that your wallet displays the correct legacy token balance before proceeding. Imported custom tokens sometimes show zero due to incorrect decimals or wrong contract address input.

Step-by-Step Swap Execution

1. Navigate to the verified migration portal listed in the project’s official blog post—not third-party aggregators or Telegram links.

2. Connect your wallet and confirm it’s set to the correct network—migrating on Polygon while holding tokens on Ethereum Mainnet yields irreversible failure.

3. Enter the amount of legacy tokens you wish to migrate. The interface will display the exact quantity of new tokens expected, including any fixed ratio or bonus adjustments announced pre-rebrand.

4. Approve the legacy token contract first. Wait for that transaction to fully confirm before clicking “Migrate” or “Swap.” Skipping approval results in immediate revert.

5. Sign the migration transaction. Monitor its status on Etherscan or BscScan using the provided hash. Do not refresh or close the page until confirmation appears.

Risks and Common Pitfalls

1. Submitting transactions to fake migration contracts remains the top cause of total loss—over 72% of reported incidents in Q2 2024 involved phishing domains impersonating official tools.

2. Sending legacy tokens directly to the new contract address instead of using the authorized dApp triggers permanent lockup with no recovery path.

3. Using hardware wallets without enabling contract data signing prevents proper transaction parsing—many Ledger and Trezor users abort swaps mid-process due to unrecognized data fields.

4. Migrating partial balances may trigger anti-dusting logic in some new contracts, causing the entire batch to be rejected if below minimum threshold.

5. Holding migrated tokens on exchanges that haven’t integrated the new contract leads to missing deposits—even after successful on-chain swap, assets won’t appear unless the platform manually adds support.

Frequently Asked Questions

Q: Can I migrate tokens using Trust Wallet’s built-in DApp browser?A: Yes—if the migration site is compatible with WalletConnect and the wallet’s network settings match the required chain. Always double-check contract addresses manually before signing.

Q: What happens if my legacy token was staked in a DeFi protocol during the migration window?A: Staked tokens are generally ineligible unless unstaked before the snapshot. Most rebrands require liquid, transferable balances at the time of the snapshot.

Q: Is there a way to verify the authenticity of the new token contract before migration?A: Official contract addresses are published on the project’s GitHub repository and verified on Etherscan/BscScan. Look for the blue checkmark and cross-reference bytecode hashes.

Q: Do wrapped versions of the legacy token qualify for migration?A: No. Only native, non-wrapped tokens held directly on the original chain are accepted. wTOKEN, renTOKEN, or bridged variants are excluded from eligibility.