Allow all custom fields in personal Vault to get exported to CSV as different columns

Feature name

  • Allow custom fields to be exported to CSV into different columns.

Feature function

  • What will this feature do differently?
    As of today the custom fields get exported in CSV into same column and so importing back is a problem for those additional custom fields.

  • What benefits will this feature bring?
    Allowing Export of custom fields as different columns will allow user to download in .csv the entire vault structure , then user can manually add more entries to the CSV and import them back. This will help Data migration as well. Json is not a very friendly approach for a NON programmer like myself.

1 Like

Hi Ravi,
this makes sense if all your items have the same custom fields.
But imagine having 200 items (that’s not very much), and every one of them has 1 unique custom field.
You end up with a CSV with over 200 columns.

1 Like

Has this feature been added yet? Honestly, we just spent a lot of time entering custom fields for a couple different users in a format that works for everyone. However, it doesn’t look like we can export those custom fields or find them in individual CSV columns. It also doesn’t appears we can create any password template.

This is all incredibly disappointing as it seems like this is basic 101 stuff - we need to be able to save username and logins for multiple sites under a single client. While we have the ability to create custom fields under a single client for additional logins, we can’t export them?

Is this still the case or am I missing something. We’re honestly just one more “surprise missing standard feature” away from switching to LastPass who has FTP templates, etc already built in.

Can someone confirm?

Could you please elaborate how you would want to see that implemented?

The more logic solution in my opinion is to use a more flexible output format for this (XML, JSON) which - to my understanding - is available.

Set 1: Legal website:

USER
PASSWORD

  • custom fields: INSURANCE NUMBER

Set 2: Medical website:

USER
PASSWORD

  • custom fields: Medical ID, Main doctor, Name surgeon, Name psychiatrist

Set 3: Secret friends club

USER

  • custom fields: secret handshake, totem, Swiss bank account

Thank you for your quick response. Unfortunately, we just canceled our Bitwarden account and switched to Keeper. They provide all the functionality that’s missing here (aka, custom password templates, FTP password templates ready to go, etc)

1 Like

Hey, no worries. I don’t work for Bitwarden (just a happy user).
Not sure if you made the best choice, but if those features are a priority, then it’s your better choice.

At a quick glance, I see that Keeper is not open source. It also doesn’t have a free tier (but that’s not as important). More importantly, I don’t seem to find any external security audits that have been performed on Keeper.

On their page about “Bitwarden vs Keeper” they suggest that they have SOC 2 and ISO 27001 certifications. Yet the page it links to, is merely their release notes. Can’t find any info on those certifications there. At the same time, you can find that Bitwarden is also certified, and you can even read all the security reports there. This gives me a bad taste in the mouth regarding Keeper.

I noticed that Keeper only allows export to the (rather limited) CSV format, but doesn’t even support JSON. I’m curious… how do they export custom fields? Could you tell us?

Anyway… I wish you all the best with Keeper. (I just checked… there is an option to import Keeper CSV-files into Bitwarden, were you ever to change your mind again)

@JurgenG Wow! You’ve really done your homework. Thanks for providing such great information!

Yes, I did my homework when we needed to pick a password management system for our organization (70+ employees). So it was a quick lookup now.

1 Like