MetaMask Wallet: Importing Accounts From Other Wallets (Trust Wallet, Exodus, Coinbase)

A cryptocurrency user holds assets across multiple wallets. Some funds originated in Trust Wallet, others entered through Exodus, and a third portion came from a Coinbase self-custody wallet. Consolidating these holdings into a single interface—while maintaining self-custody and control—requires understanding how different wallets derive accounts, protect private keys, and store recovery information. MetaMask wallet supports account import from competing platforms, but the process differs based on whether the source is a seed phrase, a private key, or a hardware wallet. The fundamental question is not whether migration is possible, but how to execute it safely without exposing credentials during transfer.

This migration scenario is common enough that understanding the mechanics saves time and prevents costly mistakes. Each wallet uses cryptographic methods to convert a recovery phrase or private key into blockchain accounts. Trust Wallet, Exodus, and Coinbase wallets all support standard derivation paths, meaning a seed phrase can theoretically generate the same accounts across different applications. Yet the practical reality involves format differences, network-specific rules, and the critical distinction between importing a recovery phrase versus importing a single private key. Moving assets carefully requires knowing which approach preserves full account recovery and which creates a partial account that cannot be restored from the same seed.

Understanding wallet structure and derivation paths before import

Every blockchain account begins with a cryptographic secret—either a private key or a hierarchical deterministic seed that generates multiple private keys. The Secret Recovery Phrase is a 12 or 24-word mnemonic representing a master seed. When you import this phrase into MetaMask or any other wallet, it derives child private keys using a standard called BIP-32 (Hierarchical Deterministic Wallets). The derivation path—a sequence of numbers that determines which child key is generated—matters because different wallets may use different paths to generate what appears to be the same account.

Trust Wallet, for example, uses the Ethereum derivation path m/44’/60’/0’/0/0 for its first Ethereum account by default. Exodus uses the same standard for most networks. Coinbase self-custody wallets also follow BIP-32 derivation but may label accounts differently or prioritize certain networks. MetaMask, being fundamentally an Ethereum-focused wallet, uses this same standard path for Ethereum and EVM-compatible chains. The implication is that if you export a seed phrase from Trust Wallet and import it into MetaMask, the first Ethereum account should match. However, if the source wallet was configured with a custom passphrase or used a non-standard derivation, the accounts will not match even though the seed phrase is identical.

Private key import operates differently and more narrowly. A private key is a single 256-bit number that controls one account on one blockchain. If you export a private key from Exodus and import it into MetaMask, MetaMask will add that one account to the current wallet. That account will not be derived from the same seed phrase, and MetaMask cannot recover it by restoring the seed phrase—it exists as an isolated imported account. This distinction is crucial: seed phrase import gives you account recovery and full wallet portability; private key import gives you access to one account but no recovery mechanism tied to your MetaMask seed phrase.

Step-by-step: Importing a seed phrase into MetaMask wallet

The most complete migration path is to import your entire seed phrase from the original wallet into MetaMask. To do this, open MetaMask and look for the option to “Import an existing wallet” during setup or in the account menu. You will be asked to enter a 12 or 24-word recovery phrase. Enter the exact words in the correct order, separated by spaces. MetaMask will then derive accounts using its standard derivation path. If the source wallet used the same path (as Trust Wallet and Exodus do), your first account in MetaMask should display the same address and balance as the first account in the original wallet.

After importing, you must create a new local password for MetaMask. This password is separate from the seed phrase and encrypts your account data on the device. It does not give someone access to your funds through the network—only your seed phrase or private keys do—but it does protect your local files from casual access if your device is briefly compromised. Store this password securely, but understand that MetaMask cannot retrieve it if lost. If you forget your password, you can reset the wallet by entering your seed phrase again, starting fresh and creating a new local password.

Once the seed phrase is imported, MetaMask derives accounts automatically. The first account will appear in your account menu. You can derive additional accounts by clicking “Create Account” or “Add Account” from the same seed phrase. Each new account is a different child of the same master seed, with its own private key but ultimately traceable to the seed phrase you imported. This means that if you later export your MetaMask seed phrase, you will recover all derived accounts, not just the first one. The wallet now controls multiple blockchain accounts from the single recovery phrase.

Importing single private keys when the seed phrase is unavailable

Not every user has access to their original wallet’s seed phrase. Hardware wallets, for instance, never expose the seed phrase to the device; it remains on the hardware device itself. A Coinbase self-custody wallet might have been created only as a private key without ever displaying a recovery phrase. In these cases, the only path forward is private key import, which is more restrictive but still functional.

