Local first · Preview

Move a copy. Verify before switching.

Vault currently imports supported encrypted KDBX files. Direct browser-password access and direct CSV import are not implemented. Test the process with invented entries first; do not abandon the old vault until you verify every important field.

From an existing KeePass file

On a copy, use KeePassXC to choose KDBX4, Argon2id within Vault’s documented limits, password-only unlock and no database compression. KeePassXC’s database settings expose the compression option. Save the copy, then choose Import encrypted .kdbx in Vault and unlock it. The limit is 8 MB, with bounded entries, groups and fields. Keep the original database intact.

Custom KeePass fields may be preserved without appearing in Vault’s editor. Specialized cards, passkeys, attachments and other app-specific data do not automatically become supported Vault features. Inspect the result in both clients. KeePassXC import and database-settings guide.

From Chrome, 1Password, Bitwarden or LastPass

Export only on a trusted computer using the provider’s own instructions below. CSV exports are plaintext and can omit fields. Import the CSV locally into KeePassXC, map title/username/password/URL/notes carefully, then save a compatible encrypted KDBX copy for Vault. Do not use an online converter or email the CSV. Remove temporary plaintext exports after verifying the migration; backups, sync folders and disk snapshots may retain copies.

Chrome / Google Password Manager export guidance: use Password Manager settings for passwords; general Chrome exports are different.
1Password export guidance: CSV exports only a subset of data. Keep a separate original-format backup for fields/passkeys that do not migrate.
Bitwarden export guidance: plaintext CSV and encrypted exports are different formats. Vault does not import Bitwarden encrypted JSON.
LastPass generic CSV export help: use the official export flow; an encrypted LastPass export is not a KDBX file.

Compare entry counts and representative long/Unicode passwords, URLs and multiline notes. Re-enroll passkeys separately with a supported provider. If any field is missing or the conversion is unclear, keep using the original vault and stop the migration.