GUIDE · MIGRATION · REKEY SAFETY

Importing old MyAlgo accounts to Pera or Defly

MyAlgo Wallet · 2026-04-29 · ~9 min read

This guide covers migrating accounts from the original MyAlgo Wallet (operated by Rand Labs, 2019-2024) to Pera Wallet or Defly. Two paths are documented: direct seed import (safe only if your seed was never hot-stored on the original web wallet) and rekey-then-import (the safer path for any potentially exposed seed). The current MyAlgo desktop wallet at myalgowallet.org is also a destination option — see /migrate-from-myalgo for that path.

Decision: direct import vs. rekey first

If your seed phrase was ever hot-stored on the original MyAlgo web wallet (i.e., you used the wallet at wallet.myalgo.com between 2019 and January 2024), the safe path is rekey first, then import. Direct seed import preserves the same key that may have been exposed.

If your seed phrase was generated outside MyAlgo and only entered into MyAlgo briefly for transaction signing, direct import is reasonable.

If you can't remember whether your seed was hot-stored: assume it was, and rekey.

Path A: Direct seed import (cold seed only)

For seeds that were never hot-stored on the original web wallet:

Pera Wallet (mobile):

Install Pera from the App Store (iOS) or Google Play (Android) — verify the developer is "Pera Wallet" and not a lookalike.
Open Pera, choose "I already have an account" → "Recover with passphrase."
Enter your 25-word seed phrase in the order it was originally generated.
Set a password for the local Pera installation.
Your accounts and ASA opt-ins appear automatically — they're stored on-chain against your address.

Defly: Identical pattern — install, choose "Recover wallet," enter seed phrase, set password.

Both wallets follow the BIP39-compatible 25-word Algorand mnemonic standard, so the same seed produces the same address in either wallet.

Path B: Rekey first, then import (potentially exposed seed)

The rekey path keeps your public address but changes the signing key, so even if the original seed leaks, your funds remain controlled by the new key. After rekey, check the account's auth-addr field on a block explorer to confirm the new signer is in place before assuming the account is safe to operate.

Step-by-step

Decide between direct import and rekey-first

If your seed phrase was ever hot-stored on the original MyAlgo web wallet, the safe path is rekey first then import. If it was generated outside MyAlgo and only entered briefly for signing, direct import is reasonable. If unsure, assume hot-stored and rekey.

Direct import to Pera or Defly (cold seed only)

Install Pera from the App Store or Google Play (verify developer is 'Pera Wallet' and not a lookalike), or install Defly. Choose 'I already have an account' or 'Recover wallet'. Enter your 25-word seed phrase exactly in the original order. Set a local password. Algorand seeds are BIP39-compatible 25-word mnemonics; both Pera and Defly accept them natively.

For potentially exposed seeds: set up a fresh signing wallet

Generate a new seed in a fresh wallet that has never seen the old phrase: Ledger hardware wallet (most common rekey target), Pera or Defly mobile with a new seed, the current MyAlgo desktop with a new seed, or Lute browser extension with a new seed. Write the fresh seed on paper and store offline.

Construct and sign the rekey transaction

Open the old account using the potentially-exposed seed in any wallet that supports rekey transactions (current MyAlgo desktop, Pera, Defly all do). Move only the network fee (0.001 ALGO) into the old account if needed. Construct a rekey transaction designating the fresh wallet's address as the new signer. Sign and broadcast — this is the last operation the old key will perform.

Verify the new auth-addr and import

After confirmation, check the account on a block explorer (allo.info, Pera Explorer) and confirm the auth-addr field now shows the fresh wallet's address. Attempt a small test transaction signed by the new key before assuming control. Once verified, your account address is unchanged but only the fresh signing key controls it. ASA opt-ins, NFTs, and historical balance all remain on-chain against the same address — Pera or Defly will display them automatically.

After rekey: import to Pera or Defly

Once rekeyed, you can use any wallet that controls the new signing key. If your fresh wallet was Pera or Defly mobile, the account already shows up there. If your fresh wallet was a Ledger, connect that Ledger to Pera or Defly per their hardware-wallet flows. The migration is complete.

What about ASA opt-ins and NFTs?

Both are preserved. ASA opt-ins and NFTs are stored on-chain against your account address, not in any specific wallet. After import (or rekey), Pera and Defly will show all your previously-opted-in assets and NFTs.

For the broader wallet landscape including hardware-wallet pairings, see the comparison page.

Frequently asked questions

Will my staking participation transfer?

If you were participating in the previous Algorand governance program, that program ended in Q1 2025. For the new staking model, participation is independent of any wallet — your stake is on-chain against your address, and any wallet with signing authority can manage it.

What if my old wallet had multiple accounts?

Each account is derived deterministically from the seed by index. Importing the seed into Pera or Defly should reveal all accounts. Note that some wallets show only the first account by default; you may need to manually reveal additional account indices.

Is there a deadline for migration?

No. Your funds are on-chain regardless. They'll remain accessible whenever you decide to import the seed (with rekey safety as appropriate).

Recovery FAQ

Prefer desktop? Try MyAlgo.

Native Algorand desktop wallet for users who want the same accounts on a non-browser, non-mobile signing surface.

Download MyAlgo