How to Move Passwords from Bitwarden to 1Password
Switching password managers is mostly a data-migration problem, but the details matter because one bad export or import can leave accounts inaccessible.
This guide shows how to move passwords from Bitwarden to 1Password with minimal risk and a clean setup at the end.
What to know before you start
Bitwarden and 1Password both support encrypted password management, but they use different vault structures, fields, and attachment handling.
Before you begin, decide whether you are moving only passwords or your entire login library, including notes, secure items, identities, and attachments.
- Use a trusted computer, not a shared or public device.
- Update both apps and browser extensions before exporting or importing.
- Make sure you can sign in to both accounts before you switch.
- Plan a short window to verify logins after the import.
If you use Bitwarden for a family, team, or organization account, check whether your admin permissions affect export access.
If you rely on 1Password for personal use, family sharing, or business vaults, map your items to the correct destination before importing.
Why migrating carefully matters
Password managers often store more than usernames and passwords.
They may also hold TOTP codes, custom fields, secure notes, linked identities, card data, and file attachments.
During migration, some of these items may not transfer perfectly unless you review them afterward.
Bitwarden and 1Password are both well-known tools in the cybersecurity and identity-management space, but their import formats are not identical.
A careful migration reduces the chance of duplicate entries, broken autofill, lost attachments, or missing 2FA secrets.
Step 1: Organize your Bitwarden vault
Before exporting, clean up your Bitwarden vault so the import into 1Password is easier to verify.
Remove stale entries, merge duplicates, and confirm that each login has the correct username, password, and URL.
- Delete old or unused logins you no longer need.
- Check for duplicate entries with different passwords.
- Confirm websites use the correct domain names.
- Review notes, custom fields, and attached files for critical items.
This step is especially useful if you have imported data from browsers, previous password managers, or CSV files over time.
A cleaner source vault makes the destination vault much easier to trust.
Step 2: Export passwords from Bitwarden
Bitwarden supports export through its web vault and desktop app.
For most users, the web vault is the simplest option because it provides a straightforward export workflow.
You will typically need to authenticate again before export, which is a security safeguard.
Choose an export format that 1Password can import reliably.
CSV is commonly used for passwords and basic login fields, while JSON may preserve more Bitwarden-specific structure.
In many migrations, CSV is the practical choice because it maps cleanly to 1Password’s import tools.
- Open Bitwarden and go to the export section.
- Select the vault or items you want to export.
- Choose the format recommended for your migration plan.
- Save the file to a secure location.
After exporting, protect the file immediately.
Exported password files are sensitive because they are usually not encrypted once saved to disk.
Move them to a secure folder, delete any unnecessary copies, and avoid emailing the file or storing it in an unsecured cloud folder.
How to handle attachments and 2FA data?
Attachments and authenticator-related data need extra attention.
Depending on the item type and export format, attachments may not transfer the way you expect, and TOTP secrets may require manual review.
If you use Bitwarden Authenticator or stored one-time passcodes, verify whether each login in 1Password has the corresponding two-factor setup.
Some accounts may need you to re-scan QR codes or enter new recovery codes after migration.
For important accounts such as banking, email, Apple ID, Google Account, and Microsoft account, keep recovery codes in a secure place before making changes.
Step 3: Import into 1Password
1Password supports importing data through its desktop app and account-based import tools.
The exact path may vary slightly by platform, but the process is generally guided and designed to map common password-manager fields into 1Password items.
When importing, pay attention to the destination vault.
If you use multiple vaults in 1Password, decide whether the imported data should land in your Private vault, a Family vault, or a shared vault.
For most personal migrations, starting with a dedicated temporary vault can make cleanup easier.
- Open 1Password and find the import option.
- Select Bitwarden or a compatible CSV/JSON import source.
- Choose the exported file from Bitwarden.
- Review the item mapping before finalizing the import.
After the import completes, inspect several entries manually.
Confirm that usernames, passwords, URLs, custom fields, and notes appear in the right places.
If you rely on tags or groups in Bitwarden, expect some reorganization work in 1Password because the two apps do not structure collections exactly the same way.
What usually imports well?
Most standard login records transfer cleanly, especially when they follow a simple pattern: one site, one username, one password, and one URL.
Secure notes usually import well too, though formatting can vary depending on the source data.
- Website logins
- Secure notes
- Custom usernames and passwords
- Some identity and card entries
Items with complex custom fields, nested data, or attachments may require manual correction.
The closer your Bitwarden vault is to a clean, consistent structure, the better the result in 1Password.
What may need manual cleanup?
Even a successful import can leave behind issues that affect day-to-day use.
The most common problems are duplicate logins, malformed URLs, missing attachments, and entries placed in the wrong vault.
- Duplicate records created during import.
- Missing or truncated notes.
- Incorrectly parsed custom fields.
- Attachments that did not transfer.
- Logins that need different autofill behavior.
1Password’s item editor makes it easy to fix these issues one by one.
If you manage dozens or hundreds of entries, start with your most important accounts first: email, banking, cloud storage, social media, and any account used for password recovery.
Step 4: Verify your critical logins
Verification is the part that turns a migration into a safe switch.
Open 1Password and test a sample of your most important accounts by signing in on desktop and mobile devices.
Check whether autofill works in browsers such as Chrome, Safari, Firefox, and Edge.
For each critical login, confirm the following:
- The username is correct.
- The password works.
- The website URL matches the login page.
- Two-factor authentication still functions.
- Any custom note or PIN is present if needed.
If a login fails, do not assume the export was bad.
Sometimes the entry needs only a small correction, such as a missing subdomain, a mistyped password, or an outdated recovery field.
Should you delete Bitwarden right away?
No.
Keep Bitwarden for a short transition period until you have verified your key accounts and confirmed that nothing important is missing.
Retaining the old vault temporarily gives you a fallback if a site behaves unexpectedly or an item needs manual reconstruction.
Once you are confident in 1Password, remove the Bitwarden export file, sign out of Bitwarden on devices you no longer use, and delete any backup copies you do not need.
If you shared Bitwarden with a family or team, make sure everyone is moved before retiring the old setup.
Best practices for a smooth switch
A password manager migration is a good time to strengthen your security habits.
After you move passwords from Bitwarden to 1Password, use the opportunity to review weak passwords, enable strong two-factor authentication, and update old recovery information.
- Turn on 2FA for your 1Password account.
- Use a strong, unique master password.
- Review weak, reused, or compromised passwords.
- Store recovery codes for high-value accounts.
- Delete export files and secure backups after verification.
If you want the cleanest outcome, treat the migration as a security review, not just a file transfer.
The goal is a fully working 1Password setup with fewer duplicates, better organization, and stronger account protection than before.
Common migration mistakes to avoid
The most common errors are avoidable.
Users often export from the wrong vault, import into the wrong destination, or forget that attachments and authenticator data may need separate attention.
- Exporting on an unsecured device.
- Leaving the CSV or JSON file in Downloads.
- Skipping login verification after import.
- Assuming every field will map perfectly.
- Deleting Bitwarden before confirming critical accounts.
By treating the export file as highly sensitive and checking the imported data carefully, you reduce the chance of account lockouts and save time later.
Moving passwords from Bitwarden to 1Password on mobile and desktop
The safest migration is usually done on a desktop because export and import tools are easier to use there.
Mobile apps are better for verification, not for large data transfers.
After the import, install or sign in to 1Password on your phone and tablet, then test autofill in common apps and mobile browsers.
If you use browser extensions, install the 1Password extension after the import and remove the Bitwarden extension only when you are sure the new setup works.
This prevents autofill conflicts and makes troubleshooting much easier.
When to seek help
If your Bitwarden vault contains business data, shared vaults, large attachment libraries, or many authenticator secrets, a staged migration may be safer than a single bulk import.
In those cases, 1Password support documentation and Bitwarden help resources can clarify file formats, vault mapping, and item compatibility.
For especially sensitive environments, such as regulated workplaces or teams with compliance requirements, involve your IT or security administrator before exporting anything.
A password export is a powerful action, and it should fit your organization’s data-handling policies.