Ghost Duplicates

Key Takeaways

• Salesforce duplicate rules only flag new or updated contacts
• Duplicate Record Items report doesn’t auto‑populate existing duplicates
• Merged contacts remain in Duplicate Record Set as “ghost” duplicates
• Manual deletion required, increasing admin workload
• Current duplicate management considered incomplete by many admins

Pulse Analysis

Salesforce offers powerful matching and duplicate rules, but the system’s real‑time detection hinges on the Potentially Duplicates component embedded in Lightning pages. This component alerts users only when a record is newly created or modified, leaving historic data untouched. While admins can craft a custom report type that includes the Duplicate Record Items related list—typically on the Contact object—the report itself is a static snapshot that never pulls in pre‑existing duplicate pairs. Consequently, organizations cannot rely on standard reporting to surface legacy data quality issues.

The gap becomes most evident after a Contact Merge. Although the merge consolidates fields and relationships, the underlying duplicate record remains listed in the Duplicate Record Set, a phenomenon dubbed “ghost” duplicates. These phantom entries persist until an admin manually deletes them, adding unnecessary friction to routine data stewardship. For teams that depend on clean contact databases for marketing automation, sales outreach, and analytics, such hidden duplicates can skew metrics, inflate audience counts, and trigger compliance concerns. The inability to trigger a bulk detection process further compounds the problem, forcing administrators to resort to third‑party tools or custom Apex scripts.

From a strategic perspective, the current state signals a half‑hearted commitment to duplicate management within Salesforce’s roadmap. Companies seeking robust data governance must either allocate internal resources to build custom solutions or evaluate complementary platforms that offer automated de‑duplication and ghost‑record cleanup. Until Salesforce enhances its native capabilities—perhaps by auto‑populating the Duplicate Record Items report and purging merged records—the onus will remain on admins to maintain data integrity, a cost that can erode the platform’s promised ROI.