Switching Phones? How to Transfer Your Google Authenticator

The Most Easily Forgotten Step When Getting a New Phone

Many people excitedly unbox their new phone, rush to install apps and log into accounts, and forget one critical thing -- how to transfer the verification codes from Google Authenticator.

By the time the new phone is set up and they try to log into Binance, they discover they need a Google Authenticator code, and then remember the authenticator is still on the old phone. If the old phone is still around, it's manageable. But if the old phone has been reset, sold, or broken, things get much more complicated.

So before switching phones, always prepare for the authenticator migration in advance.

Method 1: Use Google Authenticator's Built-in Transfer Feature

Prerequisites

Both old and new phones are available, and the old phone is still functional.

Steps

Step one: Open Google Authenticator on the old phone, tap the menu icon (three dots) in the upper right corner, and select "Transfer accounts."

Step two: Choose "Export accounts." The system may ask you to verify with your phone's unlock password or fingerprint.

Step three: Select the account entries you want to transfer (check the Binance-related ones). The system will generate a QR code.

Step four: Install Google Authenticator on the new phone. Open it and select "Transfer accounts" then "Import accounts," then scan the QR code displayed on the old phone.

Step five: After scanning, the new phone will generate the same verification codes as the old phone.

Important Notes

After the transfer, use a code generated on the new phone to log into Binance and confirm it works properly. Once verified, you can delete the corresponding entry from the old phone.

Method 2: Restore Using Your Backup Key

Prerequisites

You saved the text key (also called Setup Key or Secret Key) when you first bound the authenticator.

Steps

Step one: Install Google Authenticator on the new phone.

Step two: Tap add account and select "Enter a setup key."

Step three: For the account name, enter something recognizable (any label you'll recognize), and in the key field, enter the backup key you saved.

Step four: After confirming, the authenticator will begin generating codes identical to those on the old phone.

The advantage of this method is that you don't need the old phone at all -- as long as you have the key, you can restore anytime. This is exactly why previous articles repeatedly stressed the importance of backing up your key.

Method 3: Unbind and Rebind Through Binance

When This Applies

The old phone is gone and you have no backup key. In this case, the unbinding process is your only option.

If You Can Still Log Into Binance

Some operations can be verified via email or SMS codes instead of Google Authenticator. Log into Binance, go to security settings, find the "Google Authenticator" option, and attempt to unbind. The system may require alternative verification methods (email plus SMS) to confirm your identity.

After successfully unbinding, go through the binding process again using the new phone's authenticator to scan the code.

If You Can't Log In

This is the most troublesome scenario. You'll need to contact Binance customer support and submit an unbinding request. Typically, you'll need to provide:

• Your registered email or phone number
• Photos of both sides of your ID document
• A selfie holding your ID
• Screenshots of deposit or withdrawal records (proving account ownership)
• Device information used during registration

After customer support approves the request, they'll unbind the authenticator for you. The entire process may take one to seven business days. During this time, you won't be able to perform any operations requiring Google verification, including withdrawals.

Using Authy as an Alternative

If you switch phones frequently, consider using Authy instead of Google Authenticator. Authy supports cloud backup and multi-device sync, meaning you can log into your Authy account on a new phone and automatically recover all verification codes without manual transfer.

However, cloud backup also means there's theoretically an additional attack vector. If you choose Authy, be sure to set a very strong password for the Authy account itself.

Prevention Checklist

To avoid future headaches when switching phones, take these precautions now:

Back Up Your Key

If you can still log into Binance and your old phone is available, unbind Google Authenticator first, then rebind it. During the rebinding process, the key will be displayed again -- this time, save it properly.

Set Up on Multiple Devices

When binding the authenticator, in addition to your primary phone, scan the code with a backup phone or tablet simultaneously. If your primary phone has issues, you'll still have working verification codes on the backup device.

Regular Checkups

Periodically confirm that your backup key is still accessible and your backup device is functioning. Don't wait until you need them to discover the backup is lost.

Verify Everything Works on the New Phone

After completing the transfer, download and install the Binance App on your new phone via Binance official, then try the following to confirm the authenticator is working:

• Log into Binance (requires Google Authenticator code)
• Check Google Authenticator status in security settings
• Visit the withdrawal page to confirm the verification code works

Accounts registered through Binance official have full security features. After every device change, a complete security check is recommended to ensure all verification methods are working properly.

Transferring the authenticator may seem like a small matter, but mishandling it could lock you out of your own account, watching helplessly as your assets sit inaccessible. Take a few minutes to handle the transfer properly and save yourself countless headaches down the road.

One final piece of advice for all readers: regardless of whether you're planning to switch phones, check right now whether you've backed up your authenticator key. If not, go to Binance, unbind and rebind immediately, and save the key during the rebinding process. This takes only five minutes but could save you enormous trouble at some critical moment in the future.