A user holds cryptocurrency across multiple blockchains in their phantom wallet, but decides to migrate to MetaMask for different features or integration preferences. The immediate concern is not whether the transfer is technically possible—it is, because both are self-custody wallets—but how to execute it correctly without accidentally sending funds to the wrong network, losing access to private keys, or exposing recovery information during the process. The complexity increases when assets span Solana, Ethereum, Bitcoin, and other chains, each requiring different handling rules.

The second layer of concern is less obvious: many users assume that importing a recovery phrase into a new wallet automatically recovers all assets. That assumption causes real losses. A phantom wallet and MetaMask may derive different addresses from the same seed phrase if they use different derivation standards, or they may not support the same networks at all. This guide addresses both the procedural steps and the conceptual errors that lead to permanent loss of access or funds sent to addresses that cannot be recovered.

Why direct seed phrase import does not work as expected

Both phantom wallet and MetaMask are non-custodial wallets that derive addresses from a recovery phrase using a mathematical standard called BIP39 and BIP44. In principle, this means a seed phrase should produce the same addresses in both applications. In practice, it often does not. The reason is that wallet applications can use different derivation paths, which are the specific sequences of numbers that convert a seed phrase into individual addresses for each blockchain.

A phantom wallet primarily uses Solana’s derivation path for its native network and follows Ethereum standards for EVM-compatible chains like Polygon and Base. MetaMask defaults to the Ethereum derivation path for all accounts. If you import the same seed phrase into both wallets without understanding this difference, the addresses generated will be different. This means funds sent to a Phantom-derived address will not appear when you view that same account in MetaMask, even though both are using the same seed phrase. The funds are not lost—they are simply on a different address path that MetaMask is not displaying.

The consequence is a critical operational mistake: a user thinks the transfer has failed, attempts to re-send funds from Phantom, and now has two separate transactions to track across different wallets. Worse, if the user then imports the phrase into a third wallet or creates a new account, yet another set of addresses may be generated. The safest approach is to never rely on seed phrase import as a transfer mechanism. Instead, treat it only as a recovery method for when the original wallet is unavailable.

For this migration, the correct method is to treat each asset and each blockchain independently. Send funds deliberately from Phantom to a MetaMask address, confirm the transaction, and only then remove the asset from Phantom. This is slower and involves more individual transactions, but it eliminates the address derivation ambiguity and makes each step auditable.

Step 1: Setting up MetaMask and confirming supported networks

Before moving any assets, install MetaMask from the official source: the Chrome Web Store, Firefox Add-ons, or the mobile app store. Verify that you are using the genuine application by checking the publisher name and looking for any warnings from the browser. Counterfeit extensions exist and will steal recovery phrases entered during setup.

Once installed, create a new MetaMask wallet or import an existing one. If you are creating new, MetaMask will generate a fresh recovery phrase specific to that wallet. Do not import the phantom wallet recovery phrase yet. Instead, note MetaMask’s native address for Ethereum. This will be your destination for assets currently on Ethereum or EVM-compatible chains.

Next, add the networks where your Phantom funds currently reside. MetaMask supports Ethereum, Polygon, Base, Arbitrum, Optimism, and others by default. If your funds are on Solana, Bitcoin, or a less common network supported by your phantom wallet, check whether MetaMask supports it natively. MetaMask does not support Solana directly—Solana is a non-EVM network and requires either keeping funds in Phantom or using a bridge to convert them to an EVM chain. Bitcoin is also not natively supported; you would need to use a wrapped Bitcoin token or a bridge. This is an important limitation to identify before beginning the transfer.

Add any missing networks by selecting “Add Network” and either choosing from a preset list or manually entering the network details. For Polygon, Base, and Arbitrum, MetaMask has built-in options. Do not add custom networks unless absolutely necessary, as misconfigured network details can cause transactions to fail or send funds to an incorrect destination.

The Phantom to Ethereum transfer: Checking balances and gas fees

