Skip to content

Bitwarden to KeePassXC: Export and Import

2026-11-09 · 8 min read · migration, bitwarden, keepass

A Bitwarden export file moving into a KeePassXC database

Bitwarden to KeePassXC: the direction picks the file

To move a Bitwarden vault into KeePassXC, export it from Bitwarden as .json or .json (Encrypted). Then open KeePassXC, go to Database > Import, and pick the Bitwarden option in the Import Wizard. To go the other way, export from KeePass as .kdbx, .xml, or .csv, then import it in Bitwarden under Tools > Import. Each direction needs its own file type.

You are moving Produce this file Import it with
Bitwarden to KeePassXC .json or .json (Encrypted) from Bitwarden Database > Import, then the Bitwarden option
KeePass or KeePassXC to Bitwarden .kdbx, .xml, or .csv from KeePass Tools > Import, then KeePass (kdbx) or KeePassX (csv)

Bitwarden can also skip the file entirely: on iOS 26+ and Android 10+ it exports straight to another app that supports the FIDO Credential Exchange Protocol (CXP) (Bitwarden, Export Vault Data). The route below goes through a Bitwarden export file and the Import Wizard, which is the path KeePassXC documents.

Export the Bitwarden file KeePassXC can read

Use .json, not .csv. Bitwarden states that only .json exports include cards, identities, stored passkeys, and SSH keys. No export format includes trash items or Sends (Bitwarden, Export Vault Data). A .csv export leaves those four item types behind before KeePassXC sees the file.

Format Cards, identities, passkeys, SSH keys Encrypted
.json Yes No
.json (Encrypted) Yes Yes
.csv No No
.zip (with attachments) Yes, in the inner .json, plus attachments No

Encrypted exports come in two types, and the choice decides whether the file is still usable after the move. An account restricted file imports only into the Bitwarden account that made it. Rotating the account encryption key makes it impossible to decrypt. A password protected file opens with a password you choose and imports into any Bitwarden account (Bitwarden, Encrypted Exports). For a move, choose password protected.

Export from the Bitwarden web app

  1. Sign in to the Bitwarden web app and select Tools, then Export.
  2. In the Export from menu, choose My vault, and set the File format to .json (Encrypted).
  3. In Export type, choose Password protected, set a password, and keep it apart from the file.
  4. Select Export, then enter your master password or the email verification code to confirm.

The browser extension path is Settings, then Vault options, then Export vault. Open the downloaded file in a text editor: the login fields show ciphertext instead of usernames and passwords, which confirms the encrypted form. The screen-by-screen walkthrough, with the extension and desktop paths, lives in export a Bitwarden vault.

Import the file into KeePassXC

KeePassXC reads a Bitwarden export through its Import Wizard, not through the entry list.

  1. Start KeePassXC. On the welcome screen select Import File, or select Database > Import from the menu.
  2. In the Import Wizard, select the Bitwarden option.
  3. Select the .json file. If the file is encrypted, enter the export password. KeePassXC's documentation says the password is needed only for the encrypted option.
  4. Select Continue. The wizard unlocks the file and shows a preview. Read the preview before going on.
  5. Under Import Into, choose a new database or an open one. Select Done.
  6. If you made a new database, save it with Save Database As (Ctrl+Shift+S).

Delete nothing yet. The verification section covers what to check.

What the import keeps and what it drops

KeePassXC's documentation covers the Bitwarden option and warns that the file may be unencrypted, but it does not list how each item type maps to a KeePassXC entry. The table shows what Bitwarden exports and what to check in your own database.

Bitwarden item In the .json export KeePassXC import Check
Logins, with TOTP Yes Not listed field by field Compare three entries, one with TOTP
Secure notes Yes Not listed field by field Open one note
Cards Yes Not listed field by field Find each card entry
Identities Yes Not listed field by field Find each identity entry
Passkeys Yes Not described Test each passkey on its site before deleting the export
SSH keys Yes Not described Confirm the key material is present
Attachments Only in .zip The wizard takes .json Download each attachment and store it yourself
Trash and Sends Never Not applicable Restore trash before export, re-create Sends by hand
Organization items Not in an individual export Not applicable An admin or custom-role member exports them

Bitwarden's documentation also notes that passkeys created before 2024.3.1 carry a use counter. A service may reject them, so an export of those passkeys is not a long-term backup.

Moving from KeePass or KeePassXC to Bitwarden

To move from KeePass to Bitwarden, export from KeePassXC first. For a KDBX file (.kdbx), select Database > Save Database As. For .xml or .csv, select Database > Export, confirm with Yes, enter your password, and select Unlock. Both .xml and .csv files are unencrypted, so treat them as secrets until they are deleted (Bitwarden, Import from KeePass).

