Google’s September 10, 2026 announcement describes a way to transfer passwords and passkeys between participating Android password managers without downloading an export yourself. It names Google Password Manager, 1Password, Bitwarden and Dashlane as available participants.
The useful change is a coordinated migration process. Compatibility still needs checking at the app level.
Start with the destination app
The destination password manager starts the import. Android presents available providers, then the existing manager lets the user review and authorize the transfer.
Google’s developer guidance describes transfers between providers on the same device using the FIDO Credential Exchange Format. An importer declares the credential types it accepts; an exporter registers what it can supply.
The implementation uses a Content URI backed by temporary cache files. Avoiding a manually downloaded export therefore does not mean the system never uses files internally.
Android 8 is the platform floor
The transfer API supports Android 8 and later. That does not establish the minimum for every participating app.
1Password’s import instructions require Android 14 or later for direct imports from compatible apps. Bitwarden’s July 23, 2026 update specifies Android 14 or later and Google Play Services 26.21 or later.
That earlier Bitwarden announcement also matters for the timeline: Android transfers were documented before Google’s September announcement.
Provider integration still matters
For developers building a credential provider, compatibility includes implementing the importer or exporter role and handling the supported data types. Google’s sample explicitly requires real caller-verification logic in production; its placeholder trust check is not sufficient.
For anyone planning a migration, check the source and destination apps’ current instructions before proceeding. The API’s Android minimum is only one part of that compatibility check.
