Withdraw, bridge the assets, then deposit into the new vault. The key is to check what the new vault accepts before you move funds, since the destination may use a different token or chain.
Check the new vault before withdrawing
Confirm that the new vault is the one you want to use and that it accepts the assets you expect to receive. A vault is a contract that pools deposits and puts them to work; its shares represent your portion of that pool. A chain is a separate blockchain, so assets and vault shares on one chain do not automatically work on another.
Check the new vault’s accepted deposit token, withdrawal rules, and current status in its own documentation. Kraken’s DeFi guide also advises checking the network, asset, and withdrawal terms before depositing. If the old vault has a withdrawal delay, queue, or exit fee, account for it before starting. You may have time out of the market while waiting for funds to become available.
For example, suppose your old vault is on Ethereum and the replacement is on a layer 2, a network built to process transactions alongside Ethereum. The new vault might accept a particular stablecoin, while your withdrawal returns a different asset. You need to know whether a swap is required before depositing.
Move the capital in five steps
Move the released assets in order, and confirm each stage before committing funds to the next one. Manta bridge is a cross-chain bridge and swap service; how Manta bridge moves funds across chains explains its role in moving assets between networks. The same basic plan applies to any bridge and swap service.
- Read the new vault’s deposit requirements. Write down its chain and accepted token. Check whether it requires a minimum deposit or has a deposit cap. A cap limits how much the vault can accept, and it may fill before your withdrawal completes.
- Withdraw from the old vault. Use the vault’s normal withdrawal process and wait until the assets arrive in your wallet. You usually receive the underlying tokens, not transferable shares for the new vault. A withdrawal queue can delay this step, so do not start a timed migration until you know how long exits may take.
- Bridge and swap only what is needed. Select the source chain where your withdrawn assets are held and the destination chain where the new vault lives. If the vault accepts a different token, the bridge-and-swap flow can move the assets and exchange them in one transaction. Compare the estimated output with the amount the vault needs; price impact and slippage can reduce what arrives. Slippage means the final swap price differs from the quoted price.
- Keep enough for destination gas. Gas is the network fee for processing a transaction. You may need a small amount of the destination chain’s fee token to approve and deposit your assets after they arrive. If you bridge every token you own, you could be unable to complete the deposit.
- Confirm receipt, then deposit. Wait for the transfer to complete and check the destination wallet for the correct token and amount. Match the destination chain and token to the vault’s requirements before depositing. Afterward, confirm that the wallet or vault record shows new shares; those shares are evidence your deposit entered the pool.
Bridge transfers add smart-contract and transfer risks, and Ethereum.org notes that bridge designs can differ in their security assumptions. If the destination token or amount is wrong, stop and resolve that before depositing; vault shares are not a substitute for the missing asset. For a large position, moving a small test amount first can reveal a wrong network or token before you move the rest.
Budget for the old vault’s exit costs, the bridge or swap quote, network fees on both chains, and the new deposit. These costs vary with the route and network demand, so check the current estimates before withdrawing. Move farming capital only after the new vault’s accepted asset, exit timing, and destination requirements are clear.