To import a private key into MetaMask, open the account menu and select “Import Account” (not “Import Wallet,” which is for seed phrases). You will be asked to paste the private key in hexadecimal format, usually a 64-character string starting with 0x. MetaMask will derive the Ethereum address associated with that key and add it to your wallet as an imported account. This imported account will appear in your account list alongside any accounts derived from your seed phrase, but they are separate. If you restore your MetaMask seed phrase later, the imported account will not be recovered unless you import the private key again.

The security implications are substantial. A private key in plaintext format is extremely sensitive. Never copy and paste it into a web browser, email, or message application. If you must temporarily hold a private key outside a wallet, use an offline device, air-gapped computer, or a dedicated hardware vault. Once imported, do not leave the private key in a text file or cloud service. Consider this import a one-time operation: retrieve the key, paste it into MetaMask, and then securely delete the plaintext version. MetaMask stores the imported key encrypted locally, and you can verify the account balance through the blockchain network without retaining the original key file.

Handling network-specific accounts and multi-chain wallets

Modern wallets rarely support a single blockchain. Trust Wallet handles Ethereum, Bitcoin, Solana, TRON, and dozens of other chains. Exodus supports similar diversity. When you import a seed phrase into MetaMask, the wallet derives accounts for Ethereum and EVM-compatible networks by default. But what about your Bitcoin account from Trust Wallet, or your Solana holdings?

MetaMask has expanded to support Bitcoin, Solana, and TRON accounts, but the user experience differs from Ethereum. For Bitcoin specifically, you must create or import a Bitcoin account separately through MetaMask’s Bitcoin interface. The seed phrase you imported for Ethereum can also be used to derive your Bitcoin account—MetaMask can show you the correct Bitcoin address associated with that seed on the Bitcoin network—but the Bitcoin derivation path is different from Ethereum’s. This means that when you import your Trust Wallet seed into MetaMask, the Ethereum address will match, but you must explicitly add a Bitcoin account to see your Bitcoin holdings and transact on the Bitcoin network.

For Solana and TRON, the process is similar. MetaMask can now derive accounts on these networks using your imported seed phrase, but you must add them explicitly. The wallet does not assume that because you have an Ethereum account, you automatically want Solana accounts added. This design choice reflects the technical fact that different blockchains use different signing algorithms and address formats, even though the underlying seed phrase can derive keys for all of them. When migrating from a truly multi-chain wallet, you will need to add each network separately in MetaMask to see all your imported accounts.

Data security and the irreversibility of blockchain transactions

MetaMask is a self-custodial wallet, which means you own your private keys and MetaMask cannot access them. This is fundamentally different from a custodial exchange like Coinbase, where the platform holds your private keys and you interact through an account and password. The trade-off is power and responsibility. You can move funds without anyone’s permission, but you alone are responsible for keeping your seed phrase and private keys secure. If someone obtains your seed phrase or private key, they can move your funds permanently. MetaMask cannot freeze the account, cannot reverse a transaction, and cannot recover a lost recovery phrase.

This immutability applies to every transaction confirmed on the blockchain. If you import an account, see a balance, and send funds to the wrong address, the transaction cannot be reversed by MetaMask or by the network. The Bitcoin protocol, Ethereum, and most other blockchains confirm transactions through distributed consensus; once confirmed, they become part of an immutable ledger. Your only recourse is to contact the recipient and ask for a refund, which requires trust and cooperation they may not provide. For this reason, always verify the receiving address carefully before signing any transaction, especially during a first transfer to a new destination.

When you import a seed phrase into MetaMask, verify the imported accounts before moving funds. Open the original wallet and the new MetaMask wallet side by side. Confirm that the account addresses match. Send a small test amount from the original wallet to the MetaMask account and verify that it arrives. Only after successful confirmation should you transfer larger holdings. This extra care costs a few minutes and a small network fee but prevents catastrophic mistakes such as accidentally sending funds to a newly derived account instead of the imported one, or discovering that the import used a different derivation path and created entirely different accounts.

Comparing import methods across Trust Wallet, Exodus, and Coinbase wallets

Trust Wallet and MetaMask both support standard BIP-44 derivation for Ethereum and other EVM networks. Importing a Trust Wallet seed phrase into MetaMask will recover your Ethereum accounts with matching addresses. However, Trust Wallet also manages Bitcoin, Solana, TRON, and other blockchains. If your Trust Wallet seed is used for Bitcoin accounts, you must add those accounts separately in MetaMask’s Bitcoin interface. Non-standard or legacy derivation paths in Trust Wallet—such as custom accounts created with an altered derivation—will not be recovered automatically in MetaMask and will require private key export and import instead.

