I am attempting to switch from Proton to Bitwarden. I am encountering an issue with the way that Proton stores usernames versus what Bitwarden imports.
Examining the json, it appears as if proton does export everything as a ‘username’ field which Bitwarden should be able to import. However, if I export CSV, Proton displays that it is maintaining most of the usernames in a field called ‘email’, and ‘username’ is present as a secondary field that is only used for a few of my login entries.
Does anyone have any advice on how to successfully import this?
To my knowledge, recent issues with importing from ProtonPass are caused by Proton now storing the username in a field named itemEmail (instead of the original version of their JSON export, which stored the username in a field that was simply named username). Bitwarden’s importer should be fixed to handle this change in an upcoming release.
If the above is the cause of your problem, then open the exported JSON in a text editor, and do a search-and-replace to change all instances of itemEmail to username , and then re-run the Bitwarden importer.
However, based on your description, it sounds like something else may be going on. Are you running an old version of ProtonPass (before they changed the fieldname from username to itemEmail)?
The itemEmail issue you mentioned does appear to be the cause of my problem. My other details are related to comparing the json versus csv export from Proton, which also align with what you’ve said.
I will attempt to rename the itemEmail field to username and see how it goes. Thanks for the advice!