HubSpot custom objects: when you need one and when you do not

Custom objects are powerful and easy to overuse. The wrong choice creates a data model your team quietly abandons.

The test

Create a custom object when the entity has all four of these traits: it has its own lifecycle, it can relate to many contacts or companies, it needs its own properties and reporting, and it exists independently of a single sales cycle.

If any of those is false, a property, a line item or a second pipeline is usually the better answer.

Good candidates

• Construction and engineering: project or tender — multiple contacts, its own milestones, reporting by project margin.
• Logistics: shipment or vessel — recurring events tied to one customer, with operational properties.
• Aviation and travel: aircraft or itinerary — long lifecycle, many stakeholders.
• Real estate: listing or unit — inventory that outlives any single buyer deal.
• eCommerce and subscription: subscription or contract term — renewal reporting independent of the original order.

Bad candidates

• A quote — use deals and line items.
• A meeting or site visit — use activities.
• A product variant — use the product library.
• A stage of an existing process — use a pipeline stage or a property.
• Anything created once, populated by hand, and never reported on.

Design rules that keep it usable

Define the associations before creating properties. Keep property count low and every property mandatory or reportable — optional free-text fields are where custom objects go to die. Decide the record naming convention so records are searchable by humans.

Automation and permissions

Custom objects can trigger and be updated by workflows; use that to keep operational status in sync with sales reality. Set team permissions explicitly, especially when the object holds commercial or client-confidential data.

Report from day one

Build at least two reports before rollout: one operational (status distribution, ageing) and one commercial (revenue or margin by record). If neither is possible, you did not need the object.