Keplr Wallet Import: Migrating From MetaMask, Trust Wallet, and Other Crypto Wallets

A user holding assets across multiple wallets—perhaps Bitcoin in MetaMask, Ethereum tokens in Trust Wallet, and Cosmos assets scattered across different applications—faces a practical friction point. Each wallet requires its own security practice, recovery phrase, and separate management interface. Consolidating to a single non-custodial wallet that handles both established and emerging blockchains can reduce complexity while maintaining full control over private keys. For users exploring or already committed to the Cosmos ecosystem, Keplr offers that consolidation across IBC-enabled chains in a single application.

The migration process itself, however, is not a simple import button. Moving from MetaMask, Trust Wallet, Coinbase Wallet, or similar applications to Keplr requires understanding the difference between private key formats, verifying that assets will appear correctly on their target networks, and ensuring that no funds are lost or misdirected during the transition. The right approach depends on whether you are moving a single recovery phrase, importing specific private keys, or reconstructing a portfolio across multiple networks. Each method has different verification steps and different risks of operator error.

Understanding wallet recovery phrases and private key formats

Most modern non-custodial wallets, including MetaMask, Trust Wallet, and Keplr, are built on the BIP-39 standard for generating recovery phrases. A BIP-39 recovery phrase is a 12 or 24-word mnemonic that can reproduce the same set of private keys across compatible wallets. This theoretical interoperability carries an important caveat: while the underlying cryptographic material is the same, different wallets may derive different addresses from the same seed depending on their key derivation path.

MetaMask and Trust Wallet typically use the Ethereum standard derivation path, which generates Ethereum-compatible addresses. Keplr uses the Cosmos standard, which generates addresses valid on Cosmos chains like Cosmos Hub, Osmosis, and others. If you import a MetaMask recovery phrase directly into Keplr, you will not see the Ethereum addresses and balances you expect. Instead, Keplr will derive Cosmos-format addresses from the same seed, which are different destinations entirely. This is not a bug; it is how key derivation works. Your Ethereum assets remain on their original addresses and accessible only through wallets that use the Ethereum derivation path.

The practical implication is straightforward: do not expect a single recovery phrase to move all your assets automatically between wallet applications. Instead, treat migration as a two-phase process. First, set up Keplr with either a new recovery phrase or an existing one intended for Cosmos use. Second, transfer assets from your old wallets to your new Keplr addresses on each relevant network. Test with a small amount first, verify the destination address, and only then move larger balances.

For users evaluating whether Keplr is the right choice for their needs, the Keplr wallet documentation and setup guide provides detailed instructions for each platform and network. Understanding these technical boundaries before starting the migration will prevent the frustration of discovering that your recovery phrase did not automatically bring your balances along.

Creating a new recovery phrase in Keplr

The simplest migration path for users without existing Cosmos assets is to start fresh with Keplr. Download the application from the official source—Chrome extension for desktop, iOS App Store for iPhone, or Google Play for Android—and select the option to create a new wallet rather than import an existing one. Keplr will generate a fresh 24-word recovery phrase in your language of choice.

During creation, Keplr will prompt you to write down all 24 words in order and to confirm them by selecting random words from the list. This is not a formality. The recovery phrase is the master key to all your accounts across all supported networks. If it is lost, stolen, or accidentally exposed, an attacker can drain every address derived from that seed. Store the phrase offline—on paper in a secure location, in a hardware wallet’s companion app, or in a certified steel backup device. Do not store it in cloud notes, email, screenshots, or any system connected to the internet.

After confirming the recovery phrase, Keplr will guide you through setting a password for the application itself. This password encrypts the wallet locally on your device and protects access with biometric authentication if enabled. The password is not used to recover the wallet if you lose access; only the recovery phrase can do that. If you forget the password, you can reset the wallet and re-import the same recovery phrase to regain access.

Once your new Keplr wallet is created, it will display addresses for Cosmos Hub, Osmosis, Juno, and several other networks by default. Other networks can be activated within the application. Each address is unique to that network, and all are derived from your single recovery phrase. You now have a blank non-custodial wallet ready to receive assets.

Transferring assets from MetaMask and Ethereum-based wallets

If you hold Ethereum, ERC-20 tokens, or assets on other Ethereum-compatible chains through MetaMask, you cannot access them through the same recovery phrase in Keplr. Instead, you must transfer them to an Ethereum-compatible address in Keplr, or to a wallet that continues to use your MetaMask seed with the Ethereum derivation path.

