Parent Child Companies / Pros, Cons

Smart CRM & Sales Hub CRM
1

Can someone explain the actual pros and cons of using parent child accounts in hubspot please?
Im specifically interested in a few things:
1) where does the sales outreach acitvity get logged? Probably on the company based on domain name? Only on the child company? Both child and parent?
2) Where will deals live? Only on the child company hopefully?

3) How does data copy over from parent to subsequent child companies?

2

Hi @jkim21!

Thanks for posting in the Community!

I see that you’re looking for some more insight into utilizing Parent and Child Companies in your Portal.

1.) By default, when using Company to Company associations, the activities will not be logged from one company to the other. We can find more on default activity associations here!

If you’d like activities to associate from one Company to another associated Company, then you could set up automatic associations for records and activities by following these steps - Set up automatic associations for records and activities -

this would allow you to select which types of activities should log from company to company, however, there isn’t currently a way to set this up to only sync from Child to Parent company or vice verse, it’d be for all Company to Company associations.
2.) The Deal would stay associated only to the record it was created on or associated to. Any record association (like Deals) will not automatically associate to the Child or Parent company.
3.) When creating a a Child or Parent company association, the property data is not synced over. The association label is mostly used for organizational purposes and filtering!
I’d like to tag in some of our Top Contributors to see if they have any additional pros and cons or general suggestions they’d like to add here!

@karstenkoehler, @danmoyle, @Jnix284
-- Do you have any suggestions for @jkim21?

Thank you!

Sam, Community Manager

3

WHat happens when you bcc an email - to a domain name. Will it go to the parent company or child. How do you move it child?

4

Hey there @jkim21 good question. It all depends on your needs and expected behavior of HubSpot. Bascially, their parent–child companies are purely a relationship/lookup layer. They don’t automatically roll up activities or deals. And they do have some limited native automation between the records. Most of what you’re asking about still happens at the individual company/contact/deal level, and you have to design your process around that.

You asked about where the sales activity is logged. Activities (emails, calls, meetings, tasks, notes) are logged to a) the contact you engaged with, b) that contact’s primary associated company, and c) any explicitly associated deals/tickets, etc.​

The parent–child link does not auto-share activities: if something is logged on a child company, it does not appear on the parent, and vice versa.​ But users can generally manage that. To see everything at the parent level, you typically:

  • Use lists/reports filtered by “Associated company > Parent company is X”, or
  • Manually/with workflows associate key records (contacts/deals) to the parent as well.​

So in practice, outreach logs “on the company based on the contact’s primary company,” which will usually be the child, not the parent, unless you deliberately associate the contact to the parent.

As for Deals, they’re always “owned” by the deal record itself, but they are associated with one or more companies. A deal associated to a child company does not automatically get associated to the parent company via the parent–child relationship, but that’s something users can manage when working in Deals.

​

I looked up some common best practice if you want “deals only on the child.” Here are a couple that make the most sense IMO:

  • Make the child company the primary associated company for the deal.
  • Optionally associate the parent company as a secondary company on the deal if you want visibility at both levels.​

So yes, Deals “live” on the child if that’s how you associate them; HubSpot will not move them to the parent unless you explicitly add that association.

Now, for your question on how data copies from parent to child… The parent–child relationship alone does not sync or inherit data; all company properties are independent.​ To copy values down (e.g., Owner, Contract type, Billing address), you need:

  • Company-based workflows that use company–company association rules to copy properties from parent to child, or
  • An external tool/custom code (e.g., Insycle + workflows, custom Ops Hub action) if you need more complex logic.​

Out of the box with standard set-up, HubSpot does not let you easily use “parent company” properties as sources/targets in every workflow context, so more advanced inheritance often requires workarounds or third-party tools.​ So no, nothing “just copies” on its own as you asked. You design the inheritance pattern with workflows/integration.

And finally to your added question under @SamTassey’s comment, BCC logging: parent vs child, when you BCC the HubSpot logging address here’s what happens. HubSpot logs the email to the contact record based on the email address, then it associates that email with the contact’s primary company, and with the five most recent open deals for that contact (I bolded that because a lot of us miss that early in our usage - I know I did and it confused me.).​

