So I’m trying to transfer my codes from Google Authenticator to BitWarden’s, but it seems the generated QR code URI is incompatible with BitWarden? Nothing happens when I scan, and when I parsed the actual URI i the QR code and asked an AI, it says that it’s not compatible with BitWarden. According to the AI, Google output “otpauth-migration://” while BitWarden accepts “otpauth://totp/…”
I read another thread that apparently it’a known issue and requested.
Having said that, how do I proceed from here? Is there a way to transfer the codes at all?
And if it’s the integrated authenticator, then going via the authenticator app and it’s sync function with the BW password manager / vault might be a workaround. (–> when the sync is established, its possible to transfer codes from the authenticator app into your BW vault – and since the authenticator app can “import” codes from Google authenticator…)
I was referring to the standalone BitWarden authenticator app.
I did find an annoying workaround. I took the export QR code from Google and decoded it. Then I used a tool here https://github.com/dim13/otpauth that converts this migration string into each respective TOTP code with QR and manual import codes. So I went and imported them one by one with the BitWarden app. Took some time but it worked out in the end.
That’s outdated, as Google Authenticator (QR) is not an option in the Import menu. I don’t know when it disappeared, but it’s not there in the Android app.
@ChaosHm, interesting. I can reproduce that (authenticator app 2026.4.0). – As it’s still there in the Help Sites, I guess that should be reported on GitHub (if only to get some clarity about if it’s an intentional change or a regression/bug).
Forget that… it is still there… it’s just that the instruction is a bit confusing… the important part is what innocently is just called a “Tip”… as if it was optional/additional in that case :
: