Phantom Wallet Import: How to Migrate from MetaMask, Trust Wallet, or Other Wallets

Users moving cryptocurrency holdings from MetaMask, Trust Wallet, Coinbase Wallet, or other self-custodial wallets often face the same practical question: how do I transfer my assets to Phantom without exposing my recovery phrase to unnecessary risk or accidentally losing funds on an incompatible network? The process is straightforward in principle—import your Secret Recovery Phrase, verify your addresses across blockchains, and confirm asset balances—but the execution requires attention to network selection, address derivation standards, and the specific chains where your funds actually reside. A single mistake in these steps can result in sending tokens to the wrong blockchain or failing to recover existing holdings.

The migration from one self-custodial wallet to another differs meaningfully from moving funds through a centralized exchange. With a self-custodial approach, you remain in control of the recovery phrase and private keys at every step. Phantom, like MetaMask and Trust Wallet, does not hold your assets on company servers; it instead provides the cryptographic credentials needed to authorize transactions on blockchains where your tokens actually live. This means the import process is not about “moving” funds in a traditional sense—it is about regaining access to assets that already exist on public ledgers using credentials stored in a new application.

Understanding the difference between wallet recovery and asset transfer

Before importing anything into Phantom, clarify what you are actually doing. Your Secret Recovery Phrase is the master cryptographic key from which all your wallet addresses derive. When you import that phrase into Phantom, you are not moving funds—you are regenerating the same addresses that your old wallet used to control. If your MetaMask wallet held 5 USDC on Ethereum and 10 SOL on Solana, those exact amounts remain on those chains under your recovered addresses. Phantom simply reads them from the public ledgers and displays them in its interface.

This distinction matters because it affects your security decisions during migration. You do not need to send funds from MetaMask to a temporary holding account and then into Phantom. You do not risk losing assets during “transfer.” Instead, you are restoring access to existing holdings using the same recovery phrase in a different application. The risk, if any, comes from mishandling the recovery phrase itself—exposing it during import, storing it unsafely afterward, or accidentally importing it into a malicious application that copies your phrase.

The process also reveals a practical limitation: if your original wallet used non-standard derivation paths or custom address schemes, some wallets may not find all your addresses immediately. Most self-custodial wallets follow the BIP-44 standard for deriving addresses from a recovery phrase, which means Phantom should detect the same addresses you used before. However, if you created additional accounts or used advanced settings in your old wallet, you may need to manually add accounts or adjust settings in Phantom to see all your holdings.

Preparing your recovery phrase and securing the import process

Begin by locating your Secret Recovery Phrase from your current wallet. In MetaMask, this is typically found in Settings → Security and Privacy → Reveal Secret Recovery Phrase. In Trust Wallet, navigate to Settings → Wallets → Select Your Wallet → Show Recovery Phrase. Do not screenshot this phrase, do not type it into a search engine, and do not share it with anyone. The phrase is the complete master key to every address and asset your wallet controls. Treat it as your most sensitive credential.

Before you import, ensure you are working on a secure device. Close unnecessary browser tabs, disable screen recording, and consider temporarily disconnecting from the internet if you are particularly cautious about exposure during the import step. Some users prefer to work on a dedicated device or in a fresh user account on their computer. These precautions are especially important if you hold significant value or if you have reason to suspect your device may have been compromised by malware.

Once you have verified the phrase is written down or stored offline, you can proceed to import. You will need to download phantom extension and install it in your browser, or download the Phantom mobile application from the App Store or Google Play. Verify that you are downloading from the official source—check for the correct domain name, read recent user reviews, and confirm that the application has been officially distributed by the Phantom team. A counterfeit wallet that looks identical but is installed from a malicious link can steal your recovery phrase as soon as you enter it.

Importing your recovery phrase into Phantom

Open Phantom after installation and select the option to import an existing wallet using your recovery phrase. You will be prompted to enter the 12-word or 24-word phrase depending on which wallet format you originally used. Enter the words in the exact order they appear in your original recovery phrase. Capitalization typically does not matter, but spacing and word order must be precise. Phantom will verify the phrase format and confirm that it is a valid BIP-39 mnemonic.

