Move from Aegis Authenticator to Ente Auth
Ente Auth has an importer made just for Aegis Authenticator, so it understands what Aegis Authenticator hands over.
- Carries over 8
- Secret keys
- Issuers and account names
- Digits, period and algorithm
- Counter-based (HOTP) codes
- Steam Guard codes
- Groups
- Notes
- Favourites
- Lost 4
- App settings
- mOTP and Yandex codes
- Icons
- Custom order
How to move from Aegis Authenticator to Ente Auth
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 Ente Auth
Import an Aegis vault- Open Settings, thenData, thenImport codes and pick Aegis Authenticator.
- Tap Select JSON file, choose the vault and enter its password if it's encrypted.
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 Ente Auth
Groups come in as tags and favourites as pins.
- One entry it can't read, like an mOTP or Yandex code, stops the whole import.
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
Checked against the official docs on .
We work this route out from the Aegis Authenticator and Ente Auth entries, so if something's wrong, the fix goes in one of those.
Other ways to move from Aegis Authenticator to Ente Auth
Export as plain text , then Import a list of otpauth links Same file format 5 carry over 5 lost 0 not sure
- Carries over 5
- Secret keys
- Issuers and account names
- Digits, period and algorithm
- Counter-based (HOTP) codes
- Steam Guard codes
- Lost 5
- Icons
- Groups
- Notes
- Favourites
- 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 Ente Auth
Import a list of otpauth links- Open Settings, thenData, thenImport codes and pick Plain text.
- Tap Select file and choose a text file of otpauth:// links, one per line or split by commas.
Exporting from Aegis Authenticator
There's no option to encrypt it, so every secret is in plain text.
Importing into Ente Auth
Any link it can't read, like an mOTP or Yandex one, is skipped without a warning.
- Tags, notes, pins and icons only come back from Ente Auth's own plain text export.
Export for Google Authenticator , then Scan Google Authenticator's export QR codes Same file format 3 carry over 7 lost 0 not sure
- Carries over 3
- Secret keys
- Issuers and account names
- Counter-based (HOTP) codes
- Lost 7
- Digits, period and algorithm
- Steam Guard codes
- mOTP and Yandex codes
- Icons
- Groups
- Notes
- Favourites
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 Ente Auth
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 Ente Auth, open Settings, thenData, thenImport codes and pick Google Authenticator.
- Tap Scan a QR code, or Select file for a picture of it on a computer, and repeat for each QR code.
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 Ente Auth
Ente's help says some codes, Google Account ones especially, can fail to come across and need setting up again on the site.
- Built-in importer
- Same file format
- Convert it first
- Carries over
- Lost
- Not sure
Move from Ente Auth back to Aegis Authenticator
- Move from Ente Auth to Aegis Authenticator Built-in importer 5 carry over 6 lost 0 not sure
Other places Aegis Authenticator can go
- 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
- Move from Aegis Authenticator to Proton Authenticator Built-in importer 5 carry over 6 lost 1 not sure
Other ways into Ente Auth
- Move from 2FAS Auth to Ente Auth Built-in importer 6 carry over 3 lost 0 not sure
- Move from Proton Authenticator to Ente Auth Built-in importer 5 carry over 1 lost 1 not sure
- Move from Raivo OTP to Ente Auth Built-in importer 4 carry over 3 lost 0 not sure
- Move from Google Authenticator to Ente Auth Built-in importer 3 carry over 1 lost 2 not sure
- Move from Open Authenticator to Ente Auth Built-in importer 3 carry over 2 lost 0 not sure