Export (both CSV and HTML) is incomplete

[pmorch]

Overview

When I export to my database, I never get all the database info exported.

Steps to Reproduce

When I export to HTML:

• "History" (e.g. old passwords) don't get added.

In addition, when I export to CSV:

• "Additional Attributes" don't get added (Store/Read additional attributes as JSON when exporting/importing to CSV #854)

Is there any way to export all information?

Is there a canonical/official list somewhere of what information is missing from what formats?

If not, please note any additional missing information from the two formats in comments, so we can crowdsource a complete list of missing information in the two export formats.

Expected Behavior

I expect to be able to export all information from my database.

Actual Behavior

I loose information on export.

Context

KeePassXC - Version 2.6.6
Revision: 9c108b9
Operating System: Linux
Desktop Env: Gnome
Windowing System: X11

[droidmonkey]

Export is not meant to be a complete replica of your kdbx database. HTML export is meant for printing to store in a safe or similar as backup. CSV is a limited format and we export as much as we can except for the one issue you noted. Any more information is not going to be added to exports.

If you want your full database including history you need to use the cli tool to export the database XML: keepassxc-cli export

We still don't export attachments that way. The only way to get attachments is to save the files individually.

[pmorch]

It would still be great to have a list somewhere of what is missing from the different formats.

[pmorch]

Until exporting attachments arrive, would it be possible to at least list the attachments that should've been exported? While it is manageable to save a couple of attachments, it is error-prone and less manageable to go though hundreds of entries looking for attachments...

Also, is the wiki the right place for a table of missing data per export format? If I were to take a stab at creating such a wiki page, would that be considered for merging? So far as I understand it, this would be the contents:

Missing Data per export format	Export format
Additional Attributes	CSV
History	CSV, HTML
Attachments	CSV, HTML, XML

[droidmonkey]

Sure if you want to build a table we can plop that in a wiki page. Probably better to say what is included in each export method.

To clarify something, HTML export is not meant to transfer data. It is meant for printing or saving as a visualization.

Also remember, what is the purpose of exporting. If it is to transfer to a different system then that system needs to understand the export. Some password managers understand keepass xml but how much is actually imported into those managers is questionable.

[pmorch]

In order for me to list what is included, I'll need to know what is included :-)

Would this be accurate:

Suggestion

These fields are included in all the CSV, HTML and XML export formats: "Group","Title","Username","Password","URL","Notes","TOTP","Icon","Last Modified","Created"

The HTML export, which is only intended for human consumption, also contains "Additional Attributes".

The XML export (only accessible from the command line as keepassxc-cli export - see #8496), also contains "Additional Attributes" and "History".

None of the export formats include attachments. The only way to get attachments is to save the files individually.

[droidmonkey]

for CSV the Icon is the standard icon id (number), not the actual icon data and not custom icons. XML exports everything, including Custom Data, except for attachments. XML also does not export the database credentials or anything in the header of the kdbx file like KDF used and unencrypted file data.

[pmorch]

I've created pmorch/keepassxc-wiki@d62421f introducing Export.md to a fork of the wiki. I don't think it is possible to create a pull-request for a wiki page on github (which was kinda surprising to me).

[pc-erin]

This really needs a clear warning in the import/export utility. Most people would assume that exporting and re-importing does what it sounds like: exports and imports the entire contents of the database. The only reason I didn't lose a bunch of ssh key files was because I noticed the cryptic "Unmapped keys left." message and looked it up before replacing my old database. This is a frankly insane thing for a supposedly durable data store to do.

Having learned so many of the caveats of this program in recent days while attempting to sync passwords with my coworkers has led me to completely distrust it, despite using it for years beforehand.

For anyone else finding this, wondering where their passwords/files went: There is no form of export/import that preserves all data from your database. The kdbx format is the only one that keeps the entire contents. If you delete an entry, then load it again via keeshare import, it will be deleted as soon as it's loaded. This is an intended feature to support database merging. There is no warning that this happens. The only way to prevent this is to export as XML, delete all the DeletedObject nodes, then re-import, which will not preserve any of your file attachments.

I understand this is open-source software, provided free of charge and without warranty, but it's incredibly misleading to present this as a durable password store without any warning that your extremely important data may be automatically deleted if you use the program in seemingly intended and conventional ways.