The safest migration is a one-time export, immediate import, careful verification, and deletion of the export file. Browser exports are commonly CSV files that may contain readable passwords, so keep the file local and private, never email or upload it, and remove it as soon as the new vault is confirmed. The exact menu and import format depend on your browser, operating system, and password manager.
Decide the destination before exporting
Exporting first and choosing a destination later leaves a plaintext credential file on your device longer than necessary. Open the password manager you intend to use, check its documented import options, and then export only the data that manager can accept.
As an Amazon Associate I earn from qualifying purchases.
- Confirm the accepted format. CSV is common, but some managers also accept their own encrypted or richer formats. Google Password Manager’s documented import accepts CSV only.
- Use a private local location. Save the export outside folders synchronized to cloud storage or monitored by backup software. 1Password recommends temporarily turning off backup software before creating an unencrypted export so a second copy is not made automatically.
- Prepare authentication. Browser export controls can require your computer account password, device PIN, or biometric approval.
- Plan a verification pass. Keep the old browser vault available until important accounts, usernames, URLs, and passwords are present in the new vault.
Unless the provider explicitly says an export is encrypted, treat it as readable credentials. Mozilla Support warns that passwords in its exported file are unencrypted and readable to anyone who can view it. 1Password gives the same warning for exported data files.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Export saved passwords from your browser
Chrome or another Chromium browser on a computer
Chromium-based browsers use similar concepts, but labels and locations differ. The following paths are documented examples for Chrome and Microsoft Edge rather than a guarantee for every Chromium-derived browser.
#1 Best Overall
- Auto-Fill Feature: Say goodbye to the hassle of manually entering passwords! PasswordPocket automatically fills in your credentials with just a single click.
- Internet-Free Data Protection: Use Bluetooth as the communication medium with your device. Eliminating the need to access the internet and reducing the risk of unauthorized access.
- Military-Grade Encryption: Utilizes advanced encryption techniques to safeguard your sensitive information, providing you with enhanced privacy and security.
- Offline Account Management: Store up to 1,000 sets of account credentials in PasswordPocket.
- Support for Multiple Platforms: PasswordPocket works seamlessly across multiple platforms, including iOS and Android mobile phones and tablets.
- In Chrome, open
chrome://password-manager/settings. In Edge, openedge://wallet/passwords, or open the browser’s password settings through its main menu. - Find the export control, usually labelled Export Passwords or available from a three-dot menu beside saved-password controls.
- Authenticate when prompted with the computer password, device PIN, or biometric check.
- Choose a private local folder and save the file. Confirm that the resulting file is CSV before importing it.
Do not assume a direct browser-to-manager transfer exists just because both applications run on Chromium. Bitwarden documents a direct-import route in its desktop app for supported Chromium browsers, but that route is client- and browser-specific. If it is not offered in your manager, use the browser’s CSV export and the manager’s CSV importer.
Chrome or Edge on a phone or tablet
Mobile browsers can expose export controls in different menus from their desktop counterparts. Open the browser’s password manager, use its export command, and complete the device security check if requested. Bitwarden’s instructions note that mobile users may be asked for a device PIN or biometric authorization. The exact menu names and whether a file can be saved locally depend on the operating system and browser version; use the destination manager’s mobile-import instructions rather than assuming the desktop path applies.
Firefox
Firefox exports saved usernames and passwords as a CSV file through its password-management feature. The labels can change with Firefox releases, but the workflow is:
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →- Open Firefox’s password manager (the saved-logins area).
- Open the actions menu for saved logins and choose the export option.
- Authenticate if Firefox or the operating system requests it.
- Save the CSV in a private, non-synchronized folder and proceed directly to the destination manager’s importer.
Mozilla explicitly says the exported file is not encrypted. Do not upload, email, or share it, and delete it after the import and verification steps are complete.
Safari and iCloud Passwords when the destination is 1Password
Safari migration is not a universal browser procedure: the documented workflow below is specific to moving Safari or iCloud Passwords into 1Password.
- Use Safari’s password export function to create the export archive.
- Extract the ZIP archive and locate the unencrypted CSV inside it.
- In 1Password, choose the Safari-data import path and select the extracted CSV.
- Wait for the import to finish, then inspect representative logins and important accounts.
- Delete the unencrypted CSV. 1Password also advises turning off Safari’s built-in password manager and removing iCloud Passwords only after you have confirmed the credentials are stored in 1Password.
Deleting iCloud Passwords in this migration is permanent. Credit cards, addresses, and other saved information may not be carried by the password CSV and can require manual copying.
Rank #2
- Offline Local Storage for Privacy:This Password Keeper stores all your login credentials directly on the device, with no cloud or internet connection, helping reduce exposure to hacking and data breaches.
- Full Control of Your Sensitive Data:Unlike cloud-based managers, this physical device keeps your passwords entirely under your control. Your information never leaves the device, and you won’t share it with third-party servers.
- Built-in Device Password Protection:Add an extra layer of security with optional device password protection, helping prevent unauthorized access to your stored records if the device is misplaced.
- Compact Hardware Vault for Credentials:A secure alternative to handwritten notes or spreadsheets, this portable device lets you store unique, complex passwords for all your accounts in one place.
- Simple USB Type-C Access:Connect via the included USB Type-C cable to your laptop, phone, or standard 5V charger to view and navigate your passwords on the built-in screen, no internet required.
Import the file into a password manager
Bitwarden
Bitwarden supports importing through its web app, browser extension, desktop application, and command-line interface, although available formats and controls vary by client. Use the importer that matches your browser and file type.
Recommended Free Tools
- Sign in to Bitwarden and open its import-data function in the client you are using.
- Select the source format that matches the file, such as Chrome, Edge, or Firefox CSV, rather than choosing an unrelated manager format.
- Choose the file, start the import, and wait for the completion message.
- If you are using the Bitwarden desktop application, check whether its documented direct-import option is available for your supported Chromium browser. A direct transfer avoids creating a CSV, but it is not available in every client or browser combination.
Bitwarden states that importing does not check for duplicates. Importing the same file twice can therefore create duplicate login items. Treat a re-import as a deliberate recovery action, not as a harmless way to retry.
Google Password Manager in Chrome on a computer
Google’s documented import is performed in Chrome on a computer and requires a CSV file. The first row must contain the column names url, username, and password. A minimal file therefore has this structure:
url,username,password- Open Chrome’s password manager on the computer.
- Choose the import option and select the CSV file.
- Confirm the import and wait for Chrome to report completion.
- Search for several accounts by site name, URL, and username. Google warns that some app or site names can map to an unexpected field, so an account may be easier to find by searching than by browsing the list.
- Delete the CSV from the device after verification.
Google documents a limit of 3,000 passwords per import and a storage limit of 10,000 passwords per Google Account. These are product limits published in Google’s current Chrome help instructions and may change, so check the import screen if your vault is near either threshold. Split a migration into intentional batches only when the manager’s instructions support that approach.
1Password CSV imports
1Password’s general CSV guidance requires a website, username, and password for each login, with a consistent field order and the same number of fields on every line. Values containing commas or line breaks must be enclosed in quotation marks so the importer does not treat part of a password or note as a new column.
Free tools Windows power users keep installed
One-click scans. No signup required.
- Open 1Password’s import function and select the source format that matches your browser or generic CSV.
- Map the columns to the requested fields, including website, username, and password.
- Start the import and inspect the resulting items before deleting the source file.
1Password lists CSV fields such as title, website, username, password, one-time password, favorite status, archived status, tags, and notes. CSV is not a complete vault representation: security questions, linked items, linked applications, and custom fields can be omitted, including some two-factor backup-code data. Its 1PUX format carries additional fields when the source and destination support it. Desktop exports do not export passkeys; 1Password’s mobile Credential Exchange workflows support passkey transfer only under the documented platform conditions.
Rank #3
- Auto-Fill Feature: Say goodbye to the hassle of manually entering passwords! PasswordPocket automatically fills in your credentials with just a single click.
- Internet-Free Data Protection: Use Bluetooth as the communication medium with your device. Eliminating the need to access the internet and reducing the risk of unauthorized access.
- Military-Grade Encryption: Utilizes advanced encryption techniques to safeguard your sensitive information, providing you with enhanced privacy and security.
- Offline Account Management: Store up to 1,000 sets of account credentials in PasswordPocket.
- Support for Multiple Platforms: PasswordPocket works seamlessly across multiple platforms, including iOS and Android mobile phones and tablets.
When the destination is a different manager
Use the destination provider’s named importer whenever one exists. A manager may accept a browser-specific CSV, a generic CSV, or an encrypted export from another manager. Do not rename a file or guess at its columns to make it look compatible: schemas vary, and a superficially successful import can put URLs, usernames, or notes in the wrong fields. If no direct importer exists, identify which fields the destination requires and create a small test import before moving the entire vault.
What survives a browser-to-manager migration?
Browser exports are designed for portability, not necessarily for a complete copy of every vault object. Use the route that preserves the data you actually need.
| Route | Typical format or transfer | Important qualification |
|---|---|---|
| Chrome or Edge to a manager | CSV, or a documented direct import in some desktop clients | Menu labels and direct-transfer availability vary by browser and client. |
| Firefox to a manager | Unencrypted CSV | Anyone who can access the file can read the passwords. |
| Chrome to Google Password Manager | CSV with url, username, and password headers |
Up to 3,000 passwords per import and 10,000 stored per Google Account according to Google’s current instructions. |
| Safari or iCloud Passwords to 1Password | Safari export ZIP, extracted to CSV | Some credit-card, address, and other saved data may require manual copying; deleting iCloud Passwords is permanent. |
| 1Password CSV export | CSV with a limited field set | Security questions, linked items, linked apps, custom fields, some backup-code data, and desktop passkeys are not represented. |
CSV also has practical limits. A password containing a comma or line break must be quoted correctly. Different browsers can use different column names or include an application name where a manager expects a title or URL. A file can therefore import without an error while still needing manual correction.
Verify the new vault before deleting anything
Verification is the step that prevents a clean-looking import from becoming a lockout later. Check both the number of records and the contents of records that matter most.
- Search for critical accounts. Check email, banking, work, government, cloud-storage, and domain-management logins first.
- Open individual entries. Confirm the website URL points to the intended service, the username or email is correct, and the password is present.
- Test sign-in selectively. Sign in to a few representative sites from the new manager, especially accounts with unusual usernames or multiple subdomains.
- Look for records that moved under an unexpected name. Google notes that app and site names can land in unexpected fields; search by account name, URL fragment, and username.
- Check non-login data separately. One-time-password seeds, recovery codes, security questions, passkeys, payment cards, addresses, linked items, and custom fields may not be included in a browser CSV.
- Look for duplicates before editing. Bitwarden does not perform duplicate detection during import, so compare similarly named entries before deciding which one to keep.
Do not delete the browser’s saved passwords while any important entry remains unverified. A successful import message means the file was processed; it does not prove that every field mapped correctly.
Remove the plaintext export and retire the old browser store
After verification, delete the exported CSV or extracted file from the original folder and empty the operating system’s trash or recycle bin. Also check whether your file manager, backup service, or synchronization tool made another copy. If you created the export in a temporary backup-disabled location, restore your normal backup setting only after the file is gone.
Whether to disable browser password saving is a separate choice. If the password manager is now your single source of truth, turn off the browser’s built-in saving prompt so new credentials do not split between two vaults. Remove existing browser or iCloud entries only after confirming the manager contains them. For the Safari-to-1Password procedure, 1Password specifically warns that deleting iCloud Passwords cannot be undone.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Troubleshoot common migration failures
The importer rejects the file
Confirm that the file is actually CSV, not a renamed spreadsheet or ZIP archive. Open it only long enough to inspect the first row and verify the expected headers. For Google Password Manager, the header row must include url, username, and password. For a manager-specific importer, select the matching source type instead of generic CSV when both choices are available.
The import completes but entries are missing
Compare the browser’s record count with the manager’s count, then search for several missing sites by username and URL. A site name may have been mapped into a title or note field. If the browser stored data types outside the CSV schema, copy those items manually or use a richer format supported by both applications.
Usernames, URLs, or notes are in the wrong fields
Stop editing the entire vault at once. Inspect the CSV column order and the destination’s field mapping, then correct a small sample. If the mapping is wrong, remove the bad test entries and import the original file again only after fixing the mapping. Remember that a Bitwarden import will not detect duplicates automatically.
The same accounts appear twice
Do not repeatedly re-import while diagnosing the problem. Export or otherwise preserve the original source, identify which entries are duplicates, and consolidate them manually. Repeated imports can multiply records because duplicate checking is not performed in Bitwarden.
Passkeys or two-factor details are absent
A browser-password CSV generally carries website, username, and password fields, not every credential type. 1Password documents that desktop exports do not include passkeys and that its CSV omits several advanced fields. Keep passkeys in their existing platform until you have a supported transfer method, and copy recovery codes or other missing security data manually into the destination’s appropriate secure fields.
When a direct transfer is preferable to CSV
Choose a documented direct app-to-app transfer when it is available for your exact browser, operating system, and password-manager client. It can avoid creating a plaintext file, but it may expose fewer options for field mapping and may not exist in a mobile app or a particular browser variant. CSV remains useful when you need a visible, editable interchange file, provided you protect it and delete it promptly.
The practical decision is therefore straightforward: use the destination’s direct importer when it explicitly supports your source; otherwise export the browser’s accepted format, import once, verify important entries and unsupported data types, and remove every plaintext copy before retiring the old store.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems
