Migrate Off Google Password Manager to a Vault

Google Password Manager is convenient right up until it isn't. It lives inside Chrome, syncs quietly to your Google account, and autofills logins without asking for much. But that convenience comes with a hard ceiling: it is tied to one browser ecosystem, its sharing tools are clumsy, its organization options are thin, and if your Google account is ever compromised, your entire credential vault sits behind that single point of failure.

Here is a statistic that should make you pause. According to Google's own transparency data and multiple 2024 security surveys, the average person now juggles somewhere between 90 and 170 online accounts. If you have been letting Chrome remember passwords since 2015, there is a good chance you have several hundred credentials scattered across that vault, many of them weak, reused, or belonging to services you shut down years ago. Migrating gives you a rare chance to clean house.

This guide walks you through exactly how to migrate from Google Password Manager to a dedicated vault: how to export your data safely, what to look for in a replacement, how to import without creating duplicates or orphaned passkeys, and how to scrub Chrome so it stops offering to save passwords behind your back. By the end you will have a cleaner, more portable, and genuinely more secure setup.

Key Takeaways

Export your Google passwords as a CSV, but treat that file like radioactive waste: it is plain text and must be deleted after import.

Dedicated managers beat Google's built-in option on cross-browser support, secure sharing, breach monitoring, and passkey portability.

Passkeys do not export in the CSV. Plan a separate migration for them, one service at a time.

Audit as you migrate: expect to delete 20 to 40 percent of your entries as dead, duplicated, or reused.

Disable Chrome's built-in offer-to-save and autofill after migration, or you will keep two vaults in permanent disagreement.

Verify that your new vault's cloud backup is actually zero-knowledge encrypted before you trust it with everything.

Why Move Off Google Password Manager at All?

Google Password Manager is a solid default. It is free, it is built in, and for a casual user it is far better than reusing Summer2019! across forty sites. But once you take security seriously, its limits show up fast.

Browser lock-in. It works beautifully in Chrome and Android and awkwardly everywhere else. If you use Safari on a Mac and Firefox on a Linux box, you are fighting the tool constantly.
Weak sharing. There is no clean, audited way to share a Netflix login with your partner or a set of admin credentials with a coworker. You end up texting passwords, which is exactly what you were trying to avoid.
One account, one blast radius. Your passwords are protected by your Google account. If that account is phished or session-hijacked, an attacker can potentially reach everything.
Thin organization. No folders, no tags, no custom fields for recovery codes, software license keys, or Wi-Fi passwords.
Limited auditing. The Password Checkup is decent but shallow compared to dedicated tools that flag reused, old, and weak passwords in one dashboard.

If you manage sites or infrastructure, the stakes are higher. A leaked admin credential can undo months of hardening work, the same way an unaudited plugin can. If you run WordPress, pairing a real vault with something like eDarpan WordPress Protection or SiteGuard Pro closes two very different doors that attackers love to walk through.

Choosing a Dedicated Password Manager

Before you export anything, decide where it is going. Switching twice is miserable, so pick deliberately. The four criteria that matter most for people leaving Google are cross-platform support, sharing quality, passkey handling, and the encryption model.

The comparison that actually matters

Manager	Cross-browser	Secure sharing	Passkey support	Encryption model	Self-host option
Google Password Manager	Chrome/Android only	Poor	Yes (Google-bound)	Google-managed	No
Bitwarden	All major browsers	Good (Sends + orgs)	Yes	Zero-knowledge	Yes
1Password	All major browsers	Excellent	Yes	Zero-knowledge + Secret Key	No
KeePassXC	Via extensions	Manual (file-based)	Partial	Local encrypted file	Yes (fully local)
Proton Pass	All major browsers	Good	Yes	Zero-knowledge	No

My honest read after using several of these for years: Bitwarden is the best default for most people because it is open source, affordable, and zero-knowledge. 1Password is the most polished if you will pay for it and value the extra Secret Key layer. KeePassXC is unmatched if you want zero cloud dependency and full control of the vault file. Proton Pass is a strong pick if you already live in the Proton ecosystem.

Whatever you choose, verify its encryption claims rather than trusting the marketing. Our walkthrough on how to verify cloud backup encryption before you trust it applies directly here: a "secure" vault whose provider can read your data is not the upgrade you think it is.

How to Export Your Passwords From Google Password Manager

The export itself takes about two minutes. The care around it is what matters, because the file Google hands you is unencrypted plain text.

Open Chrome and go to chrome://password-manager/settings, or visit passwords.google.com and sign in.
Find the Export passwords option (under Settings in the Password Manager).
Click Export. Chrome will ask you to confirm with your device password or biometrics. This is the account holder verification, not encryption on the file.
Choose a save location. Google produces a file named something like Google Passwords.csv.
Open the file once, briefly, to confirm it contains columns like name, url, username, and password. Every value is in the clear.

Critical: save this CSV to a local folder, never to a shared cloud drive, a Downloads folder that syncs, or an email attachment. Once you have imported it into your new vault and verified the count, delete it and empty your trash. On Windows you can go further and securely wipe the free space; on macOS, a terminal rm plus emptying trash is the baseline.

What the export does not include

The CSV captures usernames and passwords. It does not capture your passkeys. Passkeys are cryptographic key pairs bound to your device and Google account, and they cannot be dumped into a spreadsheet. You will migrate those separately, which we cover below and in our dedicated guide on how to migrate passkeys between password managers safely.

A Worked Example: Migrating 214 Passwords Without a Mess

Let me use a real-shaped scenario. Say your Google export produces a CSV with 214 entries. That number feels alarming, but it is inflated. Here is what a typical cleanup looks like.

38 entries are duplicates. Chrome saved login.example.com and example.com as separate records for the same account.
29 entries point to services you no longer use: an old forum, a defunct streaming trial, a job portal from three roles ago.
17 entries have blank or throwaway passwords Chrome captured from single-use guest checkouts.
22 entries reuse the same password across sites, which the import will flag as weak.

After deleting the dead 84 entries and merging duplicates, you land at roughly 130 real, active accounts. Now the work is manageable. Here is the process I follow:

Import the full 214-entry CSV into the new manager so nothing is lost.
Run the built-in security report (Bitwarden calls it Reports, 1Password calls it Watchtower).
Delete the 29 dead-service entries first, since they are pure noise.
Merge the 38 duplicates, keeping the one with the most complete data.
Clear the 17 junk guest-checkout entries.
Tackle the 22 reused passwords by resetting them one site at a time, starting with email, banking, and anything holding payment methods.

Budget about 90 minutes for the initial import and triage, then 10 minutes a day for a week to finish the password resets. Doing it in one marathon session leads to mistakes. Spreading it out keeps you attentive to the high-value accounts.

How to Import Into Your New Vault

Every dedicated manager supports importing Google's CSV format directly. The steps below use Bitwarden as the example, but the flow is nearly identical for 1Password, Proton Pass, and KeePassXC.

Create your new account and choose a strong, memorable master password. This is the one password you must never forget and never reuse. A four or five word passphrase like copper-lantern-drift-marble is both strong and typeable.
Turn on two-factor authentication for the vault itself immediately, before importing anything.
Go to the import tool. In Bitwarden it lives under Tools → Import Data in the web vault.
Select the format. Choose Chrome (CSV) or Google (CSV) as the source.
Upload the CSV and confirm. The vault will show you a count. Match it against the number you exported so you know nothing was dropped.
Delete the CSV from your machine and empty the trash.