Solflare Wallet Import: Migrating from Phantom, Magic Eden, or CLI Keypairs

A Solana user holds funds across multiple wallets: some in Phantom, others in Magic Eden, and perhaps a keypair generated from the command line years ago. Consolidating into a single application sounds logical, but the import process carries real risks. A keypair can be copied wrong, a seed phrase mistyped, or a recovery phrase lost during migration. Unlike exchanges where customer service can sometimes reverse mistakes, blockchain transactions are final. The money goes where the imported keypair actually points, not where the user intended.

Solflare offers a clear alternative to this scattered approach. As a non-custodial Solana wallet built specifically for the Solana blockchain, it supports SOL, SPL tokens, NFTs, staking, and dApp connections from a single interface. The wallet is available as a browser extension for Chrome, Brave, Edge, and other Chromium-based browsers, as well as mobile applications. But before importing, a user should understand exactly what they are importing, how to verify it worked, and what to do if something goes wrong halfway through.

Understanding what you are actually importing

A Solana keypair is fundamentally a cryptographic secret: a private key that authorizes transactions and proves ownership of a public address. That secret can be stored in many formats. Phantom and Magic Eden present the keypair as part of a recovery phrase—typically 12 or 24 words derived from a BIP39 seed. A CLI keypair, by contrast, is often a raw JSON file containing base58-encoded or hex-encoded private key data. A keystore file is an encrypted container holding the private key behind a password. Each format requires a different import path, and using the wrong path is one of the easiest ways to lose access to funds.

The critical distinction is between the secret itself and its representation. Two wallets can point to the identical Solana address if they import the same private key correctly, even if the original wallet applications looked completely different. But if a character is miscopied, if a JSON field is truncated, or if the wrong encoding is assumed, the resulting wallet will have a different address and no funds. The original keypair is still valid; it is just not tied to the new wallet application.

Before importing anything into Solflare wallet, confirm the source of what you are importing. If the keypair came from Phantom, locate the recovery phrase—not a screenshot or password, but the actual 12 or 24 words. If it came from Magic Eden, use the same recovery phrase if the wallet was created with one, or export the private key if it was imported from elsewhere. If it came from a CLI tool, find the JSON keystore file or the raw private key string. Do not trust memory here. Write down or copy the exact source, verify it offline once, and only then proceed to import.

Importing from Phantom or other BIP39 seed phrases

Phantom wallets typically use a 12 or 24-word recovery phrase that follows the BIP39 standard. This phrase is a mnemonic representation of a master seed, and from that seed, Phantom derives one or more keypairs depending on the derivation path it uses. When you import this phrase into Solflare, the wallet needs to apply the same derivation rules to arrive at the same address.

The standard Solana derivation path is m/44’/501’/0’/0′. Some wallets default to this; others let you choose. If you import a phrase and the resulting address does not match your original Phantom wallet, the derivation path may be the culprit. Phantom, Magic Eden, and Solflare should all use the standard path by default, but if a wallet was set up with a custom derivation path or an older tool, you may need to specify a non-standard route.

To import in Solflare, open the wallet setup screen and select the option to import an existing seed phrase. Enter the recovery words carefully—spacing and order matter. Solflare will display the derived address before you confirm. Stop and compare this address to your original wallet address. If they match, you can proceed. If they do not, do not press confirm. Instead, double-check the phrase for typos, verify the word order, and try again. Once you confirm, Solflare will create a wallet pointing to that address. If the address is wrong, the wallet will be created, but it will show zero balance because it is not the address holding your funds.

One often-overlooked step is creating a new backup. Even though you are importing an existing phrase, generating a new backup in Solflare and storing it securely creates a record of where this wallet is now active. If Solflare is later uninstalled and you need to restore, you will have documentation of which phrase to use with which application. This backup should be stored offline, away from cloud services, email, or any internet-connected device.

Importing from a JSON keystore file or private key string