After entering the phrase, Phantom will ask you to create a password for accessing this wallet within the application. This password is different from your recovery phrase—it is a local encryption key that secures the wallet file on your device. Choose a strong password that you have not used elsewhere. If you forget this password later, you can recover the wallet by importing the recovery phrase again, so the password protects convenience rather than preventing ultimate access.

Phantom will then scan for addresses derived from your recovery phrase. For a wallet that previously used MetaMask or most other standard Ethereum-compatible wallets, Phantom should automatically detect your Ethereum, Base, Polygon, and other EVM-compatible addresses. For Solana wallets imported from Phantom’s own prior version or other Solana wallets, it will recover your Solana address. Bitcoin addresses may require additional account setup if you previously used a Bitcoin-specific derivation path that Phantom does not use by default.

The import process typically completes within seconds. Phantom will display your recovered accounts and show you a summary of the addresses it found. Do not be alarmed if the interface looks slightly different from your old wallet—Phantom has its own design. What matters is that the addresses shown match the ones you remember from your previous wallet. You can verify this by copying an address and checking it against transaction history in a block explorer like Etherscan, Solscan, or BlockScout to confirm it is the correct address.

Verifying assets across all supported blockchains

Once your addresses are recovered, Phantom will begin fetching your portfolio data from the blockchains where your assets live. Because Phantom supports Solana, Ethereum, Base, Polygon, Bitcoin, Sui, and HyperEVM, your assets may be distributed across multiple networks. The portfolio view in Phantom should display tokens and balances across all these chains, but verification requires confirming that the displayed amounts match your expectations.

For each blockchain where you held tokens, open Phantom’s portfolio view and check that the assets listed are correct. Compare the balance shown in Phantom against the balance you see in a block explorer by looking up one of your recovered addresses. Enter your Ethereum address on Etherscan, for example, and verify that the USDC, USDT, DAI, or other tokens you remember owning still appear in the address holdings. If your assets are on Polygon, use Polygonscan. For Solana, use Solscan. This step confirms that the recovery worked and that you are looking at the correct address.

Pay particular attention to chains where you may have sent assets but are unsure whether the transaction succeeded. If you sent funds to a Bitcoin address through a bridge and are now uncertain whether they arrived, look up the address on a Bitcoin block explorer to confirm the transaction is visible on the public ledger. If the transaction appears to be missing, check your old wallet’s transaction history to see whether the outgoing transaction was broadcast at all. Assets that were never sent will not appear in your recovered wallet simply because they do not exist on that blockchain yet.

Some tokens may not display automatically in Phantom even if they exist at your address. This is especially true for newly created tokens, spam tokens, or less common assets. If you remember holding a token that does not appear in your portfolio, you can manually add it to your watchlist by entering its contract address. In Phantom, use the “Add Token” or similar function, enter the contract address for the token, and Phantom will fetch its details and display your balance.

Handling tokens and assets across different blockchain networks

One complication that often trips up users migrating between wallets is that the same token ticker can represent different assets on different blockchains. For example, USDC exists on Ethereum, Polygon, Solana, Base, Arbitrum, and many other networks, but these are technically different token contracts. When you import your wallet into Phantom and see “USDC” displayed, you need to verify which USDC you actually hold. Phantom typically shows the blockchain network next to the token name, but it is still worth checking block explorers to confirm.

If you previously used a bridge to move tokens from one chain to another—say, moving USDC from Ethereum to Polygon using a cross-chain bridge—the bridged USDC will appear on Polygon under your recovered address. Some bridges create wrapped versions of the token with a different contract address. If you previously held “Wrapped Ethereum” (WETH) or another wrapped token, it will still appear in your recovered wallet at its actual contract address on the blockchain where it lives. Phantom will attempt to identify and display these assets correctly, but you should verify by checking the contract address and comparing it against your transaction history.

For Bitcoin holdings, the process is slightly different because Bitcoin is not an EVM chain and does not use the same address derivation. If you previously held Bitcoin in Trust Wallet, MetaMask’s Bitcoin support, or another wallet, Phantom will need to recover your Bitcoin address separately. Your Bitcoin recovery phrase may use the same master seed as your Ethereum addresses, but the Bitcoin address derivation path (typically m/44’/0’/0’/0/0 for standard Bitcoin wallets) is different. Phantom derives Bitcoin addresses using its standard path, so your recovered Bitcoin address should match what you used before if both wallets follow the BIP-44 standard.

