Import from Aegis
In progress
Export from Aegis
Section titled “Export from Aegis”- In Aegis, open Settings → Import & Export → Export.
- Choose Aegis (.JSON).
- Leave Encrypt the vault on. This is recommended: the file stays encrypted until Octa Pass decrypts it on your device with your Aegis password.
- Save the file.
What’s kept
Section titled “What’s kept”| Aegis | Octa Pass |
|---|---|
| TOTP codes (SHA-1, SHA-256, SHA-512, 6 to 8 digits) | The one-time code of a login |
| Issuer and account name | Login title and username |
| Note | Login notes |
| Groups | Tags |
| Favorite | Favorite |
uuid |
Kept with the login, so importing the backup again updates it instead of adding a copy |
| HOTP codes | Counter-based codes, with their counter |
| Steam, mOTP and Yandex codes | A hidden field on the login, with the full setup. Octa Pass can’t show these codes yet. |
| Icons | Not imported |
Aegis exports have no dates. A code that is already in the vault (from an earlier import, or by another route with the same secret) isn’t added again; a matching login with a changed entry is updated and keeps what you added in Octa Pass since.
How codes are matched
Section titled “How codes are matched”Each code joins the login already in your vault whose name or website matches the code’s issuer, and whose username matches the account name when both have one. Codes without a match, or with more than one possible match, become new logins. A login that already has a code is never changed.
When a code joins an existing login, its note becomes a separate secure note, so nothing is lost. The code’s groups aren’t added to that login.
Import into Octa Pass
Section titled “Import into Octa Pass”Choose Import → Aegis, drop the file, enter the export password if it’s encrypted, then review and import. See the import overview.