A JSON keystore file is an encrypted container that holds a private key. The encryption key is a password you set when the file was created, often by a command-line tool like the Solana CLI. The file typically contains an array of byte values, base58-encoded strings, or hex-encoded data depending on how it was generated. If you have this file, import it into Solflare using the JSON import option.

The process requires you to upload the keystore file and enter the password. Solflare will decrypt the file, extract the private key, and derive the corresponding public address. Again, verify the address before confirming. If the password is wrong, decryption will fail and the wallet will not be created. If the file is corrupted, the same result occurs. A corrupted keystore file cannot be salvaged through Solflare; you would need to restore it from a backup of the original file.

If you have only the private key string—not a keystore file—Solflare also supports direct private key import. This is riskier because a raw private key in text form is highly exposed. If you must use it, copy the string to a text editor offline, verify it once, and delete the clipboard immediately after pasting it into Solflare. Do not save the private key in a file on your computer or write it in an email. The moment Solflare has imported it and created the wallet, the private key should never be stored again in plaintext.

Verifying the import worked and confirming balances

After Solflare creates the wallet, the first verification step is to confirm that it shows the correct address. You can find the public address in the wallet interface; it should match the address you were using before. The address is not secret—you can display it, copy it, and share it. The private key is what you protect.

Next, check the balance. If SOL and SPL tokens are not visible immediately, give Solflare a moment to sync with the Solana network. The wallet may need to contact a public RPC endpoint to fetch account data. If the balance still does not appear after 30 seconds, refresh the page or close and reopen the wallet. If it still does not appear, the address in the wallet is not the address holding your funds. This is the most common import error: the address was derived incorrectly.

To troubleshoot, verify the address against a blockchain explorer. Go to Solscan.io or Solana Explorer, paste the address shown in Solflare, and check whether it has a balance and transaction history. If the explorer shows no balance but the address is correct, you may have imported the right address but it actually has no funds—perhaps they were already moved. If the explorer shows a balance but Solflare shows zero, the address in Solflare is different from what you thought. Go back and re-verify the imported source material.

Testing with a small transfer before moving all funds

Once the balance appears correctly in Solflare, resist the urge to move everything at once. Instead, send a small amount—0.1 SOL, a single NFT, or a test amount of SPL tokens—from another wallet to your Solflare address. This transaction should arrive within seconds. If it does, the wallet is receiving correctly and the address is definitely correct. If it does not arrive after two minutes, check the transaction ID from the sending wallet in the blockchain explorer to see what happened.

After the test transfer arrives, make a small outbound transfer from Solflare to a different address—another wallet, an exchange deposit address, or a friend’s wallet if they are willing to help. This confirms that Solflare can sign and broadcast transactions correctly. Do not use your backup address as a test destination, because if the transaction is lost, you might confuse the test with a real backup check.

These small transfers cost nothing meaningful in terms of fees—typically a few thousand lamports, a fraction of a cent. They are insurance against a much larger mistake. Only after both inbound and outbound transfers work should you consider moving your entire balance into Solflare or consolidating funds from multiple wallets.

Consolidating funds from multiple sources safely

If you are importing multiple keypairs—one from Phantom, another from Magic Eden, and perhaps a CLI keypair—each one becomes a separate wallet in Solflare. Solflare supports multiple accounts within a single wallet file, so you can import several keypairs and switch between them without having to reinstall or reconfigure the extension.

The challenge is moving funds from those separate accounts into a single consolidated address without making a mistake. Create the primary wallet first, generate a fresh backup, and verify its address. Then, from each secondary account, transfer your funds to the primary address. Do this one account at a time, and verify that each transfer arrives before initiating the next. If you batch multiple transfers simultaneously and something goes wrong, you will not know which transfer failed until they all settle.

After consolidation, you have a choice: keep the secondary imported accounts in Solflare for record-keeping, or delete them to simplify the interface. There is no technical reason to keep them, but some users prefer to retain them as a record of where funds came from historically. If you delete them, ensure that you have your recovery phrase backed up offline, because you will not be able to restore them from Solflare alone. The primary backup covers only the first imported phrase; additional imported keypairs may require separate backups of their original phrases.

