A user holding cryptocurrency across multiple platforms faces a practical problem: fragmented asset locations, multiple login credentials, and the risk that any single platform could be compromised, restrict access, or disappear. Consolidating those holdings into a wallet where the user controls the private keys reduces some exposure, but the migration process itself requires care. Moving funds from an exchange, a legacy wallet, or another application introduces several decision points where mistakes can result in permanent loss.
Guarda Wallet’s non-custodial architecture means that once assets are imported, the user retains full control—but that control is only as good as the recovery process and the verification steps taken during import. Whether moving Bitcoin from a hardware wallet, Ethereum tokens from a MetaMask installation, or a complete portfolio from an exchange, the underlying principle is the same: confirm the destination, test with small amounts, and verify that funds arrive before moving larger balances.
Understanding the difference between creating and importing
Guarda Wallet supports two distinct entry points for users. The first is creating a new wallet from scratch, which generates a fresh recovery phrase and produces entirely new addresses for each supported blockchain. The second is importing an existing recovery phrase, private key, or public address from another wallet application. These are fundamentally different operations with different security implications and different use cases.
Creating a new wallet is appropriate when beginning with no prior holdings, or when a user wants to maintain a separate wallet for specific purposes—perhaps a “spending wallet” for frequent transactions and a “savings wallet” for long-term holdings. Importing is the correct choice when consolidating existing assets that are already stored elsewhere, whether in another non-custodial wallet, a hardware device, or an exchange-issued custody account.
The distinction matters because importing an existing recovery phrase into Guarda Wallet produces the same addresses and can access the same funds as the original wallet. If that original wallet is still in use on another device or application, the same private keys are now loaded on two separate systems. This is not necessarily dangerous—many users maintain copies of their recovery phrase written on paper and stored in physical vaults—but it does mean that the security of those funds is only as strong as the least-secure location where the keys exist. Once imported, Guarda Wallet’s encrypted local key storage and device-level encryption become part of the protection chain, but they cannot retroactively secure a recovery phrase that has already been exposed or stored carelessly elsewhere.
Obtaining and verifying a recovery phrase for import
A recovery phrase, also called a seed phrase or mnemonic, is typically a list of 12 or 24 English words that can regenerate all the private keys associated with a wallet. If the current wallet is a non-custodial application such as MetaMask, Trust Wallet, Ledger Live, or Trezor Suite, the user can access this phrase through the application’s settings menu. The process varies slightly between apps, but the principle is consistent: navigate to security or advanced settings, authenticate with a password or biometric, and display the recovery phrase on screen.
That moment of display is a critical security checkpoint. The recovery phrase should never be photographed, copied into a notes app, sent via email, or displayed on a screen shared with video conferencing software. Instead, transcribe it by hand onto paper, verify that each word matches exactly, and store that paper in a secure physical location such as a safe. If the current wallet is on a device that will be discarded or repurposed, the recovery phrase should be recorded before any factory reset occurs. Once a factory reset happens without a backup, recovery is generally impossible.
For users whose current holdings are on a cryptocurrency exchange such as Coinbase, Kraken, or Binance, the situation is more complex. Exchange-issued accounts do not typically provide a recovery phrase, because the exchange controls the keys on behalf of the user. In these cases, the user must withdraw the funds from the exchange to a self-custody address before importing into Guarda Wallet. The withdrawal process requires creating a receiving address in Guarda Wallet first, then using the exchange’s withdrawal form to send the assets. This introduces a network fee and a confirmation delay, but it is the necessary step to move from exchange custody to self-custody.
Preparing Guarda Wallet and creating the import destination
The wallet download page provides access to all platform versions: desktop clients for Windows, macOS, and Linux, mobile applications for iOS and Android, a web interface, and browser extensions for Chrome and other browsers. The choice of platform should reflect the user’s primary device and workflow. Desktop clients provide isolated encryption without relying on a web browser’s security model. Mobile applications offer convenience for frequent transactions and easier biometric authentication. Browser extensions integrate with existing browsing habits, though they share the browser process and any vulnerabilities the browser may have.
Once installed, launching Guarda Wallet for the first time presents a choice: “Create Wallet” or “Import Wallet.” Users migrating existing holdings should select “Import Wallet.” The interface will then ask for the recovery phrase, typically accepting either 12 or 24 words in the correct order. Do not skip the word verification step. After entering the phrase, Guarda Wallet will derive the same addresses that the original wallet produced, making the funds accessible through this new interface.
Before confirming the import, the user should verify that the wallet address list matches expectations. For Bitcoin, this means checking that the first few receiving addresses match what was shown in the original wallet. For Ethereum and other EVM-compatible networks, there is typically only one address per network, though the wallet can generate multiple addresses if configured for hierarchical deterministic (HD) key derivation. If the addresses do not match after import, do not proceed further. Instead, verify that the recovery phrase was entered correctly, character by character, and try again. A single letter error in a 24-word phrase will produce completely different addresses and access the wrong funds.
Setting up security after import
Guarda Wallet’s non-custodial architecture stores the decrypted private key material only in memory when the application is active and only after authentication succeeds. At rest, the keys are encrypted with a user-chosen password. On mobile devices, biometric authentication (fingerprint or face recognition) can be enabled as a convenience layer, though the underlying encryption key is still derived from the password. Device-level encryption on iOS and Android provides an additional barrier: the encrypted wallet file itself is protected by the device’s hardware security module or secure enclave.
After importing a recovery phrase, the user should immediately set or confirm the password used to encrypt the wallet. This password should be strong—at least 12 characters, using uppercase, lowercase, numbers, and symbols—and should be different from any password used elsewhere. The wallet will never transmit this password to Guarda’s servers or any third party; it is used only locally to encrypt the key material on the device. Losing the password does not mean losing access to the funds, because the recovery phrase can be used to re-import into Guarda Wallet or any other compatible wallet application. However, losing both the password and the recovery phrase means permanent loss of access.
For users storing significant amounts, a written copy of the recovery phrase in a secure location is important not as a replacement for the password, but as a recovery mechanism if the device is lost, stolen, or damaged. Some users maintain an additional paper copy in a second physical location, such as a safe deposit box or with a trusted attorney. The recovery phrase should be written in the same order as displayed, with each word verified as it is written, and stored in a way that is neither accessible to casual observers nor vulnerable to a single point of physical compromise.
Handling address sweeping and multi-asset consolidation
A user importing multiple wallets or consolidating assets from several addresses faces a choice: import each recovery phrase separately into Guarda Wallet, or export addresses from the imported wallet and sweep them into a single consolidated address. Sweeping means withdrawing all funds from an address and sending them to a new address under the same wallet’s control. For multi-asset wallets that support many blockchains, consolidation within Guarda Wallet is usually simpler than maintaining separate wallet applications for each asset type.
Guarda Wallet’s support for hundreds of cryptocurrencies and thousands of tokens across Bitcoin, Ethereum, Binance Coin, Litecoin, Polygon, Avalanche, and other major blockchains makes such consolidation practical. Once a user has imported a recovery phrase and verified that all assets are accessible, the migration is largely complete. However, if the original wallet contained multiple addresses that are not automatically generated by Guarda Wallet’s derivation path—for example, custom addresses created with non-standard tools—those addresses will not be automatically visible in Guarda Wallet’s interface.
In such cases, the solution is to send the funds from those addresses to a Guarda Wallet address belonging to the same imported wallet. This is a regular transaction that incurs a network fee, but it ensures that all funds end up in a single wallet that the user controls and can back up with a single recovery phrase. After the transaction confirms, the user should verify the new balance in Guarda Wallet and retain the original wallet until they are certain the transfer succeeded. Double-checking the receiving address before confirming a send operation is essential; typos or clipboard manipulation can result in funds sent to an unrelated address.
Verifying balances and testing transactions before moving large amounts
After importing a recovery phrase into Guarda Wallet, the wallet should immediately show the same balance as the original wallet for each asset. If the balance is different, something went wrong during import. The most common cause is entering the recovery phrase incorrectly. Before investigating further, delete the imported wallet from Guarda Wallet without removing the recovery phrase from storage, and attempt the import again, word by word, verifying against the original source document. If the balance is still incorrect, the original recovery phrase may have been transcribed or stored incorrectly.
Once the balance matches, a good practice is to test with a small transaction before moving larger amounts. Send a small amount of the most liquid asset—typically Bitcoin, Ethereum, or a stablecoin—from Guarda Wallet to an external address, such as a paper wallet backup or a second wallet controlled by the same user. Verify that the transaction confirms on the blockchain and that the receiving address shows the correct amount. This test accomplishes several goals: it confirms that Guarda Wallet can successfully create and broadcast transactions on that blockchain, it verifies the user’s ability to copy addresses without typos, and it reduces the risk of discovering a critical problem only after a large amount has been moved.
Network fees vary significantly based on blockchain congestion, transaction size, and the user’s fee preference. Guarda Wallet typically displays an estimated fee before the user confirms a send operation, with options to select slower confirmation for lower fees or faster confirmation for higher fees. For a test transaction, choosing a moderate fee is reasonable. For larger migrations, the user might accept slower confirmation if the difference in fees is substantial. The key point is to review the fee, the destination address, and the amount one final time before clicking the send button.
Managing NFT imports and Web3 dApp access
Users migrating to Guarda Wallet may also hold non-fungible tokens (NFTs) in an external wallet, particularly on Ethereum or other EVM-compatible networks. The recovery phrase that controls the fungible token holdings on those networks typically also controls the NFTs, because both are managed by the same private keys. Importing the recovery phrase into Guarda Wallet will therefore give access to any NFTs associated with those addresses.
Guarda Wallet includes built-in NFT storage and management, allowing users to view their collections directly in the wallet interface. However, the display of NFT metadata—images, titles, descriptions—depends on blockchain indexing services and NFT databases. If an NFT does not display immediately after import, it may simply be a caching or indexing delay. Refreshing the wallet or waiting a few minutes often resolves this. If an NFT belongs to a newer or less common contract, it may not display at all in Guarda Wallet’s interface, even though the wallet controls the underlying asset.
For users who interact with DeFi platforms, decentralized exchanges, or other Web3 applications, Guarda Wallet’s browser extension provides connectivity to those services. The extension can sign transactions submitted by dApps, allowing the user to approve swaps, provide liquidity, or stake assets without exposing the recovery phrase to the application. This is the same permission model used by MetaMask and other Web3 wallets: the application requests a signature, the wallet displays what is being signed, and the user approves or rejects it. After import, the extension will control the same addresses as the imported recovery phrase, so any approvals granted to dApps using the old wallet should be reviewed in the new wallet to understand what permissions are already in place.
Long-term management after import: backups, device security, and ongoing access
Once import is complete and verified, the user’s ongoing security depends on maintaining the password, protecting the device, and keeping the recovery phrase backed up safely. Guarda Wallet’s encrypted local key storage means that even if a device is stolen, the attacker cannot easily extract the private keys without the password. However, device-level encryption assumes that the device itself is protected against physical tampering or boot-level attacks. For ordinary users in ordinary threat environments, standard device security practices—a strong device PIN or password, automatic screen lock, and timely software updates—are sufficient.
The recovery phrase should be treated as equivalent to the master key to the account. If someone obtains the recovery phrase, they can import it into any wallet application and withdraw all funds, regardless of the password or device security. This means the recovery phrase should not be stored digitally unless encrypted with a key that the user controls independently. Cloud storage, email, and note-taking applications are not appropriate locations for an unencrypted recovery phrase. A paper copy in a physical vault, a certified safe deposit box, or a split recovery phrase distributed across multiple secure locations are more appropriate for high-value holdings.
Users should also test the recovery process before urgently needing it. This means writing down the recovery phrase as instructed, storing it, and then on a separate occasion—days or weeks later—creating a new Guarda Wallet on a different device and importing that phrase to verify that it works and produces the same addresses and balances. This test should be done proactively, not when the original device has been lost and funds urgently need to be accessed. The recovery phrase is only valuable if the user is certain it is correct and that they know how to use it.
For users holding assets across multiple blockchains, Guarda Wallet’s multi-asset design simplifies ongoing management by centralizing address monitoring, transaction history, and balance reporting. Rather than logging into separate exchange accounts or managing multiple wallet applications, a single Guarda Wallet can display holdings across Bitcoin, Ethereum, Binance Coin, Litecoin, Polygon, Avalanche, and hundreds of other assets. This convenience should not be confused with security, however. The safety of the holdings depends on the security of the device, the password, and the recovery phrase, not on the number of asset types the wallet can display.
Frequently asked questions
Can I import the same recovery phrase into Guarda Wallet on multiple devices?
Yes. Importing the same recovery phrase on multiple devices produces the same private keys and addresses on each device, making the funds accessible from all of them. This is useful for maintaining backups or accessing funds from different devices. However, it means that the security of the funds is only as strong as the least-secure device where the wallet is installed. If one device is compromised, the attacker can potentially access and withdraw all funds.
What should I do if the balance shown in Guarda Wallet doesn’t match the original wallet after import?
The most common cause is an error in entering the recovery phrase. Delete the imported wallet from Guarda Wallet without deleting the original recovery phrase, then import again, verifying each word carefully against the source document. If the balance still doesn’t match after a second careful import attempt, verify that the original recovery phrase was written correctly by accessing it again in the source wallet application.
How do I move funds from an exchange account into Guarda Wallet?
Exchange accounts do not provide a recovery phrase because the exchange controls the keys. Instead, create a receiving address in Guarda Wallet for each asset you want to withdraw, then use the exchange’s withdrawal form to send the funds to those addresses. The funds will then be under your control through the Guarda Wallet recovery phrase. Always test with a small amount first to confirm the destination address is correct.
