How to Migrate to a New Wallet Without Losing Funds

Migrating to a new wallet safely means generating a fresh wallet with its own new seed phrase, transferring assets over deliberately and carefully, and — critically — revoking outstanding token approvals on the old wallet, rather than simply abandoning it and assuming the funds and permissions associated with it are no longer a concern.

Wallet migration happens for many reasons: upgrading to a hardware wallet, switching software wallet providers, recovering from a suspected compromise, or simply consolidating a sprawling collection of wallets into a more organized setup. Whatever the reason, the process carries real risk if rushed.

Why you should generate a new seed, not reuse the old one

If you're migrating specifically because of a suspected security issue with the old wallet — a phishing incident, a device compromise, or simply wanting a fresh start — the new wallet should use an entirely new seed phrase generated independently, not just a new account derived from the same compromised seed. Reusing a potentially exposed seed, even to create a "new" address, doesn't actually isolate you from whatever risk prompted the migration, since BIP-32 derivation means every address from that seed is exposed if the seed itself is compromised.

Step-by-step migration checklist

1. Set up the new wallet first, completely, before touching the old one. Generate the new seed phrase, back it up physically in a secure location, and verify the backup before moving any funds.
2. Test with a small transfer. Send a small amount to the new wallet's address and confirm it arrives correctly before transferring larger amounts.
3. Transfer the bulk of funds once the small test is confirmed successful, ideally token by token or in batches if you hold many different assets, rather than assuming a single transfer covers everything correctly.
4. Move any staked or locked positions carefully. Some positions (staking, liquidity pool deposits, lending positions) may need to be unwound or withdrawn before they can move, rather than simply transferring a token that represents a position — check each protocol's specific process.
5. Revoke token approvals on the old wallet. This is the step most commonly skipped, and it matters: an old wallet with lingering, unrevoked approvals to various contracts remains a risk if any of those contracts are later exploited, even though the wallet itself may feel "retired." Use an approval-checking tool to review and revoke unnecessary approvals.
6. Disconnect the old wallet from all connected dApps and WalletConnect sessions, both for cleanliness and because some session-based permissions can otherwise linger.
7. Update any records, bookmarks, or automation (like recurring deposit addresses on exchanges) that reference the old wallet's address, so future transfers don't accidentally go to the retired wallet.
8. Retain the old wallet's seed phrase securely for a period rather than immediately destroying it, in case you discover a missed asset or position later — but plan to eventually retire it properly once you're confident everything has moved.

Common migration mistakes

Mistake	Consequence
Skipping the small test transfer	Risk of a larger transfer going to a mistyped or unintended address
Forgetting to revoke old approvals	Old wallet remains a latent risk if an approved contract is later exploited
Not accounting for staked/locked positions	Assets can be left stranded or require unwinding a position after the fact
Destroying the old seed phrase too soon	No way to recover a forgotten or overlooked asset left behind
Reusing a potentially compromised seed for the "new" wallet	Migration doesn't actually solve the underlying security concern

Migrating due to a suspected compromise

If migration is prompted by a suspected compromise — a phishing incident, a malware infection, or exposure of the seed phrase — treat it with more urgency than a routine upgrade. Move funds as quickly as is safely possible (still using a small test transfer first if time allows), assume the old wallet's seed phrase is fully known to an attacker, and don't reuse any part of the compromised setup, including derived addresses, in the new wallet.

Migrating between wallet types

Migration often coincides with moving between fundamentally different wallet types — for example, moving from a browser extension wallet to a hardware wallet, or consolidating several wallets into a more deliberate structure as discussed in organizing multiple wallets. The same core checklist applies regardless of the specific wallet types involved: new seed, small test transfer, careful handling of any locked positions, and revoking old approvals.

Bottom line

Safe wallet migration means generating a genuinely new seed phrase, moving funds deliberately with a small test transfer first, carefully handling any staked or locked positions, and — the step most often overlooked — revoking outstanding token approvals on the old wallet before considering it retired. Rushing any of these steps, particularly the approval revocation, can leave real risk behind even after the funds themselves have successfully moved.