KeePass KDBX Import to Passary
By Mihaly Kertesz · Updated
Passary imports supported KeePass KDBX files directly, without an intermediate plaintext CSV. The importer requires the source database’s credentials and converts its contents into a separate Passary vault. This conversion does not establish ongoing synchronization between the two formats.
KeePass import source databases
A saved source copy provides the starting point for import. Its normal opening procedure establishes the password and any required keyfile. Custom templates, attachments and older generations may still be needed if the destination does not reproduce their behavior.
Unsupported credentials or database versions can require a documented compatibility step in the original manager. Removing protection from the only working database would also remove a recovery fallback.
KeePass: database master key and keyfiles · KDBX backup requirements · Missing keyfile diagnosis
KeePass import credentials in Passary
Passary’s KeePass action selects the copied KDBX within an unlocked destination. It requests the source password and any required keyfile, with a folder-preservation option where offered. An encrypted pre-import backup preserves an existing destination.
The web importer decrypts KDBX through a local worker and maps the result into the destination. Source-database decryption and destination-vault unlock are separate operations with potentially different credentials.
- Copied source KDBX
- Source master password and required keyfile
- Available folder-preservation setting
- Import summary
- Saved destination and independent backup
KeePass import field mapping
URLs, usernames, passwords, notes, folders, custom fields and attachments are relevant to the mapped result. Database-specific triggers, plugins, auto-type sequences and templates do not necessarily have equivalent Passary behavior.
A preserved value does not establish preservation of its earlier application behavior. TOTP and URL matching need their own comparison. A protected source backup retains material that has not yet found a suitable destination.
| Sample | What to compare |
|---|---|
| Nested group | Folder placement and name |
| Login with several URLs | Each URL and matching behavior |
| Note with punctuation | Text and line breaks |
| Attachment/custom field | Presence, content and type |
| Special integration | Whether the destination offers a compatible workflow |
KeePass import practice databases
The password-only practice KDBX contains two invented logins in a group, a Unicode note, a custom field, password history and a small text attachment. A second database also requires the provided practice keyfile. Both use public fictional credentials and are intended for disposable destinations, not real account storage.
These KDBX 4 files were generated with kdbxweb 2.1.1 and AES-KDF. Their fixture settings are not recommendations for real vaults. Automated checks load the exact bytes through Passary’s bounded web importer and verify entries, history, note, custom field and attachment. The keyfile database returns no entries when its required file is absent or changed. This demonstrates parsing and decryption, rather than a completed KeePass desktop, browser or Windows UI workflow.
| Practice item | Expected value |
|---|---|
| Current login password | FICTIONAL_PASSWORD_CURRENT |
| Earlier password in history | FICTIONAL_PASSWORD_OLD |
| Group | Practice logins |
| Custom field | Practice label: Fictional value |
| Attachment | practice-note.txt — fictional practice text |
FICTIONAL-PRACTICE-ONLY-NOT-FOR-REAL-VAULTSPassword-only practice KDBX · Keyfile-required practice KDBX · Fictional 32-byte practice keyfile · Practice-file sizes and hashes
KeePass import failures
File selection, source credentials and the original manager’s ability to open the same copy help locate a failure. A corrupted-file error does not justify replacing the only backup, and an unchanged retry does not resolve a compatibility difference.
Application version, database format and a sanitized error can describe the problem. A fictional reproduction avoids disclosure of a real vault or keyfile.
KeePass import and later vault changes
A copied encrypted Passary backup provides a destination restore check. The protected source archive can remain as a fallback while one manager becomes the place for subsequent password changes. Independent edits in both formats cause divergence that an earlier import cannot reconcile.
KDBX import compatibility does not make Passary and KeePass share a live-file contract. Each format retains its own backup and transport procedure.
Different formats and file transport · Passary recovery policy