Hardware wallet integration and cold storage options

For larger balances, Solflare supports hardware wallet integration with Ledger and Keystone. Instead of storing your private key in the browser extension, you can use a hardware device to sign transactions. This means your private key never touches the computer or browser, only the hardware device. Solflare can still manage your addresses, tokens, and NFTs—it just cannot spend them without the hardware device authorizing each transaction.

If you currently have funds in a software wallet like Phantom and want to move to hardware-backed Solflare, the process is different from a seed phrase import. You would create a new wallet on your hardware device, generate a new address, and then transfer your existing funds from the software wallet to that new hardware-backed address. This breaks the continuity with the original keypair but gives you a fresh, hardware-protected wallet.

The trade-off is convenience versus security. Hardware wallet transactions take longer because the device must physically sign each operation. Recovery is also less familiar—if you lose the hardware device, restoring access requires restoring the seed phrase on a new device. For most users holding five or more SOL or significant amounts of other tokens, the security benefit of hardware backing outweighs the convenience cost.

Common mistakes and how to recover from them

The most frequent import error is importing the wrong seed phrase or typing it incorrectly. The resulting wallet looks correct—it is a valid wallet with a valid address—but the address has no balance. If this happens, do not panic. You have not lost your funds; you have just created an extra wallet. Go back and re-import using the correct phrase, being extremely careful with spacing and word order. If you are unsure whether you have the phrase right, write it down and have someone else read it aloud while you verify each word against your backup. Once you import the correct phrase, the wallet with your actual balance will appear.

A second common mistake is importing the same phrase twice with different derivation paths, producing two wallets with two different addresses, both of which appear valid. To avoid this, check Solflare’s derivation path setting before importing. The default should be m/44’/501’/0’/0′, which is the standard. If you see an option to customize, do not change it unless you have a specific reason and understand what you are doing.

A third mistake is importing a phrase that was not actually associated with your balance. For example, you might have imported a phrase from an old wallet you no longer use, or a test phrase you created years ago. The wallet will import fine, but it will have no balance. To verify that you have the right phrase, check whether the address matches what you are looking for. You can cross-reference with a blockchain explorer, your exchange withdrawal history, or any record where you previously noted your Solana address.

If you delete a wallet from Solflare and later want to restore it, you will need the original recovery phrase. Solflare does not store the phrase—it only stores the encrypted wallet state. If you do not have the backup, you cannot restore that wallet. This is why creating and storing a backup immediately after import is critical, even if you also have the original backup from Phantom or Magic Eden. Keep multiple copies of critical backups in physically separate locations.

Securing the wallet after import

Importing a wallet is not the end of the security process. After the wallet is created and funds are confirmed, set a strong password if Solflare prompts for one. Some browser extensions offer optional password protection, requiring a PIN or password to access the wallet. If available, enable it. This prevents casual access if someone gains brief access to your browser.

Similarly, if you are using a mobile version of Solflare, enable biometric authentication or a strong PIN. On Chromium browsers, browser-level security such as operating-system fingerprint or system password can add another layer. None of these protections prevents a determined attacker who has full access to your computer or phone, but they make casual access significantly harder.

The backup phrase remains your most sensitive asset. Once Solflare has imported a phrase, you should treat the plaintext backup phrase as equivalent to the private key itself. Store it offline, away from cloud services, cameras, and shared devices. Consider splitting the backup into parts stored in separate physical locations—one copy in a safe deposit box, another in a fireproof safe at home, for example. If the entire recovery phrase is stored in one place and that place is compromised, all funds in that wallet can be stolen.

Finally, consider whether you should delete the old wallet applications after successful import. If Phantom and Magic Eden are no longer needed, uninstalling them reduces the number of extensions and applications that could be compromised. Solflare provides a cleaner, purpose-built interface for Solana, and consolidating into one application is often simpler than maintaining multiple wallet tools.