Move from Raivo OTP to Bitwarden Authenticator
Bitwarden Authenticator 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
- Favourites
- Lost 3
- App settings
- Counter-based (HOTP) codes
- Icons
How to move from Raivo OTP to Bitwarden Authenticator
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 Bitwarden Authenticator
Import from a file- Open Settings and tap Import.
- Pick where the file came from under File format.
- Tap Import (Import items on iOS) and choose the file.
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 Bitwarden Authenticator
Aegis files only work on Android, and Raivo files only on iOS.
- Encrypted or password-protected files don't work, so export without a password first.
- On Android, a single HOTP code in a 2FAS or Aegis file stops the whole import.
- It can't read Bitwarden CSV files, even though it writes them - use JSON.
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 Bitwarden Authenticator
- Official docs bitwarden.com/help/authenticator-import-export
- Evidence github.com/bitwarden/android/blob/v2026.11.0-bwa/authenticator/src/main/kotlin/com/bitwarden/authenticator/data/platform/manager/imports/model/ImportFileFormat.kt
- Evidence github.com/bitwarden/android/blob/v2026.11.0-bwa/authenticator/src/main/kotlin/com/bitwarden/authenticator/data/platform/manager/imports/parsers/TwoFasExportParser.kt
- Evidence github.com/bitwarden/android/blob/v2026.11.0-bwa/authenticator/src/main/kotlin/com/bitwarden/authenticator/data/platform/manager/imports/parsers/AegisExportParser.kt
- Evidence github.com/bitwarden/ios/blob/v2026.11.0-bwa/AuthenticatorShared/Core/Vault/Models/Enum/ImportFormatType.swift
- Evidence github.com/bitwarden/ios/blob/v2026.11.0-bwa/AuthenticatorShared/Core/Vault/Services/Importers/TwoFasImporter.swift
Checked against the official docs on .
We work this route out from the Raivo OTP and Bitwarden Authenticator entries, so if something's wrong, the fix goes in one of those.
Edit the Raivo OTP entry Edit the Bitwarden Authenticator entry
Move from Bitwarden Authenticator back to Raivo OTP
There's no way back from Bitwarden Authenticator 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 2FAS Auth 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 Bitwarden Authenticator
- Move from Aegis Authenticator to Bitwarden Authenticator Built-in importer 5 carry over 7 lost 0 not sure
- Move from 2FAS Auth to Bitwarden Authenticator Built-in importer 4 carry over 5 lost 0 not sure
- Move from Google Authenticator to Bitwarden Authenticator Built-in importer 2 carry over 3 lost 1 not sure