This is for me a very important one, before deciding to host all my details with or in bitwarden.
I need to be sure that I am not vendor locked in. Especially with this important data.
I need a way out, for when bitwarden stops or …
Exporting to csv, and then importing loses a lot of the important data and structure which for me is more or less like being locked in.
I would propose to have an keepass xml 2 export possibility:
Keepass is open source, free, a standard, and also supports attachments.
I think this would make a lot of people reassure to have a fallback, just in case.
I presume since the importing module is already working, the keepass xml is an open standard, the export module should be reasonably easy to do.
Agreed: 2fa is then not backed up, but the most will be usable without to much effort.
But these could be text notes in keepass, so the key is at least available to use in a another app like authy.
I love the features of bitwarden. But as long as there is no external backup that is uasable, I am not moving my account data.
I’d also suggest to include attachments base64 encoded into the exported JSON file. This way at least the JSON file contains all the data of the user account. For most users the JSON file is a proprietary file format anyway, so it doesn’t really matter if it is usable anyway.
The exported base64 files should be imported as well if a user imports the JSON file again obviously.
I was shocked after exporting my vault for the first time today because i thought i was going to have a backup of my vault.
Exporting the attachments together with the JSON file can be very easy.
All logins already have their own id in the JSON file (“id”: “01234-56789”,) so you can create an Attachment directory and put all attachments in the directory with a name like
Zip the directory+JSON file for download and we can make backups ourself.
Next step would be importing that zip file the other way around and somehow encrypt the backup but that’s for later. I think so many users first would like to have a possibility to make a consistent backup.
@kspearrin, Kyle can you please let us know whether this is doable and on the roadmap (short term)?
Thanks a lot!
This is also something that I would really like to have.
I think that a single ZIP file with a JSON file + directory structure of the JSON ID that @Marvin_S suggested would be perfect. I also wouldn’t mind the BASE64 encoded single JSON file option either, but it’s somewhat less accessible for the attachments than the ZIP with directory structure option.
Restrict this to admins only being allowed to backup organisations, but users still having permissions for their own vaults.
Optional encryption would certainly be an added bonus.
Yes, this is huge for those of us who use attachments. I think what makes sense is the following method:
Assign each attachment a UUID, export it to an attachments directory with just the UUID filename. This gets around any issues of filenames being invalid for different filesystems. If you wanted it to be friendlier you could use the ID of the item and append an index and keep the extension. [item-id]-[attachment-index].[attachment-extension]
In each item object have an “attachments” key which is a dictionary of UUID:OriginalFilename.
Currently Bitwarden export is only exporting usernames, passwords, TOTPs, folders and so on
but if you have attached a file to an entry it will not be exported while it would be essentials (e.g. PGP key).
@kspearrin Any update on this? I’m a new Bitwarden Premium user and spent today uploading all of my important documents to my vault, and was absolutely shocked and devastated to read that they wouldn’t be included in my backup exports. This means, for me at least, Bitwarden sadly isn’t a viable place for secure file storage, since if something happens to my account all of my important files are gone! This is especially frustrating since I purchased Premium predominately for the secure attachment storage!
1Password allow attachments to be exported as part of a whole vault export, and in a range of formats too. Even a proprietary format for exporting the whole Bitwarden vault would be better than nothing at all!
Bitwarden is great and 1GB storage is quite generous compared with the other password managers.
However, we now live in an age where cloud security is a growing concern.
So yes please - could we have on the shopping list:
Ability to upload/download multiple files for attachment.
It’s now JSON. Base64 encoding would work. This is a really annoying thing to miss. I really thought I had a full backup of my stuff until I saw the JSON is unexpectedly small given the attachments I’ve stored in BW. I use this to sync between two different BW accounts (paid one here, and my privately hosted one). Only it’s not really syncing, if the attachments are missing. These are scans of identity documents, private keys for PGP.
I understand this may be an issue for people who have huge amounts of attachments due to the size of the resulting JSON, but simply omitting them is not a solution. If that’s the concern, make it optional or filter by size or something.