How to build parent-child companies in HubSpot from NPI numbers
Yes, HubSpot can build a parent-child company hierarchy from NPI numbers. The catch is that the NPI doesn’t tell you which organization is the parent. Your business does. If you already have a rule for which NPI sits above which, the hierarchy can be built automatically, for the first import and for every company added after it.
We built this for Asaar Medical, a healthcare company selling into provider organizations. Their full CRM went live in 3 weeks, against their own expectation of 60 to 90 days.
Why healthcare teams want this
Healthcare sales teams sell to groups, not single offices. A health system or management group owns several locations, and each location often has its own NPI. If every location sits in HubSpot as an unrelated company, reps can’t see the whole account, owners can’t roll up pipeline by group, and two reps end up calling the same organization from different doors.
HubSpot has native parent and child company associations on every plan. A child company can have one parent, and a parent can have many children. The structure is there. Filling it by hand across hundreds of locations is the part nobody finishes.
The rule comes first
An NPI is an identifier, not a hierarchy. CMS calls it a 10-digit, “intelligence-free” number: it carries nothing about who owns whom. Before anything gets automated, you need a written answer to one question: for any two related NPIs, which one is the parent?
That answer usually lives in your own data already. It can be a parent NPI field in your billing system, a group or tier field in your ERP, or a list your ops team maintains. If the answer is “it depends who you ask”, settle it in scoping. Automating a fuzzy rule just produces a wrong hierarchy faster.
The same approach works with any external identifier that carries a parent: NPI in healthcare, DUNS numbers, or a tier field in the client’s own system.
How the build works
- Store the NPI on every company record, and the parent NPI wherever the rule says one exists.
- When a company is created or its parent NPI changes, look up the company that holds that NPI.
- Associate the two with HubSpot’s parent and child company association.
- Run the same logic once across the initial import, so existing records get their parents too.
For Asaar we ran this through custom code in Zapier, checked against the NPI registry. It covered the initial load and keeps covering new companies as they come in, with no one maintaining the tree by hand.
What breaks
- No rule, no hierarchy. If the parent can’t be determined from data, the automation has nothing to act on. That’s a scoping problem, not a build problem.
- Missing NPIs. Any company without an NPI stays unlinked. Make NPI required on the record types that should have one.
- One parent only. HubSpot allows one parent per child. If a location truly belongs to two groups, decide which relationship drives reporting and track the other with an association label.
Proof
“What we thought would take 60–90 days took just 3 weeks. ProfitPad pivoted, came up with viable solutions, and built us an amazing CRM. By far the best team out there.” JJ Gilmore, VP of Sales, Asaar Medical
FAQ
Can HubSpot create parent-child companies automatically?
Partly. On Professional and Enterprise plans, the Create associations workflow action links records whose property values match. HubSpot’s docs don’t say whether it can set the parent-child company link itself, so test it in your portal first. Otherwise custom code or an integration tool does the job. We used custom code in Zapier.
Does a parent-child hierarchy need a specific HubSpot plan?
No. Parent and child company associations are available on all HubSpot products and plans. The automation that builds them is a separate question: custom coded workflow actions need Data Hub Professional or Enterprise, while an outside tool like Zapier or n8n works on any plan.
What if we don’t know which NPI is the parent?
Then settle that before building anything. The automation only applies a rule you already have, such as a parent NPI field in your billing system or a group list from operations. If the rule is unclear, the hierarchy will be wrong, just faster. We resolve it in scoping.
Selling to provider groups and can’t see the whole account in HubSpot? Book a 30-minute systems review →