Hi, which file format should I use when importing CSV file from ESET Password Manager?
There is no direct option in Bitwarden to choose it..
@user141 Welcome to the forum!
To import an format that does not have a supported import tool, you need to create a conditioned CSV file, and then import it using the “Bitwarden (csv)” format.
If you need help with the conditioning process, you will need to provide information about the exported CSV file format. According to this post, the column headers (first row) present in the ESET export are as follows:
"modelType","modelVersion","title","url","username","password","notes","favorite","firstName","lastName","country","zip","city","street","street2","company","county","region","email","phoneNumber","text","color"
Is this accurate? The advice given below assumes that the above is an accurate representation of your CSV export.
To condition your CSV file, you need to first delete all rows except those that contain data for login accounts or notes — Bitwarden will not import other types of data from a CSV file.
Next, create a new column that has the column header type (all lowercase). For each row, fill this column with the value login or note (all lowercase), according to what type of data is stored in each row.
Delete the following columns:
modelTypemodelVersionfirstNamelastNamecountryzipcitystreetstreet2companycountyregionphoneNumbercolor
At this point, do you have any non-empty data in the columns email and text? If so, please explain what type of data is found there. If not, please delete those two columns, as well.
Next, create three new columns, with column headers folder, fields, and login_totp (all lowercase); leave these columns blank.
In the favorite column, set the value to 1 in each row of any item that is designated as a “favorite”, and set the value to 0 for all other rows.
Rename the column headers for the following headers (all headers should be all-lowercase):
- Change
urltologin_uri(note that the final character is a lowercasei, notl) - Change
usernametologin_username - Change
passwordtologin_password
Does the column that is named title contain descriptive names of each account (e.g., “Bank account”, “Bitwarden Community Forum”), or any other string that allows you to distinguish one account from another (e.g., usbank.com, community.bitwarden.com, etc.)? If so, please rename the title column to name; if not, please explain what type of data is contained in the title column (if any).
Don’t forget to save your changes.
I will provide further instructions after I have received your responses to the three questions I posed above.
Hello @grb
thanks for your reply, I appreciate it.
However I have found that method a bit difficult, but based on general instructions you provided I have managed it in Excel - importing CSV, copying/pasting appropriate data into Bitwarden’s schema, exporting it to CSV and voila - works ok.
As ESET Password Manager is discontinuing, it may be a good idea to have direct import for Bitwarden.
Generally, the main hurdle to getting an importer developed for Bitwarden is that Bitwarden does not have access to the format of the exported files from the source password manager (they are not going to purchase an ESET license for this purpose).
If you (or anybody else) can provide the needed information (e.g., a sample export file with a few rows of redacted data — with one data row for each vault item type), perhaps an importer tool can be developed.
Perhaps a “universal CSV importer”, where it shows the foreign column headers and lets me specify to which Bitwarden “column” each one belongs.
I am not sure, if column headers are always unmistakably. If they are not, the importer has to display credentials in plain text in order to get the associations right.
If the source CSV export contains more than just login credentials (e.g., secure notes, cards, identities, etc.), then importing becomes more complicated than simply mapping column headers.