How to Transfer Authy to a New Phone
If you use Authy for two-factor authentication, moving to a new device takes a little planning.
This guide explains how to transfer Authy to a new phone while keeping your accounts accessible and minimizing the risk of lockout.
Authy is different from many authenticator apps because it supports multi-device access and encrypted backups, but those features work only if your phone number, devices, and backup settings are handled correctly.
What Authy does during a phone transfer
Authy stores your 2FA tokens in encrypted form and can sync them across approved devices.
When you switch phones, the app on the new device must be approved before it can access your tokens.
The transfer process usually depends on three things:
- Whether you still have access to your old phone
- Whether you have the same phone number on the new device
- Whether Authy multi-device is enabled
If you understand these conditions first, the transfer is much easier and you are less likely to lose access to accounts protected by 2FA.
Before you start: prepare for the transfer
Preparation matters because losing access to your authenticator can also mean losing access to email, banking, cloud storage, and social accounts.
Before you change phones, make sure you can still approve login prompts for your most important services.
Check your recovery options
Review each important account and confirm whether it has backup codes, recovery email addresses, recovery phone numbers, or alternate sign-in methods.
Save backup codes in a secure place, such as a password manager or encrypted note.
Confirm your phone number
Authy account access is tied to your phone number.
If you are also changing carriers or numbers, expect the process to be more involved.
In many cases, keeping the same number simplifies how to transfer Authy to a new phone.
Keep the old phone available
If possible, do not wipe the old device until the new one is fully working.
Having both devices during the transition makes it easier to approve the new installation and verify tokens.
How to transfer Authy to a new phone with the same number
This is the most straightforward scenario.
If your new device uses the same phone number and you still have access to the old phone, the process is usually simple.
- Install Authy on the new phone from the App Store or Google Play.
- Enter the same phone number used on your current Authy account.
- Complete the verification step, which may involve SMS or a phone call.
- Approve the new device from your existing Authy installation if prompted.
- Wait for your tokens to sync to the new phone.
Once the new phone is approved, open each important account to confirm that the codes appear and the time-based one-time passwords work correctly.
How to transfer Authy if you still have the old phone
If the old phone is still functional, your transfer is easier and safer.
In many cases, you can use the old device as the approval method for the new one.
Follow these steps:
- Install Authy on the new device.
- Sign in with the same phone number.
- Respond to any approval request on the old phone.
- Enable access on the new device once approved.
- Test at least one or two high-priority accounts before retiring the old phone.
Keep both devices powered on until the process is complete.
If the old phone is lost, factory reset, or no longer able to receive approvals, your recovery path may depend on backup codes or account-specific support procedures.
How to transfer Authy without the old phone
Transferring Authy without the old phone is possible in some cases, but it can take more time.
If you still control the phone number, you may be able to verify the new phone through Authy’s recovery process.
If you no longer have the old device, check the following:
- Can you receive SMS or phone calls at the registered number?
- Do you have access to the email account connected to your services?
- Do the protected accounts offer backup codes or recovery options?
If you cannot verify the number or approve the device, you may need to contact each service’s support team individually.
Authy cannot restore access to every third-party account, because the 2FA codes protect accounts owned by separate providers such as Google, Microsoft, Dropbox, Coinbase, or GitHub.
What to do if your phone number changed
A new phone number adds an extra layer of complexity.
Since Authy relies on the registered number, a number change can trigger device verification issues.
If you are moving to a new number, update services before the switch whenever possible.
Best practice:
- Keep the old number active temporarily if your carrier allows it.
- Update your Authy account details if the app prompts you to do so.
- Re-approve the new phone after the number change.
- Review all critical accounts and update recovery details.
For high-value accounts, it is wise to keep backup codes stored offline before changing numbers or devices.
Authy multi-device settings and security considerations
Authy’s multi-device feature can make phone changes easier, but it also has security implications.
If multi-device is enabled, tokens may be accessible on more than one approved device.
That is convenient during a transfer, but you should disable extra devices you no longer use.
Security checklist after the transfer:
- Remove old devices you no longer trust
- Update the lock screen security on the new phone
- Use a strong device passcode or biometric authentication
- Enable encrypted device backups where appropriate
- Review accounts for unauthorized login attempts
This is especially important for financial services, cryptocurrency exchanges, enterprise apps, and developer tools, where 2FA compromise can have serious consequences.
Common problems when moving Authy to a new phone
Several issues can interrupt the process.
Most are easy to diagnose once you know what to look for.
Verification code not arriving?
Check whether the phone number is correct, whether the device has signal, and whether your carrier is blocking short codes.
Restarting the phone and retrying after a short delay can help.
Tokens not showing on the new phone?
Make sure the new device has been approved and that sync is complete.
Also confirm that you are signed into the correct Authy account using the same phone number.
Old phone still shows codes, but new phone does not?
This usually means the new device has not finished approval or synchronization.
Recheck Authy settings and any prompts on the old phone.
Account login fails even though Authy transferred?
Some services require you to re-enroll 2FA after a major device or number change.
If that happens, use backup codes or the service’s recovery flow to reconnect Authy.
Best practices to avoid losing 2FA access
Planning ahead is the easiest way to avoid problems when you transfer Authy to a new phone.
Treat your authenticator app like a critical part of your identity and access management strategy.
- Store backup codes securely before changing devices
- Keep one active recovery method for every important account
- Test 2FA access before wiping your old phone
- Use a password manager to document recovery settings
- Review Authy device approvals after every transfer
If you manage work accounts, coordinate with IT or security teams before switching phones.
Many organizations enforce stricter policies for authenticator changes, especially in Microsoft Entra ID, Google Workspace, Okta, and other identity platforms.
When to contact support
If the registered phone number is inaccessible, the old device is gone, and backup codes are missing, support may be your only path forward.
Start with the provider of the protected account, not just Authy, because each service controls its own sign-in recovery process.
Use support when:
- You cannot receive verification codes
- Your account is locked after a device change
- The service requires manual 2FA reset
- You suspect unauthorized access during the transfer
The safest approach is to plan the transfer before replacing your phone, verify each important account afterward, and keep recovery methods current so you are never locked out when you need access most.