Migrating from Trust Wallet to Phantom: Import Seed Phrase, Move Assets, and Avoid Double-Bridge Losses

A user has accumulated assets across multiple blockchains using Trust Wallet over several years. They now want to switch to Phantom for its superior transaction simulation, scam detection, and cleaner interface. The practical question is not whether migration is possible—it is how to move substantial holdings without triggering bridge failures, double-spending, or accidental losses that are difficult to reverse. Trust Wallet and Phantom both support self-custody, but they have different network support, different security features, and different fee structures. Moving between them requires a methodical approach.

The stakes are high because the two wallets do not share identical blockchain support. Trust Wallet may have assets on chains that Phantom does not support directly, forcing a choice between abandoning those positions, bridging to a supported chain with execution risk, or maintaining a split wallet setup. A hasty migration can result in funds locked on unsupported chains, unnecessary bridge slippage, or transactions approved without the plain-language preview and scam detection that Phantom provides. The goal is to move assets safely, understand the true cost of cross-chain transfers, and reach a state where all holdings are accessible through a single application.

Understand what Phantom will and will not support

Before importing anything into Phantom, audit your Trust Wallet holdings against Phantom’s supported networks. Phantom officially supports Solana, Ethereum, Polygon, Base, Bitcoin, Sui, and several others. If you hold assets on Arbitrum, Optimism, Avalanche, Cosmos, or less common chains, Phantom may not have built-in support for those networks. This does not mean the tokens are lost, but it does mean you cannot access them directly through Phantom’s interface without adding custom network configurations—and Phantom’s limitations on custom networks mean this option has significant practical constraints.

The implication is straightforward: any holdings on unsupported chains must be bridged to a supported network before you can manage them through Phantom. Bridging introduces slippage, bridge fees, and execution risk. A bridge failure can leave funds locked in a contract or on an intermediate chain. If you have, for example, USDC on Arbitrum, you must choose between bridging it to Ethereum, Polygon, Base, or another supported chain supported by Phantom, or leaving it behind in Trust Wallet. The “correct” destination depends on your transaction patterns, fee tolerance, and whether you plan to use those funds for DeFi or simply hold them.

Review each asset and its current blockchain location. List the unsupported chains explicitly. Then decide: bridge to a supported Phantom network, convert to a supported equivalent, or leave the position in Trust Wallet as a long-term secondary wallet. This decision should be made before you touch the recovery seed phrase, because reversing a bridge after it has been initiated is impossible. The cost of waiting a few minutes to verify bridge routes is trivial compared to the cost of bridging to the wrong destination.

Create a new Phantom wallet and verify the recovery phrase before importing

Do not immediately import your Trust Wallet seed phrase into Phantom. Instead, create a fresh Phantom wallet first. This step allows you to verify that Phantom generates correctly on your device and that you can view your recovery phrase in Phantom’s interface. Many users skip this step and regret it later, because if you discover a problem after importing your existing seed phrase, you have already put your Trust Wallet funds at risk by adding them to Phantom’s application environment.

To begin, install Phantom on your browser or device. The browser extension is available on Chrome, Brave, and Firefox; the mobile version is available on iOS and Android through the Phantom mobile app stores. Launch the extension or app, select “Create Wallet,” and Phantom will generate a new 12-word recovery phrase. Write this phrase down on paper or use a hardware backup device. Do not skip this step—the recovery phrase is the master key to this wallet and must be stored offline.

After writing down the recovery phrase, Phantom will ask you to verify it by selecting the words in the correct order. Complete this verification. Then, set a password and enable biometric authentication if your device supports it. Test a simple transaction or network switch to confirm that the wallet is working. Only after this entire process should you proceed to import your Trust Wallet seed phrase. If anything is unclear at this stage, do not continue. An extra 30 minutes of testing now prevents hours of confusion later.

Import your Trust Wallet seed phrase and verify all addresses match

Once you have created and tested a fresh Phantom wallet, you are ready to import your Trust Wallet recovery phrase. In Phantom, select “Import Wallet,” choose the number of words in your recovery phrase (usually 12), and enter the words exactly as they appear in Trust Wallet. Case and spelling matter. If you make a mistake, Phantom will detect it and show a different set of addresses.

