Welcome to the Community @EricH20! You are running into a real data-model mismatch: in Salesforce Financial Services Cloud, a Person Account is both an Account and a Contact, while HubSpot’s native Salesforce integration treats Salesforce Contacts/Leads as HubSpot Contacts and Salesforce Accounts as HubSpot Companies. If you enable both standard Account/company sync and Contact sync without careful filtering, the same person can appear once as a HubSpot contact and again as a “company” created from their Person Account.
The cleanest pattern is generally: Person Accounts >> HubSpot Contacts; Households >> a dedicated HubSpot custom object; Institutions >> HubSpot Companies. Avoid treating Person Accounts as HubSpot Companies. HubSpot matches Salesforce contacts/leads to HubSpot contacts primarily by email address, so email quality and uniqueness are essential before enabling the sync.
The one setting that actually prevents the duplication: Filter your Account-to-Company sync so it excludes Person Accounts and includes only true institutional records. Something like IsPersonAccount = FALSE, a record type check, or a dedicated field you maintain just for this. Don’t lean on company name or domain to sort this out. Person Accounts often don’t have one, and they’re not companies to begin with.
Now on Households specifically. If your HubSpot plan supports custom objects, a Household object with Contact associations (and association labels like Spouse, Trustee, Advisor) is the cleanest long-term answer. It preserves the real relationship instead of flattening it.
If custom objects aren’t in reach right now, a simpler phase one works fine: sync people as Contacts, skip a separate Household record, and carry a few household attributes (segment, advisor team) as Contact properties instead. You can build the object later once the rest is proven out.
One more thing worth saying plainly, since you’re in wealth management: keep account balances, holdings, and anything like SSNs out of the sync entirely unless you’ve got a documented reason and the access controls to back it up. Marketing doesn’t need it, and every additional field you sync is one more thing to defend later.
Start with a pilot team before you flip this on for the whole book. It’ll tell you fast whether your email data is clean enough to match reliably, which is the other half of this working the way you want.
Hope that helps!