<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic DemandTools Contact Merge Leaving Child Records Stranded on Anonymous Household Accounts in DemandTools</title>
    <link>https://mycommunity.validity.com/t5/demandtools/demandtools-contact-merge-leaving-child-records-stranded-on/m-p/2995#M1702</link>
    <description>&lt;P class=""&gt;Hello Validity Community,&lt;/P&gt;&lt;P class=""&gt;I'm experiencing an issue with Contact merges in DemandTools that's causing data integrity problems in our NPSP org, and I'm hoping someone has encountered and solved this.&lt;/P&gt;&lt;P class=""&gt;&lt;STRONG&gt;Our Setup:&lt;/STRONG&gt;&lt;/P&gt;&lt;UL class=""&gt;&lt;LI&gt;Salesforce NPSP (Nonprofit Success Pack)&lt;/LI&gt;&lt;LI&gt;Household Account Model enabled&lt;/LI&gt;&lt;LI&gt;DemandTools for data deduplication&lt;/LI&gt;&lt;/UL&gt;&lt;P class=""&gt;&lt;STRONG&gt;The Problem:&lt;/STRONG&gt; When we merge duplicate Contacts using DemandTools:&lt;/P&gt;&lt;OL class=""&gt;&lt;LI&gt;DemandTools merges the Contacts successfully ✓&lt;/LI&gt;&lt;LI&gt;The losing Contact is deleted (as expected) ✓&lt;/LI&gt;&lt;LI&gt;The losing Contact's Household Account becomes an "Anonymous Household" ✓&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;BUT:&lt;/STRONG&gt; Child records (Opportunities, Payments, etc.) remain attached to the Anonymous Household Account instead of moving to the winning Contact's Household ✗&lt;/LI&gt;&lt;/OL&gt;&lt;P class=""&gt;&lt;STRONG&gt;What We Need:&lt;/STRONG&gt;&amp;nbsp;&lt;/P&gt;&lt;OL class=""&gt;&lt;LI&gt;Move child records from Anonymous Household to the winning Contact's Household during merge.&lt;/LI&gt;&lt;/OL&gt;&lt;P class=""&gt;Has anyone successfully solved this in DemandTools? Is there a merge configuration, field mapping, or workflow we're missing that would handle Household Account consolidation?&lt;/P&gt;&lt;P class=""&gt;Any guidance would be greatly appreciated!&lt;/P&gt;&lt;P class=""&gt;&lt;STRONG&gt;Environment Details:&lt;/STRONG&gt;&lt;/P&gt;&lt;UL class=""&gt;&lt;LI&gt;DemandTools Version: 5.46.2.0&lt;/LI&gt;&lt;LI&gt;Salesforce Edition:&amp;nbsp;&lt;SPAN&gt;Enterprise Edition&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
    <pubDate>Wed, 04 Feb 2026 00:56:29 GMT</pubDate>
    <dc:creator>Baymed</dc:creator>
    <dc:date>2026-02-04T00:56:29Z</dc:date>
    <item>
      <title>DemandTools Contact Merge Leaving Child Records Stranded on Anonymous Household Accounts</title>
      <link>https://mycommunity.validity.com/t5/demandtools/demandtools-contact-merge-leaving-child-records-stranded-on/m-p/2995#M1702</link>
      <description>&lt;P class=""&gt;Hello Validity Community,&lt;/P&gt;&lt;P class=""&gt;I'm experiencing an issue with Contact merges in DemandTools that's causing data integrity problems in our NPSP org, and I'm hoping someone has encountered and solved this.&lt;/P&gt;&lt;P class=""&gt;&lt;STRONG&gt;Our Setup:&lt;/STRONG&gt;&lt;/P&gt;&lt;UL class=""&gt;&lt;LI&gt;Salesforce NPSP (Nonprofit Success Pack)&lt;/LI&gt;&lt;LI&gt;Household Account Model enabled&lt;/LI&gt;&lt;LI&gt;DemandTools for data deduplication&lt;/LI&gt;&lt;/UL&gt;&lt;P class=""&gt;&lt;STRONG&gt;The Problem:&lt;/STRONG&gt; When we merge duplicate Contacts using DemandTools:&lt;/P&gt;&lt;OL class=""&gt;&lt;LI&gt;DemandTools merges the Contacts successfully ✓&lt;/LI&gt;&lt;LI&gt;The losing Contact is deleted (as expected) ✓&lt;/LI&gt;&lt;LI&gt;The losing Contact's Household Account becomes an "Anonymous Household" ✓&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;BUT:&lt;/STRONG&gt; Child records (Opportunities, Payments, etc.) remain attached to the Anonymous Household Account instead of moving to the winning Contact's Household ✗&lt;/LI&gt;&lt;/OL&gt;&lt;P class=""&gt;&lt;STRONG&gt;What We Need:&lt;/STRONG&gt;&amp;nbsp;&lt;/P&gt;&lt;OL class=""&gt;&lt;LI&gt;Move child records from Anonymous Household to the winning Contact's Household during merge.&lt;/LI&gt;&lt;/OL&gt;&lt;P class=""&gt;Has anyone successfully solved this in DemandTools? Is there a merge configuration, field mapping, or workflow we're missing that would handle Household Account consolidation?&lt;/P&gt;&lt;P class=""&gt;Any guidance would be greatly appreciated!&lt;/P&gt;&lt;P class=""&gt;&lt;STRONG&gt;Environment Details:&lt;/STRONG&gt;&lt;/P&gt;&lt;UL class=""&gt;&lt;LI&gt;DemandTools Version: 5.46.2.0&lt;/LI&gt;&lt;LI&gt;Salesforce Edition:&amp;nbsp;&lt;SPAN&gt;Enterprise Edition&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Wed, 04 Feb 2026 00:56:29 GMT</pubDate>
      <guid>https://mycommunity.validity.com/t5/demandtools/demandtools-contact-merge-leaving-child-records-stranded-on/m-p/2995#M1702</guid>
      <dc:creator>Baymed</dc:creator>
      <dc:date>2026-02-04T00:56:29Z</dc:date>
    </item>
    <item>
      <title>Re: DemandTools Contact Merge Leaving Child Records Stranded on Anonymous Household Accounts</title>
      <link>https://mycommunity.validity.com/t5/demandtools/demandtools-contact-merge-leaving-child-records-stranded-on/m-p/2996#M1703</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://mycommunity.validity.com/t5/user/viewprofilepage/user-id/2742"&gt;@Baymed&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;We have a workflow that will accomplish this for you.&amp;nbsp; In a standard Salesforce environment, we would recommend deduping on the accounts first before the contacts.&amp;nbsp; In many cases, in NPSP environments, there's not enough information on the account for you to match and merge.&lt;BR /&gt;&lt;BR /&gt;Please checkout this article:&lt;BR /&gt;&lt;A href="https://knowledge.validity.com/s/articles/Dedupe-Household-Accounts-and-Contacts-npsp?language=en_US" target="_blank"&gt;https://knowledge.validity.com/s/articles/Dedupe-Household-Accounts-and-Contacts-npsp?language=en_US&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Best,&lt;/P&gt;</description>
      <pubDate>Wed, 04 Feb 2026 13:23:56 GMT</pubDate>
      <guid>https://mycommunity.validity.com/t5/demandtools/demandtools-contact-merge-leaving-child-records-stranded-on/m-p/2996#M1703</guid>
      <dc:creator>AnthonyValidity</dc:creator>
      <dc:date>2026-02-04T13:23:56Z</dc:date>
    </item>
  </channel>
</rss>

