Move from Raivo OTP to 2FAS Auth
2FAS Auth has an importer made just for Raivo OTP, so it understands what Raivo OTP hands over.
- Carries over 4
- Secret keys
- Issuers and account names
- Digits, period and algorithm
- Counter-based (HOTP) codes
- Lost 3
- App settings
- Icons
- Favourites
How to move from Raivo OTP to 2FAS Auth
Export from Raivo OTP
Export to a ZIP archive- Open Settings and, under Data, tap Export OTPs to ZIP archive.
- Tap Export, then save or share raivo-otp-export.zip.
- Unzip it with your Raivo master password. Apps that import Raivo want the raivo-otp-export.json inside.
Import into 2FAS Auth
Import another app's export file- On Android, open Settings, thenImport Tokens. On iOS, it's Settings, thenTransfer tokens.
- Pick the app you're leaving, or General OTPAuth file for a list of otpauth links.
- Tap Choose JSON file (or text or CSV, depending on the app) and pick the export.
What to watch out for
Exporting from Raivo OTP
The zip is locked with your master password, but nothing inside it is. It also holds a web page with every secret and a QR code for each, so delete both files once you're done.
- Raivo warns that unzip tools without AES support, or a password with special characters, can trip it up. The Files app on the phone can open it.
Importing into 2FAS Auth
Password-protected exports don't work, so export without a password first.
- 2FAS only takes 10, 30, 60 or 90-second periods and 5 to 8 digits, and skips anything else.
- Raivo's JSON has to come out of its zip first.
Where this comes from
Exporting from Raivo OTP
- Official docs raivo-otp.com/faq
- Evidence github.com/raivo-otp/ios-application/blob/build-1108/Raivo/Features/DataExportFeature.swift
- Evidence github.com/raivo-otp/ios-application/blob/build-1108/Raivo/Models/Password.swift
- Evidence github.com/raivo-otp/ios-application/blob/build-1108/Raivo/Forms/MiscellaneousForm.swift
- Evidence github.com/raivo-otp/ios-application/blob/build-1108/Raivo/Views/SwiftUI/MainDataExportView.swift
Importing into 2FAS Auth
- Official docs 2fas.com/support/2fas-auth-mobile-app/which-imports-are-supported-in-the-2fas-app
- Evidence github.com/twofas/2fas-android/blob/6.1.0/feature/externalimport/src/main/java/com/twofasapp/feature/externalimport/domain/ImportType.kt
- Evidence github.com/twofas/2fas-android/blob/6.1.0/feature/externalimport/src/main/java/com/twofasapp/feature/externalimport/domain/AegisImporter.kt
- Evidence github.com/twofas/2fas-android/blob/6.1.0/feature/externalimport/src/main/java/com/twofasapp/feature/externalimport/domain/BitwardenImporter.kt
- Evidence github.com/twofas/2fas-android/blob/6.1.0/data/services/src/main/java/com/twofasapp/data/services/ServicesRepositoryImpl.kt
- Evidence github.com/twofas/2fas-ios/blob/vv6.0.3/TwoFAS/Data/Interactors/ImportFromFileInteractor.swift
Checked against the official docs on .
We work this route out from the Raivo OTP and 2FAS Auth entries, so if something's wrong, the fix goes in one of those.
Move from 2FAS Auth back to Raivo OTP
There's no way back from 2FAS Auth to Raivo OTP that we know of, so hang on to your Raivo OTP data until you're happy with the move.
Other places Raivo OTP can go
- Move from Raivo OTP to Bitwarden Authenticator Built-in importer 4 carry over 3 lost 0 not sure
- Move from Raivo OTP to Ente Auth Built-in importer 4 carry over 3 lost 0 not sure
- Built-in importer
- Same file format
- Convert it first
- Carries over
- Lost
- Not sure
Other ways into 2FAS Auth
- Move from Aegis Authenticator to 2FAS Auth Built-in importer 5 carry over 7 lost 0 not sure
- Move from Proton Authenticator to 2FAS Auth Built-in importer 4 carry over 2 lost 1 not sure
- Move from Google Authenticator to 2FAS Auth Built-in importer 3 carry over 1 lost 2 not sure