Move from Aegis Authenticator to Proton Authenticator
Proton Authenticator has an importer made just for Aegis Authenticator, so it understands what Aegis Authenticator hands over.
- Carries over 5
- Secret keys
- Issuers and account names
- Digits, period and algorithm
- Steam Guard codes
- Notes
- Lost 6
- App settings
- Counter-based (HOTP) codes
- mOTP and Yandex codes
- Icons
- Groups
- Favourites
- Not sure 1
- Custom order
How to move from Aegis Authenticator to Proton Authenticator
Export from Aegis Authenticator
Export the vault- Open Settings, thenImport & Export, thenExport.
- Pick Aegis (.JSON) and leave Encrypt the vault ticked, unless the app you're moving to needs a plain file.
- Tap OK to save the file, or Share to send it somewhere.
Import into Proton Authenticator
Import a Proton Authenticator or Aegis file- Open Settings and pick Import.
- Pick Proton Authenticator or Aegis, then choose the .json file.
- Enter its password if it's protected.
What to watch out for
Exporting from Aegis Authenticator
An unencrypted export holds every secret in plain text, so delete it once you're done.
- 2FAS and Bitwarden Authenticator can only read an unencrypted one.
- Automatic backups (Settings, thenBackups) write the same file, but always encrypted.
Importing into Proton Authenticator
Aegis HOTP codes are skipped, and a single entry of a type it doesn't know, like mOTP or Yandex, stops the whole vault from importing.
Where this comes from
Exporting from Aegis Authenticator
- Official docs github.com/beemdevelopment/Aegis/blob/v3.4.3/FAQ.md
- Evidence github.com/beemdevelopment/Aegis/blob/v3.4.3/app/src/main/java/com/beemdevelopment/aegis/ui/fragments/preferences/ImportExportPreferencesFragment.java
- Evidence github.com/beemdevelopment/Aegis/blob/v3.4.3/app/src/main/java/com/beemdevelopment/aegis/vault/VaultEntry.java
- Evidence github.com/beemdevelopment/Aegis/blob/v3.4.3/app/src/main/res/values/strings.xml
Importing into Proton Authenticator
- Official docs proton.me/support/import-2fa-codes
- Evidence github.com/protonpass/proton-pass-common/blob/2.4.0/proton-authenticator/src/entry/exporter.rs
- Evidence github.com/protonpass/proton-pass-common/blob/2.4.0/proton-authenticator/src/parser/aegis/db.rs
- Evidence github.com/protonpass/proton-pass-common/blob/2.4.0/proton-authenticator/src/parser/aegis/json.rs
Checked against the official docs on .
We work this route out from the Aegis Authenticator and Proton Authenticator entries, so if something's wrong, the fix goes in one of those.
Edit the Aegis Authenticator entry Edit the Proton Authenticator entry
Other ways to move from Aegis Authenticator to Proton Authenticator
Export as plain text , then Import an Aegis or Ente Auth text file Built-in importer 4 carry over 6 lost 0 not sure
- Carries over 4
- Secret keys
- Issuers and account names
- Digits, period and algorithm
- Steam Guard codes
- Lost 6
- Icons
- Groups
- Notes
- Favourites
- Counter-based (HOTP) codes
- mOTP and Yandex codes
Export from Aegis Authenticator
Export as plain text- Open Settings, thenImport & Export, thenExport.
- Pick Text file (.TXT) and tick I understand the risk.
- Tap OK to save the file, or Share to send it somewhere.
Import into Proton Authenticator
Import an Aegis or Ente Auth text file- Export a plain text file from Aegis or Ente Auth.
- In Proton Authenticator, open Settings, thenImport, pick Aegis or Ente and choose the .txt file.
Exporting from Aegis Authenticator
There's no option to encrypt it, so every secret is in plain text.
Importing into Proton Authenticator
On Android the Aegis option only takes the vault's .json file, so use that instead.
- Lines it can't read, HOTP codes included, are skipped.
- Official docs proton.me/support/import-2fa-codes
- Evidence github.com/protonpass/proton-pass-common/blob/2.4.0/proton-authenticator/src/parser/ente/txt.rs
- Evidence github.com/protonpass/proton-pass-common/blob/2.4.0/proton-authenticator/src/parser/aegis/txt.rs
- Evidence github.com/protonpass/proton-pass-common/blob/2.4.0/proton-authenticator/src/entry/mod.rs
- Evidence github.com/protonpass/android-authenticator/blob/1.3.10/business/entries/src/main/kotlin/proton/android/authenticator/business/entries/domain/EntryImportType.kt
Export for Google Authenticator , then Scan Google Authenticator's export QR codes Same file format 2 carry over 8 lost 0 not sure
- Carries over 2
- Secret keys
- Issuers and account names
- Lost 8
- Digits, period and algorithm
- Steam Guard codes
- mOTP and Yandex codes
- Icons
- Groups
- Notes
- Favourites
- Counter-based (HOTP) codes
Export from Aegis Authenticator
Export for Google Authenticator- Open Settings, thenImport & Export, thenExport for Google Authenticator.
- Scan the QR code with the other app, then tap Next and repeat until you get to Done.
Import into Proton Authenticator
Scan Google Authenticator's export QR codes- In Google Authenticator, tap Menu, thenTransfer codes, thenExport codes on Android, or Menu, thenTransfer accounts, thenExport accounts on iOS.
- In Proton Authenticator, open Settings, thenImport and pick Google Authenticator.
- Scan each QR code, or pick screenshots of them (Choose one or more Photos on Android).
Exporting from Aegis Authenticator
Only TOTP and HOTP codes with 6 digits and SHA1 go in, and the rest are skipped.
- The QR codes can't hold a period, so any code that isn't on a 30-second timer comes out wrong.
Importing into Proton Authenticator
Every code gets a 30-second timer, since Google's QR codes don't carry one.
- Built-in importer
- Same file format
- Convert it first
- Carries over
- Lost
- Not sure
Move from Proton Authenticator back to Aegis Authenticator
- Move from Proton Authenticator to Aegis Authenticator Built-in importer 4 carry over 2 lost 1 not sure
Other places Aegis Authenticator can go
- Move from Aegis Authenticator to Ente Auth Built-in importer 8 carry over 4 lost 0 not sure
- Move from Aegis Authenticator to Stratum Built-in importer 7 carry over 5 lost 0 not sure
- Move from Aegis Authenticator to 2FAS Auth Built-in importer 5 carry over 7 lost 0 not sure
- Move from Aegis Authenticator to Bitwarden Authenticator Built-in importer 5 carry over 7 lost 0 not sure
Other ways into Proton Authenticator
- Move from 2FAS Auth to Proton Authenticator Built-in importer 4 carry over 4 lost 1 not sure
- Move from Ente Auth to Proton Authenticator Built-in importer 4 carry over 6 lost 1 not sure
- Move from Google Authenticator to Proton Authenticator Built-in importer 2 carry over 2 lost 2 not sure