Migrating from Phantom to Another Wallet: Complete Export and Import Checklist

A user holds assets across Solana, Ethereum, Bitcoin, Base, and Sui blockchains through Phantom, but plans to consolidate or switch to a different wallet application. The immediate question is straightforward: how do I move everything out? The practical answer is more complex. A self-custodial wallet like Phantom does not hold assets on centralized servers; it holds the cryptographic keys that authorize transactions on public blockchains. Migration therefore means transferring control of those keys, not moving digital objects from one place to another.

The difference matters because the blockchain itself is the source of truth. Your balances, NFT ownership, and transaction history live on-chain, not inside Phantom. What the wallet application controls is access to the private keys that prove you own those assets and can move them. Exporting and importing those keys requires careful sequencing, because a single mistake—entering a recovery phrase incorrectly, sending to the wrong blockchain network, or losing track of which accounts belong to which chain—can result in lost funds or inaccessible assets that remain visible on-chain but permanently out of reach.

Understanding what your Secret Recovery Phrase actually controls

The Secret Recovery Phrase is the master key to every address Phantom generates under that wallet. Typically twelve or twenty-four words in a specific order, it represents a single seed from which the application derives multiple addresses—one for Solana, separate ones for Ethereum and Base, another for Bitcoin, and others for Sui and any supported blockchain. If you have created multiple accounts within Phantom (by selecting “Create Account” rather than importing), each account may have a different derivation path, which affects how the recovery phrase generates addresses on the destination wallet.

This is the critical constraint of migration. When you export the Secret Recovery Phrase and import it into a new wallet application, the destination wallet will generate addresses using its own derivation standard. If the new wallet uses a different derivation path—a technical detail that specifies how the recovery phrase transforms into addresses—the addresses it generates will not match the ones Phantom created. Your assets will still be on-chain, but the new wallet will not see them unless you manually derive the correct path or the new application supports Phantom’s specific derivation method.

The recovery phrase is also the single point of failure for the entire wallet. Unlike exchange accounts, where a password reset or account recovery process exists, a compromised recovery phrase cannot be changed. Anyone who sees it can derive all addresses and sign transactions on your behalf. This means that during the migration process, you must never type the recovery phrase into a website, email, or untrusted application. The safer pattern is to export it from Phantom, store it temporarily in a secure offline space, and import it directly into the new wallet application through its official interface.

For accounts created within Phantom after the initial wallet setup, you may have additional recovery options specific to that account. Check Phantom’s account settings to see whether any accounts have separate recovery information. If they do, you will need to handle them separately from the main recovery phrase. This is uncommon for most users but becomes important if you have organized assets into multiple accounts for organizational reasons.

Preparing for migration: the multi-blockchain complication

Phantom supports Solana, Ethereum, Bitcoin, Base, and Sui. Each blockchain has its own address format, fee structure, and native asset. When you migrate, the recovery phrase will generate addresses on each of these chains in the new wallet, but those addresses will not necessarily be the same ones Phantom showed you. This creates a verification problem: you need to confirm that the new wallet correctly imported your keys before moving assets.

The practical approach is to identify exactly which addresses hold which assets in Phantom before beginning the migration. Open Phantom, note the Solana address and its balance, write down the Ethereum address and the Bitcoin address, check Base and Sui as well. Then, in the destination wallet, import the recovery phrase and check whether those same addresses appear. If the new wallet shows different addresses, the recovery phrase may have been imported successfully, but the derivation path does not match. At that point, you can either adjust the derivation in the new wallet (if it offers that option), manually derive the addresses using a tool, or import the recovery phrase into Phantom again and use Phantom itself as the bridge to move assets to a new set of addresses in the destination wallet.

