A cryptocurrency user holds assets across MetaMask, a Ledger hardware wallet, and a legacy desktop application. Moving to a consolidated interface presents a practical choice: which wallet supports multiple blockchains, keeps private keys under personal control, and makes the transition straightforward without resorting to exchanges or risky manual transfers. Guarda wallet addresses this directly by accepting import from dozens of wallet types while maintaining non-custodial architecture, meaning the user retains control over their recovery phrase and signing keys throughout the process.

The import process, however, is not a single standardized flow. Different wallet types—hierarchical deterministic wallets, hardware devices, paper backups, and platform-specific applications—each follow their own rules for key derivation, address generation, and recovery. Moving from MetaMask to a multi-platform wallet like Guarda requires understanding not only the technical steps but also the security implications of exposing private keys or recovery phrases, the proper sequence of verification, and how to confirm that funds have moved correctly before closing the original wallet.

Understanding wallet import versus wallet recovery

Before performing any import, distinguish between two different operations. Recovery means restoring a wallet from a backup phrase that the user previously created and saved offline. The recovery phrase—typically 12 or 24 words—contains the seed from which all addresses and private keys can be mathematically derived. Import

Guarda wallet supports all three approaches. A user can recover an existing wallet by entering a 12 or 24-word seed phrase directly into the application. They can connect a hardware device such as Ledger or Trezor without ever exposing the seed phrase to the computer, because the device performs signing internally. They can also link to MetaMask or other browser extensions via API connection, allowing asset viewing and transaction approval without exporting keys. Each method carries different security properties and different operational workflows.

The most common confusion arises when users treat import and recovery as interchangeable. Importing a recovery phrase into a new wallet is technically recovery, but it requires typing or pasting that phrase into the application—an exposure point that hardware wallets are designed to eliminate. Similarly, connecting to MetaMask via API is an import operation that does not require the private key to leave the original application, whereas exporting MetaMask’s private key and pasting it into Guarda wallet exposes the key to the clipboard, browser memory, and the destination application simultaneously. The security implications are not equivalent, and the choice of method matters more than the convenience of a particular interface button.

Users migrating to Guarda wallet from other applications should therefore start by asking: Do I need to move the key itself, or can I keep it in its current location and access it from the new wallet? If the original wallet is a hardware device or MetaMask instance that the user trusts, keeping the key there and connecting via Guarda wallet’s import features is safer than extracting it. If the original wallet is a mobile app being retired or a paper backup being consolidated, recovery into Guarda wallet may be the appropriate step.

Recovering from a backup phrase into Guarda wallet

The most straightforward recovery uses a seed phrase that the user has safely stored offline. To begin, open Guarda wallet on the desired platform—web, desktop, mobile, or browser extension. Select the option to import or recover an existing wallet rather than creating a new one. The application will prompt for the recovery phrase and, in some cases, an optional passphrase (also called a BIP39 passphrase) that may have been set on the original wallet.

Enter the 12 or 24 words in the correct order without alterations, hyphens, or extra spaces. Even a single character error will produce a completely different set of addresses. If a passphrase was used on the original wallet, it must be entered exactly as it was created—capitalization, punctuation, and spacing all matter. After entering the phrase and any passphrase, Guarda wallet will derive the wallet’s public addresses and display them. At this point, the application has reconstructed the wallet mathematically but has not yet moved any funds; the blockchain balances are checked via an external node or service.

Before confirming the import, verify at least one address and its balance against the original wallet or a blockchain explorer. Open the wallet from which you exported the phrase—MetaMask, MyEtherWallet, a previous Guarda wallet instance, or any other application—and compare the first or most recently used address. If the addresses match, the phrase was entered correctly. If they differ, double-check for transcription errors and try again before proceeding. This step prevents the common mistake of recovering the wrong wallet or discovering too late that a backup phrase is corrupted or incomplete.

Once verification is complete, Guarda wallet will display the recovered accounts and their balances across supported blockchains. The wallet is now ready to use, and the original application can be closed. However, if funds are spread across multiple blockchains or multiple addresses within the recovered wallet, do not close the original application immediately. Instead, allow a few minutes for the Guarda wallet to fully sync and display current balances, then perform a quick sanity check: the total balance across all addresses in Guarda wallet should match the original wallet’s total. Discrepancies are rare but indicate either a network synchronization delay or an import error that requires investigation before moving funds.

Connecting a hardware wallet to Guarda wallet

Ledger, Trezor, and other hardware wallets follow a different import model. These devices never export their private keys to any software. Instead, when a transaction requires signing, the hardware device receives an unsigned transaction, performs the cryptographic signing internally, and returns only the signature. Guarda wallet supports this model by detecting connected hardware devices via USB or Bluetooth, querying them for the public addresses they control, and passing unsigned transactions to the device for approval.

