Browse Tools Top 100
BCUP KDBX
File conversion

Convert BCUP to KDBX

Verified by Adam B.· reviewed by FE Editorial ·updated Aug 5, 2026
QUICK ANSWER
Is it possible to convert BCUP to KDBX?
Yes - BCUP converts to KDBX.

KeePassXC has no native Buttercup importer, so the reliable route is two steps. Use buttercup-to-keepass (or Buttercup's CSV export) to turn the vault into a .csv, then in KeePassXC create a database and use Database > Import > CSV file. Delete the intermediate CSV afterwards.

Also to KDBX: KDB

On this page

Tested on macOS, Windows & Linux
Last verified Sep 2026

More free converters

HEIC, PNG, WEBP, MP3 and more - every tool here is free.

Open the toolbox

Why convert BCUP to KDBX?

A .bcup is a Buttercup vault and .KDBX is the KeePass database format, so people convert when moving from Buttercup to the KeePass ecosystem. Because no tool reads .bcup directly into KeePass, CSV is the accepted bridge between the two.

How to convert BCUP to KDBX

buttercup-to-keepass + KeePassXC OPEN-SOURCE

Run npx buttercup-to-keepass -s vault.bcup -p <master> -t vault.csv -c, then in KeePassXC choose Database > Import > CSV file and map the columns into a new .kdbx.

Buttercup Desktop CSV + KeePassXC FREE

Export the vault to .csv from Buttercup's export menu, then import it via KeePassXC's Database > Import > CSV file wizard to build the .kdbx.

pass-import OPEN-SOURCE

The pass-import tool understands both the buttercup and keepassxc formats and can act as the intermediate converter on Linux/macOS.

About these formats

.BCUP Buttercup Vault File

A .bcup file is an encrypted password vault created by Buttercup, a free open-source password manager. It holds logins, notes, and other secrets protected by AES-256 encryption and a master…

Open .BCUP details →
.KDBX KeePass 2 Password Database

A KDBX file is an encrypted password database created by KeePass 2 or a compatible app such as KeePassXC. It stores logins, passwords, URLs, and notes locked behind a master password and…

Open .KDBX details →

Quality & what to watch

  • There is no one-click Buttercup-to-KeePass path; the CSV middle step means a plaintext file exists briefly and must be securely deleted.
  • Group hierarchy, attachments and custom fields may not survive the CSV bridge, so expect a flattened entry list to verify after import.
  • OTP/2FA secrets only transfer if you export them explicitly (e.g. the -o otp flag), and you must still map the CSV columns correctly in KeePassXC.

Frequently asked questions

Can KeePassXC open a .bcup file directly?
No. Native Buttercup import has been requested but not implemented, so you must go through CSV.
How do I import the CSV into KeePassXC?
Create or open a .kdbx database, then use Database > Import > CSV file and match each column to the correct KeePass field.
Will my 2FA codes come across?
Only if the CSV export includes OTP secrets (for example the -o otp option); otherwise they are lost.
Is the process reversible?
Buttercup can also import KeePass files, but note it cannot read .kdbx databases that use Argon2 key derivation.