How to move Google Authenticator codes to another app
Moving passwords to a new password manager is usually straightforward. Moving the verification codes you keep in Google Authenticator can be a little less obvious.
Google Authenticator does have an export option, but the QR codes it produces use a format designed for transferring accounts between copies of Google Authenticator. An app expecting the usual two-factor authentication setup QR code may not recognise them.
That's why we built the Google Authenticator QR converter. It turns those exports into individual setup QR codes you can scan with Secrets or another compatible authenticator.
Your OTP secrets stay on your device. The tool runs entirely in your browser: it reads the export and generates the new QR codes locally, without uploading them to us or any other server. We never receive your authenticator secrets.
Here's how to use it, including how to check that everything arrived safely.
What are you actually moving?
The changing number you type when signing in is generated from a longer-lived secret stored in your authenticator. For the usual time-based codes, the app combines that secret with the current time to calculate the next code.
When you move an account, you're copying that underlying secret and its settings. You aren't copying today's six-digit number and hoping it will keep working tomorrow 😉.
There are two QR formats involved:
- A Google Authenticator export QR code can contain several accounts in Google's
otpauth-migration://format. - A regular setup QR code contains one account in the
otpauth://format used by many authenticator apps and password managers.
The converter translates between those formats. It doesn't change the account's secret or reset two-factor authentication on the website.
If your destination app already supports Google's export format directly, you can use its own import flow. The steps below use the converter to produce regular setup QR codes for Secrets.
Before you start
For this walkthrough, you'll need your iPhone with Google Authenticator, Secrets installed on that iPhone, and a Mac with a working camera. Another trusted computer with a camera can also run the converter.
The Mac scans the export displayed on your iPhone. Then Secrets on your iPhone scans the converted codes displayed on the Mac. So you can use the same phone for both apps; you don't need a second phone.
Make sure you can still sign in to the accounts you're moving, and locate their recovery codes or another recovery method before making changes. Keep those recovery options somewhere you can access if you're ever locked out of your password manager.
Keep both the export and the converted QR codes private. They contain the secrets needed to generate future verification codes. Treat them like passwords, and avoid saving screenshots to a shared or cloud-synced photo library.
1. Export the accounts from Google Authenticator
On your iPhone:
- Open Google Authenticator.
- Open its menu and choose Transfer accounts, then Export accounts.
- Authenticate when asked.
- Select the accounts you want to move and tap Next.
These are the steps in Google's transfer instructions for iPhone and iPad. If you select several accounts, Authenticator may display more than one export QR code. You'll need to process each one.
Leave the first QR code visible on your iPhone. Keep the original accounts in Google Authenticator while you complete the transfer.
2. Convert the export on your Mac
Open the QR converter on your Mac, then:
- Click Scan QR Code and allow the browser to use the camera.
- Hold your iPhone's export QR code in front of the Mac's camera.
- Once it's recognised, the page displays an individual setup QR code, along with its Issuer and Account.
The issuer identifies the service, while the account helps you distinguish between logins for that service. For example, two entries might belong to the same email provider but use different email addresses.
If the export contains multiple accounts, use the numbered buttons beneath the result to view each one. Import all the accounts in this result before clicking Scan another QR Code, which replaces the displayed results with the next export.
The camera permission lets the page read the QR code on your phone. The camera images and decoded OTP secrets are processed locally in your browser, and the converter doesn't send them to a server.
3. Add each account to Secrets
Now switch from Google Authenticator to Secrets on your iPhone:
- Unlock Secrets and open the Login matching the Issuer and Account shown on your Mac. Create a Login if you don't have one yet.
- Edit the Login, tap + Add, and choose One-Time Password.
- Tap the QR code button beside the new field. Allow camera access if asked, then scan the converted QR code on your Mac's screen.
- Save the Login.
Secrets can now generate that account's verification codes. Repeat these steps for each converted QR code, taking care to match it to the right Login.
If Google Authenticator produced another export QR code, switch back to it on your iPhone, choose Scan another QR Code on the Mac, and repeat the conversion and import steps.
Our Importing from Google Authenticator support article also explains the conversion approach.
4. Check the codes before removing anything
For each time-based account, compare the code in Secrets with the one in Google Authenticator during the same time interval. They should match. If one is about to expire, wait for the next code before comparing.
Then test an actual sign-in using the code from Secrets. Keep your existing signed-in session open and use a separate browser or private window for the test, so you still have access if something needs correcting.
If a code fails, check the account you selected, whether the code expired, and that your devices' date and time are set correctly. Leave the original entry in place while you investigate.
Once you've checked every account and confirmed your recovery options, you can remove the original entries if you want to. Be aware that deleting a synced entry in Google Authenticator also deletes it from the other devices syncing that entry.
Removing an entry from an authenticator is separate from disabling two-factor authentication on the website. You don't need to disable that protection to complete this transfer.
What if you no longer have the original codes?
The converter needs an export from Google Authenticator. It can't reconstruct an account's secret from a single six-digit code.
If you can't access the original entries, use the service's recovery codes, another sign-in method, or its account recovery process. Once you've recovered access, follow that service's instructions to set up an authenticator again.
Moving apps shouldn't mean starting over with every account. If you're ready to keep verification codes alongside your logins, download Secrets, open the converter on your Mac, and start with one account. Check that it works, then work through the rest.
