bitwarden/importer

Bitwarden standalone importer tool.

---

Bitwarden Client Applications

This repository houses all Bitwarden client applications except the Mobile application.

Please refer to the Clients section of the Contributing Documentation for build instructions, recommended tooling, code style tips, and lots of other great information to get you started.

Related projects:

• bitwarden/server: The core infrastructure backend (API, database, Docker, etc).
• bitwarden/mobile: The mobile app vault (iOS and Android).
• bitwarden/directory-connector: A tool for syncing a directory (AD, LDAP, Azure, G Suite, Okta) to an organization.

We're Hiring!

Interested in contributing in a big way? Consider joining our team! We're hiring for many positions. Please take a look at our Careers page to see what opportunities are currently open as well as what it's like to work at Bitwarden.

Contribute

Code contributions are welcome! Please commit any pull requests against the main branch. Learn more about how to contribute by reading the Contributing Guidelines. Check out the Contributing Documentation for how to get started with your first contribution.

Security audits and feedback are welcome. Please open an issue or email us privately if the report is sensitive in nature. You can read our security policy in the SECURITY.md file.

importer's Issues

Importer throwing BW Vault logon error

Bitwarden Importer is not working for me while trying to import from LastPass. It seems to logon to the BW Vault, because I immediately get a logon message in my e-mail. But the importer shows this error. (Screenshots below)

If I get an e-mail notification, does not that mean that my password was actually correct, and that BW was in fact able to logon? I have triple checked my password, it is surely correct. I have also disabled 2FA inside both BW and LP.

Please advise on how to proceed.

Issue with special character `$` while importing from LastPass

Having imported one-time from LastPass, I have observed that whenever there is a $ symbol in the password, Bitwarden imports it as double dollar symbol $$.

e.g.
Original password in Lastpass: abx3$%
Imported password in Bitwarden: abx3$$%

LastPass favorites selection is lost

The "Favorites" settings per item is not brought over by this tool for LastPass. This should be fixed when the following PR is merged from the upstream library used for this project: detunized/password-manager-access#86

LastPass service only imports password types

Currently only password/logins/websites types are supported in LastPass. Credit cards, addresses, secure notes, and others are skipped. This should be fixed when the following PR is merged from the upstream library used for this project: detunized/password-manager-access#86

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• Update nuget minor (PasswordManagerAccess, ServiceStack.Text, dotnet-sdk)

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• Update dependency PasswordManagerAccess to v14
• Update dependency ServiceStack.Text to v8
• Update dotnet monorepo to v8 (major) (Microsoft.Extensions.Logging.Debug, dotnet-sdk)

Detected dependencies

github-actions

.github/workflows/enforce-labels.yml

• ubuntu 22.04

.github/workflows/workflow-linter.yml

nuget

global.json

• dotnet-sdk 7.0.401

src/Importer/Importer.csproj

• ServiceStack.Text 6.7.0
• PasswordManagerAccess 12.0.0
• Microsoft.Extensions.Logging.Debug 7.0.0

---

• Check this box to trigger a request for Renovate to run again on this repository

Warning or errors must be reported for incomplete or corrupt data (e.g., LastPass Attachments)

In the case that a source Vault, such as LastPass, has records or fields that are not handled by the importer, errors and warnings need to be provided to the user indicating what information will be lost, inaccurately, or incompletely represented in Bitwarden.

For example, if a LastPass account has attachments on records and the destination Bitwarden account does not support attachments, then the user must be notified about the presence of attachments that have not been imported.

The current user experience of a bulk export, bulk import, and notification of success implies that the operation completed and accounted for all data from the source system with no loss of user data. The user may presume from a simple success report that deletion of the source data can be performed since all data has been accounted for. However, the user will then be destroying the only copy of records that were in the source system but not transferred and not reported as such.

API key login still requires master password

I ran into another problem, that's already listet here: #6

While being lazy and trying to use the API-key as a login instead, the importer still required the master password, which in my case didn't work. In the end I had to remove the spaces in my master password to make it work.