In your phantom wallet, navigate to the Ethereum account and verify your balance. Take a screenshot or note the exact amount. Also check the balance of any tokens: if you hold stablecoins, governance tokens, or other ERC-20 tokens on Ethereum, you will need to transfer these separately from the native ETH.

Open your MetaMask wallet and go to the Ethereum network. Copy your MetaMask Ethereum address. Return to Phantom and initiate a send transaction. Paste the MetaMask address as the recipient. Phantom will calculate the gas fee—the cost of the transaction in ETH. Do not skip reviewing this fee. If Ethereum network fees are high, the transaction may cost more than expected. In that case, you can wait for lower congestion or proceed now, knowing the exact cost.

Before confirming, review the transaction details in Phantom. Verify the recipient address matches your MetaMask Ethereum address exactly—do not assume, check character by character. Verify the network is Ethereum mainnet, not a testnet or another chain. Verify the amount is correct. Only after all three are confirmed should you approve the transaction in Phantom. Once signed, the transaction cannot be reversed.

Wait for the transaction to confirm on the blockchain. This typically takes 10 to 30 seconds on Ethereum, but can be longer during network congestion. You can monitor progress using a block explorer like Etherscan by pasting your transaction ID. Once confirmed, check your MetaMask Ethereum account—the funds should appear within moments.

Handling EVM-compatible chains: Polygon, Base, and others

If you hold assets on Polygon, Base, Arbitrum, or other EVM-compatible chains in your phantom wallet, the transfer process is identical to Ethereum but with one critical difference: the receiving address in MetaMask is the same across all EVM chains. This is because EVM wallets use the same address format for all compatible networks.

In MetaMask, switch to the Polygon network and verify your address. It should be the same as your Ethereum address—something like 0x1234… rather than a different format. In Phantom, switch to your Polygon account. Initiate a send to the MetaMask address you just verified. Phantom may show a different gas fee because Polygon uses different fee mechanics than Ethereum, but the process is the same: confirm the network, recipient, and amount.

Repeat this for each EVM chain where you hold assets. The key discipline is to confirm the network name in both wallets before initiating any transaction. Sending funds to the correct address on the wrong network is a common mistake. For example, if you send Polygon tokens to a MetaMask Ethereum address, the tokens will be sent to that address on the Polygon network, not on Ethereum. They will be recoverable but require manually adding Polygon to MetaMask and re-importing that account, creating unnecessary friction.

Once all EVM assets are transferred, verify your MetaMask balances across all networks. Add any token contracts that are not automatically visible. Token lists in MetaMask may not include every token you own, so if an asset does not appear, search for its contract address and add it manually using the “Import Tokens” function.

Non-EVM assets: Solana, Bitcoin, and what cannot be transferred

A phantom wallet supports Solana natively, and the Phantom team offers the official phantom wallet extension for this purpose. MetaMask does not. This means you cannot transfer SOL or Solana-based tokens directly to MetaMask using a normal wallet transfer. You have three options: keep Solana assets in Phantom, use a bridge to convert them to an EVM token, or use a cross-chain protocol.

If you want to keep your Solana assets but use MetaMask for everything else, the simplest approach is to continue using Phantom for that network alone. This is neither unsafe nor unusual—users often maintain multiple wallets for different blockchains. Alternatively, you can use a bridge like Wormhole or Portal to convert SOL or SPL tokens to their wrapped equivalents on Ethereum or another EVM chain. Be aware that wrapped tokens are different assets from the originals and may have lower liquidity or different trading mechanics.

Bitcoin is handled similarly. Phantom supports Bitcoin, but MetaMask does not. You can keep Bitcoin in Phantom, or convert it to a wrapped Bitcoin token (WBTC, renBTC, or others) on an EVM chain and then transfer that to MetaMask. This conversion introduces an intermediary token and comes with bridge fees and counterparty risk. For Bitcoin holdings, the most secure approach is to keep them in Phantom or use a Bitcoin-specific wallet like Ledger or Blue Wallet.

Before deciding to bridge, understand the mechanics. A bridge usually involves sending your asset to a smart contract, which locks it and mints an equivalent amount of a wrapped token on the destination chain. The wrapped token can be traded or transferred, but if you want to unwrap it back to the original asset, you must use the bridge again and pay another fee. This is a permanent architectural difference, not a temporary step.

