I have a CSV file from bitwarden which i would like to import into my current keepassxc vault
it imports the entries from the CSV into my current vault
it asks me to create a new db with password/keyfile
change it so it imports my data into my currently opened vault
KeePassXC - 2.3.1
Operating system: Ubuntu Gnome 16.01
CPU architecture: x64
Kernel: 4.13.0-38-generic
Currently KXC supports merge (Database->Merge from KeePassXC database). So you can import to a new database, save it after acknowledging its contents, and then merging with your vault.
Having a separate step for CSV import instead of an import&merge aims towards a clear understanding of what actually is acquired. Yes, the burden is on the user, who has to verify and choose in case of same entries with different values before merging, but otherwise there is the possibility of overwriting what should remain the same.
We might want to add a drop-down selection to enable direct import to an open database. Default would be to create a new database.
Well, the best way would be ask user, where (which group) he want's to import to. If he select root - then there will be overwrite as he having some reason why he act like that. If want merge and check, lets make possible to select folder (or create new one) where all passwords will be imported.
Making merging, without possibility to control, where new data will be merged it's not good anyway.
And for me - new DB during importing is unexpected behaviour as well.
new DB during importing is unexpected behaviour
I agree with that, although I have gotten used to it now.
A drop-down selection to enable direct import to an open database would be useful for me too.
Most helpful comment
Well, the best way would be ask user, where (which group) he want's to import to. If he select root - then there will be overwrite as he having some reason why he act like that. If want merge and check, lets make possible to select folder (or create new one) where all passwords will be imported.
Making merging, without possibility to control, where new data will be merged it's not good anyway.
And for me - new DB during importing is unexpected behaviour as well.