Exodus wallets typically follow the same BIP-44 standard, making seed phrase imports to MetaMask straightforward for Ethereum accounts. Exodus does not require a passphrase for its seed, which simplifies migration. However, Exodus also manages Bitcoin, Solana, and other networks with separate derivation paths. If you created accounts in Exodus on these networks, you will need to add them separately in MetaMask or export the individual private keys and import them.

Coinbase self-custody wallets present a different case. Coinbase’s self-custody offering does support seed phrase export, and if you have access to it, the import process to MetaMask is similar to Trust Wallet. However, Coinbase often emphasizes hardware wallet integration, and many Coinbase users store keys on external devices rather than in software. In this scenario, private key import is not an option—you must use the hardware wallet with MetaMask through its hardware wallet connection feature, which is a separate process from importing a seed phrase or private key into MetaMask’s own wallet. The metamask wallet interface supports direct hardware wallet pairing for devices like Ledger and Trezor, which may be preferable to importing keys from them.

Common mistakes and how to avoid them

One of the most frequent errors during migration is failing to verify the derivation path before importing. A user exports their seed phrase from Trust Wallet, imports it into MetaMask, and expects to see the same accounts. If Trust Wallet had used a custom passphrase or non-standard derivation, the accounts will be entirely different. The seed phrase is correct, but the accounts do not match. To avoid this, confirm account addresses in both wallets before moving funds. If addresses do not match, do not proceed with seed phrase import; instead, identify the accounts by exporting their private keys from the original wallet and importing them one by one into MetaMask.

Another common mistake is confusing the local password with the seed phrase. MetaMask’s password encrypts your data on your device. It does not protect your account from network access. Someone with your seed phrase can access your accounts from any device, even without knowing your password. Conversely, someone who knows your password but not your seed phrase cannot move your funds on the blockchain. When migrating, create a strong local password, but do not assume it secures your funds. Only the seed phrase and private keys provide that security.

A third pitfall is importing a seed phrase but then creating new accounts in the new wallet and sending funds to those new accounts, thinking they are “fresh” and therefore safer. New accounts are still derived from the same seed phrase. If you later lose that seed phrase, you lose all derived accounts, whether they were imported from the original wallet or created fresh in MetaMask. The security of all accounts depends on protecting the single seed phrase. Creating new accounts does not create new security; it merely increases the complexity of recovery.

Finally, users sometimes import a private key and then forget that it is not backed up by their seed phrase. If the device is lost and you restore MetaMask from your seed phrase, the imported account is gone unless you saved the private key separately. Imported accounts must be manually backed up. Keep a secure, offline copy of any private keys you import. This is more cumbersome than relying on seed phrase recovery, which is why imported accounts are best treated as a temporary solution for consolidating holdings during migration, not as a long-term account strategy.

Testing your import and verifying account recovery

After importing a seed phrase into MetaMask, the critical verification step is to test account recovery. Write down the imported seed phrase on paper (never store it digitally). Then, uninstall MetaMask or reset the wallet completely. Reinstall the wallet and select “Restore from Recovery Phrase.” Enter the seed phrase you wrote down and confirm that MetaMask derives the same accounts with the same addresses and balances. This test demonstrates that your seed phrase is correctly recorded and that MetaMask can recover all imported accounts from it. Performing this test before moving large amounts of cryptocurrency provides confidence that your recovery process actually works.

If the test fails—if the recovered accounts show different addresses than the original import—stop immediately and investigate. The most likely cause is a transcription error in the seed phrase. Check each word carefully. Seed phrases are case-insensitive and space-separated, so common mistakes include omitting words, reversing word order, or recording a visually similar word (such as “panda” instead of “panda” or “hand” instead of “land”). Go back to the original wallet and re-export the seed phrase to confirm each word. Once you have verified it, repeat the import and recovery test.

A secondary verification is to check blockchain explorers. After importing, open a block explorer for the blockchain network you are using (such as Etherscan for Ethereum). Navigate to one of your imported account addresses and confirm that the balance shown on the blockchain matches the balance displayed in MetaMask. MetaMask retrieves balance information from blockchain nodes through its configured RPC endpoints, and occasional synchronization delays can occur. If MetaMask shows a balance but the block explorer shows zero, or vice versa, wait a few minutes and refresh. If the discrepancy persists, it may indicate a configuration issue with your RPC endpoint or a network connectivity problem rather than an import failure.