How do I model parent-child accounts in Salesforce?
Represent groups and their locations correctly so rollups, routing, and reporting all work.
Model parent-child accounts by linking each location to its owning group with the Salesforce Parent Account field, building the account hierarchy so Fit and Health, opportunities, and activity roll up to the parent and your team works the group as one account. The hierarchy is how resolved ownership becomes usable in the CRM.
This guide is about the Salesforce account hierarchy mechanics: the Parent Account field, rollups, and reporting. For working out who actually owns whom from public data, see the flagship guide on resolving parent-child ownership.
How does the Salesforce account hierarchy work?
Each child Account carries a Parent Account lookup pointing at its owning group. Chain those lookups and Salesforce builds the account hierarchy, the tree you see in View Account Hierarchy. Roll-up summary fields and reports then aggregate the children into the parent. Resolving ownership (resolving parent-child ownership) tells you who owns what, matched from NPI, CCN, and public ownership records; the Parent Account field is where that truth lives so reports and automation can use it.
What should roll up to the parent?
| Rolls up to the parent | Why it matters |
|---|---|
| Fit and Health at the group level | Leadership sees the group's total standing, not one clinic's |
| Open opportunities across locations | Reps avoid competing on the same group |
| Activity and ownership across sites | The whole relationship is visible on one record |
| Product ownership per location | Whitespace across the group becomes obvious |
How do I keep the hierarchy correct?
Update the Parent Account links as ownership changes, because acquisitions and divestitures reshape groups constantly and a DSO rebrand can move dozens of locations under a new parent overnight. SignalRx assigns the relationships for you, writing the Parent to Child links, and Reseller to End-Customer where a group sells through a channel, so each location rolls up to its owning group, MSO, or PE platform. The ownership it writes to the Parent Account field is triangulated across registries like PECOS and CMS, news and company websites, and LinkedIn, which is how a PE rebrand gets caught and the affected locations re-parented (resolving parent-child ownership). That keeps the hierarchy from drifting: a newly acquired clinic is re-parented by resolved ownership rather than left as an orphan account, and a location that arrived with a blank parent is connected from that resolved ownership instead of dropping out of every group rollup. The same resolved data feeds scoring, where SignalRx weighs public healthcare data against your own internal signals of revenue, support, and product usage tracked over time, lets inference decide which source to trust, and writes Fit and Health scores, segments, and tags to native Salesforce fields for both accounts and contacts, turning them into Revenue Plays and list views.
Key takeaways
- The Parent Account field and the account hierarchy make resolved ownership usable in Salesforce.
- Roll up Fit, Health, opportunities, and activity to the parent group.
- Update parent links as DSO, MSO, and PE ownership changes.
See it in action: Discover High-Fit Prospects with SignalRx.
Related: How do I resolve parent-child ownership? and How do I find whitespace across locations?
Want any of these running on your data?
Frequently Asked Questions
.svg)
.avif)