Google Password Manager conflicting logins explained
Android can now move saved passwords and passkeys directly between password manager apps in a few taps, with no exported file involved. Google announced the feature two months ago, and the company says the experience already works across Google Password Manager, 1Password, Bitwarden Password Manager, and Dashlane on Android 8 and later.
That's the confirmed part. Google's announcement doesn't address the Google Password Manager conflicting logins scenario: what happens when a saved login already exists in the destination app, or when passwords and passkeys for the same site sit in both managers at once. Anyone planning a switch should know that gap exists before assuming the tool handles it automatically.
What actually changed: direct transfer replaces the old export file
Google says that, historically, moving passwords meant downloading them into an unencrypted text file that sat exposed on the device. Passkeys couldn't transfer at all, so switching meant recreating them one site at a time, according to Google's announcement.
The new process starts inside the app someone is switching to. Tapping an option to import or copy credentials from another provider hands the task off to Android, per Google.
Android then detects which compatible managers are already installed and lists them as import sources. Tapping continue brings the user into the old manager to select, review, and authorize the transfer, Google says.
An authorized transfer completes in a few seconds, Google says, and the experience already covers the four named providers, with more partners expected to join later. The feature requires Android 8 or newer.
What Google Password Manager's transfer tool doesn't explain about duplicate logins
Google's announcement walks through selecting, reviewing, and authorizing a transfer, but it never addresses what happens when a password or passkey for a given site already exists in the destination manager, based on Google's description of the feature. It doesn't say whether the tool flags a duplicate, overwrites an older entry, keeps both copies, or just leaves the cleanup to whoever is switching.
That gap covers more than one kind of conflict. At least three distinct cases are possible, and nothing in Google's announcement says whether the tool treats them differently:
- Two entries for the same site with an identical username and password, like duplicate records for one shopping account.
- Two different logins for the same site, such as separate personal and work accounts on one banking app, each with its own password.
- A saved password and a saved passkey for the same site, where one manager holds one credential type and the destination holds the other.
None of those scenarios get settled in the announcement, and there's no mention of what happens to the source entry in the old manager once a transfer finishes.
Google has solved an adjacent problem before, just not this one. Chrome's password manager has automatically grouped multiple saved logins for the same site since 2022, and added a notes field for people managing several logins on one website in 2023, according to Google's earlier announcement and feature update. Those tools organize credentials a person already saved inside one account. They don't describe what happens to a credential arriving from an outside app during a cross-provider transfer, and nothing in the September announcement says that grouping logic carries over.
What's confirmed and what's still unknown
Confirmed, based on Google's announcement:
- A transfer starts inside the destination app, not the old one.
- Android automatically detects compatible managers already installed on the device.
- The old manager shows a screen to select, review, and authorize before anything moves.
- The feature works on Google Password Manager, 1Password, Bitwarden Password Manager, and Dashlane, and requires Android 8 or later.
Still unaddressed:
- How existing or duplicate logins in the destination app get handled, whether merged, overwritten, duplicated, or flagged.
- Whether the original password or passkey stays in the source manager after a transfer or gets removed.
- Whether certain passkey types are excluded or treated differently during the move.
What to check before trusting the switch
None of this means the feature is broken. It means Google's published steps stop short of describing conflict handling, so a few precautions are worth taking rather than assuming the rest resolves itself.
- Confirm the device runs Android 8 or later, and check that both the old and new password manager show up as compatible options before starting a transfer.
- Start the process from the new app. Google's documented flow begins in the destination manager, which then hands off to the existing app for the review-and-authorize step; nothing past that point is spelled out.
- Read the authorization screen instead of tapping through it. Google names this as the review step, but doesn't say how a duplicate would even appear there, if at all.
- Spot-check a few important logins and passkeys in the new manager once the transfer finishes, and test an actual sign-in wherever the service allows it.
- Keep the old manager installed until those checks are done. Nothing in Google's announcement guarantees the original credential survives the move, so there's no confirmed fallback if something needs rechecking later.
What to do now
Hold off on deleting anything from the old password manager until a transfer has been spot-checked. Start the move from the new app, read the authorization screen line by line instead of approving on autopilot, and test sign-ins on a handful of accounts that actually matter before clearing out the source manager.
Watch each provider's own support documentation rather than Google's announcement for the duplicate-handling answer, since that's the level of detail Google hasn't published. If 1Password, Bitwarden, or Dashlane release guidance on how their side of the transfer treats existing or conflicting entries, that's the point to trust the process fully. Until then, treat the switch as safe to try, not safe to walk away from unattended.
Comments
Be the first, drop a comment!