Bitwarden Export and import to 1Password [Solved]

Outstanding, @TheMadCow .

You're welcome, and have a great weekend.

Enjoy 1Password!

Wacky. I was added as an admin to the company account (user was leaving) and I had all access. But the export thing. Mashing around I see that it's also an organizational account, too. So I click on the company organization. Presents the same. But from that I exported again and it worked. Odd. But huge huzzahs for the utilities. Imported (finally) like a charm. Thanks for the response.

@TheMadCow

I looked at the BitWarden GitHub site and didn't see any recent commits that would cause the issue (but I didn't look carefully, or deeply). No issues reported, nor commits that might have changed JSON / CSV exports.

Within the past 30 days, I've exported from BitWarden (on Windows) to add some code to the converter for another user, and know it works. I wonder if there is something with your data, or something about how you are exporting, that is creating the issue?

Doh, you're right. Appears to be borked on .json exports, too. The vault in question only has about 20 entries. This is what is showing:
{
"encrypted": false,
"folders": [],
"items": []
}

@TheMadCow

That JSON file only contains 56 bytes, and that doesn't seem like much data. You can look at the contents - it's a plain text file.

Does the export contain what you were expecting?

Not saying anything new.

@TheMadCow

Hey MadCow, sorry for your troubles. The bitwarden converter only accepts JSON, so let's ignore the CSV issues (and yes, the 0 byte export would be their issue).

If you enable verbose output in the converter using the -v option, do you see any results? And how about with the debug option -d. What happens then (this output will contain sensitive data).

This is the debug output for the .json file.