Big accounts are rarely one company — they're a parent with subsidiaries, divisions, or regional entities. HubSpot's parent-and-child company associations let you model that real corporate hierarchy, so you can see every entity in an account family, roll up the activity, and report on the relationship as a whole instead of as scattered records. Set up well, it turns a pile of disconnected company records into a clear org tree. Here's the practitioner's read on doing it right.
What is a parent-child company relationship in HubSpot?
It's a structured link that says one company owns or sits above another — a parent at the top, child companies beneath it, mirroring how the real business is organized. A single parent can have many children, and the relationship is hierarchical, so you can represent a corporate group, a franchise network, or a company split into regional entities. This is different from a casual association between two companies; the parent-child link carries direction and meaning, which is what lets HubSpot roll activity and reporting up the tree. Worked example: a holding company with three operating subsidiaries becomes one parent record with three children — and now anyone looking at the parent can see the whole relationship at a glance.
How do you actually add a parent or child company?
Open the company record, find the associated-companies section, and create the link — choosing whether the company you're adding is the parent or the child. From an existing company record, go to the section that lists associated companies, choose to add a related company, and pick the relationship type so HubSpot knows the direction. You can build the hierarchy from either end: start at the parent and attach children, or start at a subsidiary and point it up to its parent. Worked example: you're on a subsidiary's record and realize it belongs to a larger group — add the parent from that record, set the relationship, and HubSpot reflects the link on both records automatically. Get the direction right; a reversed parent-child link inverts your whole rollup.
Why bother modeling the hierarchy at all?
Because it gives you account-level visibility and cleaner reporting — you see the whole relationship, route work correctly, and stop double-counting the same customer. Without the hierarchy, a global account looks like five unrelated companies, and a rep can pitch a subsidiary something the parent already bought. With it, the activity and deals associated across the family can be viewed together, account owners see the full picture, and your reporting doesn't treat one customer as five. Worked example: a renewal conversation where you can see that two sister subsidiaries are already customers — that context changes the pitch and prevents an embarrassing cold approach to a company that's effectively already inside the account.
How do you keep the hierarchy accurate over time?
Treat it like any other data model — review it when the business changes, because acquisitions, divestitures, and reorgs silently break the tree. When a customer acquires another company, the new subsidiary should be linked under the parent. When a division spins out, the link should be removed or repointed. The common failure is a hierarchy built once during onboarding and never touched, so two years later it shows a corporate structure that no longer exists. A periodic check on your top accounts — does this tree still match reality — keeps the rollup trustworthy. This is the same hygiene discipline that keeps the rest of the portal reliable: structure is only useful while it's true.
The IV-Lead take
Parent-child company associations are one of HubSpot's quieter features, and on enterprise-style accounts they're the difference between seeing a customer and seeing a customer family. The mechanics take a minute; the value is in the discipline of keeping the tree accurate and using it — for account planning, for clean reporting, for not pitching a company something its parent already owns. Model the hierarchy where it matters most, on your largest and most complex accounts, and revisit it whenever those accounts change shape.
Want your account hierarchies and reporting structured to match how your customers are really organized? Book a 30-minute portal audit — we'll show you where account structure is costing you visibility. For the bigger picture, see how we approach HubSpot implementation and optimization.
Frequently asked questions
Can one company be both a parent and a child?
Yes. A mid-level entity can be a child of a top parent while being the parent of its own subsidiaries, which lets you model multi-level corporate structures rather than a single flat layer.
Does activity automatically roll up from child companies to the parent?
The association gives you account-level visibility across the family and lets you report on the relationship together. Exactly how rollups and views behave depends on your HubSpot tier and configuration, so confirm the behavior in your portal.
Can I import a company hierarchy instead of linking records one by one?
Yes. If your import file includes the parent identifier on each child record, you can establish the relationships during import rather than linking manually — useful when migrating a large account structure.
What happens to the link if I delete a company record?
Deleting a company removes its associations, which can leave the rest of the tree incomplete. Before deleting an entity in a hierarchy, repoint or clean up its parent-child links so the remaining structure still reflects reality.