This is why many users choose not to migrate the recovery phrase directly. Instead, they create a fresh wallet in the destination application, generate new addresses, and then transfer assets from each Phantom address to the corresponding chain in the new wallet. This requires paying network fees for each transfer, but it eliminates the risk that the destination wallet uses a different derivation method. The trade-off is cost and time; the benefit is certainty and control. For small balances or testing, the transfer-first approach is often safer.

Exporting from Phantom: what you can and cannot take with you

The Secret Recovery Phrase is the only portable credential that Phantom exports. Everything else—NFT metadata, transaction history, custom names for addresses, saved contacts, staking positions, and transaction preferences—remains in the Phantom application and cannot be exported. A new wallet will be able to see the same blockchain addresses and assets once you import the recovery phrase or manually enter the addresses, but it will not see Phantom’s local database.

NFTs are a useful example of this limitation. Phantom displays your NFTs with metadata: images, names, descriptions, and collection information. That display is powered by Phantom connecting to metadata services and showing the indexed information. When you move to a new wallet, the blockchain still knows you own those NFTs because your address appears in the smart contract records. However, the new wallet may display them differently, show different metadata, or not show them at all until it indexes the same data. Some wallets display NFTs from every blockchain; others are chain-specific. Checking the destination wallet’s NFT support before migration can prevent the surprise of seeing assets disappear from view even though you still own them.

Staking positions require similar attention. If you have Solana staked through Phantom, the staking is actually managed by a smart contract on Solana. Your recovery phrase gives you access to the account that initiated the stake, but the new wallet may not have a built-in interface to manage that stake or check its status. You may be able to see your SOL is locked in the smart contract, but claiming rewards or unstaking could require manually interacting with the contract through a different interface, using Solana’s command-line tools, or connecting the account to a separate staking application.

Similarly, any bridge or swap transactions that are pending will not automatically complete in a new wallet. If you initiated a bridge transfer from Ethereum to Solana before migrating, the bridge service has a record of the transaction. You can find that record and complete it by connecting the relevant address to the bridge interface, but the new wallet will not inherit Phantom’s integration with that service.

Creating a clean migration path: step-by-step verification

The safest migration sequence involves these steps. First, download and install the destination wallet application on the same device as Phantom. Do not uninstall Phantom yet; you will use it for comparison. Second, in the destination wallet, select the option to import an existing wallet and choose to enter or paste the recovery phrase. Write down the first address the destination wallet displays for each blockchain it supports. Compare those addresses to the ones shown in Phantom. If they match, continue. If they do not match, stop and check the destination wallet’s settings for a derivation path or account path option that matches Phantom’s standard.

Once addresses match, perform a small test transfer from Phantom to the destination wallet using one blockchain. For example, send a small amount of SOL from Phantom to the imported Solana address in the new wallet, wait for confirmation, and verify that the destination wallet shows the received balance. Do not proceed to larger transfers until this test succeeds. This step costs network fees but eliminates the risk of discovering an address mismatch after sending large amounts.

After the test transfer confirms, you can transfer the remaining assets. For multi-chain holdings, handle one blockchain at a time: transfer all Solana, wait for confirmation, then transfer Ethereum, then Bitcoin, then Base, then Sui. Document each transaction’s hash. Keep Phantom installed and accessible for at least one week after the final transfer, in case you need to verify addresses or retrieve any information. Only after confirming that all assets appear in the destination wallet and you have tested receiving a new transaction should you consider the migration complete.

When you decide to delete Phantom, export or photograph the Secret Recovery Phrase one final time and verify it matches your written record. Some users keep a copy of the recovery phrase as a backup even after migrating, in case they need to access the Phantom account again. Others store it offline as a secondary recovery mechanism. The choice depends on your security practices and whether you plan to use Phantom again.

Special considerations for hardware wallet integration

If you use Phantom with a hardware wallet—such as a Ledger device—migration becomes simpler in some ways and more complex in others. The hardware wallet is the actual source of the private keys; Phantom is the interface that connects to it. When you migrate, the hardware wallet itself does not change. Instead, you would connect the same Ledger to the destination wallet application, and it would generate the same addresses.

