Compare the operating models
In this fictional example, Jo is buyer and trainer. Equipment E9 has model, serial and service history, with Jo/Pat as contacts. Duplicating Jo splits identity; storing E9 only on Jo hides the maintained thing.
| Business requirement | Existing contact plus roles | Independent entity |
|---|---|---|
| Jo buyer/trainer | One person, two roles | No second person needed |
| E9 equipment | Not a contact role | Own identity and service links |
| E9’s two contacts | Role per relationship | One E9 linked to both |
Work through the chosen model
First test standard company/product/deal/case objects. Add a custom entity only for independent attributes and relationships. E9 stores serial/model/site and service links; Jo remains one contact.
- Identify person, role or thing
- Check existing object fit
- Link the selected records
Entities add screens, migration and maintenance. HubSpot’s cited custom objects require a qualifying Enterprise plan.
Keep one Jo with two roles and one E9 linked to Jo/Pat. Two contacts do not produce two equipment records.
When the other model fits
Only a Newsletter reader classification is needed. Create a reader object?
Show the worked answer
No independent reader lifecycle exists here; a contact classification suffices.