To connect a Ledger to Guarda wallet, first ensure the Ledger is connected to the computer or mobile device via USB or Bluetooth and unlocked. Install the appropriate app on the Ledger for the blockchain you want to access—the Ethereum app to manage ERC-20 tokens, the Bitcoin app for BTC, and so forth. The Ledger’s apps do not store funds; they only enable signing for that particular blockchain. Open Guarda wallet and select the option to connect a hardware wallet.

Guarda wallet will display detected devices and their addresses. Select the Ledger, and the application will load the public addresses currently derived from that device’s seed. These addresses are mathematically identical to the addresses shown on the Ledger’s own screen and in any other software that connects to the same Ledger. Verify one address on the Ledger’s display to confirm the connection is working and that you are about to control the correct device. After confirmation, Guarda wallet will display your Ledger accounts and balances without ever requiring the Ledger’s private key or recovery phrase to enter the application.

When you later approve a transaction in Guarda wallet, the wallet creates the transaction details and sends them to the connected Ledger. The Ledger’s display shows the recipient address, amount, and fee. You review these details on the hardware device’s small screen and approve or reject the transaction by pressing physical buttons. Only after you press approve does the signature return to Guarda wallet, which then broadcasts the completed transaction to the blockchain. This design means that even if the computer running Guarda wallet is compromised by malware, the transaction details and signing authority remain under the Ledger’s control.

Importing from MetaMask while managing security exposure

MetaMask is a browser extension that controls private keys in a browser environment. Moving to Guarda wallet often makes sense for users who want a dedicated, non-custodial wallet application separate from their browser or who want access across multiple platforms without relying on browser extensions. However, the import process requires careful handling because MetaMask stores private keys in browser storage encrypted with a password, and exporting them into a different application temporarily exposes them to the clipboard and application memory.

The safer approach is to treat MetaMask as a persistent connection rather than a one-time migration. Guarda wallet’s browser extension can connect to MetaMask via injected web3 APIs, allowing you to approve transactions and view balances without exporting your MetaMask key. If you use both wallets alongside each other, MetaMask remains the custodian of its own keys, and Guarda wallet can route certain transactions through MetaMask when appropriate. This avoids the need to export the key entirely.

If you do decide to migrate your MetaMask accounts to Guarda wallet completely, the proper procedure is to recover using your MetaMask recovery phrase rather than exporting individual private keys. Open MetaMask, go to the settings menu, select “Security & Privacy,” and locate your recovery phrase. Write it down offline in a safe location—never store it in a cloud service or digital file. Once you have the phrase securely backed up, open Guarda wallet, select recover from existing wallet, and enter the recovery phrase. Guarda wallet will derive the same addresses that MetaMask controls, and you will have access to the same funds through Guarda wallet. The key difference is that Guarda wallet is now the application holding the recovered key, and MetaMask’s instance of the same key can be deleted afterward.

Do not export individual private keys from MetaMask and paste them into Guarda wallet. This approach creates unnecessary exposure: the key passes through the browser clipboard, MetaMask’s memory, and the Guarda wallet’s import field. If your computer is compromised or if a malicious browser extension is running, any of those intermediaries could capture the key. Recovery phrase import is more secure because the phrase is more easily typed from a written backup and is more resistant to automated clipboard theft due to its length and format.

Multi-blockchain address verification after import

Guarda wallet’s support for 400+ cryptocurrencies and tokens across multiple blockchains creates a verification complexity that single-chain wallets avoid. When you recover a wallet that previously contained Bitcoin, Ethereum, Tezos, Cardano, and Cosmos assets, Guarda wallet must derive addresses across all those blockchains from the same recovery phrase. The application uses standardized derivation paths defined by BIP44 and blockchain-specific standards, which means the addresses should match any other wallet software using the same phrase and paths.

After recovery, spend time verifying addresses on at least two different blockchains. Open a blockchain explorer—Etherscan for Ethereum, blockchain.com for Bitcoin, or a chain-specific explorer for Cosmos or Cardano—and search for the first address shown in Guarda wallet. The explorer should display the address’s current balance and transaction history. Compare this with the balance shown in Guarda wallet. If they match, the recovery was successful for that chain. Repeat this check for a second blockchain to gain confidence that the derivation paths are correct across the board.

If an address shows in Guarda wallet but the explorer returns no results or a zero balance, do not assume the recovery failed. The address may simply have no transactions yet. However, if you know the original wallet had a specific balance and Guarda wallet shows a different total, investigate before closing the original application. Common causes include uncompleted syncs—Guarda wallet may still be querying blockchain nodes for the latest balance—or incorrect recovery if a passphrase was used and not properly entered. Give the wallet five to ten minutes to fully sync, then check again.

Handling wallet-specific complications and edge cases

