A user holds SOL, several SPL tokens, and NFTs spread across Phantom, MetaMask, and a Coinbase wallet. They have heard that the Solflare wallet extension offers superior staking functionality, better hardware wallet support, and a cleaner interface for managing Solana assets. The natural question is how to move everything over without creating duplicate wallets, losing access to funds, or exposing private keys to unnecessary risk during the transition.
Migration between non-custodial wallets is technically straightforward—a private key or seed phrase works the same regardless of which application reads it—but the operational sequence matters. Moving funds carelessly can create orphaned balances, confuse transaction history, or accidentally expose recovery information. This guide covers the safest paths to switch to the official Solana wallet extension, preserving all holdings and ensuring zero downtime.
The Solflare wallet extension accepts three independent import pathways: seed phrase, private key, and hardware wallet connection. Each has different security implications and recovery considerations. A seed phrase is a 12 or 24-word mnemonic that cryptographically derives all wallet addresses and private keys; it is the most portable recovery method but also requires the most careful protection during entry. A private key is a single credential that controls one specific account; importing it allows access to that address without knowledge of the seed phrase that originally generated it.
Hardware wallet connection differs fundamentally because it does not import a key at all. Instead, the extension communicates with a Ledger or other compatible hardware device to request signatures for transactions, keeping the private key isolated on the device itself. This is the most secure path for high-value accounts, but it requires the hardware wallet to be physically present and charged whenever a transaction is approved. For users migrating from a software wallet on their phone or laptop, hardware connection may represent an upgrade in security; for users accustomed to one-click approvals, it requires a workflow adjustment.
Choosing the right import method depends on whether the original wallet’s seed phrase is known and trustworthy. If migrating from Phantom, the user owns the seed phrase and can safely enter it into the Solflare wallet extension. If migrating from a centralized exchange connected wallet like Coinbase or MetaMask connected to a cloud recovery service, the seed phrase may have never been written down, making hardware wallet or private key export the only viable option. Users should never enter a seed phrase into an online or cloud-based service, regardless of how reputable the provider appears.
Before making any changes, create a backup of the current wallet’s seed phrase if possible. Write it on paper and store it separately from any device. This ensures that even if the migration encounters an unexpected issue, funds can be recovered from the original wallet indefinitely. Most wallet providers including Phantom, MetaMask, and Coinbase Wallet allow exporting a private key directly from a specific account without exposing the seed phrase.
The private key export process is usually found in wallet settings under a menu labeled “Export Private Key” or “Account Details.” The wallet typically requires the user to confirm ownership by entering the password or biometric authentication. Never screenshot or photograph the key; copy it directly from the wallet’s interface into a text document, a password manager, or a temporary note that will be deleted immediately after importing into Solflare. An intermediate step of pasting the key into an email draft or cloud note is acceptable only if the document is deleted within minutes and the account password is not reused elsewhere.
Once the private key is obtained, open the Solflare wallet extension and select “Import Account” rather than “Create New Wallet.” Choose the “Private Key” option and paste the credentials. The extension will derive the corresponding Solana address and display all associated SOL, SPL tokens, and NFTs. Verify that the displayed address matches the one shown in the original wallet—if it does not, stop immediately and check that the correct key was copied. Once confirmed, the imported account is now accessible through the Solflare wallet extension with the same security and functionality as a newly created wallet.
If the seed phrase from the original wallet is available and has been securely stored offline, importing it directly into the Solflare wallet extension is often faster than extracting individual private keys. This is the most practical path for users migrating from Phantom or other wallets where the seed phrase was properly documented during initial setup. The process carries no additional security risk compared to using the original wallet, provided the seed phrase has remained unexposed to networks, cloud services, or screenshots.
To import a seed phrase, open Solflare and select “Import Wallet” on the initial setup screen. Enter the 12 or 24-word mnemonic in the correct order, then set a password to encrypt the keys locally on the device. The extension will derive the same wallet addresses as the original application, allowing immediate access to all SOL, SPL tokens, and staking rewards. Because the same seed phrase is now accessible through two different wallet applications, users should consider this a temporary state: once all activity is migrated to Solflare and the old wallet is no longer needed, the seed phrase should remain stored securely but the original application can be disconnected or removed.
One critical detail is that Solflare will display a recovery phrase that differs from the one being imported. This is normal and does not indicate an error. When a wallet application imports a seed phrase, it generates a new recovery phrase for that application’s own backup purposes. The imported phrase still controls the accounts, but Solflare’s recovery phrase is what should be written down and stored if the user wants to recover the wallet through Solflare specifically. For most users, keeping the original seed phrase in secure storage and relying on it for long-term recovery is the simpler approach.
After successfully importing an account into the Solflare wallet extension, the next step is optional but recommended: transfer all remaining balances from the old wallet to the new one. This consolidates all activity under one application and reduces confusion about which wallet holds which assets. Solflare supports batch transaction functionality, allowing the user to bundle multiple token transfers into a single network request, which can reduce fees compared to sending each token individually.
Before initiating any transfers, open both wallets side by side and verify the receiving address shown in Solflare. Copy the address directly from the extension and paste it into the sending wallet’s “destination” field rather than typing it manually or relying on clipboard history. Even a single character error will send funds to a different address on the Solana network, where recovery may be impossible. Many wallet applications display a QR code that can be scanned to reduce typing errors; this is a worthwhile use of the feature.
Start with a small test transfer of one SPL token or a portion of the SOL balance. Confirm that the funds arrive in the Solflare wallet extension within a few seconds—Solana’s network typically finalizes transactions in under a minute. Only after verifying the test transfer should the user proceed to move larger amounts. For NFTs, the process is similar: open the collection view in the original wallet, select the NFT, and choose “Send” or “Transfer.” Paste the receiving address from Solflare and confirm. NFT transfers may take slightly longer to confirm but follow the same security practices as token transfers.
Once all funds have been moved and confirmed in Solflare, the original wallet can be disconnected from dApps and DeFi platforms. Users can remove the extension or app from their device if they are confident they will not need to access it again. The seed phrase or private key from the old wallet should remain stored securely in case emergency recovery is ever necessary, but active use should shift entirely to the Solflare wallet extension to avoid confusion about which wallet is the “primary” one.
For users who own a Ledger device or other compatible hardware wallet, migrating to the Solflare wallet extension can involve upgrading from a software-only setup rather than simply importing credentials. This approach keeps the private key isolated on the hardware device, which is more secure than any software wallet but requires the device to be connected whenever a transaction must be signed. Open Solflare, select “Connect Hardware Wallet,” and follow the prompts to authorize the connection over USB or Bluetooth, depending on the device type.
The Solflare wallet extension will detect the accounts available on the Ledger and display them with their current SOL and token balances. Select the account to use—typically the first one, labeled “Account 0″—and approve the connection. From that point forward, any transaction initiated in Solflare will require confirmation on the Ledger device itself. This two-step approval process is inconvenient for frequent traders but is the gold standard for security, particularly for accounts holding significant value.
If the user already held assets on a Ledger account before switching to Solflare, the same account will be accessible immediately; no funds need to be transferred because the account is controlled by the hardware wallet, not by the software extension. The Solflare interface is simply a new way to manage the same credentials. If migrating from a software wallet to a newly purchased Ledger, funds should be transferred from the old account to the new Ledger-backed account using the batch transfer process described above.
One of the primary reasons users switch to Solflare is its native staking functionality, which allows earning rewards by delegating SOL to validators directly from the extension. After successfully importing an account or connecting a hardware wallet, users can navigate to the staking section, select a validator, and approve a delegation transaction. Solflare displays estimated annual percentage yield (APY) and allows adjusting the amount of SOL to stake, while keeping the remainder liquid for other transactions. Staking is non-custodial: the validators do not control the funds, only the delegation, and the SOL can be undelegated at any time, though it takes approximately one epoch (roughly 2–3 days) to return to the wallet.
Advanced users who want to use a custom RPC node or private endpoint can configure this within the Solflare wallet extension settings. The default public RPC endpoints are sufficient for most users, but custom nodes can improve privacy by reducing exposure to Solflare’s standard routing or support specialized use cases like validating transactions against an archival node. Users should verify the RPC endpoint URL is correct before saving; an incorrect endpoint could cause the wallet to appear empty or display stale balances. For most users, the default Solana RPC configuration requires no action.
The Solflare wallet extension also enables offline transaction signing for additional security in high-stakes scenarios. A transaction can be created, signed locally on a secure device without internet connection, and then broadcast from a connected machine. This reduces the risk of malware or network interception during the signing process. For typical users managing moderate amounts of SOL and tokens, this advanced feature is optional, but it is available for those who want the maximum possible separation between the signing environment and the broadcasting environment.
The most frequent error during migration is re-entering a seed phrase into multiple applications simultaneously and then leaving both active. This defeats the purpose of migration because it doubles the number of devices and applications that could be compromised. If a user imports a seed phrase into Solflare and then continues using Phantom, both applications can spend from the same accounts. A compromise of either application compromises the entire wallet. The correct approach is to import once, verify balances, transfer all active funds to the Solflare wallet extension, and then discontinue use of the old wallet.
Second, users should avoid importing private keys or seed phrases into any online wallet, browser-based interface, or service offering to store them “in the cloud.” Even reputable-appearing services can be compromised, and the recovery phrase stored remotely is exponentially more vulnerable than one stored in a password manager on a personal device. The Solflare wallet extension itself is an offline-first application—the private keys are encrypted locally and never leave the browser—but third-party services claiming to back up or recover wallets should be treated with extreme skepticism.
Third, do not transfer all funds immediately after importing. Instead, send a small amount first to confirm the receiving address is correct. On blockchains like Ethereum or Polygon, this verification step is somewhat optional because erroneous addresses are usually inaccessible but harmless; on Solana, there is no inherent prevention against sending funds to an address that does not yet exist or is not owned by the intended recipient. Once the test transfer confirms successful delivery, proceed with moving larger amounts.
Finally, store the seed phrase or private key from the old wallet separately even after all funds have been migrated. The temptation to delete the recovery information is understandable—it feels like “cleaning up”—but that information is an irreplaceable backup. If the Solflare wallet is ever lost, deleted, or corrupted, the original recovery phrase can restore access to the funds. Deleting the backup only to discover a need for it weeks or months later is a common and preventable tragedy.
Once funds have been moved into the Solflare wallet extension, verify completion by checking the extension’s dashboard for the expected SOL balance, SPL token list, and any NFTs that were originally held. The solflare wallet extension should display the same token names and amounts visible in the original wallet, adjusted for any transfers that occurred. Open a Solana block explorer such as Solscan and search for the receiving address to confirm that all inbound transactions have been finalized.
For NFTs, the Solflare gallery should display thumbnails of each collection. If an NFT appears in the original wallet but not in Solflare’s gallery, it may be due to a network synchronization delay or a display issue. Refresh the extension or wait a few minutes, then reload. If the NFT still does not appear, open a block explorer, search for the NFT’s mint address, and verify that the ownership has been transferred to the Solflare wallet’s address. Solana NFTs are standard SPL tokens and should transfer identically to fungible tokens; if ownership is confirmed on-chain but not displayed in the extension, the issue is typically a gallery indexing delay rather than a missing asset.
Finally, disconnect the old wallet from any dApps or DeFi platforms where it was previously authorized. Open each application—Marinade, Magic Eden, Jupiter, or whichever services were used—and look for a “Disconnect Wallet” or “Revoke Access” option. This prevents the old wallet from continuing to grant approvals and reduces the number of active authorization touchpoints. Most dApps allow connecting multiple wallets, so the user can authorize the new Solflare wallet extension while disconnecting the old one.
Yes. If you have the seed phrase written down and stored safely, you can import it into the Solflare wallet extension by selecting “Import Wallet” and entering the mnemonic. The extension will derive the same accounts and display all associated balances. However, if the seed phrase has been stored in a cloud service, email, or messaging app, it should be considered compromised; in that case, export the private key from the original wallet instead and import only the specific account you want to use.
Importing a seed phrase or private key does not move any funds; it simply allows the Solflare wallet extension to access accounts that already exist on the Solana blockchain. All balances remain where they are. To consolidate everything into one wallet application, you must explicitly transfer the funds from the old wallet to the Solflare wallet extension using separate send transactions. Start with a test transfer of a small amount to verify the address is correct.
No. Once you have imported your seed phrase into the Solflare wallet extension and confirmed that all funds are accessible, you should discontinue active use of the original wallet. Keeping both applications active with the same seed phrase doubles the number of devices and applications that could be compromised. Instead, move all funds to Solflare, then uninstall or disable the old wallet.