I know that the recommended tool for merging contacts is the NPSP Contact Merge. And I'm excited for the updates that will make that play better with native Duplicate Management. But convenience of placing the native "Potential Duplicates" component on contact records is compelling, so I was reviewing *why* the native merge wasn't recommended.
I believe that in the past, using the native merge could leave Opportunities on the empty household record (if the Contact with the Opportunities wasn't chosen as the master record). But after doing some testing yesterday, it seems like that's not true anymore -- Opportunities were successfully moved to the master record's household account. (Maybe that was a change in NPSP triggers?)
The only issue I could see with the native merge is that it doesn't delete the empty household account at the end, which is renamed "Anonymous Household". That seems like a drawback we can live with -- it's easy enough to clear those out periodically. But are there other issues I'm missing?
Yes @Chris McCullough that seems likely. I'll look into whether it has value. I know we have both customizable rollups active and DLRS. Thanks for your insights!
