I am part of a start up that is working to prep a marketing campaign. Due to our client base, there is a strong parent to child relationship between entities with very different data descriptors. In order to facilitate managing our data, we have decided to create a custom object that will represent the top tier parent entity, which will have different data points and marketing efforts than the child subsidiaries. Where we are stuck a bit, is how to update the existing data to reflect this new hieararchy. We have a field we can filter on to isolate the company population that we want to move to the new parent object, but have no idea how to initiate this. We also don't want to lose the existing parent to child tagging that exists within the base company object. Help!
Where we are stuck a bit, is how to update the existing data to reflect this new hieararchy. We have a field we can filter on to isolate the company population that we want to move to the new parent object, but have no idea how to initiate this.
What exactly does 'move to the new parent object' constitute? Do you want to create a new custom object record for those company records and keep the company record? If so, a company-based workflow would potentially see the best option: enroll those companies, use the 'Create record' workflow action to create the custom object record, carry over the associations from the company.
If that's not what you mean, could you share more context / details / examples?
Best regards
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
Where we are stuck a bit, is how to update the existing data to reflect this new hieararchy. We have a field we can filter on to isolate the company population that we want to move to the new parent object, but have no idea how to initiate this.
What exactly does 'move to the new parent object' constitute? Do you want to create a new custom object record for those company records and keep the company record? If so, a company-based workflow would potentially see the best option: enroll those companies, use the 'Create record' workflow action to create the custom object record, carry over the associations from the company.
If that's not what you mean, could you share more context / details / examples?
Best regards
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
That actually sounds exactly like what I am trying to do. I want to take the subset of the curent "Company" object and fully migrate them to the new Custom Object that will take the place of "Parent" in the "Parent" to "Child" hierarchy that currently exists in the base "Company" object. I want to do this without losing any of the current contact conections or "Parent" to "Child" relationships. For context, we are M&A consultants, so we engage with private equity investors and their portfolio companies, with most of the actual work being for the portfolio companies, but the connections will come through the investors. So we want to have a seperate "Investors" custom object to contain facts about the investing entity, but not intermix them with the list of actual companies we'd work with. We want to do this without any data loss between both the new custom "Investors" object and the original "Companies" object. Will take a look at the workflow, maybe there is a course that can help. If you have any further suggestions please share, thanks!