Connecting the full customer relationship in HubSpot

Why one Company record was not enough

One customer could have several Company records, licenses, deals and service projects. Parent companies and subsidiaries made grouping harder. The data team needed one customer identifier for retention reporting across current and historical contracts.

How I connected the records

I defined the Account model and association rules, reviewed duplicates and parent-child relationships, and backfilled active and historical B2B customer records. Older licenses stay linked for retention reporting.

Three automated paths create or find Accounts for new licenses and professional services, and link deals. The associated Company is the matching point. The setup uses HubSpot custom objects, workflows and JavaScript.

A customer layer for reporting

The Account layer gives the data team a consistent customer identifier for account-level retention reporting.

Weekly review and its limits

I manually start a weekly check comparing new Accounts with the full account base. It looks for possible duplicates and parent-company relationships using names, domains and previously reviewed relationships.

It also flags licenses and professional services without an Account, and signed deals missing expected service records. Codex and Claude Code help assess candidate matches and put findings in context.

Incomplete source data or an unexpectedly large candidate list stops the run for investigation. I review the findings before changing HubSpot. The check itself does not merge records or change associations.