Chain Migration Checklist
A complete step-by-step checklist for safely moving your crypto assets between blockchains. 16 tasks across 4 phases to ensure nothing goes wrong.
Before You Start
Cross-chain transfers are irreversible. Sending tokens to the wrong chain or using the wrong bridge can result in permanent loss. Follow every step in this checklist, especially the test transaction step. Rushing is the #1 cause of migration errors.
Pre-Migration Planning
Verify wallet supports destination chain
Not all wallets support all chains. MetaMask supports most EVM chains, but you may need to add custom RPC endpoints. Solana, Cosmos, and other ecosystems need separate wallets.
Wallet Compatibility Checker →Check token availability on destination chain
Not all tokens exist on every chain. Verify that your token has liquidity on the destination chain. Some tokens use different contract addresses per chain.
Research bridge options and compare fees
Compare at least 2-3 bridges for your route. Check fees, speed, security model, and whether the bridge is audited. Aggregators like Li.Fi can find the best route automatically.
Bridge Comparison →Budget for gas on both chains
You need native tokens (ETH, MATIC, etc.) on both source and destination chains. Check current gas costs before bridging to avoid being stranded without gas.
Gas Estimator →Security Preparation
Verify you're on the official bridge website
Bookmark the official bridge URL. Never click bridge links from search ads, Discord DMs, or social media. Verify the URL character by character.
Check recent bridge security status
Before using any bridge, check if there have been recent exploits or security incidents. Bridges are high-value targets for hackers.
Network Health →Set specific token approval amounts (not unlimited)
When the bridge asks to approve tokens, set a specific amount rather than unlimited. This limits your exposure if the bridge contract is compromised.
Signature Decoder →Back up wallet and record all transaction hashes
Before any migration, ensure your seed phrase backup is current. Record every transaction hash during the migration for troubleshooting.
Execute Migration
Send a small test transaction first
Bridge a small amount ($5-$20) to verify the route works correctly. Wait for full confirmation before bridging larger amounts.
Bridge main assets in batches (not all at once)
Split large migrations into 2-3 batches. This limits loss if something goes wrong mid-migration. Wait for each batch to confirm before sending the next.
Bridge native gas tokens first
Ensure you have gas on the destination chain before bridging other tokens. Without gas, you can't do anything with your bridged tokens.
Monitor each transaction to completion
Don't close your browser or assume the bridge worked. Watch each transaction through to final confirmation. Most bridges have a status page for tracking.
Post-Migration Verification
Verify all tokens arrived on destination chain
Check your wallet on the destination chain's block explorer. Confirm the token amounts match what you sent minus bridge fees.
Revoke bridge token approvals
After migration is complete, revoke the token approvals you granted to the bridge contract. This is a critical security step.
Add destination chain tokens to wallet display
You may need to manually add token contract addresses to your wallet to see them. Get addresses from official sources (CoinGecko, project docs).
Test a small interaction on destination chain
Make a small swap or transfer on the destination chain to verify everything works. This confirms your wallet, gas, and tokens are all functioning.
Common Migration Routes
| Route | Best Bridge | Cost | Time |
|---|---|---|---|
| Ethereum → Arbitrum | Canonical / Across | $0.50–$3 | 1–10 min |
| Ethereum → Base | Canonical / Across | $0.50–$3 | 1–10 min |
| Arbitrum → Optimism | Across / Hop | $0.30–$1 | 1–5 min |
| Ethereum → Solana | deBridge / Wormhole | $1–$5 | 2–10 min |
| Any L2 → Ethereum | Canonical (7 day) / Across | $1–$5 | 1 min–7 days |
| Ethereum → zkSync | Canonical / Across | $0.50–$5 | 1–10 min |
This content is for educational purposes only and does not constitute financial, tax, or legal advice. Always consult a qualified professional for advice specific to your situation.
Frequently Asked Questions
How long does cross-chain migration take?
It depends on the bridge type. Liquidity bridges (Across, Hop) typically complete in 1-5 minutes. Canonical bridges (Arbitrum, Optimism official bridges) take 10 minutes for deposits but 7 days for withdrawals back to Ethereum. Plan your timing accordingly.
Can I lose funds during chain migration?
Yes, though it's rare with established bridges. Risks include: sending to the wrong network, using a malicious bridge, or bridging a token that isn't supported on the destination chain. Always verify the bridge URL, send a test transaction first, and confirm token support before bridging large amounts.
Do I need to pay gas on both chains?
Yes. You need native gas tokens on both the source chain (to initiate the bridge transaction) and the destination chain (to interact with dApps after bridging). Some bridges include a small gas airdrop on the destination chain, but don't rely on this for larger amounts.