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

I think duplicates issue is the biggest tragedy of 1password8. If user has 1password on two devices, there will be prompt on both and it will migrate vault twice.
Can imagine high segment of 1password users who have multiple devices and gotten into this problem.

So what happens when you write email to support+tradein@1Password.com as suggested above ? Do they give you special spell, hidden key combination to remove duplicates?

Yes, this lack of function is unfortunate!
If you have decent password hygiene, you might be able to find the duplicates easier in the Watchtower->Duplicate Passwords view.

Several of the people here are in this situation due to some issue occurring on migration from 1Password 7 to 1Password 8. This issue on its own is a failure of a critical part of the migration function and seems unaddressed in the thread. The system quite simply be checking much better than it does to avoid that fate and recover from it.

The fact that manual duplicate clean up is the solution on a database that for many can approach 1k or greater is simply not good enough. If migration issues occur the duplicate search should really be moved up your priority queue.

Lastly I ended up just deleting everything from the account online and then re-importing. This would be my suggestion to anyone who identifies this problem before using the new data base too much.

This issue alone mostly just got me thinking again about bailing on the product all together. After all it's simply database app at it's core function and if it can't be trusted w that what's the use?

In general the migration process didn't feel well designed to me. For example why would the system not remind the user to go ahead and detach the other vault? This upgrade process is not good, keep working on that or just expect additional users in here over time complaining about that (well the one's that bother to give feedback).
...
For example presently on iOS I have 2 Vaults in iOS 7. This is how the UI is confusing

All Vaults Screen
1. "Vault for Saving" was still set to iCloud... Not updated to save to the online account... So right there if I didn't change that I would have the issue of saving newly created passwords to a vault I am migrating off of.

1. The old vault was still "On" so of course you end up w a confusing set of duplicates that way too

2. The naming structure is just confusing to someone not working for the company.

"Vaults included in all vaults"
You have
[FirstName LastName] ON
Personal ON

On iCloud
Primary ON

Let me ask you do you think that the average non technical user can tell you quickly which vault is which w this kind of naming structure? Or that one is their old vault from 7 vs where they are trying to migrate too?

In short your UI and migration does the user very little favors to be honest to the point its borderline user hostile. What % of users hose their migration 10-20%?
...
Another issue you have a promotional upsell function where users can get a discounted price - that's fine... But does this disappear after you pay and sign in with an account - no it doesn't. So is there no QA validation of something as simple as 'if user has paid account stop displaying the promotional notice'... Guess not? Seems like a simple nuance but it's not accounted for.

Hi @elxris, I'm sorry to learn of your experience with this. We do appreciate having your feedback on the migration process.

Since it sounds like you still have a lot of those duplicates at the moment, I invite you to send a brief email to support@1Password.com, with a link to your post here. That way our support team can quickly catch up with your current situation and help you (literally) sort it out. And again, my apologies for the inconvenience you've experienced so far. We'd love to help set it right.

I migrated from v7 from Apple Store, to v8 from your website, and I also find this duplicate issue very annoying. I feel like the culprit here is the migration tool. I feel like it imported some old iCloud backup, that I no longer use since I am on subscription. I have hundreds of duplicates now. Dumb tool.

Also, while trying to delete duplicates, if you press delete key and then down arrow to select the next one the selection goes to the first element of the list and I need to scroll all the way back to where I was. Very annoying as I need to use keyboard + mouse to properly delete the duplicates.

This version is no longer convenient to use as I never know which one of the credentials I must use.

While I understand this is a new codebase, I feel like the migration processes are less polished and we are featureless. I am sorry to say I feel disappointed. I remember being here and proud with 1Password since 2015.

Thanks! I look forward to it, though I've only ever had duplicate problems in this upgrade. A feature I'd prioritize over that is the ability to have "local vaults" (for security requirements of clients) made by the per-vault option to sync or not to sync.

@ronread, I'm sorry to learn you encountered that duplicate issue. If there's anything further we can do to help with your specific case, let me know and I'll be happy to do what I can.

Meanwhile, we do have a request for a Duplicate Detective 🕵️‍♂️ feature (I'm lobbying hard for that terminology, as a fan of alliteration), and are collecting customer votes for it to get a sense of the demand. I can really see why it'd be useful in your case and am happy to add a vote on your behalf.

To your question:

So back to the original point: Is the loss of finding dups due to the switch to Electron?

No, to my knowledge Electron didn't have anything to do with this. One of the big challenges of creating 1Password 8 is that it's an entirely new app - a true generational shift - and not an iteration built upon 1Password 7. So that meant "coding from the ground up", as it were.

There are a lot of great things about that (the memory security that Rust offers, much faster ability to roll out bug fixes consistently cross-platform, Universal Autofill, etc). But we do have some features that were in some versions of 1Password 7 (which wasn't nearly as consistent from OS to OS - Windows never had a duplicate removal feature) that aren't in the current release. This is certainly one I'd like you to be able to use, and I'll advocate for it on your behalf.

ref: IDEA-I-615

note: edited for atrocious grammar

Hi @CFS, I'm sorry to hear of this experience. Our Mac specialist team would be happy to help with this - please send us a brief message at support@1Password.com, with a link to your post (so that we know it's you, and you don't have to tell the whole story again), and we'll get you some customized help.

I also miss the previous 'find duplicate' tool in V7. After finally upgrading after figuring out I had to first import my standalone vault syncing with dropbox (AB: you need to make this requirement MORE prominent on your website!), I had several dups, sometimes 3 copies for each item. Funny thing was, some of the dups did not have the attachments that were included in the item. I finally manually cleaned out dups (down to around 700 items), and in some cases had to reattach files that landed in the "Salvage" vault. I think I've got things under control, but the upgrade was not smooth. So back to the original point: Is the loss of finding dups due to the switch to Electron?

I recently updated to 1Password for Mac 8, and also have a "duplicates" issue. But they're not really duplicates. My Personal vault of 500-600 entries (I forget which) suddenly ballooned to over 1,000 entries, because most (not all) of the entries now show up as pairs. There is the current version, and then an entry which is some archived version that somehow made its way back into the vault. In many cases it's easy to tell which is which, but there are lots where it is almost impossible, without testing each entry to find out whether it's current or not, and then re-archiving the invalid entry. This will be, to put it mildly, a huge PITA -- and needless to say, a job I shouldn't have to be doing. Any suggestions for how to fix this problem? After a similar disaster I had with a recent updating of 1Password for Windows, where every entry went blank (thankfully, this was finally fixed), I don't have a lot of confidence that 1Password updates are fully tested before they are released.