Best Practice for Sub-Companies? (Rolling up to a Parent Company)

[Jame Healy]

Hi all,

We have a situation where we have a parent company that needs to keep the legal identities and engagement with several wholly owned subsidiary companies distinct. Similarly, we also have a situation where one of our clients acquired another client, but they (and we) wish to in some ways keep the history, and interaction distinct too.

Currently, we have a Custom Profile Field set up for Accounts/Company with a Lookup Field on the "company" object type. This works, but of course, there is no way (as far as we can tell) to do any roll-up analysis.

Does anyone else have a similar challenge? Any more creative solutions or best practices?

[Lissa Meade, GRAYBOX]

It sounds like you might be interested in utilizing the Divisions feature in Accelo. We don't use them, but here are some details: https://www.accelo.com/resources/help/faq/divisions/

[Trae Dantzler]

We have a similar issue where we are dispatched by say a service company out to a location that they have a contract to maintain. For instance- Company A has a contract to maintain restaurant IT Equipment for a national chain. They partner with us to be their boots on the ground for those restaurants that are in our region. Other than by contract, the companies are not actually affiliated legally. If company A dispatches us to location A to do an Install then its a project and needs all information stored for that project to be associated with that location. However, the bill will go to company A. Same is true of a service call which of course would use a Ticket instead of a Project. In either case, we have multiple parties with a specific Hierarchy that needs to be able to be organized properly but doesn't necessarily always fit that mold. I would love some Ideas on how to make that more transparent within the Parent-Child relationship and even have the documents storage be able to nest accordingly or at least be tagged with specific locations.