Keplr supports Evmos, which is an Ethereum-compatible blockchain within the Cosmos ecosystem. If your goal is to consolidate onto a single Keplr interface while keeping some Ethereum assets accessible, you can send ERC-20 tokens from MetaMask to a wrapped or bridged version on Evmos. This requires a bridge service and introduces an additional execution risk—the bridge must work correctly, and you must verify the destination contract address. Verify the correct bridge before sending any substantial amount.

Alternatively, if your primary goal is to manage Cosmos assets and you want to keep Ethereum assets separate, leave them in MetaMask and use Keplr exclusively for Cosmos chains. This separation is not a drawback; it is a reasonable security practice. A single recovery phrase controlling assets across incompatible ecosystems means that compromise of that phrase affects everything at once. Splitting keys between applications can reduce the impact of a single failure.

To transfer assets out of MetaMask, open the application, select the relevant account and network, click “Send,” paste your new Keplr address (copied from the Evmos or appropriate network tab in Keplr), verify the address matches what you expect, set a gas fee, and confirm. Wait for the transaction to settle—block time varies by network—before assuming the transfer succeeded. Once funds arrive in your Keplr address, they are controlled by your Keplr recovery phrase, not MetaMask’s.

Importing an existing recovery phrase from another wallet

If you already have a recovery phrase created by another wallet and you want to use it in Keplr—perhaps because you created it in a Cosmos-compatible wallet previously—Keplr can import that phrase. Open the wallet application, select “Import existing wallet,” enter your 12 or 24-word recovery phrase in the correct order, and set a password. Keplr will derive addresses from that phrase using the Cosmos key derivation standard.

A critical warning applies here: importing a phrase from a wallet that is still in use is risky. If the original wallet and Keplr are both generating addresses from the same recovery phrase, and both are actively sending transactions, they may not stay synchronized. One application might not immediately see transactions created by the other. More importantly, if your phrase has been exposed in any way—written down in a public location, seen by someone, or accessed by malware—importing it into a new device does not change that exposure. A compromised seed remains compromised on every device it is imported to.

The safer pattern is to use recovery phrase import only for recovery after a device loss or as part of a deliberate migration away from the original wallet. Set up Keplr with the import, verify that your expected addresses appear and display the balances you expect, and then retire the original wallet application. Do not run both simultaneously for extended periods.

To verify that the import worked correctly, open the Accounts tab in Keplr and check each network. Your addresses should match the addresses you see in the original wallet for the same derivation standard. If you are importing from a Cosmos-compatible wallet, the addresses should be identical. If you are importing from a non-Cosmos wallet, the addresses will be different, and you should treat the import as a dry run unless you specifically understand the implications.

Verifying assets and networks after import

After transferring assets or importing a recovery phrase, the next critical step is verification. Open Keplr and examine each network where you expect to have a balance. Check the native token first—Cosmos Hub shows ATOM, Osmosis shows OSMO, and so on. Then verify any secondary tokens you have. The wallet should display the current balance and recent transactions.

A common point of confusion arises with token symbols. A token called “ATOM” on Ethereum is not the same as ATOM on Cosmos Hub. ERC-20 ATOM is a wrapped representation issued on Ethereum; native ATOM is the actual token on Cosmos Hub. If you have wrapped tokens, they will not appear as balances in Keplr unless they are on a network Keplr supports. Knowing which version you hold matters for deciding where to move them.

Cross-chain bridges and IBC transfers can complicate this picture. Cosmos assets can move between different Cosmos chains using the Inter-Blockchain Communication protocol. Keplr is designed specifically to handle IBC transfers—you can send ATOM from Cosmos Hub to Osmosis through Keplr’s built-in routing. However, if you have bridged assets from non-Cosmos chains, the token may appear on Cosmos with a different name or require special handling. Check the transaction history or the token’s documentation to confirm its origin.

If assets are missing after import, do not panic immediately. Check whether the correct network is selected in Keplr. The default view may not show all networks. You can add additional networks by scrolling to the bottom of the chain list and selecting “Add More Chains.” If a network was active in your old wallet but is not in Keplr, you may need to enable it manually or transfer assets to a supported network.

Staking and DeFi integration after migration

Once your assets are in Keplr and verified, the wallet offers direct access to staking, liquidity pools, and other DeFi interactions. Unlike some wallets that require external platforms or separate applications, Keplr integrates with these services within its own interface. You can stake ATOM directly from the Cosmos Hub tab, participate in Osmosis liquidity pools, or use Juno’s smart contracts without leaving the wallet.

Before engaging in any staking or liquidity provision, understand the risks specific to each action. Staking locks your assets for an unbonding period, typically 21 days on Cosmos Hub, during which they cannot be moved or sold. Liquidity pools expose you to impermanent loss if the relative price of two assets diverges. These are not wallet-level risks; they are protocol-level risks that apply regardless of which wallet you use to interact with them.