After you import the phrase, Phantom will display the master wallet address and, if you expand the wallet view, the individual addresses for each network. Here is the critical step: compare these addresses to what Trust Wallet shows for the same recovery phrase. Open Trust Wallet on the same device, go to the wallet settings, and view the recovery phrase. Then add that phrase to a separate temporary wallet or use a tool like Ian Coleman’s BIP39 tool to verify that the derivation paths match. The addresses should be identical.

If the addresses do not match, do not proceed further. This indicates a derivation path issue, meaning the two wallets are generating different addresses from the same seed phrase. This is not uncommon and is usually caused by differences in how each wallet interprets the recovery standard. If addresses do not align, you have three options: use Trust Wallet’s derivation path by checking whether Phantom offers a custom derivation option, manually verify which addresses actually hold the funds in a blockchain explorer, or accept that you may need to use both wallets and bridge assets manually. The worst mistake is to assume the addresses match when they do not, then send funds to an address you do not control.

Audit asset locations and plan your bridging strategy

Once addresses are verified, review every asset and its current blockchain location. Use a blockchain explorer such as Etherscan (for Ethereum and Ethereum-compatible chains) or Solscan (for Solana) to confirm the exact balances and chain positions. Create a simple spreadsheet listing each asset, its current chain, its current balance, the supported Phantom chain you plan to move it to, the bridge you will use, and the estimated cost.

For example, if you hold 1,000 USDC on Arbitrum, you might decide to bridge it to Ethereum using Stargate, Across, or Arbitrum’s official bridge. Each bridge has different fees and settlement times. Stargate might charge 0.5% plus gas, Across might charge 1% plus gas, and the official bridge might have no token fee but higher gas costs. For a $1,000 position, this could be a $5 to $15 decision per bridge. For smaller positions, the percentage fee might exceed the absolute value it makes sense to migrate.

Assets on chains Phantom does not support but which have a wrapped equivalent on a supported chain can often be converted more efficiently. For instance, if you hold wrapped MATIC on a non-Ethereum chain, you might unwrap it, bridge the underlying Polygon native token to Ethereum or Polygon, and then re-wrap if needed. This is not always cheaper, but it is worth calculating before committing to a bridge.

The golden rule is: never bridge without checking the destination. Confirm that the receiving chain and wallet address are correct. Confirm that the bridge route exists and is actively supported. Confirm the fee and expected output. Only then initiate the transfer. A bridge transaction cannot be reversed once it has been signed.

Execute bridges with confirmation, not speed

When you are ready to move an asset across chains, open Phantom (not Trust Wallet) and navigate to the token or asset you want to bridge. Many assets can be bridged directly through Phantom’s swap interface or through partner bridges integrated into the wallet. If Phantom does not offer a direct bridge route, use a bridge interface such as Stargate, Across, or the official bridge for the source chain. In either case, follow the same verification steps.

Before signing any bridge transaction, Phantom will display a transaction simulation and a plain-language preview of what the transaction will do. Read this preview carefully. It should clearly indicate the source chain, the asset being bridged, the destination chain, the receiving address, and the expected output amount. If the preview is vague, confusing, or different from what you expected, do not sign the transaction. Close the browser tab or app, wait a few minutes, and try again.

After signing a bridge transaction, the funds will be locked on the source chain and the bridge contract will orchestrate the release on the destination chain. This process typically takes seconds to minutes for optimistic bridges (like Stargate), but can take much longer for message-passing bridges (like IBC for Cosmos chains) or finality-dependent bridges. Do not assume a bridge has failed just because it is slow. Check the transaction hash on a blockchain explorer and look for “In Progress” or “Pending” status.

Once a bridge has confirmed and you see the asset appear in Phantom on the destination chain, verify the balance. If the amount is less than you expected, check whether the bridge fee was larger than you anticipated or whether the token has a transfer tax. Some tokens charge a percentage of every transfer as a fee; if you moved 1,000 tokens and received 950, the difference is the token’s tax, not a bridge failure. This is worth knowing now so you can adjust your migration plan for other assets.

Handle small or dust positions carefully

As you migrate, you will likely encounter small positions that have accumulated over time—a few dollars worth of a testnet token, a reward from an airdrop, a failed purchase on a small exchange. These “dust” positions often have two characteristics: they are on unsupported chains, and the cost to bridge them exceeds their value.

