I am trying to migrate my vault from LastPass to Bitwarden, but every import attempt fails with the error: “no elements in sequence.”
Here is what I have tried so far:
Exported my vault from the LastPass web vault using Advanced Options → Export → LastPass CSV.
Attempted to import the file through the Bitwarden Web Vault → Tools → Import Data → LastPass.
Attempted the import using the Bitwarden desktop app → File → Import → LastPass.
Tried the “Import directly from LastPass” option in the Bitwarden app by logging in with my LastPass credentials and authenticator code.
Opened the CSV file in a text editor to verify the header format. The header appears as: url,username,password,totp,extra,name,grouping,fav
Re-exported the vault from LastPass multiple times to ensure the file was fresh and unmodified.
Attempted imports with both the original export file and versions saved again as CSV.
In every case, the import fails with the same error message: “no elements in sequence.”
Because the error occurs both when importing the CSV and when using the direct LastPass import option, I suspect there may be a parsing issue with one of the entries in the vault.
Could you please advise on:
How to identify the specific entry causing the import failure, or
Whether there is a diagnostic or alternative import method that would allow the vault to be migrated successfully.
Lastpass is known to sometimes produce CSV files that do not adhere to standards for CSV formatting, or that are otherwise corrupt.
I would suggest trying to do the CSV export from the Lastpass browser extension, instead.
Also, instead of a text editor, I would recommend using a spreadsheet app (e.g., Microsoft Excel) to open the CSV file, and examine its contents. A few things to look for:
Do any items in the url column contain a value like http://sn ?
Does the fav column contain any non-blank entries that are not 0 or 1?
Do any rows seem to contain extra columns, or data that don’t line up with the other data in the file?
Are there any rows with obvious signs of data corruption?
If you are satisfied that your CSV export does not contain any problematic items, then you can try to use the step-by-step method that I’ve outlined in this comment to import your data. Warning: The linked instructions include steps for purging the vault contents prior to importing (to avoid creation of duplicate vault items) — if your Bitwarden vault contains any data that you don’t want to lose, you should take steps to download the vault contents before purging.
I changed only the “URL” header got changed to “login_uri” the error went away and was imported. But some of the URLs didn’t get imported. Everything else was imported.
If using the instructions linked above, then you should cut those rows from the original CSV file, and save them in a separate CSV file — these can be imported into Bitwarden as secure notes, but the data conditioning steps are slightly different than what I had described in the instructions for login items. If you would like to import the secure notes, please let me know.
If you are selecting the file format option “Bitwarden (csv)” when importing, then you need to follow the provided instructionsexactly, renaming all columns (except “name”), and adding the 3 required additional columns.
This is probably because you didn’t follow the instructions exactly as described.
Just for general information: there is a fix in the works for this issue (and if I understand it correctly, it gets triggered by card items in an to-be-imported vault):
Warning: The linked instructions include steps for purging the vault contents prior to importing (to avoid creation of duplicate vault items) — if your Bitwarden vault contains any data that you don’t want to lose, you should take steps to download the vault contents before purging.