The non-custodial design of Keplr means that you maintain control over your funds throughout these interactions. When you approve a transaction to stake or provide liquidity, Keplr shows you the details, you sign with your recovery phrase or hardware wallet, and the transaction is broadcast to the network. The platform hosting the smart contract or validator cannot prevent the transaction or seize your assets. It can only honor valid transactions correctly.

Verify reward addresses and validator selections carefully before confirming. If you delegate ATOM to a validator with a history of downtime or poor performance, you will receive fewer rewards or experience slashing. Small mistakes here can be recovered by re-delegating; large ones can reduce your balance. Read validator descriptions, check their historical performance, and start with delegation to well-known operators if you are new to staking.

Hardware wallet integration for added security

For balances that justify additional security measures, Keplr supports integration with Ledger hardware wallets. A Ledger device stores your recovery phrase in isolation from the internet and requires physical confirmation to authorize transactions. Even if your computer or phone is compromised, an attacker cannot sign transactions without access to the Ledger device itself.

Setting up Ledger integration involves installing the official Cosmos app on your Ledger device, connecting the device to your computer or phone, and selecting “Connect Ledger Wallet” during Keplr setup. The process differs slightly between platforms. On desktop, you typically need to connect via USB and approve the connection. On mobile, you use Bluetooth after pairing the Ledger device with your phone.

A Ledger device generates its own recovery phrase, separate from any other wallet you may have. Do not import an existing Keplr recovery phrase into a Ledger; instead, use the Ledger to create a new seed and manage it independently. This separation means that if your Ledger is lost, you have a recovery phrase written down elsewhere, and vice versa. Organize your recovery phrases carefully and store them in different physical locations when possible.

Transaction confirmation on a Ledger device is slower than confirmation within Keplr on a phone or computer. Every transaction requires navigating the Ledger’s small screen and manually confirming each action. For frequent or small transactions, this can become tedious. For large holdings or high-value operations, the extra friction is a feature, not a drawback; it forces intentionality and prevents impulse actions.

Common mistakes and how to avoid them

One recurring error is sending assets to the wrong address on the wrong network. If you copy an Ethereum address and paste it into Keplr’s Cosmos Hub field, the transaction will likely fail or the funds will be directed to an uncontrolled destination. Always verify the network explicitly before sending. Read the destination address character by character if moving a large amount. Use QR codes when available to reduce manual copy-paste errors.

Another mistake is assuming that a balance visible in an old wallet has automatically moved to Keplr after import. It has not. Importing a recovery phrase creates addresses in Keplr that can receive funds, but it does not automatically transfer existing balances. You must explicitly send assets from the old wallet to the new Keplr address on each network. This is by design—no wallet should ever move your funds without explicit action.

Users sometimes forget their password and panic, believing their assets are lost. The password protects local access to the wallet application but is separate from recovery. If you forget the password, you can uninstall and reinstall Keplr, then re-import your recovery phrase to regain full access. This is true whether you created a new wallet in Keplr or imported an existing phrase. Keep your recovery phrase secure and backed up offline, and the password is merely a convenience layer.

Finally, avoid enabling unknown networks or approving unusual transactions. Keplr allows users to add custom blockchain networks, but an attacker could direct you to add a malicious network or trick you into approving a token transfer that drains your account. Stick to official networks and verify transaction details carefully before signing. If something feels wrong, it probably is.

Testing the migration with small amounts first

Before moving significant balances, perform a small test transfer on each network. Send $10 to $50 of a token from your old wallet to the corresponding Keplr address, then verify that it appears in Keplr within the expected timeframe. Examine the transaction confirmation, check gas fees, and ensure the destination address is correct. Only after this successful test should you move larger amounts.

This testing phase is not paranoid; it is professional practice. A small test costs a modest fee and reveals configuration errors, network issues, or misunderstandings about which token or version you actually hold. If the test fails, you learn the problem at minimal cost. If it succeeds, you have demonstrated that the address, network, and pathway all work as expected before committing larger funds.

For staking and other advanced features, run the same test cycle. Stake a small amount with a validator you are researching, observe the rewards accrual, and verify the unbonding process if you later decide to unstake. Understanding the mechanics at a small scale before scaling up prevents expensive surprises.

Document each step: the old wallet address, the new Keplr address, the network, the transaction ID, the timestamp, and the amount. If something goes wrong, this record helps you trace what occurred and recover the funds if possible. It also serves as a record for tax purposes, since most jurisdictions treat token transfers as taxable events even if you are the sender and receiver.