Search for help moving your Battle.net authenticator to a new phone and you'll find a decade of advice about serial numbers, restore codes, and a standalone authenticator app. Most of it no longer applies. Blizzard retired the separate Battle.net Authenticator app and folded its function into the main Battle.net mobile app, which changed what "moving your authenticator" actually means.
The good news: the current process is simpler than the old one. The bad news: if you follow outdated instructions, you'll go looking for screens and codes that no longer exist. Here's how it works now, in the right order, so a phone upgrade doesn't turn into a support ticket.
The authenticator lives in the Battle.net app now
The old standalone Battle.net Authenticator, both the physical keyfob and the dedicated mobile app, has been phased out. Today, authenticator functionality is built into the official Battle.net mobile app: the same app you might already use for news and account management also handles your login approvals and security codes.
That has one big implication for migration. You're not transferring authenticator data from one phone to another. You're installing the Battle.net app on the new phone, signing in to your account, and attaching the authenticator to that device. The account relationship is what matters, not the app's local data, so there's no backup file to carry over and no secret to re-scan.
It also means, as with Steam Guard, that Battle.net's authenticator is proprietary. You can't move it into Google Authenticator, our app, or any other standard TOTP app. It only lives in the Battle.net mobile app, by design.
Before you switch phones
Nearly every painful Battle.net migration story starts the same way: the old phone was wiped before the new one was verified. A few minutes of checking prevents all of it.
- Confirm your Battle.net email and password. Signing in on a new device is the core of this process, so make sure those credentials aren't trapped in a password manager that only exists on the old phone.
- Check the phone number on your account. Battle.net's SMS Protect feature uses your phone number as a recovery channel for exactly this situation: approving changes and restoring access when your authenticator device is unavailable. If you're changing numbers along with phones, update the number before you retire the old SIM. Keep in mind that phone-number recovery is convenient but not invulnerable; it's the channel SIM-swap attacks go after, so treat it as a fallback rather than your primary defense.
- Keep the old phone working until the end. An active authenticator on the old device can approve logins during the transition and saves you from every recovery flow.
If you want the general version of this checklist for all your accounts, our guide to avoiding account lockout covers the same principle: verify your recovery paths while everything still works, not after.
The move, step by step
The Battle.net app's exact screens change with updates, so treat this as the shape of the process and lean on Battle.net's official support pages for the current tap-by-tap version. They maintain those pages; screenshots in blog posts go stale.
- Install the Battle.net mobile app on the new phone from the App Store or Google Play. Make sure it's the official Blizzard app.
- Sign in with your Battle.net account. Expect a verification step. That might be an approval on your old phone, an SMS code, or email verification, depending on what your account has set up.
- Set up the authenticator on the new device. The app's security area walks you through attaching the authenticator to this phone. If an authenticator is still attached to the old device, the app guides you through moving it over.
- Test it. Log in to Battle.net on your desktop or in a browser and confirm the approval prompt or code now comes from the new phone. Don't skip this; it's the only real proof the migration worked.
- Retire the old phone. Once the new device is confirmed handling logins, sign out of the Battle.net app on the old phone and wipe it whenever you're ready.
If the old phone is already gone
Lost or wiped the old device before setting up the new one? You still have paths back in, roughly in this order of speed:
- SMS Protect. If your account has a current phone number attached, Battle.net can verify you by text and let you remove the old authenticator and attach a new one. This is the recovery path SMS Protect exists for, and it usually resolves things in minutes.
- Email verification. Depending on your account's setup, Battle.net may verify you through your registered email for some steps.
- Battle.net Support. If neither works, Blizzard's account recovery process can remove the authenticator after you prove ownership, potentially including government ID. It's reliable but slow compared to the options above.
Serial numbers and restore codes: the legacy era
If you've been a Blizzard player for a long time, you may have a serial number and restore code written down from the old standalone authenticator or physical keyfob. Those belonged to the retired system. They identified a specific authenticator device and let you re-attach it after a reinstall, and they don't map onto how the current in-app authenticator works.
If an old-style authenticator is still attached to your account, expect Battle.net to steer you toward the current in-app system when you next manage your security settings. Don't count on a years-old restore code as your safety net; your live recovery paths today are your phone number, your email, and Blizzard support. This is a good example of why recovery codes need occasional review: a code for a retired system is worse than no code, because it feels like protection and isn't.
The rest of your accounts move differently
Battle.net and Steam are the outliers. Most of your other two-factor accounts, email, banking, social, other game platforms, use standard TOTP, and those migrate through an entirely different process that you control. Our guide to moving your authenticator to a new phone covers that side.
For those standard accounts, this is where an authenticator built for migration earns its keep. Authenticator by Vidus6 syncs codes across devices with end-to-end encryption, and a new phone only gains access after an existing trusted device approves it, so the key material never leaves hardware you own. Battle.net's codes will always stay in Blizzard's app, but the rest of your vault can move in minutes instead of an evening of re-scanning QR codes.
Can I put my Battle.net authenticator in a regular 2FA app?
No. Battle.net's authenticator is proprietary and only functions inside the official Battle.net mobile app. Any tool claiming to export it into a standard TOTP app is unofficial and unsupported by Blizzard.
What happened to the old Battle.net Authenticator app?
Blizzard retired it. Its functionality now lives inside the main Battle.net mobile app, which handles login approvals and security codes alongside account management. If you still have the old app installed somewhere, it's not the current system.
Do I need SMS Protect if I have the authenticator?
It's worth keeping. SMS Protect is Battle.net's built-in recovery channel for exactly the moment your authenticator device is lost or wiped. Just keep the number current, and stay aware that SMS-based recovery is a weaker link than the authenticator itself.
The short version: forget the serial-number era. Install the Battle.net app on the new phone, sign in, attach the authenticator, and confirm a real login before wiping the old device. Keep your phone number current as the safety net, use Battle.net's official support pages for exact steps, and save the flexible migration tools for the accounts that actually support them.