For these positions, you have limited practical options. You can leave them in Trust Wallet and maintain it as a secondary wallet for historical holdings. You can attempt to bridge them and accept a net loss if the fee is high. Or, if the token has a centralized exchange listing, you can sell it for a stablecoin, transfer the stablecoin to a supported chain, and hold the proceeds in Phantom. The key is to make a deliberate decision rather than forgetting about the position and discovering months later that you have forgotten funds somewhere.

Document which assets you chose to leave behind and where. Keep the recovery phrase for Trust Wallet in a secure location as long as it contains funds, even if you no longer use it for regular transactions. Future versions of Phantom might add support for more chains, or you might want to move those funds years from now when the bridge environment has changed.

Test transactions in both wallets before declaring migration complete

Once you have imported your seed phrase into Phantom and bridged the major assets to supported chains, do not immediately archive Trust Wallet. Instead, conduct a series of small test transactions to confirm that Phantom’s security features are working as expected and that you understand how to use them.

Send a small amount of a supported asset (such as SOL, ETH, or USDC) to a test address you control on another wallet or exchange. As you do this, pay attention to Phantom’s transaction simulation feature. Before you sign any transaction, Phantom should display a clear preview showing the receiving address, the amount, the network, and the estimated gas fee. If the address is flagged as “high risk,” pay attention to that warning. Scam detection is not perfect, but it catches many common phishing attempts and token scams.

Perform a plain-language preview for a swap or bridge transaction as well. This feature is where Phantom’s design philosophy differs from Trust Wallet. Instead of showing you raw hexadecimal code or a generic “approve transaction” button, Phantom attempts to explain what the transaction actually does in human-readable terms. If the preview does not match what you intended, Phantom makes it easy to reject the transaction without penalty.

These test transactions may cost a few dollars in gas fees, but they are educational investment. You will learn how to read Phantom’s interface, understand its warnings, and build confidence before moving larger amounts. After a few successful tests, you can consider the migration functionally complete and begin using Phantom as your primary wallet.

Maintain backup security and plan for long-term recovery

You now have a new Phantom wallet with a recovery phrase that you wrote down when you first created it. You also still have your Trust Wallet recovery phrase, which might contain some remaining assets. Both recovery phrases are cryptographic access keys. If either is compromised, an attacker can transfer all assets associated with that wallet.

Store both phrases in a secure offline location. Options include a hardware security key, a safe deposit box, a metal backup device like a Ledger Steel or KeepKey, or a hidden physical location. Do not store recovery phrases in cloud services, email, text messages, or password managers. Do not type them into websites, even if the website claims to verify them. Do not take photographs of the phrases unless you have secure storage for the resulting images.

Consider whether your recovery strategy is survivable if you become incapacitated. Some users create a written letter of instructions for family members, stored with the physical recovery phrases, explaining where assets are located and how to recover them. Others use a separate Phantom wallet specifically for emergency funds with a recovery phrase known to a trusted contact. The trade-off between security and recoverability is personal, but it is worth considering.

As a final step, perform a Phantom wallet setup review. Ensure that your password is strong and unique, that you have enabled biometric authentication if available, and that you understand how to export your recovery phrase again if needed. Phantom’s settings should include an option to view your recovery phrase; use this to verify that you have the correct phrase written down. Then store the written version offline and disable the “show recovery phrase” option if it is enabled in sensitive locations.

Troubleshoot common migration problems

If you encounter problems during migration, the most common issues are address mismatches, failed bridges, and forgotten asset locations. Address mismatches occur when the imported seed phrase produces different addresses in Phantom than it did in Trust Wallet. This is usually a derivation path issue and cannot be fixed by re-importing; instead, verify which wallet actually controls the funds using a blockchain explorer and keep both wallets accessible.

Failed bridges typically manifest as a transaction that appears “stuck” on the source chain or a transaction that completes on the source chain but does not appear on the destination chain within a reasonable time. Most bridges provide a status dashboard where you can enter the source transaction hash and check progress. If the bridge interface shows “Pending” after several hours, you can often manually trigger a “release” or “claim” transaction on the destination chain to complete the transfer. Avoid initiating a new bridge transaction unless you have confirmed that the original transaction failed; double-bridging can leave you with funds on two chains.

Forgotten asset locations are less technical but more frustrating. If you moved assets months ago and cannot remember which chain a particular token is on, use a blockchain scanner to check all your Phantom addresses on different chains. Phantom’s address book and transaction history can help, but the ultimate source of truth is the blockchain itself. A tool like Zapper or DefiLlama can aggregate your holdings across multiple chains and show you everything at once.