We’re running into a modeling challenge with customers that operate across multiple locations under a single legal entity (same company and ID).
In our ERP, these locations are treated as separate objects linked to a company, rather than separate companies themselves. However, in HubSpot, we’re struggling to represent this structure cleanly. A parent–subsidiary relationship doesn’t seem appropriate, since all locations belong to the same company rather than being distinct legal entities.
Has anyone found a robust way to model this in HubSpot? Or is using Custom Objects effectively the only viable approach?
It feels like a fairly common use case, so I’m a bit surprised there isn’t a more native way to handle it in the standard data model.
This is a common gap in HubSpot, its company model doesn’t naturally support multiple locations under one legal entity, so using parent–subsidiary often misrepresents the data and creates reporting issues. The most reliable approach is typically a Custom Object for locations, properly associated with the main company to keep structure, reporting, and automation clean. I’ve helped implement this in a way that avoids complexity while keeping everything scalable, so happy to guide you through it. Are you trying to track deals and performance per location or just maintain structured visibility across them?
Right now the main need is clean visibility across locations under the same legal entity. But this is not just for viewing purposes—we expect to eventually track deals, deliveries, and performance per location, so the structure should support that from the start.
That’s a smart call, planning for future deal and performance tracking now will save you a lot of rework later. The cleanest way is to set up “Locations” as a Custom Object tied to the main company, so each one can grow into its own reporting and deal layer over time. I’ve helped set this up in a simple but scalable way without overcomplicating things. If you want, I can take a look at your setup and assist you directly?.
Thanks for yor help. We deliberately chose Pro, as Enterprise didn’t seem to provide additional value for our needs. Right now I’m mainly trying to understand whether Custom Objects are truly necessary in our case, or if we could still operate effectively on Pro.