Importing Your Phantom Wallet Into Another Wallet: When and How to Export Your Seed Phrase

A user holds significant assets across Solana, Ethereum, and Bitcoin within Phantom Wallet, but circumstances change. A competitor wallet may offer better token-trading features, superior NFT support, or compatibility with a specific blockchain that Phantom does not yet cover. A user may also need to migrate for device reasons—moving from browser extension to mobile, or consolidating multiple wallets into a single backup recovery phrase. The practical question is straightforward: how do I safely move my assets to another wallet without losing control of them or exposing my recovery phrase to unnecessary risk?

The answer depends on understanding the relationship between your seed phrase, your private keys, and the blockchain itself. Phantom is a self-custody wallet, meaning you retain control of your credentials and assets remain on their respective blockchains—Phantom does not hold them on your behalf. That arrangement is both the source of security and the reason migration is possible. Your recovery phrase is mathematically linked to every address and private key Phantom generates. Exporting that phrase to another wallet does not move assets; it grants that wallet the ability to sign transactions from the same addresses. The assets themselves stay on the blockchain. Understanding this distinction prevents a common mistake: sending funds before migration is complete, or assuming that a new wallet application automatically receives what the old one managed.

Why migration matters and when it is necessary

Migration from Phantom to another wallet is not always required. Many users find that Phantom’s support for Solana, Ethereum, Bitcoin, Base, and Sui, combined with its transaction previews, scam detection, and spam filtering, covers their needs indefinitely. However, legitimate reasons for migration exist. A user may need access to a blockchain Phantom does not support—Polygon, Arbitrum, or other Layer 2 networks. Another may prefer a wallet with better hardware wallet integration, more granular privacy controls, or a different user interface. Some users migrate because they are moving from desktop to mobile, and the phantom mobile app may not yet offer all features available in the browser extension.

Device consolidation is another common driver. A user may have created separate Phantom wallets on different devices and now wants to manage them from a single recovery phrase. This is not a security upgrade—multiple isolated wallets can actually be more secure than consolidating them—but it may improve usability. A user might also migrate to maintain operational separation: keeping long-term holdings in one wallet while moving active trading funds to another. The key principle is that migration should be intentional, planned, and tested with small amounts before moving significant assets.

Recovery scenarios also demand knowledge of migration. If Phantom crashes, becomes unavailable, or you lose access to a particular device, having confirmed that your recovery phrase works in an alternative wallet creates a safety net. This is not paranoia; it is an operational check. A recovery phrase is worthless if you have never verified it can actually restore your wallet. Many users assume their backup is correct until disaster forces them to test it under pressure, when mistakes become catastrophic. Running a dry migration—importing your seed phrase into a test wallet, verifying the addresses match, then deleting the test wallet—is one of the few completely safe tests available before real migration.

Understanding the difference between exporting and migrating

Exporting and migrating are not synonymous. Exporting means obtaining your recovery phrase from Phantom—the 12 or 24-word sequence that generates all your private keys. Migrating means using that phrase in another wallet application. The critical point is that exporting does not remove the phrase from Phantom, nor does it move your assets anywhere. Your recovery phrase remains valid in Phantom after migration. Both Phantom and the new wallet will control the same addresses and private keys, because both derive them from the same seed phrase.

This creates a non-obvious security implication. If you export your recovery phrase from Phantom and import it into a second wallet while still using Phantom as your primary wallet, both applications will watch the same blockchain addresses. Both can initiate transactions. Both can be compromised independently. If one application is malware or uses fraudulent code, it could sign and broadcast transactions without the other wallet’s knowledge. For true migration—where you intend to stop using Phantom—you should plan to delete or discard the Phantom application after confirming that your new wallet controls all the relevant addresses and can sign transactions.

The timing and sequencing of this transition matter considerably. The safest sequence is: obtain your recovery phrase from Phantom, import it into the new wallet, verify that all expected addresses appear in the new wallet, test with a small transaction, wait for confirmation, and only then disable or delete Phantom. Reversing this order—deleting Phantom first, then scrambling to import elsewhere—leaves a window where you cannot access your assets if something goes wrong. Importing without verification, then immediately moving significant funds, risks sending assets to an unrecognized address or losing them to a malformed transaction.

Step-by-step export of your Phantom recovery phrase

The process differs slightly between the browser extension and mobile. On the browser extension version of Phantom, the sequence is: click the Phantom icon, select the menu (three horizontal lines), navigate to Settings, then Security and Privacy. Under the Recovery Phrase section, click “Show Secret Recovery Phrase.” Phantom will ask you to confirm your password. After entry, your 12 or 24-word recovery phrase appears on screen. This is the moment where environment matters. Do not take a screenshot or photograph the phrase if your device has network access or cloud backup enabled. Do not select and copy the text into a notes application that syncs to the cloud. The phrase should be written by hand on paper—ideally multiple copies—or stored in an encrypted container under your physical control.

