CSV Import from Msecure has issues with many credit card records and some notes

Which Bitwarden app is your issue or question about?

3 - Desktop App

Operating System

03 - Windows

Where is your vault hosted?

Bitwarden (default)

Attach a screenshot

Description

Hi - I am trying to import msecure data into bitwarden. I have tried to use the import tool and I select msecure but I keep getting the following error.
Cannot read properties of undefined (reading ‘trim’). See attached screenshot

I have tried limiting the import to just a few records or even 1 record and it seems many of the issues are credit cards but not all the time. Some work others don’t. I also had 1 really long note fail but other records import. But some of the credit cards that do not work are small. Not a lot of data/notes with the record.

I have tried using the read file and just copy/paste and it gives the same result.

My doing it the copy and paste way, I can copy a bunch of records and it works. Then I grab another bunch and get the error and have to figure out which record is doing it by just importing 1 record at a time. Then I add the record manually. I then grab a bunch and it works until I get another one that gives the same error.

I really cannot tell what is wrong with some of the records that experience this. Has anyone else encountered this?

I was able to import using a python script that I found in one of the other bitwarden community support discussions concerning msecure.

At first I was hesitant to do this as I have never used python before but the instructions on the linked page and using AI to figure out why certain commands were not working ended up in it working.

The python script read the file in without issue and created the json I was able to use to import in bitwarden.

I think the msecure import should be updated or maybe make the python script a standard to use as it was amazing to use and solved all the import issues I was experiencing.

@allanweinman Welcome to the forum!

Great that you succeeded in the end – and share it here with us!

If you find the time, you could file a short bug report about this on GitHub (“New issue”). Maybe @djsmith85 also sees your post and can pick it up.