The advantage is that you never need to export or import a recovery phrase at all. The hardware wallet remains in your physical control, and the recovery phrase for the hardware device never leaves the device. The disadvantage is that the destination wallet must support hardware wallet integration. If it does not, you cannot simply import the hardware wallet’s recovery phrase in the normal way. You would need to create a new wallet in the destination application and manually transfer assets from the hardware wallet addresses to the new wallet, just as you would if the derivation paths did not match.

Testing becomes even more important with a hardware wallet migration. Before transferring funds, connect your hardware wallet to the destination wallet, verify that the addresses shown match the ones from Phantom, and perform a test transaction. Hardware wallets have long recovery procedures and require careful handling, so confirming compatibility before committing large amounts is essential.

Data you lose and cannot recover in migration

Transaction history within Phantom is local to the application. When you move to a new wallet, the new wallet will not automatically import your past transactions. You can reconstruct the history by connecting to a blockchain explorer and searching for your address, but any notes, categories, or personal labels Phantom stored for those transactions will be gone. If you need a complete record for tax or accounting purposes, export or screenshot your Phantom transaction history before deleting the application.

Custom address labels and contact names are also stored only in Phantom’s local database. If you have saved addresses under names like “Exchange withdrawal” or “Friend’s Solana account,” those labels will not transfer. The destination wallet will show raw addresses until you re-enter those names manually.

Phantom’s swap and bridge history is another area of loss. The application may have recorded which swaps you performed and on which dates. That information does not export. If you need it, the blockchain explorer can show you the transactions, but you will see only the contract interactions, not the human-readable swap intent. Similarly, any security preferences or notification settings in Phantom must be reconfigured in the new wallet.

The most important safeguard is understanding that blockchain data—your balances, NFT ownership, transaction records, and on-chain interactions—persist regardless of which wallet application you use. What does not persist is application-level metadata. By understanding the difference, you can plan a migration that preserves what matters and accepts the loss of what is merely convenient.

Why some wallets cannot import a Phantom recovery phrase

Not every wallet application can import a Phantom recovery phrase and generate the same addresses. This happens because of derivation path standards. Bitcoin wallets typically use BIP44, Ethereum wallets use BIP44 with a specific path, Solana wallets often use a different path, and some newer chains have their own conventions. If Phantom and the destination wallet do not both support the same standard for a given blockchain, the recovery phrase will not produce matching addresses.

Before migrating, check the destination wallet’s documentation to see which derivation paths and blockchain standards it supports. If it explicitly states support for Phantom or for the specific blockchains you hold assets on, migration is likely to work. If the destination wallet is chain-specific (such as a Bitcoin-only wallet) or uses proprietary derivation methods, you may need to transfer assets instead of importing the recovery phrase.

Some wallets offer flexibility by allowing you to manually specify a derivation path or import using a non-standard seed. That option can work if you know the exact path Phantom uses, but it requires technical knowledge and is prone to error. For most users, comparing documentation or performing a test import on a small test recovery phrase is more practical.

Using Phantom as the intermediary if migration fails

If the destination wallet does not generate matching addresses when you import the recovery phrase, you have not lost access to your assets. You still own them and can access them through Phantom. The most straightforward recovery is to reinstall Phantom, import the recovery phrase again, and then transfer assets from Phantom to the destination wallet’s addresses the same way you would send funds to any external address.

This means Phantom serves as a bridge. You can download Phantom again from visit phantom.com and reimport the recovery phrase to get access to the original addresses. From there, you can move assets to the destination wallet at your own pace, one blockchain at a time, without worrying about derivation paths.

The cost is network fees for each transfer and the inconvenience of running Phantom temporarily. The benefit is that you maintain full control and can ensure every asset reaches its destination correctly. For users with significant holdings or complex account structures, this approach is often worth the time and fees.