Overview
The NPSP Donor Household Deduplication Engine is a Salesforce accelerator for nonprofit organizations using Nonprofit Success Pack. It automates the cleanup of duplicate household accounts created when spouses or related donors exist in separate households.
Business Problem
Nonprofits frequently receive gifts, event registrations, imports, and legacy records that create separate household accounts for people who should be managed as one household. Manual merging is time-consuming and risky because donations, pledges, recurring donations, tasks, and contact relationships must be preserved. For development teams, duplicate households reduce the accuracy of donor history, segmentation, acknowledgment, and relationship reporting.
How It Works
The accelerator uses a record-triggered Flow and Batch Apex to evaluate spouse relationship records. When a current spouse relationship is created between two contacts with the same last name, the automation can merge the separate household accounts. The process retains the oldest household account and reparents related records, including contacts, pledges, donations, recurring donations, and tasks, to the surviving household. The batch framework allows the process to handle data changes at scale instead of relying only on one-off manual merges.
Where This Fits
This accelerator fits faith-based nonprofits and other nonprofit organizations using Salesforce NPSP for donor and household management. The same pattern can be adapted for organizations importing data from legacy fundraising systems or dealing with recurring household duplication caused by spouse relationships, event registrations, or separate giving histories. For reuse, the implementation should start by confirming the object model, required fields, record types, status values, ownership rules, and security model in the target Salesforce org. The existing pattern can then be adjusted for naming, page layout placement, validation rules, reporting needs, and integration points. Sample records should be used to test the automation path, exception handling, and user-facing screens before rollout. This keeps the accelerator grounded in the original delivered pattern while allowing the details to fit the new organization and its operating process fully.