On mobile, the process is similar but the interface differs. Open the Phantom app, tap the menu icon, select Settings, then navigate to Security. Find the Recovery Phrase option and tap “Display Secret Recovery Phrase.” You will be asked to confirm with biometric authentication or your PIN. After confirmation, your recovery phrase displays. The same writing-by-hand rule applies. Mobile devices are particularly vulnerable to cloud backups, clipboard managers, and app-level surveillance. Typing the phrase into the mobile device to copy it or photographing it creates additional risks that outweigh convenience.

Before completing this process, pause and ask yourself: do I have a secure storage location for this phrase before it appears on my screen? A locked desk drawer, a safe deposit box, or a physical location you control is appropriate. A file on your phone, a cloud note, a text message, or an email message is not. Once you have written the phrase and confirmed it is legible and correct, do not keep the screen displaying the phrase any longer than necessary. Phantom’s show-and-hide interface is designed for this reason—the phrase disappears after a timeout, reducing the window where it exists on screen.

Importing into a new wallet and verifying addresses

After obtaining your recovery phrase from Phantom, the new wallet application must support the same blockchain derivation standard. Most modern wallets use the BIP-39 standard for 12 or 24-word recovery phrases, and the phrase should work across them. However, some wallets use non-standard derivation paths or older standards. Before committing to a new wallet, check its documentation to confirm it uses BIP-39 or the same standard as Phantom.

The import process typically involves selecting “Import” or “Restore Wallet” in the new application, then entering your recovery phrase word by word. Most wallets will validate each word as you type to catch misspellings immediately. After completing the phrase entry, you may be asked to set a password or PIN for the new wallet application—this protects the application itself, but does not change your recovery phrase or addresses. The new wallet will then scan the relevant blockchains and display all addresses that hold funds.

This is the critical verification moment. Compare the addresses shown in the new wallet with those shown in Phantom. For Solana, Ethereum, Bitcoin, and other chains you use, the addresses should be identical. If they differ, the new wallet is using a different derivation path. Do not proceed. Delete the imported wallet from the new application and investigate further. Different derivation paths mean the new wallet is generating different addresses—and any funds you move to those addresses will be lost because Phantom cannot sign transactions from them.

A practical test is to take a small amount of a token you hold in Phantom and send it to the corresponding address in the new wallet. On Solana, send a small amount of SOL; on Ethereum, a small amount of ETH or a test ERC-20 token. Wait for the transaction to confirm on the blockchain explorer. The funds should appear in your new wallet’s address. This confirms that the address derivation is correct and the new wallet can receive funds. Only after this test succeeds should you consider moving significant amounts or disabling Phantom.

Handling NFTs and token positions during migration

Assets on blockchains include both fungible tokens (like SOL or ETH) and NFTs. Phantom displays both, and migration affects them identically: the new wallet sees all NFTs and tokens held at the addresses derived from your recovery phrase. When you import your phrase into the new wallet, it should automatically detect and display your NFTs. However, the way NFTs are presented varies by wallet. Some wallets show NFT galleries, some show minimal metadata, and some require manual refresh to load image data.

Token positions are simpler. An ERC-20 token, SPL token, or other standard token held at your address will appear in any wallet that imports the same recovery phrase. Phantom’s token detection and spam filtering work automatically; another wallet may require you to add token contract addresses manually. If you hold tokens that are not immediately visible in the new wallet, check whether you need to manually import the token by its contract address. This is an interface difference, not a blockchain difference—the token still belongs to your address.

A common mistake during migration is moving assets from Phantom to the new wallet before confirming that the new wallet displays them correctly. This reverses the logical order: you should first verify that the new wallet shows all your assets correctly, then delete Phantom. If you move funds to the new wallet before testing, and then discover the new wallet cannot display or sign with some addresses, you may be unable to recover those funds.

Staking positions and liquidity provider tokens require special attention. If you have SOL staked through a Solana validator, the stake account is separate from your token account. It will not automatically migrate; you may need to unstake in Phantom, wait for the unstaking period, and re-stake in the new wallet. Liquidity provider tokens—like those from Raydium, Uniswap, or other DEXs—are standard tokens and will appear in the new wallet, but the interface for viewing yields or removing liquidity may differ. Plan for this before migrating large positions.

Security considerations during and after export

The moment you display your recovery phrase on any device, assume that device is temporarily exposed. This is why air-gapped or offline import is preferable where available. Some hardware wallets support offline seed entry; a dedicated offline device for this purpose is overkill for most users, but the principle—minimizing the time between revealing the phrase and securing it—remains sound. For most users working with a phone or computer, the practical steps are: have secure storage prepared before viewing the phrase, view it briefly, write it down, verify the writing, hide the screen, and immediately secure the paper copy.

