Looks like Bitwarden doesn’t support the import file from Password Depot.
You will have to manually condition a CSV file and enter all the data. Just copy and paste the entries in the CSV file. Maybe you can just change the field name and make it identical to the Bitwarden CSV file.
Looked into the CSV-file from Password Depot. And it misses the userdefined fields
Bitwarden can import fields via CSV. But now I would have to use XML-export with all necessary information and somehow morph this to csv.
Oh man. This will be hard one. So many entries to move. And 4 users.
Have to put more effort into the test of Bitwarden. I´m not sure if I really want to switch from Password Depot. But there are a couple of problems with it so I want to switch
That would seem to be a Password Depot limitation. Have you asked in whatever support is available for it?
The usual approach is to read the exported data into a spreadsheet, adapt it and then read it into the new software. If fields are not exported than the only way to get that data into any other software is to cut and paste it manually.
I have the same issue. Since Bitwarden is still not supporting Password Depot as an import source, I wrote a conversion tool, that can be run locally in your browser (just local HTML and Javascript). This was necessary, since the Password Depot XML export structure must be completely converted to fit Bitwarden JSON import structure. Simply renaming the fields would not suffice.
If anyone would like to use that script, just let me know. It’s written for Password Depot 10, but should work for newer versions as well if adjusted a bit.
Input is a Password Depot XML export, output is a conditioned Bitwarden JSON file.
Do you have the code published in an open-source repository (e.g., Github or Sourceforge)? This may help users to trust your tool, by allowing third parties to review the published code.
@dig I personally haven’t seen many requests for adding support for Password Depot.
The biggest issue I have usually ran into, when wanted to develop importers/add support for them, was getting access to example data or better the product targeting to support itself.
Bitwarden does have support for parsing xml files from some vendors. It’s largely a mapping effort, which you seemed to have solved. I’d be intrigued to see your solution. It might have potential with some little adjustments to be included as a dedicated importer within Bitwarden. Making it easier for anyone else looking to migrate in the future.
With being open source we’d obviously also appreciate any contributions. I’ll make sure my team has time to review any kind of contributions.
Please feel free to @ me when you have added the link.
I’m almost done. I’m just struggling a little bit with the resulting structure for converting hierarchical folders into Bitwarden collections. If you have any suggestions or ideas for this, please reply here:
Sorry for the long pause in communication. I was sick at first and then on vacation.
I’m planning to release it in a fully functionable but stand-alone JS version on Github until the end of May. I’ll let you know here when as soon as it’s available.
As already mentioned in our exchange, thanks a lot for keeping us in the loop. Looking forward to your work!
In the meantime I have started with a dedicated in-product importer and have opened:
Over the next couple of days, I’ll be adding support for the different item types other than passwords and doing some reverse-engineering for some of the values missing.
