How to Import Passwords Into Bitwarden Safely

To import passwords into Bitwarden, choose a supported direct transfer or import an export file through the web vault’s Tools > Import screen. Match the source format, choose the correct destination and check the results before removing anything from your old manager. Importing the same data again can create duplicates.

The steps below cover a personal vault. If an employer manages the data, use its approved migration process and permissions. Do not transfer organisational passwords into a personal account just because you can export them.

Before You Start

• Sign in to the correct Bitwarden account and server region. Confirm you can unlock it and access your recovery information.
• Keep the old manager available. Check which items belong to your personal vault and which are shared or owned by an organisation.
• Note the item types you need: passwords, notes, cards, attachments, passkeys and verification-code secrets.
• Use your own updated device. Decide where an export will be saved before creating one; avoid a folder that automatically syncs to the cloud.

Check the source-specific instructions linked from Bitwarden’s import and export FAQ. A file’s extension is not enough: two CSV files can use different field layouts. Do not upload a password export to an online converter or AI chat to “fix” it.

Import a File Through the Web Vault

1. Open your Bitwarden web vault and select Tools > Import.
2. Choose My vault as the destination for personal data. You can select a folder to help identify the imported batch.
3. Select the format matching the manager or browser that produced the file.
4. Choose the export file, then select Import. If the supported file is password-protected, supply that export password when prompted.
5. Read the result and inspect your vault before repeating the operation.

These web instructions follow Bitwarden’s current import guide. In the browser extension, the documented route is Settings > Vault options > Import items. Interfaces differ; do not assume every app uses the web vault’s Tools menu.

Import Directly From a Desktop Browser

A direct import avoids leaving a manually exported password file behind. Bitwarden supports this in its desktop app for selected Chromium browsers, with platform-specific availability. It is available in the Windows and macOS downloads from Bitwarden and the Linux AppImage, but not desktop builds downloaded from app stores.

1. Open the Bitwarden desktop app and choose File > Import data.
2. Select your vault and the correct browser format.
3. Choose Import directly from browser if offered.
4. Select the browser profile containing your passwords, then import and complete the requested device authentication.

Chrome, Opera and Brave are listed; Edge and Vivaldi are limited to Windows and macOS, and Arc to macOS. If your combination is unsupported, use the documented file-export route instead. Do not disable security software to force a transfer. On a managed computer, ask your administrator about a blocked import.

Mobile Transfers: Check the Direction and App Pair

For a direct transfer into Bitwarden, its current mobile import instructions specify iOS 26+ or Android 14+ and a compatible source app. These are Bitwarden import requirements, not a universal minimum for every password-manager transfer.

• iPhone: start the export in the compatible source app, select the items and choose Bitwarden as the destination.
• Android: in Bitwarden, use Settings > Vault > Import items > Import from another app, then choose the source and authorise the transfer.

Bitwarden currently says importing Dashlane data through this direct Android route is unsupported. If your app pair is unavailable, use an accepted file format.

Check What Your Format Actually Includes

Do not assume a successful password import has moved every kind of item. Bitwarden’s custom-file documentation distinguishes its CSV and JSON structures. A basic CSV is useful for logins and secure notes, while other item types require appropriate support.

For a hand-maintained spreadsheet, use the documented Bitwarden format and UTF-8 encoding. Work locally and check that the editor has not changed leading zeros, punctuation or other credential characters. Keep the original vault intact while diagnosing a problem.

Passkeys are not carried in an ordinary password CSV. However, it would also be wrong to say that JSON can never contain passkeys: Bitwarden’s own JSON exports can include stored passkeys. Successful transfer to another product depends on what the destination can import, not only what the source can export.

If the source is 1Password, its export documentation explains that CSV includes fewer item types and fields than its richer 1PUX format. Select a format that Bitwarden actually accepts. Check attachments and sharing permissions separately rather than assuming they accompany the login.

Verify the Import Before Cleaning Up

1. Compare totals by item type. A matching overall count is helpful, but does not prove that fields mapped correctly.
2. Inspect important entries for the right username, website and password. Check records with notes or unusual characters.
3. Test sign-in to essential accounts using the new vault, while keeping a working recovery route.
4. Check any transferred passkeys and verification codes separately. Test shared access with the authorised people who need it.
5. Confirm the vault is available on your other devices and set up autofill there.

Choose a few low-risk accounts for the first sign-in checks, then check your important services. Avoid repeated guesses against banking or work systems that may lock an account. If a record is wrong, compare it with the source rather than immediately resetting everything.

Fix Errors Without Purging Your Vault

If an import fails, record the error, check the source format and consult the relevant importer’s instructions. For a field or size problem, fix only the affected data and preserve any information removed from an import in the original vault. Do not post the export or passwords in a support forum.

Bitwarden imports add records rather than automatically merging duplicates. Before retrying, establish whether the previous attempt added anything. Identify the imported batch and review duplicate entries carefully; purging the entire vault is not a routine troubleshooting step.

Remove Temporary Files and Finish the Move

After verifying the import, delete unencrypted export files and remove their copies from Trash or Recycle Bin. Check whether downloads, backups or sync tools made additional copies. Deletion is not a guarantee of forensic erasure, so avoiding unnecessary plaintext files is preferable.

Keep the old manager intact until all required items and recovery methods work. For the wider migration, use our guide to switching password managers. Our password-manager safety guide covers ongoing account and device protection.

Frequently Asked Questions

Share this article

WhatsAppLinkedInRedditFacebookX