Why Passkey Portability on Android Matters
Passkeys promise a passwordless future, but they’ve come with a hidden catch: portability. On Android, Google Password Manager has been great at syncing passkeys across devices in the same ecosystem, yet it has effectively locked those credentials inside Google’s own system. That’s been a major friction point for anyone who wants to switch to another password manager or simply test alternatives without losing access to their accounts. Unlike traditional passwords, which can be exported as text or CSV files, Android passkeys haven’t had a straightforward way to move between apps. This lack of passkey portability on Android has discouraged password manager switching and created a sense of vendor lock‑in. With Google now testing a way to move passkeys between apps, that barrier is finally starting to come down, promising more user control and flexibility.
How Google’s New Passkey Transfer Feature Works
AndroidAuthority’s teardown reveals that Google has quietly enabled a new interface in Google Password Manager labeled “Import passwords & passkeys” and “Export passwords & passkeys.” While these options aren’t live for everyone yet, they already function in testing. Instead of a simple export file, Google uses an in‑app flow powered by the Credential Exchange Protocol (CXP). When you tap to import, Android prompts you to choose the password manager that currently stores your passkeys. A list of supported apps—such as Bitwarden in their tests—appears, and once selected, control passes to that app to transfer passwords, passkeys, and other stored items into Google Password Manager. The reverse direction is more dynamic: when you open another password manager, Android can prompt you to pull passkeys out of Google’s vault. This design keeps the process secure while making Android passkeys more portable between apps.
What This Means for Password Manager Switching
For years, moving from one password manager to another on Android has been simple for passwords but difficult for passkeys. The new passkey portability Android feature changes that equation. By supporting transfers both into and out of Google Password Manager, Android lowers the risk of getting locked into a single provider. Users can now consider third‑party tools based on features, design, or pricing, without worrying that passkeys will be stranded. The reliance on the Credential Exchange Protocol means only participating apps will support this, but the list already includes major players like Google, Apple, and Samsung. That should cover a large portion of mainstream users. While the feature is still hidden and may evolve before public release, it signals a clear move toward easier password manager switching and a healthier, more competitive ecosystem for passkey‑based security on Android.
Vendor Lock‑In, User Control, and the Future of Passkeys
Passkeys were supposed to fix passwords, but proprietary implementations risked replacing password fatigue with ecosystem lock‑in. Google’s move toward passkey portability directly tackles that problem on Android. Once widely deployed, users will be able to treat passkeys more like traditional credentials—assets they own and can move—rather than tokens bound to a single platform. This aligns with broader efforts by Google and Apple to make switching platforms less painful, including wireless transfers of apps, files, and home screen layouts. Although it’s still unclear if passkeys will be included in those cross‑platform migration tools, the underlying Credential Exchange Protocol shows that the industry recognizes portability as essential. For Android users, the emerging ability to move passkeys between Google Password Manager and other apps is a key step toward genuine user control, reduced vendor lock‑in, and a more open passwordless future.
