How to Move Crypto to a New Wallet Safely

Moving crypto to a new wallet is one of the most common tasks in self-custody—and one of the easiest to get catastrophically wrong. Maybe you are upgrading from a phone app to a hardware wallet, consolidating scattered funds, or escaping a wallet you fear is compromised. Whatever the reason, the same hard truth applies: on-chain transactions are irreversible. There is no support line to reverse a transfer sent to the wrong address or over the wrong network. The good news is that a disciplined, test-first process makes the whole thing safe and boring, which is exactly what you want.

This guide walks through that process step by step, then covers the special case of leaving a wallet you suspect is compromised. The principles are the same whether you are moving to a hardware wallet, a mobile app, or a fresh browser wallet.

Before you move anything: prepare the destination

The single most important preparation is your new wallet’s recovery phrase (seed phrase). Set up the new wallet, let it generate its phrase offline, and back it up properly before a single coin moves. If you skip this and something happens to the device, the funds you just transferred are gone. Our guide on how to back up a seed phrase covers doing this correctly.

Also confirm the new wallet is genuine. Fake wallet apps and cloned sites exist specifically to capture your funds or your phrase. Install only from a verified source and confirm authenticity using the steps in how to verify a wallet app is genuine. Never, ever type any seed phrase into a website.

The core process, step by step

Here is the safe sequence. It looks slow; the slowness is the point.

1. Copy the receiving address from the new wallet. In the new wallet, select the asset and network you plan to use and copy its receiving address. Do not type an address by hand—ever.
2. Verify the address character by character. Paste it into the sending (old) wallet, then compare the first five and last five characters against the new wallet’s display. This defends against clipboard-hijacking malware, which silently replaces a copied address with an attacker’s. See what is clipboard-hijacking malware for how this attack works.
3. Match the network on both ends. Confirm the sending network and the receiving network are the same. Sending an asset over a network the destination does not support is one of the most common ways beginners lose funds permanently.
4. Send a small test transaction. Move a small amount first. Wait for it to confirm on-chain and actually appear in the new wallet’s balance. This proves the address, asset, and network are all correct.
5. Move the rest. Once the test lands, transfer the remaining balance. If you hold several different assets, treat each one as its own transfer and re-verify the address and network each time.

Why the test transaction is non-negotiable

A test transaction is cheap insurance against irreversible loss. If any detail is wrong—a swapped address, a mismatched network, the wrong asset—you find out having risked only a few dollars instead of your entire holding. The confirmation step matters too: do not assume a transaction “went through” because the old wallet said sent. Wait until the funds visibly arrive in the new wallet, and if in doubt, look the transaction up on a block explorer and confirm it reached the expected number of confirmations before treating it as final.

Do not carry the seed phrase across

A frequent misconception is that “moving” a wallet means importing your old seed phrase into the new app. It does not. Each wallet has its own recovery phrase, and moving funds is simply an on-chain transfer between addresses. Importing an old seed into a new wallet does not move anything—it just gives that app control of the same old keys. Worse, prompts to “restore” or “migrate” by entering a seed phrase are a classic phishing pattern. Keep the phrases separate, and only ever enter a seed into official, verified software when you genuinely intend to restore that specific wallet.

If the funds are coming from an exchange

Many first moves are not wallet-to-wallet but exchange-to-wallet, and this introduces a few extra wrinkles worth naming. On an exchange you are withdrawing from an account the exchange controls, so you will typically paste your new wallet’s address into the exchange’s withdrawal form, choose a network, and confirm. The same rules apply—copy-paste the address, verify its characters, match the network, and send a test amount first—but pay special attention to the network dropdown, because exchanges often support many networks for the same asset and default to whichever is cheapest for them, not whichever your wallet expects. Exchanges may also impose withdrawal minimums, flat fees, and short holds for security review; none of these are cause for alarm, but they mean your test withdrawal might carry a fixed fee that feels large relative to the test amount. That is the price of confirming everything works before you move the bulk.

One more habit: confirm the withdrawal completed by looking it up on a block explorer using the transaction hash the exchange gives you, and wait for it to show as confirmed before assuming success. “Processing” on an exchange dashboard is not the same as “confirmed on-chain.”

Clean up what you leave behind: token approvals

If you are retiring the old wallet—especially for security reasons—moving the coins is only half the job. Over time, wallets accumulate token approvals: permissions you granted to smart contracts to move specific tokens on your behalf. These do not expire on their own. If any approved contract is later exploited, it could pull approved tokens from an address that still holds them. Before fully abandoning a wallet, review and revoke stale approvals. Our guide on how to revoke token approvals shows the process, and token approvals: the risk nobody explains explains why they matter more than most people realize.

Getting the network and asset details right

Beyond the address itself, two technical details cause most preventable losses. The first is the network. The same token can exist on several networks, and each has its own version of your receiving address’s context. Sending a token over a network your destination wallet does not watch—or that the token does not natively exist on—can leave funds stranded or unrecoverable. Always confirm that the network selected when sending exactly matches the one shown for the receiving address. The second is the asset and its contract. If you are moving a token rather than the chain’s native coin, make sure the new wallet recognizes that specific token; you may need to add its contract address manually so the balance displays. A hidden balance is not a lost balance, but confirming visibility is part of a clean move.

Timing is a smaller but real consideration. Fees rise and fall with network demand, so a non-urgent transfer can cost noticeably less at a quieter time. Never let a desire to save on fees tempt you into skipping the test transaction, though—the few cents saved are trivial next to the amount at risk.

The special case: escaping a compromised wallet

If you believe your keys are exposed, the calculus changes. Assume an attacker may be watching the address and ready to sweep incoming funds or contest your moves. Work from a clean, uninfected device and a brand-new wallet whose seed phrase has never touched the compromised machine. Move the most valuable and liquid assets first. Be aware that assets requiring an on-chain approval to move can be raced by an automated drainer, so environment and speed both matter. Once done, treat the old seed phrase as permanently burned—never reuse it, and never store new funds there.

A quick pre-send checklist

• New wallet’s recovery phrase is backed up and stored offline.
• Receiving address was copy-pasted and verified character by character.
• Sending and receiving networks match exactly.
• A test transaction was sent and confirmed to arrive.
• For a retired wallet, token approvals have been reviewed and revoked.

After the move: verify and monitor

Finishing the transfer is not quite the finish line. Take a moment to confirm every asset you intended to move now shows in the new wallet, adding any token contracts manually if a balance is not displaying. If you moved from a wallet you are keeping, note that leaving small “dust” amounts behind is normal and usually not worth the fee to sweep. If you moved away from a retired or suspect wallet, set that address aside mentally—do not send anything back to it, and do not enter its seed phrase anywhere ever again. Finally, record the new wallet’s recovery-phrase backup location somewhere you will actually remember, because the most common long-term loss is not theft but simply losing access to a correctly funded wallet.

None of these steps is difficult, but skipping any one of them is how people turn a routine transfer into an irreversible loss. Slow down, verify twice, and let the test transaction do its job. For more on protecting funds once they arrive, explore the wallets hub.

Sources

• Ethereum security and scam prevention — ethereum.org
• Ethereum wallets — ethereum.org
• How to revoke token approvals — Revoke.cash
• Moving your funds — MetaMask Support