Feature request – native deduplication & merge for credential items

Hello 1Password team,

TL;DR:

• Imports from browsers/other managers create lots of duplicate logins in 1Password.
• Cleaning them up now is manual, tedious, and risky (easy to delete or overwrite the “real” password or 2FA).
• 1Password should add a merge/dedup feature where users can select 2+ items and:
  • Default to the most recently updated record for conflicts.
  • Let users override at the field level (password, username, notes, 2FA, etc.).
• Optional “find possible duplicates” and an undo/archive mechanism would make it safe and powerful.
• No major password manager offers this today, so this is a chance for 1Password to differentiate and improve user experience.

---

I’m a 1Password user and rely on it as my primary password manager. After importing data from other systems, I’ve run into a recurring problem: duplicated credential records for the same account, often with slightly different fields and timestamps.

Right now, resolving this is manual and error-prone:

• I have to visually compare multiple entries for the same site/service.
• I’m forced to guess which record has the most current password, notes, or 2FA details.
• I then manually copy fields over, delete old items, and hope I didn’t miss anything.

This is exactly the kind of problem software should solve better than humans.

What I’m asking for

A native deduplication and merge feature that lets a user select two or more credential items and merge them into one, with:

1. Most recently updated record as the default source of truth
   • For any conflicting fields (e.g., password, username, notes), the system should default to the most recently updated item.
   • The user can override this per field before confirming the merge.
2. Field-level conflict resolution UI
   • Side-by-side comparison of the items.
   • Clear indication of which value is newer.
   • Simple controls to choose “keep this value” per field.
3. Safety + auditability
   • Option to archive original items for a period of time or keep an “undo” path.
   • Activity log entry noting that a merge occurred and which items were involved.
4. Bulk assistance (optional, but powerful)
   • A “Find possible duplicates” view based on domain/URL, username, and title similarity.
   • Let users step through suggested merges in a guided flow.

Why this matters (for users and for 1Password)

From a user’s perspective:

• Imports from browsers, legacy managers, and old vaults are normal. Duplicates are inevitable.
• The current manual cleanup is tedious and fragile, especially when 2FA secrets or secure notes are involved.
• Fear of losing the “real” password discourages cleanup, which leads to messy vaults and lower trust in the manager.

From 1Password’s perspective:

• A robust deduplication/merge feature directly improves data quality and user confidence in the product.
• It reduces support load from users who are confused about “which item is correct” after migrations or vault consolidations.
• To my knowledge, no major password manager offers a proper, user-controlled merge workflow like this; it’s an opportunity for 1Password to lead in a very practical, real-world scenario that almost every serious user hits at some point.

Summary

1Password already nails security and cross-platform usability. The next logical step—especially as more users consolidate from multiple tools—is helping them safely clean up and normalize their data. A first-class deduplication and merge workflow would solve a real pain point for me and, I suspect, a large portion of your power users.

I’d appreciate it if you could pass this request to your product team and let me know if something like this is on your roadmap.

Thanks.