Moving Liquidity When a Pool Changes Chains
When a pool moves chains, liquidity usually must be withdrawn, bridged and added again; check the new pool, token addresses, fees and migration terms first.
The Chain Times Desk3 min read

When a liquidity pool moves to a new chain, you usually need to withdraw your position on the old chain and add it to a pool on the new one. The pool’s assets and its liquidity-provider (LP) position do not move automatically. The change can leave the old pool with less liquidity, while the new pool may have different fees, rules or token versions.
What happens to liquidity when a pool changes chains?
A pool is a smart contract on a specific chain, so a new pool on another chain is a separate contract. If you hold a position in the old pool, it remains there until you withdraw it or the project’s migration process changes it. For a fuller explanation of how Rango bridge routes move assets between chains, see this guide to Rango bridge routes for cross-chain transfers. Moving the tokens is one step; you still need to deposit them into the new pool.
Check the project’s announcement for what is changing and when. Some projects keep the old pool open while users migrate. Others may reduce incentives or stop supporting it. A pool’s displayed name is not enough to confirm it is the right destination: check the chain, contract address and token pair.
How do you move your position?
In most cases, the process has three parts: withdraw from the old pool, move the assets to the new chain, then add liquidity to the new pool. The exact steps depend on the pool design and the project’s instructions. A basic checklist is:
- Confirm the new chain, pool address, token pair and migration deadline from the project’s official channels.
- Withdraw your position and claim any fees or rewards available under the pool’s rules.
- Bridge or otherwise transfer the required tokens, keeping enough of the new chain’s native token to pay transaction fees.
- Review the new pool’s deposit terms and confirm the amounts before adding liquidity.
If the pool uses concentrated liquidity, your position may be an NFT, a token that records a specific price range and amount of liquidity. That position does not become a new-chain position by bridging the NFT. You may need to close it, collect its assets and open a fresh position with the new pool’s interface.
What should you check before adding liquidity?
Confirm that the tokens arriving on the new chain are the versions accepted by the pool. A bridged token can have a different contract address from a native token with the same ticker. A mismatch can stop a deposit or leave you holding an asset the pool does not accept.
Compare the new pool’s fees, incentives and liquidity depth with the old one. Lower depth can mean more price impact for trades, while a new fee tier or price range can change how a position earns fees. For most users, following the project’s stated migration steps is simpler than choosing a route and pool independently, but check every token and destination before confirming. Once the assets are in the new pool, monitor that position on its own chain.