How to Move Passwords from Chrome to 1Password
If you are switching from Google Chrome’s built-in password manager to 1Password, the process is straightforward but worth doing carefully.
This guide explains how to move passwords from Chrome to 1Password, what gets transferred, and how to verify that your logins are ready to use.
Chrome can store hundreds of credentials across desktop and mobile devices, but 1Password adds stronger organization, sharing controls, and vault-based security.
The key is exporting your saved passwords from Chrome in the right format and importing them into 1Password without exposing sensitive data longer than necessary.
Why people switch from Chrome to 1Password
Google Password Manager works well for basic autofill, but many users move to 1Password for more advanced password management.
1Password is designed as a dedicated password manager rather than a browser feature, which gives it broader control over logins, secure notes, identities, payment cards, and shared credentials.
- Cross-platform access: Use the same vaults on macOS, Windows, iPhone, iPad, Android, and Linux.
- Better organization: Group items into vaults and categories such as logins, secure notes, and credit cards.
- Family and team sharing: Share selected items securely instead of relying on browser sync.
- Security features: Use Watchtower, Travel Mode, and stronger vault permissions.
- Independent app: Your passwords are not tied to a single browser session or profile.
Before you export passwords from Chrome
Before starting, make sure you are signed into the correct Chrome profile.
Many people have multiple profiles, and passwords may be spread across them.
Check whether your saved logins are stored in the profile you use most often, especially if you have separate work and personal accounts.
It also helps to clean up duplicates and old logins first.
Chrome often stores multiple versions of the same website entry, and importing them into 1Password without review can create clutter.
- Confirm the correct Chrome profile is active.
- Remove outdated or duplicate saved passwords.
- Check that important logins are complete, including usernames.
- Review any two-factor authentication apps or backup codes you may also need to move.
How to export passwords from Chrome
Chrome lets you export saved passwords as a CSV file, which is the standard format 1Password can import.
Because CSV files are plain text, handle the file carefully and delete it after the import is complete.
On Windows or Mac
- Open Chrome.
- Select the three-dot menu and go to Passwords and autofill or Google Password Manager, depending on your version.
- Open Settings or the password manager menu.
- Look for Export passwords.
- Authenticate with your device password, PIN, or system prompt.
- Save the CSV file in a secure location.
On ChromeOS
The export flow is similar, but device-level authentication may differ.
Use the password manager menu inside Chrome and follow the export prompts.
If your Chromebook is managed by an organization, exports may be restricted by policy.
On Android or iPhone
Mobile exports depend on the Chrome app and operating system permissions.
In many cases, exporting is easier from a desktop browser.
If you use Chrome on mobile only, you may need to sign in on a computer to complete the export.
How to import Chrome passwords into 1Password
Once you have the CSV file, import it into 1Password using the desktop app or web workflow supported by your plan.
1Password recognizes Chrome’s export format and maps the data into login items.
Import using the 1Password desktop app
- Open 1Password on your Mac or Windows computer.
- Go to the import option in the app menu or settings.
- Select Chrome or CSV as the import source.
- Choose the exported Chrome CSV file.
- Review the preview to confirm usernames, passwords, and website fields look correct.
- Complete the import into the desired vault.
What gets imported?
Chrome exports primarily include login data, so the import usually brings in website URLs, usernames, and passwords.
Depending on the item and export version, some additional fields may transfer, but you should not expect every type of browser-stored data to map perfectly.
- Commonly imported: website address, username, password
- May require manual cleanup: duplicate entries, missing labels, outdated URLs
- Usually not transferred directly: browser-only preferences, some custom notes, and non-login data
How to verify your imported logins
After the import, test the most important accounts first: email, banking, cloud storage, social media, and any work tools you use daily.
Open each site and confirm that 1Password autofill works correctly and that the saved username and password match what you expect.
If a login fails, check whether the website has changed its sign-in URL or whether Chrome stored the entry under a different address.
Some services use multiple domains or redirect patterns, which can create duplicate or partial entries.
- Test high-value accounts before removing Chrome data.
- Look for duplicates with slightly different URLs.
- Update weak or reused passwords where needed.
- Add missing one-time passwords or recovery details manually.
What to do with two-factor authentication and recovery codes
Moving passwords is only part of the migration.
If you use two-factor authentication, make sure the authenticator method stays accessible after the switch.
Some users store recovery codes in Chrome notes or elsewhere in the browser ecosystem, but those codes should be moved into 1Password secure notes or another protected location.
If a site uses app-based authentication, verify whether the secret can be moved or whether you need to re-enroll.
For some services, you may need to disable and re-enable two-factor authentication to place it under your preferred setup.
How to delete the exported Chrome CSV safely
The exported CSV file contains plain-text passwords, so delete it as soon as the import is finished and verified.
Emptying the trash is not always enough on every platform, especially if the file synced to cloud storage or appeared in a recent files list.
- Delete the CSV from downloads and desktop folders.
- Empty the recycle bin or trash.
- Remove any copies from cloud sync folders such as Google Drive, Dropbox, or OneDrive.
- Check recent files and file previews if your system stores them.
Common issues when moving passwords from Chrome to 1Password
Most migration problems come from formatting, duplicates, or account confusion.
A few simple checks usually solve them.
The import file is not recognized
If 1Password does not accept the CSV, confirm that it is the Chrome export file and not a different spreadsheet.
Do not open and resave the file in a spreadsheet app unless you know the formatting will stay intact, because that can break the import structure.
Some logins are missing
Missing entries often mean they were stored in another Chrome profile, another device, or never saved in Chrome at all.
Check the password manager in each browser profile before assuming the export failed.
Duplicate logins appear in 1Password
Chrome may have saved the same site more than once under different URLs.
In 1Password, merge or remove duplicates after you identify the correct active login.
Best practices after the migration
Once your passwords are in 1Password, start using it as the primary source of truth.
Turn off Chrome’s password-saving prompts if you do not want new logins saved in the browser again.
This reduces confusion and keeps future password changes in one place.
- Set 1Password as your main password manager.
- Use a strong master password and enable two-factor authentication for your 1Password account.
- Review Watchtower alerts for weak, reused, or compromised passwords.
- Update saved logins whenever you change a password so your vault stays current.
- Store secure notes, recovery codes, and important documents in the appropriate vault.
Can you keep Chrome and 1Password side by side?
Yes, but it is best to define a clear role for each tool.
Many users let 1Password handle all stored credentials while Chrome remains just the browser.
That approach avoids conflicts between autofill prompts and reduces the chance of saving a password in the wrong place.
If you still want Chrome to remember a few items, be deliberate about it.
For most people, a single dedicated password manager is easier to maintain and more secure than splitting data between browser storage and a standalone vault.