Then import in Bitwarden:

  1. Open Tools > Import in the web app. In the browser extension, use Settings > Vault options > Import.
  2. In the Vault menu, select My vault. You can also pick a folder.
  3. In the File format menu, select KeePass (kdbx). For an XML file, select KeePass 2 (xml). For CSV, select KeePassX (csv). Bitwarden accepts CSV only when KeePassX or KeePassXC created it.
  4. Enter your KeePass master password.
  5. If the database uses a key file, select Add key file and choose the .keyx file.
  6. Choose the .kdbx file and select Import.
  7. Delete the exported file.

The XML and CSV paths stop after Import: no key file field, no KeePass password prompt.

KeePass groups become Bitwarden folders in My vault, or collections in an organization vault.

Bitwarden does not check for duplicates. Each import creates every record as a new item (Bitwarden, Import & Export FAQs). Before a second attempt, either edit the file to include only new items, or purge the vault from Settings > My account. A purge deletes everything in that vault, so run it only when you hold a copy of what is there.

Verify before you delete the export

  1. Count entries in the source and the target, group by group. KeePass groups arrive as Bitwarden folders, so compare folder totals.
  2. Pick three logins that have TOTP. In KeePassXC, copy the code with Ctrl+T and compare it with the code from the original app.
  3. Check cards, identities, passkeys, SSH keys, and attachments one by one, using the table above.
  4. Sign in to one low-stakes site with a migrated password.
  5. Delete the export file only after steps 1 to 4 pass. If any step fails, keep both the source and the export until you find the cause.

Frequently asked questions

Does KeePassXC import a Bitwarden JSON file?

Yes. Open the Import Wizard from Database > Import, choose the Bitwarden option, and enter the export password only when the file is encrypted.

Does Bitwarden import a KeePass .kdbx file?

Yes. Bitwarden accepts .kdbx with an optional key file, plus .xml and .csv. The .csv option works only for files created by KeePassX or KeePassXC.

Do passkeys survive a Bitwarden to KeePassXC import?

The sources checked do not say. Bitwarden's .json export includes stored passkeys. KeePassXC's documentation does not describe how its Bitwarden importer handles them, so test each passkey on its site before you delete the export.

Is the Bitwarden export file encrypted?

Only the .json (Encrypted) option is encrypted. Plain .json and .csv files are readable by anyone who opens them. Delete them right after use.

Can I move an organization vault to KeePass?

Not with an individual export. Only admins, owners, and some custom roles can export organization items, through the web app or the CLI. Members with Manage collection permission can export the collections they can access.

When the import goes wrong

  • The wizard shows the wrong format. Cancel the wizard, reopen it from Database > Import, and pick the Bitwarden option again.
  • The password is rejected. Either the password does not match the one you set, or the export was account restricted and the account encryption key was rotated after the export. No password fixes the second case. Export again with password protected.
  • Entries are missing. Trash items and Sends never appear in an export. Restore trash items to My vault before you export, and re-create Sends by hand.
  • Entries appear twice. You ran the import twice. Remove the duplicates or purge the target before retrying.
  • The Bitwarden option is missing from the wizard. Update KeePassXC and reopen Database > Import.

What this procedure does not protect you from

A plaintext .json or .csv export puts every password on disk, unencrypted, for as long as the file exists. Anyone who copies that file reads your vault. The encrypted option reduces that risk, and the export password is then the only barrier.

A compromised computer defeats the whole procedure. Malware on the export machine can capture the master password and the export password while you type them.

The verification steps check what you test. They do not prove that KeePassXC maps every item type correctly, because its documentation does not list the mapping.

Do not follow this as written if you use Bitwarden organization items and lack export rights. Ask an admin to export them first. Do not delete anything from Bitwarden until the target database opens with the password and key file you set, and you have stored both somewhere you control.

Where VaultKeepR fits

VaultKeepR is a password manager with no email required. Your vault is encrypted on your device before anything goes to IPFS. The core manager is free forever; Premium, from €2.49 a month, adds encrypted cloud backup, TOTP 2FA and Shamir recovery. If you are leaving Bitwarden for a product that holds no account for you, the Bitwarden migration guide covers that move. For the feature-by-feature view, see the KeePass alternative page.

Sources

FAQ

Does KeePassXC import a Bitwarden JSON file?
Yes. Open the Import Wizard from Database > Import, choose the Bitwarden option, and enter the export password only if the file is encrypted.

Direct link to this question

Does Bitwarden import a KeePass .kdbx file?
Yes. Bitwarden imports .kdbx with an optional key file, .xml, and .csv. It accepts .csv only when KeePassX or KeePassXC created the file.

Direct link to this question

Do passkeys survive a Bitwarden to KeePassXC import?
The sources checked do not say. Bitwarden's .json export includes stored passkeys, but KeePassXC's documentation does not describe how its Bitwarden importer handles them, so check each one before you delete the export.

Direct link to this question

Is the Bitwarden export file encrypted?
Only the .json (Encrypted) option is encrypted. Plain .json and .csv files are plaintext, and Bitwarden says to delete them right after use.

Direct link to this question

Can I move an organization vault to KeePass?
Not with an individual export. Only admins, owners, and some custom roles can export organization items, through the web app or the CLI.

Direct link to this question

Keep reading