Skip to main content
Two paths reach the full vault: the export button in the app, and a separate command-line tool that connects straight to the database. Both write one CSV row per credential: name, url, user, password, comment and category. The command-line tool refuses to write the file when the row count does not match the store.

What ports as-is

  • One CSV export of the whole vault, current version of each credential
  • A separate command-line tool with direct database access
  • A passphrase check before any password gets decrypted
  • A row-count check that blocks an incomplete export file

What we build for you

  • Which fields the export must carry for your compliance needs
  • Where the exported file is stored once it is generated