Testing transactions before moving large amounts

After recovering your wallet and verifying your assets, do not immediately perform large transactions. Instead, make a small test transaction to confirm that Phantom is functioning correctly and that you can send and receive funds. If you have a small amount of SOL, USDC, or another token, send a minimal amount to an address you control (such as a second wallet or exchange address) and verify that it arrives correctly. This test transaction serves multiple purposes: it confirms that your recovered wallet can authorize transactions, it tests the network connection and gas fee calculation, and it gives you confidence before moving larger amounts.

When making this test transaction, pay attention to the gas fees shown in Phantom. Different blockchains have different fee structures. Solana typically has very low fixed fees. Ethereum and Polygon fees vary based on network congestion. Bitcoin fees depend on transaction size and network demand. Phantom should estimate and display the fee before you confirm the transaction, allowing you to adjust settings if needed. Some wallets offer options to customize gas prices or transaction speed; Phantom provides reasonable defaults, but understanding the fee structure helps you make informed decisions.

Also test the receiving address handling. Copy an address from your recovered wallet and send a token to it from an external source, or send a token from your recovered wallet to another address and verify it arrives. This confirms that address copying and transaction destination selection are working correctly. Once you have successfully completed a small test transaction, you can proceed with confidence to move larger amounts if needed.

Common issues and troubleshooting during migration

If your recovered wallet shows a different address than your old wallet for the same blockchain, the most common cause is a mismatch in derivation paths or account numbers. Most wallets derive multiple accounts from a single recovery phrase, each with its own set of addresses. Your old wallet might have used Account 0, Account 1, and Account 2, while Phantom starts by recovering Account 0. If you were actively using Account 1 or Account 2 in your old wallet, you need to manually add those accounts in Phantom. Look for an option like “Add Account” or “Derive Additional Account” and increment the account number until you see your expected addresses.

Another common issue is that a token does not appear even though you know you own it. This often happens when a token is not recognized by Phantom’s default token list. If you hold a less common ERC-20 token, for example, Phantom may not display it automatically. The solution is to manually add the token by contract address. Find the token’s contract address on a block explorer like Etherscan, enter it into Phantom’s “Add Token” interface, and Phantom will fetch the token details and display your balance.

If you accidentally entered your recovery phrase incorrectly during import, Phantom will not display any of your original assets. The safest response is to start over by importing the wallet again and carefully re-entering the phrase word by word. Some users find it helpful to write the phrase down on paper first, then read from the paper during entry rather than copying and pasting (which reduces the risk of malware capturing the text).

For users migrating with significant holdings on multiple chains, verify connectivity to each blockchain before relying on displayed balances. Phantom may take some time to fetch data from slower or congested networks. If a blockchain’s data appears not to load, try disconnecting and reconnecting from the network, or wait a few minutes and refresh. If balances still do not appear correctly, check a block explorer directly to see if your address truly holds the assets you expect.

Security practices after successful migration

Once you have verified that your wallet is recovered and all assets are visible, you face a security decision about your old wallet. You can continue to use both MetaMask and Phantom simultaneously since they both access the same addresses and blockchains. Some users prefer this approach as a backup. Others prefer to disable or uninstall the old wallet after migration to reduce the risk of accidentally using the wrong wallet or exposing the recovery phrase through multiple applications.

If you decide to uninstall your old wallet, do not delete your backup of the recovery phrase. Store it in the same secure offline location you use for backing up Phantom. The recovery phrase is not tied to any particular wallet application—it can be imported into MetaMask, Trust Wallet, Phantom, or other compatible wallets at any time. Keeping a backup allows you to recover your wallet if Phantom ever becomes unavailable or if you prefer to use a different wallet in the future.

For enhanced security, consider storing your recovery phrase in a hardware wallet like a Ledger or Trezor if you hold significant assets. Phantom supports hardware wallet connections, allowing you to authorize transactions on your recovered addresses without storing the private keys on your computer or phone. This approach provides strong protection against malware and phishing, though it does require the hardware device to be connected when you perform transactions.

Do not re-export or photograph your recovery phrase after importing it into Phantom. The phrase should remain written down in one secure offline location. If you ever need to check it again, refer to your original written copy rather than asking Phantom or any wallet software to reveal it. The more you handle or transmit the phrase, the greater the risk of exposure.