Source references: KDBX specification and KeePassXC user guide. No UnumVault KDBX importer is implemented.
Reference documentation reviewed 16 October 2026.
Keep the native database intact.
- Keep a backup of your existing encrypted KDBX database.
- Retain its master passphrase and any required key file or other unlocking factors.
- Wait for the tested UnumVault compatibility guide before choosing a migration route.
- Avoid converting to CSV merely to prepare for UnumVault; that can discard information.
What we’re validating.
- Evaluate groups, credentials, custom attributes, attachments, and history against the development vault engine.
- Publish supported KDBX versions and unlock methods before advertising compatibility.
- Use an explicit field and file report for anything the UnumVault interface cannot represent.
Know what needs extra care.
- KDBX4 local storage is implemented, but importing arbitrary KeePass databases is not yet verified or advertised as supported.
- KeePassXC’s CSV export omits attachments, advanced attributes, Auto-Type settings, and custom icons.
- KeePassXC’s XML export also omits attachments. A generic export is not equivalent to the native database.
Finish the move with confidence.
Our release workflow will ask you to review the report, verify representative credentials and authenticator settings, and create an encrypted backup. Keep your source manager available until all unresolved items have a migration action.
Remove plaintext exports when you’re done and check for extra copies in Downloads, Trash, backups, or synced folders. Deleting a file does not guarantee secure erasure.