The company picked is not chosen by parent/child hierarchy, but by the contact’s primary company association (and, if enabled, auto-association by domain to create/associate a company).​ If the email logs to the “wrong” company and you want it under a child:

  1. Re-associate the contact to the correct child company (either change primary company or add associations and adjust primary).
  2. On the email activity itself, you can also edit associations and add/remove company records so the activity appears under the correct child company timeline.​

You asked for some real world pros and cons of parent–child accounts in HubSpot. Here’s what I’d say in my experience.

Pros

  • Cleaner account hierarchy for multi-location / franchise / holding-company structures (I see this one as the most common, honestly).​
  • Easier reporting and list-building using “Parent company” filters (like roll up pipeline or activity across all children in a report, not on the parent timeline).​
  • Helps ABM/strategic account workflows where you need to group related companies.​

Cons / gotchas

  • No automatic activity or deal roll-up from child to parent timelines.​
  • Very limited native workflow actions specifically on “parent vs child” properties, so inheritance needs careful design or external tooling.​
  • Can create confusion if sales assumes the parent record will show “everything” for the group; in reality you need reports/dashboards for that view.

I hope that helps!

5

Hi Dan, your latest post indicates activities [meetings] are not automatically logged to the Parent company if originally logged on Child company. We are noticing this behavior is happening by default. Any thoughts how to ‘break’ the association so a meeting logged with a Child account does not log to the Parent activity feed (and in our case, slack integration!)

7

Hey @MC1,

Thanks for following up here!

Re-tagging @danmoyle for visibility.

Shane, Senior Community Moderator

8

Welcome to the Community @MC1! You are correct in that HubSpot’s native parent/child setup does not provide true data separation or sync controls between those company records. HubSpot states there is no data sync between parent and child companies, and activities stay on the company record where they’re logged unless additional association behavior pulls them elsewhere.

HubSpot doesn’t truly “break” parent-child visibility with a special toggle, so the fix is usually to change the automatic activity association settings, especially for meetings, and make sure the parent is not included as a default associated company. If Slack is also receiving the activity, tighten the Slack notification workflow so it only fires on child-company records.

Here are a few workarounds out there others have suggested.

Use workflows to re-associate or suppress notifications. If the meeting must be logged on the child, you can create a workflow that identifies child-company meetings and then either updates downstream notifications or creates a separate internal alert only for the child record. That won’t stop the original activity from existing on associated records if HubSpot’s association rules already copied it, but it can reduce unwanted Slack noise.

Separate the operational record from the reporting record. Some teams keep the parent company as a reporting-only container and log day-to-day meetings only on child companies, with stricter association rules so the parent is not an automatic activity target. This is usually the simplest native approach when you want hierarchy without activity bleed-over.

Remove the parent association when needed. If a child company should be completely isolated for activity logging, the most reliable native option is to avoid associating it to the parent until after the meeting is logged, or remove the association before logging sensitive activities. That is manual, but it gives you the cleanest separation.

Honestly, I haven’t used another system in a minute, so I don’t know how HubSpot’s behavior compares to other tools. What I’ve told clients is that some of the work may be manual, and admin time is important to bake into the work. No tool I know of works perfectly, so the workarounds above may help, but it also may be a limitation that means manual association of meetings when you know parent/child relationships are involved.

Hope that helps some!

9

Hey thanks Shane ( @STierney ) for the tag! I did indeed need the nudge to see it. Cheers!

11

Parent/child companies mainly help organize related businesses. Deals stay with the child company, and activities are usually logged against the company/contact where they happen rather than automatically on both parent and child. Data also doesn’t automatically copy between parent and child records—you’ll need workflows or automation if you want that.

12

Hi @jkim21

Those are great questions. Before diving into the details, could you share a bit more about your use case?

For example:

  • Are you using parent-child companies to represent branch offices, franchises, subsidiaries, or multiple locations?
  • Will your sales team primarily work with the child companies, or do they also manage relationships at the parent company level?

Those answers can influence the most practical setup.

Regarding your specific questions, I’d also be interested to hear from others who have implemented this in production:

  • How activities (emails, calls, meetings) are associated when working with parent-child companies.
  • Whether deals are typically associated only with the child company or also with the parent, depending on the sales process.
  • Whether any company properties are synchronized automatically between parent and child records, or whether workflows or other automation are needed to keep data aligned.

Looking forward to hearing how others have approached this, as it’s an important consideration when designing a scalable company structure.