The most expensive mistake in HubSpot is using Deals to model something that isn’t a deal. Subscriptions, projects, assets, vehicles, properties. Teams bend the standard object until reporting becomes guesswork. The right answer is sometimes a custom object, sometimes not. Here’s how to decide.
The four-question test
Before creating a custom object, answer:
- Does this entity have a lifecycle independent of a Deal? (Renewals, projects)
- Will users associate multiples of this to a single Contact or Company?
- Does it need its own pipeline or stage logic?
- Will reporting need to count and segment these distinctly?
Two or more yeses, build a custom object. One yes, force-fit a property or line item.
What standard objects handle just fine
A subscription with a single renewal date and one owner can live as a Deal in a Renewals pipeline. A simple service request can live as a Ticket. A customer reference can live as a Contact property. Don’t reach for custom objects to feel sophisticated.
What standard objects can’t handle
Insurance policies (one customer, many policies, each with unique coverage and renewal). Real estate listings (one agent, many properties, each with its own viewings). Service contracts where one company has 30 SLA-tracked agreements. These need custom objects or your reporting will lie.
The hidden cost of custom objects
Custom objects don’t get the full feature surface. Sequences won’t enroll based on custom object properties without workflow plumbing. Some integrations skip custom objects entirely. Native lead scoring ignores them. Budget for the gaps.
The schema discipline that matters
When you do build a custom object, declare singular and plural names carefully:
objectTypeId: 2-12345678
name: policy
labels: { singular: "Policy", plural: "Policies" }
primaryDisplayProperty: policy_number
secondaryDisplayProperties: ["policy_status", "renewal_date"]The display properties drive every right-rail card. Get them wrong and reps won’t trust the data.
Associations are the whole game
A custom object’s value comes from its associations to standard objects. Define labeled associations from day one (Policy Holder, Beneficiary, Broker). Unlabeled associations turn into noise within six months.
What to do this week
Audit your Deal pipeline. If you have stages that exist only to model a non-deal entity (e.g., “Active Subscription,” “Renewed”), you’ve outgrown the standard object. Spec the custom object before next quarter’s reporting cycle.
