Import from andOTP
In progress
andOTP is no longer developed, but its backups still import.
Export from andOTP
Section titled “Export from andOTP”- In andOTP, open Backups.
- Choose Backup (encrypted). This is recommended: the
.json.aesfile stays encrypted until Octa Pass decrypts it on your device with the backup password. Backup (plain) makes an unencrypted.jsonfile. - Save the file.
Backups made with OpenPGP (.json.gpg) can’t be imported. Make a password-encrypted or plain backup instead.
What’s kept
Section titled “What’s kept”| andOTP | Octa Pass |
|---|---|
| TOTP codes (SHA-1, SHA-256, SHA-512, 6 to 8 digits) | The one-time code of a login |
| Issuer and label | Login title and username |
| Tags | Tags |
last_used |
Last-used date |
| HOTP codes | Counter-based codes, with their counter |
| Steam and mOTP codes | A hidden field on the login, with the full setup. Octa Pass can’t show these codes yet. |
| Thumbnails and usage counts | Not imported |
andOTP entries have no id. Importing the same backup again recognises codes by their secret, so nothing is added twice.
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.
Import into Octa Pass
Section titled “Import into Octa Pass”Choose Import → andOTP, drop the file, enter the backup password if it’s encrypted, then review and import. See the import overview.