Move from Microsoft Authenticator to Aegis Authenticator

Aegis Authenticator has an importer made just for Microsoft Authenticator, so it understands what Microsoft Authenticator hands over.

Carries over 2
Secret keys
Issuers and account names
Lost 1
App settings
Not sure 1
Digits, period and algorithm

How to move from Microsoft Authenticator to Aegis Authenticator

Export from Microsoft Authenticator

Read the app's data with root
How
File
Needs
  • Root access
  • Android only
  1. Before rooting, open Settings in Authenticator, switch on Cloud Backup and pick a personal Microsoft account to keep it in.
  2. Root the phone and reinstall Authenticator. Select Restore from backup before signing in to anything, with that same account.
  3. Leave Authenticator installed, so the app you're moving to can read its data off the phone.

Import into Aegis Authenticator

Import from another app with root
How
File
Needs
  • Root access
  • The other app installed on the same phone
  1. Open Settings, thenImport & Export, thenImport from app.
  2. Pick the app and let Aegis have root access when it asks.
  3. Pick the entries to bring in and confirm.

What to watch out for

Exporting from Microsoft Authenticator

Unlocking the bootloader to root a phone wipes it, which is why Cloud Backup has to be on first.

  • Only codes that change every 30 seconds come back from the backup. Passwordless sign-in and work or school accounts have to be set up again.
  • Microsoft's sign-in approvals aren't one-time codes, so they don't come across either.
  • From January 2027, Android backups go through Google One instead of a Microsoft account.
  • Without root, the only way out is setting 2FA up again at every site with your new app.

Importing into Aegis Authenticator

Google Authenticator only works up to version 5.10, and Steam only before version 3.0.

  • If your Authy tokens are encrypted, Aegis asks for your Authy backup password.
  • FreeOTP+, Stratum and TOTP Authenticator can be read this way too, though they have normal exports.

Where this comes from

Checked against the official docs on .

We work this route out from the Microsoft Authenticator and Aegis Authenticator entries, so if something's wrong, the fix goes in one of those.

Edit the Microsoft Authenticator entry Edit the Aegis Authenticator entry

Move from Aegis Authenticator back to Microsoft Authenticator

There's no way back from Aegis Authenticator to Microsoft Authenticator that we know of, so hang on to your Microsoft Authenticator data until you're happy with the move.

Other places Microsoft Authenticator can go

Nothing else we list can take Microsoft Authenticator's exports yet.

Other ways into Aegis Authenticator

  • Built-in importer
  • Same file format
  • Convert it first
  • Carries over
  • Lost
  • Not sure