2FA Setup

How to Migrate Binance 2FA When Changing Phones? Steps to Avoid Losing Your Seed

The seed migration process for Google Authenticator / Authy when switching to a new iPhone or Android device, preventing 2FA loss that could lock your account.

When getting a new phone, you cannot just uninstall your Authenticator—you will lose your seeds. This article provides the migration process. Download entry: Binance Website, mobile Binance Official App. If you haven't installed the iOS app, see the iOS install guide.

I. Core Migration Principle

Confirm the new device works before uninstalling from the old device.

If you directly uninstall the Authenticator from your old phone without a backup:

  • All your Binance 2FA codes become invalid
  • Once your backup codes run out, your account will be locked
  • In the worst case, you will have to go through support for a 24-72 hour reset

II. Google Authenticator Migration

Method A: Enable Google Account Sync (Most Reliable)

  1. Old device: Google Authenticator → Settings → Sign in to Google account → Enable cloud sync
  2. Wait a few minutes for the sync to complete
  3. New device: Install Google Authenticator → Sign in with the same Google account → All seeds automatically restore
  4. Generate a Binance verification code on the new device and test it

Method B: Transfer via QR Code (Manual)

  1. Old device: Authenticator → Menu → "Transfer accounts" → Select the accounts to transfer (Select all) → Display QR code
  2. New device: Authenticator → "Scan a QR code" → Point it at the old device's screen
  3. Automatic import

Method C: Rebind with Backup Seed (Most Reliable)

If you previously saved the original seed:

  1. Install Authenticator on the new device
  2. Re-enable 2FA in your Binance account
  3. Bind it using the original seed or a newly generated QR code

III. Authy Migration

Authy features cloud synchronization. The process is:

  1. Install Authy on the new device
  2. Log in using your original phone number
  3. SMS verification (if multi-device is enabled)
  4. Enter your Backup Password (the one you previously set)
  5. All seeds automatically restore

If you forget your Backup Password, there is no way to restore it—so make sure you memorize it during initial setup.

IV. Aegis Migration (Android)

Aegis is strictly local. Migration process:

  1. Old device: Aegis → Settings → Import/Export → Encrypted Export → Save the file to a cloud drive / email / USB
  2. New device: Install Aegis → Import the encrypted file → Enter the password
  3. Verify the codes

V. What to Do at the Binance Account Level

After migrating your Authenticator, you do not need to rebind it on Binance. Binance recognizes the seed, so the codes generated by the new device will perfectly match the old one.

However, it is recommended to perform a "new device login" test:

  • Log in and immediately check your login history
  • Confirm the device list
  • If you want extra peace of mind, choose "Revoke other device sessions"

VI. Prerequisites Before Migrating

1. The Old Device Must Turn On

The old device must be involved in the migration process. If it is broken, you can only use a "backup seed" or request a support reset.

2. Have Backup Codes on Hand

In case the migration fails, backup codes allow you to log in.

3. Network Connection

All synchronization requires an internet connection.

4. Sufficient Time

Set aside 30 minutes. Rushed migrations often lead to overlooked accounts.

VII. Emergency Process If You Lose Your Phone

If the old device is already lost:

You Have the Backup Seed

Install Authenticator on the new device and enter the seed (type it manually or scan the QR code from your backup paper).

No Backup Seed But Have Backup Codes

Log into Binance using a backup code → Reset 2FA → Bind on the new device.

Have Neither

Submit a request for customer support to reset your 2FA.

VIII. Long-Term Recommendations

1. Enable Cloud Sync

Cloud synchronization for Google Authenticator / Authy is the key to recovery.

2. Back Up the Seed

Even with cloud sync enabled, manually write down the seed on paper. It's the ultimate fallback.

3. Group Multiple Accounts

Create groups for accounts within your Authenticator (e.g., "Binance", "Email", "GitHub") to make migration easier.

4. Regular Drills

Every six months, use your backup seed to restore onto an empty spare device to verify that your backup is still valid.

FAQ

Q1: Can I use Binance normally during the migration? Yes. Your Binance account itself does not change, only the Authenticator device changes.

Q2: Can I continue using the old device? Yes. Both devices share the same seed and will generate the exact same verification codes. It is recommended to uninstall Authenticator from the old device so no one else can use it if they find it.

Q3: Can backup codes from the old device still be used after migration? Yes. Backup codes are tied to the Binance account level, not the specific device.

Q4: Do I need to rebind my YubiKey when changing phones? No. YubiKey is a physical device and operates independently of your phone.

Further Reading

Keep going

After this article, head back to the topic index and pick up the next piece in the same category.

Topics

Related security guides

2FA: Google Authenticator, SMS, or Hardware Key? 2026-04-21 How to Bind Google Authenticator for Binance 2FA? Where to Back Up the Setup Key 2026-04-18 What to do if you can't receive Binance SMS verification codes? Carrier blocking and roaming 2026-01-31 What to Do When Binance 2FA Codes Are Always Wrong? Time Sync is the Culprit 2026-01-28