After import, the security question becomes: do I still need Phantom? If your new wallet is working, addresses match, and funds transfer successfully, keeping Phantom installed provides no benefit and creates a potential attack surface. A malware-infected or phishing extension version of Phantom would see your address activity, and if it is a fraudulent copy, it might prompt you for your recovery phrase again. Download applications only from official sources—Phantom NFT wallet applications should come from phantom.com or official app stores. Do not trust download links in emails or from social media.

Disabling or uninstalling Phantom after confirming your new wallet works removes this attack surface. You are not destroying anything—your recovery phrase and addresses remain on the blockchain indefinitely. If you ever need Phantom again, reinstalling it and importing your recovery phrase will show the same addresses and balances. This is the fundamental property of self-custody: your assets are defined by the blockchain, not by any single application.

One additional safeguard: update your recovery phrase storage security. If you wrote it on paper during initial Phantom setup and have carried it for months, migration is a good checkpoint to review the storage location. Is the paper still secure? Has the location changed? Have you tested the phrase in a backup scenario? If your original paper copy is aging or stored in a location that has become less secure, consider creating a fresh copy during migration and upgrading the storage method.

Handling multiple Phantom wallets or unusual setups

Some users have created multiple Phantom wallets—either because they created one, forgot about it, and created another, or intentionally to separate funds. Each Phantom instance (per browser profile or device) has a unique recovery phrase. When migrating, you must export and import each recovery phrase into the new wallet separately. Most modern wallets support multiple accounts from a single recovery phrase, or multiple independent recovery phrases. This allows you to consolidate your management without losing isolation if you intended it.

If you set up Phantom with a Ledger hardware wallet, the recovery phrase is stored on the Ledger, not in Phantom. In this case, you would not export from Phantom; you would import the Ledger’s recovery phrase into the new wallet using the Ledger itself as the signing device. This actually simplifies migration because you do not need to extract the phrase onto a computer at all. The new wallet connects to your Ledger, and the Ledger signs transactions. Phantom acted only as an interface; the Ledger remains the source of truth.

If you used Phantom’s password-protected feature (where Phantom encrypts the wallet locally with a password rather than displaying the recovery phrase), the process is slightly different. You would still need to display the recovery phrase to export it, but the password protection is an additional security layer within Phantom itself. It does not change the migration process, but it means you must have access to both the password and the recovery phrase to export the wallet.

Testing and rollback procedures

Migration should never be rushed. A deliberate testing phase prevents most losses. The sequence is: obtain recovery phrase, import into new wallet, verify addresses match Phantom, send a test transaction of small value, wait for confirmation, check that the new wallet received it, repeat with a different token or blockchain if you use multiple networks. Only after all tests pass should you move larger amounts or consider Phantom migration complete.

What if verification fails? The new wallet shows different addresses than Phantom. This means the wallet is using a different derivation path. Do not send funds to the new addresses. Delete the imported wallet from the new application and investigate. Check the wallet’s documentation to confirm it uses BIP-39 standard derivation. Some wallets allow you to select the derivation path during import; try alternative paths if available. If the new wallet genuinely does not support the same derivation as Phantom, you have three options: find a wallet that does, manually move funds using Phantom to the new wallet’s supported addresses (functionally equivalent to a standard transfer), or remain on Phantom.

If you have already moved funds to the wrong address, do not panic. Blockchain transactions are not reversible, but the funds belong to whatever wallet controls that address. If you imported the address from the new wallet but Phantom controls the same private keys, you can always open Phantom and move the funds from there. This is why the verification step matters more than the migration speed. Time spent testing now prevents irreversible losses later.

After migration: maintaining security and staying aware

Once you have completed migration and confirmed that your new wallet controls all your addresses and assets, you can uninstall Phantom if you choose. However, keeping a backup installation on a separate device without sensitive data can serve as a recovery option. Some users keep the original Phantom installation archived—with a copy of the recovery phrase and associated setup information—as a failsafe. This is optional, but it reflects the operational principle that self-custody means you are responsible for recovery.

Do not assume that migration to a new wallet changes your operational security obligations. You still must protect your recovery phrase, use strong passwords, verify addresses before sending, and avoid phishing attempts. The new wallet’s security depends on how well you use it. A superior wallet cannot overcome carelessness, and a good wallet is useless if you lose access to your recovery phrase or enter it into a malicious application.

As your cryptocurrency holdings grow or diversify, you may need to migrate again—to a wallet with better multi-chain support, hardware wallet compatibility, or additional features. Each migration follows the same principle: obtain your recovery phrase safely, verify it works in the new wallet with small transactions, and only then commit to the new wallet as your primary interface. The recovery phrase itself is your real wallet. The applications—Phantom, MetaMask, Ledger Live, or others—are merely interfaces to those addresses and the blockchains underlying them.