Overview
Moving a software wallet from one app to another is a common task for DeFi users. This guide explains practical, tested ways to: how to import Trust Wallet to MetaMask, how to add Coinbase Wallet to MetaMask, how to import wallet to MetaMask with recovery phrase, and how to import private key MetaMask. I’ve imported wallets across mobile and desktop dozens of times. The goal here is measurable: complete the transfer while minimizing exposure of your seed phrase and private keys.
(Yes, this is about hot wallets and risk trade-offs.)
If you want the basics of seed backups first, see [/seed-phrase-backup-recovery]. For step-by-step restore details on other workflows, check [/import-and-restore-wallet].
Core concepts: seed phrase vs private key
- Seed phrase (recovery phrase): a human-readable set of words that deterministically derives a sequence of private keys using standard derivation paths. Restoring a seed phrase typically regenerates all derived accounts that follow the same path.
- Private key: a single account’s secret. Importing a private key gives you access to one address only; that account may not be tied to a wallet’s seed phrase in the destination app.
Why does this matter? Because importing a seed phrase restores multiple accounts (if the destination wallet uses the same derivation path). Importing a private key creates a "loose account" inside MetaMask that will not be recovered by the MetaMask seed phrase later. Keep that in mind if you later change or back up only one seed phrase.
Useful reads: [/export-private-keys-and-loose-accounts] and [/seed-phrase-backup-recovery].
Import & export methods (what they do)
- Seed phrase import: Restores the HD wallet. Best for moving all accounts from one software wallet to another. Faster to set up, but exposes the seed phrase.
- Private key import: Adds a single account. Good when you want one address in MetaMask without replacing the MetaMask seed phrase.
- WalletConnect (or connecting apps): Does not move keys; it connects mobile wallets to dApps on desktop. Useful for using the same account across devices without exporting secrets. See [/walletconnect-guide].
- Hardware wallet connection: Keeps private keys offline. If long-term custody is needed, connect a hardware wallet instead of importing secrets. Related: [/hardware-wallets-with-metamask].
How to import wallet to MetaMask with recovery phrase (step-by-step)
Estimated time: under 5 minutes on mobile or desktop (if you have the recovery phrase ready). What I do every time:
- Put the source device in airplane mode (optional but safer) and confirm you can read the seed phrase offline.
- Open the MetaMask app or extension on the target device. Go to "Import wallet" or "Restore using recovery phrase."
- Type the seed phrase exactly in order (no extra spaces). Set a strong local password for the app.
- After import, verify the top account address matches the address shown in the source wallet.
- Add missing networks/tokens if balances don't appear (see [/add-custom-token-to-metamask] and [/connecting-networks]).
And always verify addresses on an on-chain explorer (link to [/using-etherscan-with-metamask]) before moving funds.
Import private key MetaMask: quick steps and caveats
Use-case: you want one account in MetaMask without restoring a different seed phrase. Steps (desktop extension and mobile have similar paths):
- In the destination MetaMask, open account menu > "Import Account."
- Choose "Private Key" and paste the private key string (never paste into websites).
- The imported account will appear under "Imported Accounts" and is not covered by MetaMask's seed phrase.
Caveats:
- Imported accounts are stored locally/encrypted, but they increase exposure if someone gets your device.
- If you only back up the MetaMask seed phrase later and lose the local private-key-backed device, you lose access to imported accounts. See [/export-private-keys-and-loose-accounts].
But don't paste private keys into cloud notes or email. Ever.
How to import Trust Wallet to MetaMask and add Coinbase Wallet to MetaMask
The steps for moving from Trust Wallet or Coinbase Wallet to MetaMask are the same at a conceptual level: export (seed phrase or private key) from the source app, import into MetaMask. Here’s a safe checklist rather than UI-specific clicks (because app UIs change):
- Export method: prefer a seed phrase if you want to restore all accounts. Use a private key if you only need one address.
- Security: export only on a secure, offline device; protect with PIN/biometric; do not screenshot the phrase.
- Verify: after import, compare the address on the on-chain explorer and check small test transfers (e.g., 0.001 ETH) before moving large balances.
If you specifically searched "how to import Trust Wallet to MetaMask" or "how to add Coinbase Wallet to MetaMask," this checklist applies. If you want step-by-step screenshots, see the mobile setup guide [/metamask-mobile-ios-android] and browser instructions [/install-metamask-chrome-extension].
Troubleshooting: missing accounts, tokens, and derivation-path issues
Common problems and fixes:
- Missing token balances: confirm you're on the correct network (mainnet vs L2). Add the token contract manually if needed via [/add-custom-token-to-metamask].
- Expected account not visible after seed import: different wallets can use non-standard derivation paths or reorder accounts. Solution: export the private key for that specific account from the source app and import it into MetaMask (see [/export-private-keys-and-loose-accounts]).
- Transactions not showing: check the network's block explorer (use [/using-etherscan-with-metamask]) and confirm the address.
Why does this happen? Different wallets can default to different HD paths or account indexes. It’s a frequent cause of confusion.
Security checklist before and after transfer
- Never type your seed phrase into a web page or untrusted device.
- Prefer restoring on a clean device and change the device’s password/biometric immediately after import.
- Revoke token approvals on the old account if you continue to use the old app (see [/token-allowances-and-revoke]).
- Consider moving large holdings to a hardware wallet (see [/ledger-with-metamask-guide] and [/hardware-wallet-integration]).
And yes, enable phishing protections and verify site domains before confirming signatures (see [/phishing-address-poisoning] and [/security-checklist]).
Comparison: import methods at a glance
| Method |
Restores multiple accounts |
Security risk |
Typical use-case |
MetaMask support |
| Seed phrase import |
Yes |
High if exposed |
Full migration between apps |
Supported (restore) |
| Private key import |
No (single account) |
High if exposed |
Add one account quickly |
Supported (Import Account) |
| WalletConnect |
N/A (no export) |
Low |
Use mobile account on desktop dApps without moving keys |
Supported via WalletConnect |
| Hardware wallet |
N/A (keys offline) |
Lowest |
Long-term custody, frequent dApp use with signing |
Supported (connect) |
This table helps pick a method based on risk tolerance and workflow.
FAQ
Q: Is it safe to keep crypto in a hot wallet?
A: Hot wallets are fine for active trading and DeFi interactions, but they carry higher online exposure than hardware storage. Use amounts you can accept losing and keep long-term funds offline.
Q: How do I revoke token approvals after moving wallets?
A: Revoke approvals from the originating address using a revocation tool or dApp, and then confirm on-chain changes using MetaMask. See [/token-allowances-and-revoke].
Q: What happens if I lose my phone after importing a wallet?
A: Restore the wallet on a new device using the seed phrase. If you imported private keys only and didn't back them up, you may lose access. Read [/compromised-wallet-what-to-do] and [/seed-phrase-backup-recovery].
Q: How do I export private key Trust Wallet?
A: The source wallet app has export options in its security/manage wallets area. The exact UI varies. Always protect any exported string with a strong offline process. (If unsure, check the source app’s help pages.)
Takeaway & next steps
Moving wallets is routine, but the security trade-offs are real. Seed phrase restores are efficient for full migration; private-key imports are useful for single addresses; WalletConnect avoids moving secrets at all. I believe a short test transfer (small amount) after any import is the most practical check. Want to tighten security next? Read [/hardware-wallets-with-metamask] and [/token-allowances-and-revoke].
If you need targeted procedures for mobile or extension setups, see [/metamask-mobile-ios-android] and [/install-metamask-chrome-extension].
![screenshot-placeholder]
Ready to transfer? Follow the steps above, back up your recovery phrase in multiple secure places, and verify on-chain before moving larger balances.