Some wallet types do not follow standard BIP44 derivation paths, which can create address mismatches during import. Exodus wallet, for example, uses a custom derivation scheme for certain blockchains. If you are moving from Exodus to Guarda wallet using a recovery phrase, your Bitcoin addresses in Guarda wallet may differ from those in Exodus even though the phrase is the same. In this case, you cannot simply recover the phrase into Guarda wallet and expect to see all previous addresses. Instead, you must move funds from Exodus to a standard address (such as a Bitcoin address in Guarda wallet that uses BIP44 derivation) and then manage the Exodus wallet and Guarda wallet as separate entities.

Paper wallets—addresses and private keys printed on paper—must be imported into Guarda wallet by entering the private key manually. This is riskier than phrase recovery because a single private key gives access to one specific address, and if compromised, the entire balance at that address can be moved. Only import a paper wallet private key when you are about to move the funds out of that address to a new wallet. Enter the private key once, transfer all funds, and never reuse that paper wallet address.

Wallets that use non-standard passphrases or have been restored with errors may show unexpected addresses or balances. If you are recovering a wallet that you have not used in years and are uncertain of the passphrase, write down what you believe the passphrase was and try the recovery in Guarda wallet without a passphrase first. If that produces addresses you recognize, no passphrase was used. If not, try recovery again with a passphrase. Trying multiple times is safe because entering an incorrect recovery phrase or passphrase in Guarda wallet generates a valid but wrong wallet—it does not damage the blockchain or the original wallet.

Some users have accessed a guarda wallet on multiple platforms—web, desktop, and mobile—using the same recovery phrase. If you are consolidating devices, remember that all platforms will derive the same addresses from the same phrase. You do not need to import the phrase into each platform separately unless you want separate wallets. For most users, one recovery phrase creates one logical wallet that can be accessed from any Guarda wallet instance.

Post-import security and cleanup procedures

After successfully importing into Guarda wallet, the original wallet application or device is no longer the active custodian of your funds. However, the security of your migration is not complete until you have performed final cleanup and secured your backup phrase. First, create a new backup phrase in Guarda wallet itself if you have not already done so. The imported phrase is still valid, but Guarda wallet may have its own backup and recovery procedures that you should become familiar with.

Second, verify that you can recover your Guarda wallet independently. Write down the recovery phrase provided by Guarda wallet, store it offline, and then delete and reinstall the application on one device. Use the recovery phrase to restore the wallet from scratch. This test confirms that your backup is accurate and that you can recover independently if you lose access to your devices. Do not skip this step, even if it feels redundant. A backup phrase that has never been tested is not a reliable backup.

Third, and only after you are confident in your Guarda wallet access, decide what to do with the original wallet. If it was a hardware wallet such as Ledger, you may want to keep it as a backup device. If it was MetaMask or a mobile wallet, you can uninstall it. If it was a paper wallet, destroy the paper securely—burn it, shred it, or use another method that prevents recovery. If the original wallet was a multi-signature wallet or had specific settings you want to preserve, consider leaving it installed but not using it for new transactions; this gives you a fallback if something goes wrong with Guarda wallet.

Finally, examine your staking and DeFi positions in Guarda wallet’s interface. If you had staked Tezos, Cardano, Cosmos, or Tron in the original wallet, those positions may require unstaking and re-staking through Guarda wallet to ensure delegations are correctly configured. Guarda wallet supports staking for these assets, but the delegation may not transfer automatically during import. Verify that any staking or yield-generating positions are active in Guarda wallet before closing the original wallet application.

Common mistakes and how to avoid them

The most frequent import error is mistyping or miscopying the recovery phrase. Users often try to speed through the recovery process and make a single-character mistake, which produces a valid but wrong wallet. To avoid this, type the recovery phrase carefully, one word at a time. Guarda wallet’s interface typically suggests words as you type; use these suggestions rather than typing the entire word. After entering all words, review each one before confirming. If you are reading from a written backup, have someone else read it aloud while you verify what you have entered, or read it yourself twice to catch errors.

A second common mistake is importing the same recovery phrase into multiple Guarda wallet instances and then using them as if they were separate wallets. They are not separate—they all derive from the same phrase and control the same addresses and funds. Using two instances simultaneously can create confusion about which wallet is authoritative and can lead to sending funds to the wrong address or approving conflicting transactions. If you want separate wallets, create a new wallet in Guarda wallet rather than importing the same phrase twice.

A third mistake is not verifying addresses after import. Users sometimes recover a wallet successfully and then immediately move funds without checking that the recovered addresses match the original. Days later, they realize the addresses do not match and conclude that their funds have disappeared, when in fact the import went wrong and they now control a different wallet. Address verification takes only a few minutes and prevents this kind of panic and potential fund loss.

Finally, users sometimes import a wallet into Guarda wallet and then close the original wallet application without ensuring that the import was complete and correct. If the Guarda wallet application encounters an error during sync or if a passphrase was mistyped, you may not discover the problem until after you have deleted the original wallet and erased the backup phrase from memory. Always keep the original wallet and backup available for at least one week after import, during which time you should verify that everything works and that you can access all of your funds through Guarda wallet.