In Salesforce orgs using Person Accounts (especially in Nonprofit Cloud), contact information such as email, phone, and address is stored in Contact Point objects (e.g., ContactPointEmail, ContactPointPhone, ContactPointAddress).
When Person Accounts are merged, Salesforce does not support merging Contact Point objects. As a result, Contact Point records associated with the losing account become orphaned and lose their relationship with the surviving Person Account.
This creates a data integrity issue during Apsona Dedupe & Merge operations, where important contact information becomes disconnected from the constituent record.
Proposed Enhancement
Enhance Apsona’s Dedupe and Merge functionality to automatically identify Contact Point records associated with the losing Person Account and re-parent them to the surviving account after the merge.
Expected Outcome
*Prevent orphaned Contact Point records during merges
Priority / Justification
Important for customers using Person Accounts, particularly Nonprofit Cloud organizations, where Contact Point objects are widely used to store contact details.