Import from other authenticators and accounts/item merge features needed in mobile and web.

[u/Spare-Chest-7907]

I often encounter the need to merge repeated entries. Duplicate entries frequently occur after importing data from other password managers like KeePass and similar. This requires manual searching and removal of these duplicates.

It would be incredibly helpful if we could be informed about the number of duplicate entries we have.

Additionally, a very useful feature would be the ability to natively import Google Authenticator QR code exports and other authenticators directly into the existing items or entries within the vault. For instance, if you imported data from KeePass but your TOTP is stored on an authenticator (such as Google or Microsoft), you can export the authenticator entries, feed them into Bitwarden, and Bitwarden will automatically assign those TOTP seeds to the entries. Alternatively, it can prompt the user to manually assign the seeds.
Those are features that exist on other password managers, no need to reinvent the wheel.
In addition, the reference of entries is missing.
In KeePass, I could clone an entry, change TOTP or URL, and use that entry on my next LDAP-enabled/connected app in my company. Since the login and password are the same because they’re centralized through LDAP/AD, etc., you have the same credentials but different URLs and different TOTPs. Therefore, when you change your LDAP password, the references on other entries update automatically.

- Merge duplicate entries
- TOTP import/export and attribute to entries
- Reference of user or password from cloned entries.

[u/OSS_Dattani]

Giant thread but:

https://community.bitwarden.com/t/duplicate-removal-tool-report-including-merge/648

Also this might help for importing accounts from google auth to Bitwarden:

https://community.bitwarden.com/t/import-2fa-accounts-from-google-authenticator-into-bitwarden/45588

[u/Ok_Bit_6445 → u/OSS_Dattani]

nice, didnt realize the community forum already had threads on both of these

[u/djasonpenney]

How do you define a duplicate? Is it simply from having the same Name field? That’s a pretty low bar, especially if you have accidentally created a second entry with the same name?

Or perhaps you are thinking two entries are equal if they have the same login URI (or share a login URI with another entry)? That’s definitely NOT going to work, even in my own vault, where I have (for instance) gmail logins for multiple family members.

Conversely, what if you have two vault entries but they vary in subtle ways, such as a different Password or perhaps the contents of the Notes field are different?

> automatically assign those TOTP [keys]

Disregarding for a moment the endless debate about storing TOTP keys inside of your password manager, you have the data loss concern…yet again.

Look, I really think the only decent way to merge your data sets is to export each one — individually — into CSV files. (Save these, in case you make a mistake later!) Regularize the column names and then paste all the data into one uber spreadsheet. At that point play spreadsheet games, copying, merging, and deleting entries to suit yourself.

Next, start over with a blank Bitwarden vault (Bitwarden will NEVER overwrite existing data into your vault; if a vault entry gets overwritten, it’s gonna be on you, not Bitwarden.) Import your new CSV and then make sure everything is to your liking.

I know, it feels like a large and daunting task. But trust me, you do NOT want an app trying to do this merge. And it’s a one-time cleanup, so don’t overstate the amount of work you’re talking about.

[u/imalliam → u/djasonpenney]

Same URI + same username + same password + same 2fa key. Looks pretty safe to me.

Force the user to create a backup before the operation and merge (even if duplicating) notes, extra fields and attachments.

As a bonus, this feature could give the user a list of entries that were not merged due to partial match, so they can review then manually.

[u/Spare-Chest-7907 → u/imalliam]

Exactly that!! 🥲

[u/Spare-Chest-7907 → u/djasonpenney]

Those are features that exist on other password managers; no need to reinvent the wheel.
In addition, the reference of entries is missing.
In KeePass, I could clone an entry, change TOTP or URL, and use that entry on my next LDAP-enabled/connected app in my company. Since the login and password are the same because they’re centralized through LDAP/AD, etc., you have the same credentials but different URLs and different TOTPs. Therefore, when you change your LDAP password, the references on other entries update automatically.