Somebody in the QBR asks what the account is worth. You open the parent company in HubSpot, read Total revenue, and the number is small enough that the account executive starts listing subsidiaries from memory. Then someone adds the children by hand in a spreadsheet, and a deal that sits on two records gets counted twice.
The hierarchy in HubSpot looks like it should handle this. It was built to show who owns whom.
The revenue math is your job, and it takes four decisions: where each deal lives, which company records are duplicates, which property holds the sum, and how you check it. The sections below take them in that order, starting with what the parent-child link does and doesn’t do.
How do parent and child companies work in HubSpot?
HubSpot links companies with the default Parent company and Child company association labels, and those labels are available on all products and plans. Each child company can have one parent, and a parent can have many children. The link describes the relationship and stops there: HubSpot says parent-child associations don’t share activities or data between records, so nothing rolls up to the parent by itself.
The details, per HubSpot’s Knowledge Base (Add a parent or child company to an existing company record, last updated January 21, 2026):
- You can add a parent or child on a company record, or in bulk through an import.
- For an import, the parent companies have to exist in your CRM before you import the children.
- A child company can only be associated with one parent company. A parent can have multiple children.
Parent and Child is a paired label, so when you set one side, HubSpot sets the other side for you (Create and use association labels, last updated August 31, 2026). HubSpot also keeps two default company properties that describe the hierarchy: Number of child companies, and Parent company, which holds the company ID of the parent (HubSpot’s default company properties, last updated August 7, 2026).
What the hierarchy doesn’t do is pool anything. HubSpot’s page on company domains says it plainly: parent-child associations do not share activities or data between records (Manage the company domain name property on records, last updated September 17, 2026). The parent sees that it has children. It doesn’t see their deals.
Why doesn’t the parent company show the whole account’s revenue?
The parent’s Total revenue counts deals closed with the parent record, and the children’s deals stay on the children. Annual revenue is a different field with a different meaning: the customer’s own size, actual or estimated, and nothing to do with what you sold them. Teams that read either field as “account revenue” end up with a number that’s too low, or one that mixes two meanings.
HubSpot defines the two fields this way (HubSpot’s default company properties, last updated August 7, 2026):
- Total revenue: the total value of deals closed with the company. HubSpot sets it automatically.
- Annual revenue: the actual or estimated annual revenue of the company.
Total revenue is your booked business with that one record. Annual revenue is how big the customer is. Put Annual revenue on a slide labeled “account revenue” and the board will read the customer’s size as your bookings, which is how board numbers stop matching the CRM.
Double counting is the other risk, and it runs the opposite direction. If the same closed deal is associated with both the parent and a child, it can show up in both companies’ totals, and adding those totals together counts it twice. HubSpot’s documentation doesn’t say how Total revenue treats a deal associated with several companies. Test it in your portal: take one closed deal, associate it with a parent and a child, and look at both records. Whatever you find decides how strict your deal rule needs to be. (If your HubSpot reports already disagree with each other, multi-company deals are one place to look, along with the others in why HubSpot reports aren’t accurate.)
Where a deal should live: parent, child or both
Pick one company of record per deal and write the rule down. A rollup only works if each deal is counted on one company. Watch the default: HubSpot says that when you associate a company while creating a new record, that company becomes the primary company. The first company a rep clicks while creating the deal can quietly become the company of record.
That default comes from HubSpot’s Knowledge Base (Associate records, last updated September 16, 2026). The same page says custom association labels need a Professional or Enterprise subscription. The default Parent company and Child company labels are on all plans; it’s the custom labels, like one that marks a deal’s extra company associations, that need the higher tier.
A workable starting rule: the company of record is the entity that signs and pays. Any other company you associate with the deal gets a label, so reports can leave it out.
| Situation | Associate the deal with | Why |
|---|---|---|
| One subsidiary signs the contract and gets the invoice | That child company | The revenue belongs to the entity that pays, and the rollup carries it up to the parent |
| A master agreement sits at the parent, and the children place their own orders | Each order on the child that places it | Each order is counted once on the child, and the parent sees the total through the rollup |
| The parent buys, and the children use it | The parent | The parent signed and pays; usage across children doesn’t move the revenue |
| You’re not sure who the buyer is | The entity on the invoice, with any other company associations labeled | One company of record keeps the sum clean, and the labels let reports exclude the extras |
The table is a recommendation, not a HubSpot setting. HubSpot will let you associate a deal with as many companies as you like. The rule is what keeps the rollup honest, and it only holds if reps and admins know it exists. Put it in the deal desk notes or wherever your team keeps CRM rules, and check new deals against it for the first few weeks.
How to roll child revenue up to the parent
On Professional or Enterprise, create a company rollup property that sums Total revenue from associated companies with the Child company label. Keep it separate from the parent’s own Total revenue, and put both side by side in a report: the parent’s own deals, its children’s deals, and the sum of the two. Then check one parent by hand before anyone trusts the number.
HubSpot’s rollup properties can calculate the min, max, count, sum, earliest date, latest date or average of a property on associated records. You can limit the calculation to specific association labels, including same-object associations like company to company, and you can add up to 50 number and enumeration conditions per rollup property (Create calculation and rollup properties, last updated October 6, 2026). That page lists the subscriptions that include rollups: Marketing, Sales, Service, Content, Smart CRM and Revenue Hub at Professional or Enterprise, plus Data Hub Professional.
HubSpot doesn’t publish this exact recipe for parent revenue, so treat the steps below as the route and test it in your portal:
- Create a new company property with the rollup type. Give it a name that can’t be confused with the default field, like “Child company revenue.”
- Set the calculation to Sum, on Total revenue, from associated companies. This is a company-to-company rollup.
- Limit it to the Child company label. Without the label filter, the rollup can pick up companies associated for other reasons.
- Add conditions only if you need them. Up to 50 number and enumeration conditions can narrow which child companies count toward the sum.
- Build a report with three columns on the parent: its own Total revenue, the new child rollup, and the two added together. HubSpot allows one same-object association label per custom report (Create and use association labels, last updated August 31, 2026), so build the parent-child view around the Child company label.
- Check one parent by hand. Pull up each child, add its Total revenue, and compare that to the rollup. If the numbers match, the property is ready for the QBR deck.
HubSpot’s own sample report for parent-child labels lists a parent’s child companies and their annual revenue values. That’s a useful view of how big the children are. For what you’ve sold them, swap in Total revenue.
Two limits to plan around:
- Grandchildren. A rollup reads the companies associated with the record it sits on. HubSpot’s documentation doesn’t describe how rollups handle a hierarchy with more than one level, so if your accounts have grandchildren, check whether each level needs its own rollup before you report on the top.
- Starter and free portals. The Parent company and Child company labels work on all plans, but rollup properties need Professional or Enterprise. On lower tiers, the account number comes from a report or an export, not a property on the parent.
Clean duplicate companies before you build the hierarchy
A parent with two records splits its children and its revenue between them. Merge duplicates first. If a merge fails, check the hierarchy for a loop, remove the Parent/Child label, and then merge. And adding a second domain to a company won’t merge an existing duplicate that already has that domain, so search for one before you add it.
Duplicates are common. Validity’s State of CRM Data Management in 2025, a survey of 602 CRM users and stakeholders published July 2025, found 76% said less than half of their organization’s CRM data is accurate and complete. A hierarchy built on top of that inherits all of it.
HubSpot’s rules that matter here:
- Domains drive identity. HubSpot uses the primary Company domain name to identify company records, and to associate contacts and companies when automatic association is on (Manage the company domain name property on records, last updated September 17, 2026).
- Adding a domain doesn’t merge. If you add a domain to one company and another record already has it, HubSpot won’t merge the records or pull their activities together. Additional domains only apply going forward (same page).
- Loops block merges. Companies in a parent-child relationship can be merged, but a merge may fail when the companies sit in a loop, where a parent ends up associated to itself through a chain. Removing the Parent/Child company label lets the merge go through (Add a parent or child company to an existing company record, last updated January 21, 2026).
- Other merge limits. The same page says merges may still fail with the Salesforce integration turned on, or once the companies hit a combined limit of 250 merges.
If duplicate contacts are part of the same mess, the HubSpot duplicate contacts guide covers that side, and two CRMs syncing into each other is a common source of both. Enrichment tools can add to it too, by matching a record to the wrong company, which puts a child under the wrong parent before anyone notices.
When should you use multiple domains instead of a parent and child?
When the “child” is the same buying entity under another web domain, like a rebrand or a regional site, add the domain to one company record. When it’s a separate legal or buying entity with its own deals, use parent and child. The choice decides whether activity and revenue sit together on one record or apart on two.
HubSpot draws the line itself: multiple domains on one company record give you a combined activity timeline, and parent-child associations don’t share activities or data (Manage the company domain name property on records, last updated September 17, 2026). One record with two domains reads as one customer. Two records with a parent-child link read as two customers who happen to be related, and their revenue only meets in a rollup you build.
The choice in front of you
You can keep reading the parent’s Total revenue and explaining the gap at each QBR. Or you can write the deal rule this week, merge the duplicates under your biggest parent account, and build one rollup you’ve checked by hand.
The first option costs you a few minutes of explaining at each QBR, for as long as you keep choosing it. The second costs you once.
If you’d rather see where duplicate companies and deals associated with more than one company are sitting in your portal before you build, the free CRM Diagnostic runs 40+ automated checks across data quality, pipeline hygiene, freshness, reachability and ICP fit. More on what it covers is on the CRM Diagnostic page.