Error importing .csv file from google password manager

Ask the Community Password Manager
,
1

Having trouble importing the .csv file created by google password manager. I have followed advice elsewhere on creating more columns, checking for incomplete data, etc, but I keep getting the error message “Cannot read properties of null (reading ‘null’)”. There are about 150 passwords in total in the file. Any suggestions please?

2

Others may have a few simpler tricks, but I can describe the bullet proof method,

Manually put one entry in Bitwarden that includes the fields you care about. Export it to a CSV. Then copy the data from the Google CSV into the Bitwarden export, placing the appropriate google data into the appropriate bitwarden column.

If you get errors, delete some of the data and try again until you narrow down which cell(s) are in error. Then, when done delete everything and redo the import using the lessons learned so that you end up with a clean import.

Then, create a final JSON export of your vault, put it and the google CSV onto a flash drive you store in a safe place to protect against data loss if you discover a few months down the road something that did not make it into your vault.

3

@BanyanBkk Welcome to the forum!

Does the exported .csv file contain five columns (titled name, url, username, password, note), and nothing else?

If so, leave the name column alone, and rename the other four column titles as follows:

  • Change url to login_uri (all lowercase, and ending with an i, not l)
  • Change username to login_username (all lowercase)
  • Change password to login_password (all lowercase)
  • Change note to notes (all lowercase)

Create 5 new columns, which should be empty, except for the following column titles in the first row (all lowercase):

  • folder
  • favorite
  • fields
  • reprompt
  • login_totp

Now add one more column, which should contain the title type (all lowercase) in the first row, and the word login (all lowercase) in every other non-empty row.

Save the .csv file, and import it into your Bitwarden vault, selecting “Bitwarden (.csv)” as the specified import file format.

4

Thanks for both suggestions. I think the first (from DenBesten) is too complicated for me. Tried to follow it but came unstuck multiple times! The second (from grb) I already tried (saw it in an earlier post) and it didn’t work for me - came back with the same error message. Is my only other option to manually fill in data for each website one by one?

5

@BanyanBkk, using either of those methods, are you able to import a single record? If so, can you import half the data and if that fails halve it again?

I am seeking firstly to find out whether you have a working process then secondly to find problematic records efficiently.

6

Can you please copy and paste the first row of the (original, unmodified) .csv export into a response here?

In my opinion, your best option is to help us figure out what is wrong with your .csv file or your conditioning method. To do so, please provide the information requested.

7

I followed the advice of Mulled7768 and it worked. Thanks to all of you for your inputs.

8

Would be helpful for future readers of this thread (who may be in a similar situation) if you could share what the cause of the error was.

9

Did it turn out that one vault entry would not import? And in that case, did the password or the notes field contain either an apostrophe, a double quote, a new-line or a comma?

1 Like
10

Sorry, but I don’t know why it didn’t work. I saved the first entry in my CSV file exported from Google pm to a new CSV file then imported that. I then saved the remaining 150+ entries into 2 separate CSV files and imported them. I didn’t make any additional changes to the entries but was able to import all 3 files.

1 Like
11

Pleased to hear you had success. Which of @DenBesten’s or @grb’s processes did you use please, just for reference?

I suspect that the reason it now worked was that writing the three new files serendipitously removed an extraneous character from the beginning or end of the original file.

12

They followed these instructions and it was resolved by simply splitting the file:

It could also be something simple like a momentary glitch, or perhaps a mistake in specifying the file format. I do suspect that if the OP was to attempt importing the original export file again (before splitting it), it may very well work this time (@BanyanBkk if you are thinking of attempting this to prove me wrong, I would suggest that you temporarily set up a new Bitwarden account for that purpose, or you may end up with duplicate entries in your vault; you can delete the second Bitwaden account after you have performed the test).