Changed info for import results, Bitwarden behaves excatly the other way round
parent
9f089e7f8f
commit
e1b1272573
|
@ -5,8 +5,8 @@ The current importers let you only choose the format, not HOW the data is transl
|
||||||
|
|
||||||
## Different import results for Keepass and KeepassX
|
## Different import results for Keepass and KeepassX
|
||||||
Importing from Keepass or KeepassX gives complete different results, although they use the same Keepass 2.x kbdx database:
|
Importing from Keepass or KeepassX gives complete different results, although they use the same Keepass 2.x kbdx database:
|
||||||
* Keepass XML files are imported at the **Organization** level (owner of each entry) and translates the Keepass Groups into Bitwarden **Collections**.
|
* Keepass CSV files are imported at the **Organization** level (owner of each entry) and translates the Keepass Groups into Bitwarden **Collections**.
|
||||||
* KeepassX CSV files are imported at the **User** level (owner of each entry) and translates the Keepass Groups into Bitwarden **Folders** with as main folder the name of the Keepass database.
|
* Keepass XML files are imported at the **User** level (owner of each entry) and translates the Keepass Groups into Bitwarden **Folders** with as main folder the name of the Keepass database.
|
||||||
|
|
||||||
It is a lot of work in Bitwarden itself to change Collections to Folders or to transfer ownership of all the entries.
|
It is a lot of work in Bitwarden itself to change Collections to Folders or to transfer ownership of all the entries.
|
||||||
So depending on what you want, choose the appropriate method!
|
So depending on what you want, choose the appropriate method!
|
||||||
|
|
Loading…
Reference in New Issue