What is a Salesforce account hierarchy?
Each Account record in Salesforce has a Parent Account field. By setting parent accounts, you build a hierarchy that can be 1 level deep (parent and children) or many levels deep (corporate, region, country, subsidiary, division).
Salesforce displays the hierarchy on the Account record under the 'View Account Hierarchy' link. Hierarchies are visible in reports, list views, and via the API for downstream applications.
When to use account hierarchies
Enterprise customers with multiple subsidiaries. Roll up revenue, opportunities, and activity at the parent level.
Named account programs that target multiple buying entities inside one parent organization.
Account-based marketing campaigns that need to attribute engagement across all entities of a parent.
Renewal planning for parent contracts with multiple subsidiary instances.
Whitespace analysis at the parent level (where in the customer's organization are we and where are we not).
How to set up an account hierarchy
Start with the highest-level entity (the corporate parent).
Create child accounts and set the Parent Account field to point at the parent.
Repeat for any number of levels. Salesforce supports up to 500 children per parent and effectively unlimited depth.
Use the View Account Hierarchy link on the Account record to visualize.
Rollup considerations
Salesforce doesn't roll up financial data automatically from children to parent. You need either roll-up summary fields (limited by Salesforce field types), an Apex trigger, or a third-party tool.
For most use cases, build custom report types that group by parent account and aggregate at that level.
Common rollups: total opportunity ACV across all children, total closed-won revenue, total active opportunities, latest activity date.
Hierarchies and account planning
Account plans typically live at the parent level for global accounts. Child accounts inherit or reference the parent plan.
Relationship maps need to span the hierarchy. A buying committee at the parent might include stakeholders from multiple children.
Whitespace analysis is most useful at the parent level. Where do we have presence in this global customer and where don't we?
Inside Prolifiq CRUSH, hierarchies are first-class. The account plan, relationship map, and whitespace all operate at the parent level by default, with drill-down to children.
Common hierarchy mistakes
Building hierarchies that don't reflect the actual buying dynamic. If the customer's subsidiaries buy independently, modeling them under a single parent obscures the real sales motion.
Going too deep. A 5-level hierarchy is hard to maintain and rarely adds value over a 2-level one.
Not aligning hierarchies with marketing's account structure. If marketing campaigns target one structure and sales uses another, attribution breaks.
Skipping the data hygiene work. Bad parent assignments mean broken rollups. Audit and clean annually.
Not handling M&A. When a customer acquires another customer, the hierarchy needs to update. Many teams don't have a process for this.
Frequently asked questions
What is a Salesforce account hierarchy?
A parent-child relationship between Account records that models corporate structures with subsidiaries, divisions, or regional entities.
When should I use account hierarchies?
For enterprise customers with multiple subsidiaries, named account programs targeting parent organizations, and whitespace analysis at the parent level.
How deep should an account hierarchy go?
Usually 2 to 3 levels. Deeper hierarchies are hard to maintain and rarely add value over flatter structures.
CTA
Run account planning across complex hierarchies with whitespace and rollups at every level? See how CRUSH handles enterprise hierarchies natively. [Book a Demo]