Verifying the transfer and securing MetaMask

Once all transfers are complete, verify every balance in MetaMask against what you had in Phantom. Create a checklist: if Phantom showed 2 ETH and 500 USDC on Ethereum, 100 MATIC on Polygon, and 50 BASE on the Base network, confirm that MetaMask now shows exactly those amounts. Account for any transaction fees you paid—these will slightly reduce your total balance but should be small relative to your holdings.

If any asset is missing, do not panic. Check the network—you may have the right asset on the wrong chain. Use a block explorer to verify that the transaction was confirmed and the funds reached the MetaMask address. You can find the transaction ID in your Phantom activity history. If the transaction shows as confirmed but the funds do not appear in MetaMask, the issue is usually that MetaMask is not displaying that particular token. Add the token contract address manually or adjust the network settings.

After verifying all balances, secure your MetaMask recovery phrase. Write it down offline, store it separately from your device, and do not enter it into any website or application. Test your recovery process by using MetaMask’s account settings to export your private key (not the recovery phrase) and storing it in a secure location as a backup. This is different from storing the recovery phrase and provides redundancy if one backup method fails.

Only after confirming that all assets are in MetaMask and your backup is complete should you consider removing Phantom from your browser or phone. Even then, there is no harm in keeping both wallets installed. Some users maintain Phantom specifically for Solana and use MetaMask for EVM chains—this is a valid long-term arrangement and eliminates the risk of needing to reverse-migrate later.

Common mistakes that cause permanent loss of access

The most frequent error is importing the phantom wallet recovery phrase into MetaMask before understanding address derivation. This creates confusion about which wallet holds which funds and can lead to re-sending assets, paying unnecessary fees, or losing track of the original location entirely. Never import a recovery phrase as a shortcut.

The second major mistake is sending assets across networks. Solana tokens sent to an Ethereum address in MetaMask will not appear. Bitcoin sent to an Ethereum address will be lost permanently. The wallet does not know how to interpret the funds because they are on the wrong blockchain. This is prevented by carefully confirming the network name in both the sending wallet (Phantom) and the receiving wallet (MetaMask) before each transaction.

A third mistake is losing the recovery phrase or private key before confirming that all assets are accessible in the new wallet. If you delete Phantom before verifying that MetaMask has everything, and then discover a missing asset, you may not be able to recover it without restoring Phantom from the recovery phrase. Always retain access to the original wallet until you are completely certain the transfer is finished.

The fourth mistake is using a counterfeit wallet or downloading MetaMask from an unofficial source. Malicious versions will appear to work normally but will steal your recovery phrase when you enter it during setup. Always download from official sources: the Chrome Web Store, the official website, or the official app stores. Verify the publisher name and look for security badges.

Post-migration management and when to keep both wallets

After the transfer, you have several choices about how to manage your wallets going forward. Option one is to delete Phantom entirely and use only MetaMask for all future activity. This simplifies your security surface by reducing the number of applications that can access your private keys. However, it eliminates your ability to interact with Solana applications and NFTs on Solana without using a bridge or setting up a separate wallet later.

Option two is to keep both wallets but disable one. For example, many users keep Phantom installed for emergency recovery or future Solana activity, but use MetaMask as their primary wallet for daily transactions on Ethereum and other EVM chains. This is a reasonable approach if you occasionally need to access Solana or want a backup.

Option three is to maintain an active presence in both. This requires managing two separate recovery phrases and two sets of private keys, but it allows you to use the best wallet for each use case. Phantom remains optimized for Solana, while MetaMask is broader across EVM chains and has better default support for NFTs and decentralized applications on those networks.

Regardless of which approach you choose, update your backup procedure. If you now control assets across multiple wallets, you need backup documentation for each one. Store recovery phrases separately, in different physical locations if possible. Test the recovery process annually by actually restoring from backup to confirm it still works. This is less exciting than active use but infinitely more valuable when something goes wrong.