Before you export anything
A CSV of every password you own is the most sensitive file you are likely to create. The procedure is short; the main risk is leaving that file behind.
- Create and unlock the new vault, and turn on two-step login for it.
- Store its recovery method, such as a recovery code or 1Password's Emergency Kit, somewhere other than the vault itself.
- Pause backup software and cloud folder sync for the folder you will export into. 1Password's Chrome guide says to temporarily turn off backup software so the unencrypted export file is not backed up. [1]
- If some passwords are saved only on your phone, sync them to the computer first; 1Password's guide asks you to sync Chrome on your mobile device with your computer before exporting. [1]
- Decide where the file will live for the next 30 minutes, and nowhere else. Do not email it or put it in a shared drive.
Step 1: export from the browser
Apple also lists what cannot be exported: Wi-Fi passwords, passwords shared with a group you did not create, and access to Sign in with Apple accounts. Leave those in Apple Passwords. [2][3][4]
| Source | Path the vendor documents | Watch for |
|---|---|---|
| Chrome | Google Password Manager, Settings, Export passwords, Download file | You may be asked for your computer's login password. |
| Apple Passwords on Mac | File, Export All Passwords to File, Export Passwords, then pick a save location | Apple says the file is not encrypted and is visible to anyone with access to it. |
| Safari on Mac | File, Export browsing data to file, select passwords, Download; unzip to get Passwords.csv | Delete both the zip and the CSV afterwards. |
| Safari on iPhone | Settings, Apps, Safari, Export, choose passwords, save to Downloads | Bitwarden warns the data is saved without encryption into iCloud Drive. |
Step 2: import into the new vault
Sources: Bitwarden Chrome and Safari import pages and 1Password's Chrome import page, read 29 October 2026. NordPass's help center refused our fetch that day; if you are moving to NordPass, follow its own import article and the same cleanup steps below. [5][4][1]
| Vault | What its help page says | Watch for |
|---|---|---|
| Bitwarden | Two methods for Chrome: export then import the file, or import directly from the browser in the desktop app. Direct import works in Windows and macOS apps from Bitwarden's downloads page and the Linux AppImage, not app-store versions. Safari exports are supported. | Delete the export file after import; Bitwarden adds that you may also want to delete data from the old tool. |
| 1Password | Imports from a Chrome CSV with the 1Password app or browser extension unlocked, or on 1Password.com. | Only passwords import. Credit cards, addresses, passkeys and other information are not imported. |
Step 3: check before you delete anything
This is our proposed acceptance check, not a test we performed. We have not imported a real vault into either product.
- Count items: the vault total should be close to the browser total. A large gap means a failed or partial import.
- Open ten logins at random, including one with a subdomain and one with a long note, and confirm username, password and web address.
- Sign in to three real sites on your phone and on your computer using the new vault's autofill.
- List what the import does not carry, such as passkeys and saved cards, and decide whether to re-create them or leave them where they are.
Step 4: clean up in the right order
- Delete the CSV export (and any zip) and empty the trash or Recently Deleted folder. 1Password and Bitwarden both say to delete the export file after importing. [1][5]
- Turn backups and cloud sync back on only after the file is gone.
- Turn off the browser's offer to save passwords. Chrome documents an Offer to save passwords and passkeys switch, which is on by default. [2]
- Delete passwords from the browser only after the new vault works on every device. Chrome's Delete all Google Password Manager data option removes both passwords and passkeys, so keep the browser copy if your new vault did not import your passkeys. [2]
Common mistakes
If something goes wrong mid-move, the browser copy is your rollback. That is why deletion is the last step, not the second.
- Exporting into a synced Desktop or Documents folder, so the file uploads to the cloud before you notice.
- Deleting browser passwords before testing the new vault on your phone.
- Assuming passkeys moved. 1Password's Chrome import brings only passwords. [1]
- Running two managers that both offer to save new passwords, so logins split between them.
Questions before you decide
Is the exported password file encrypted?
No. Apple says exported passwords are not encrypted and are visible to anyone with access to the file, and Bitwarden and 1Password both tell you to delete the export after importing.
Will my passkeys move too?
Do not assume so. 1Password says its Chrome import brings only passwords, not passkeys, cards or addresses. Keep passkeys where they are or create new ones in the new vault.
Can Bitwarden import straight from Chrome without a file?
Yes, in the desktop app installed from Bitwarden's downloads page on Windows or macOS, or the Linux AppImage. Bitwarden says direct import does not work in desktop apps downloaded from app stores.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- 1Password: import from Chrome Accessed 29 Oct 2026
- Google Chrome Help: manage passwords in Google Password Manager Accessed 29 Oct 2026
- Apple Support: export passwords from Passwords on Mac Accessed 29 Oct 2026
- Bitwarden: import from Safari Accessed 29 Oct 2026
- Bitwarden: import from Chrome Accessed 29 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.