Header Banner
Gadget Hacks Logo
Gadget Hacks
Android
gadgethacks.mark.png
Gadget Hacks Shop Apple Guides Android Guides iPhone Guides Mac Guides Pixel Guides Samsung Guides Tweaks & Hacks Privacy & Security Productivity Hacks Movies & TV Smartphone Gaming Music & Audio Travel Tips Videography Tips Chat Apps
Home
Android

How to Transfer Passwords and Passkeys Between Password Managers on Android

How to Transfer Passwords and Passkeys Between Password Managers on Android

Two months ago, Google announced a new way to transfer passwords and passkeys between password managers on Android, removing the file-export step that used to make switching apps a hassle. According to Google's announcement, the new system currently works across four named password managers: Google Password Manager, 1Password, Bitwarden Password Manager, and Dashlane. It requires Android 8 or newer, per Google, though the announcement doesn't say whether every app pairing handles the same data types or review controls, so treat your own setup as something to confirm rather than assume.

Passwords getting an easier migration path is useful by itself. But Google says passkeys previously had no transfer mechanism at all, meaning anyone switching password managers had to manually recreate every passkey, site by site and app by app. The new flow is built to remove that barrier.

Why the old method was worse than it sounds

Before this tool existed, moving saved logins meant exporting them into a CSV file, which Google describes as an unencrypted text file that sat exposed on the device until it was imported somewhere else, according to the company's post. An unencrypted export like that could expose the credentials to anyone who accessed the file. Google itself documented this exact export-and-import process in a 2023 Chrome blog post, describing how users could export passwords as a .csv file and import them directly into Chrome, roughly three years ago.

That workflow wasn't foolproof, either. One user reported in a Google Chrome Community thread from about four years ago that a CSV import failed because the file was missing the header row for URL, username, and password that Chrome expected.

Which apps support this Android password manager transfer right now

Four apps currently participate in the new system, according to Google: Google Password Manager, 1Password, Bitwarden Password Manager, and Dashlane. The company says more partners are coming, without naming any or giving a timeline, per Google's blog.

Android 8 is the stated floor for device compatibility, but that's a minimum, not a guarantee. If the import option doesn't show up in a given app, the app may simply not yet expose the transfer flow on that device.

Google's announcement confirms that these four apps work with the system. It doesn't say whether every source-and-destination combination behaves identically or moves the same categories of data, and Google does not say whether the review controls vary by app. Treat any specific pairing as something to verify yourself, not something to assume works the same way everywhere.

A few practical questions also go unanswered in Google's post: how the rollout is staggered by region, whether a Google Account is required to start a transfer, and whether the flow behaves the same on managed or work-profile devices. None of that is confirmed either way, so check your own apps' update notes before planning a switch on a work device.

How the transfer actually works

The process runs in three steps, according to Google.

First, open the new password manager, the one being switched to, and choose the option to import or copy credentials from another provider. That hands the job to Android instead of generating a file to manage.

Second, Android automatically detects which installed password managers are eligible sources and shows them as options, per Google's description of the flow. There's no need to already know which apps are compatible going in.

Third, tapping "Continue" opens the existing password manager, where the actual review happens: selecting what moves, reviewing it, and authorizing the transfer, which Google says completes within a few seconds.

What's confirmed is that some form of review and authorization happens before anything moves. What Google doesn't say is whether that review screen allows picking individual credentials, choosing by category, or only approving the entire vault as one block. That's worth checking directly in whatever app is being used, since the announcement doesn't specify it.

What moves, and what Google hasn't confirmed

Google explicitly names two data types in its announcement: passwords and passkeys. The post doesn't mention notes, payment cards, saved addresses, or other vault items many password managers store alongside logins. Don't assume full vault parity between apps just because passwords and passkeys transfer cleanly; the announcement simply doesn't address whether anything else comes along with them.

On security, Google says the system is designed to give users complete control over their data and the freedom to switch providers whenever they want, per the company's post. That's Google's own characterization of the feature, not an independent audit. The announcement doesn't detail the underlying data path, whether the transfer happens strictly device-to-device or passes through a server layer at some point, so "secure" here is a company claim to note, not a spec to verify.

The shift away from CSV exports applies specifically to transfers between these four apps on Android 8 and newer. The announcement doesn't say CSV import and export has disappeared elsewhere; unsupported app pairs, other platforms, and future partners not yet added could still depend on it.

Check these items before deleting the old manager

The following is editorial advice, not confirmed product behavior from Google, but it's worth doing given how much the announcement leaves unanswered.

Keep the old password manager installed and signed in until the new one is confirmed working. Don't uninstall anything the moment a "transfer complete" message appears on screen.

If the destination app's review screen allows picking a subset of entries, start with a small batch rather than the entire vault, especially the first time trying a specific app pairing.

After the transfer, manually test a few entries. Confirm a password actually autofills on its real site, and confirm a passkey successfully completes authentication rather than simply showing up in a list of saved credentials. A passkey appearing in the interface is worth double-checking before trusting it.

Only after transferred passwords and passkeys are verified working is it worth removing or disabling the source app.

What to do now

Android now supports direct password and passkey transfers between Google Password Manager, 1Password, Bitwarden Password Manager, and Dashlane on Android 8 and newer, according to Google's announcement, cutting reliance on unencrypted CSV exports for that specific migration path. What the company hasn't confirmed is the exact selection granularity during review, whether non-password vault data like notes or payment cards moves along with credentials, how the rollout paces by region, or how the feature behaves on managed devices. Anyone with a supported app pairing can try the transfer now, but it's worth running a small batch first and verifying that passwords and passkeys actually work on real sites before retiring the old password manager for good.

Apple's iOS 26 and iPadOS 26 updates are packed with new features, and you can try them before almost everyone else. First, check our list of supported iPhone and iPad models, then follow our step-by-step guide to install the iOS/iPadOS 26 beta — no paid developer account required.

Sponsored

Related Articles

Comments

No Comments Exist

Be the first, drop a comment!