I have several logins that somehow have been duplicated in 1Password 8. This may have happened in different times when I've attempted to migrate my 1Password 7 data to my 1Password.com account. In any case, I have a load of duplicates in 1Password 8 and it would be very helpful if there were an efficient tool or feature to help me merge/dedupe these entries (and ideally test them to make sure that I'm preserving the correct credentials). Any thoughts/ideas for how to handle this situation? 1Password Version: 1Password for Mac 8.5.0 80500017, on BETA channel Extension Version: 2.1.4 OS Version: macOS 12.0.1 (21A559)

Hello everyone! 👋 With the release of the latest beta for Mac, Windows, and Linux you can now see a list of your duplicate items in the app. Choose “Items with duplicates” in your Watchtower dashboard to see or delete all of your duplicates. Make sure that you're running the latest beta to see the feature. As always, please let us know if you find the tool useful and if you have any suggestions for the team. 🙂 -Dave

My Duplicates occurred when I upgraded from V7 standalone on my least used machine to V8. I was already using V8 on two other Macs an iPhone and two iPads. That upgrade process was terrible. It wanted me to create a new 1Password membership (I already have a membership which there was no obvious way to connect to.). I ended up downloading V8 and installing it. It said I had to convert my V7 data to V8. It was not at all clear that I could have just skipped that step. Now I've got about 800 duplicates. The upgrade process needs to be more clear so duplicates are not created in the first place. We also need a duplicate finder/remover tool.

In an ideal world, nobody will duplicate data at import time, but actually it will happen. I will not discuss how it can happen or can be avoided, only that it will happen - proof is this thread and others. Duplicate items are not always user error. Switching to a decent password manager often means merging from multiple sources, then consolidating: import from previous password manager plus Chrome's plus Firefox's plus Safari's internal password managers. One does import once directly after account creation, then never again. You at Agilebits do it never again, so you don't see really any need for postprocessing aid. However, for a new user it's crucial, it's a barrier. With duplicate items I mean login items that contain the same userid+password combination. What I propose you can do about this: - give an overview how many items match above description, in a similar way Watchtower does this. Also create filters, so the user can see a list of only matching entries. - also give an overview how many items match with url+userid, but different password. These might represent current and obsolete entries of the same login. The category could be something like "unable to merge", "merge conflict" or "password mismatch". Also make a filter for these. - explain if duplicates are distributed over multiple vaults. If 2 vaults contain the same, because the user imported the same 2 times, the user should see this and the easy fix for the user is to just delete one of these vaults - make it clear over how many different vaults how many duplicated entries are distributed - add the opportunity to "merge" duplicate entries in one vault, in spirit similar to functions to merge different address entries in address books in other apps. Merge only items within the same vault. - this merging would be available from the context menu you get if you select multiple entries. Merging candidates are only taken from the entries the user selected. - This merging functionality could find login entries with same userid+password combination, then choose the oldest entry as "merged" entry. Then merge all URLs from the other entries to this entry, the same with any custom fields and sections with different values (don't add custom fields with same title+value multiple times). And merge the password history of course. Also skip merging for history entries with identical password+timestamp combinations. After merging, add the tag "merged " to the merged entry (so the user can find all processed entries and can check if all is ok). Then delete the items their content was merged into the merged item. It's an investment in getting new users. I bet the turnover rate from ex-Lastpass users would be higher if you had such a functionality. When I was new, I merged entries from Password Safe and Chrome. I almost gave up, because it was so tedious - after all, Chrome autofill wasn't that bad, and Password Safe for just a local vault also wasn't that bad for all non-browser login items. A month after the trial expired I gave it a second shot and decided to do the tedious work.

Tool for detecting and removing duplicates? [Available in 8.10.18]

ctphoto
Occasional Contributor
3 years ago
I hope there is some compensation for those of us who were penalized for upgrading to version 8? Time is money as they say and I have spent plenty of it going through all my duplicate and archived passwords that were "merged" into version 8. I am literally afraid to ever go to version 8 now.
ag_mike_d
1Password Team
3 years ago
Hi folks, I'm sorry we don't any any further news to share at this time regarding this feature, but I've added these new votes and comments for the teams review. Thanks for the feedback.
ctphoto
Occasional Contributor
3 years ago
Why does this not address this issue yet?

https://tidbits.com/watchlist/1password-8-7-3/
Former Member
3 years ago
@1Password, you should put this in the Watchtower. You cannot have two login with the same username.

As a new user, we need to import several password database into 1Password and we need a tool to check if there is duplicate.

Regards,
Martin Roy
Former Member
3 years ago
@1Password team, please aggressively move this up your queue... In today's day and age, this is a fairly "simple" ask / obvious, table-stakes type of function that really puts a significant damper on your paid user experience. I did a fair amount of research before deciding to move forward with 1Pw, and I am actually shocked that this isn't showing up as a significant downside in your online reviews and by media outlets... It's only a matter of time, and it's going to continue to significantly negatively affect ux until it's fixed. The fact that this has been deprioritized for 18 months is... disappointing, to say the least.
1P_Tommy
Moderator
3 years ago
👍 ✏️
mikesilva
Occasional Contributor
3 years ago
+1 on this issue for me.
1P_PeterG
Community Manager
3 years ago
Hi ctphoto, I don't have any updates to supply at the moment but can tell you that I'm happy to pass on your feedback - and have now done so. Thanks for letting us know this is a priority for you. 🙏
ctphoto
Occasional Contributor
3 years ago
Has this still not been fixed yet? Wasn't there any beta testing to discover the duplicate issue before it happened to us paying customers?
1P_PeterG
Community Manager
3 years ago
Hi @olivierP and @czyzczyz, I have added votes on the issue for each of you in turn. Thank you for taking the time to let us know why you find value in that feature and the specific circumstances you've run into. I'm passing it on to our development team now and appreciate your sharing this with us - and the thoughts on how a solution could be implemented.

ref: IDEA-I-615