HubSpot has standard objects for contacts, companies, deals and tickets. But sometimes they are not enough. A real estate company has properties, a SaaS company has licenses, a training company has course dates. Then custom objects can be the solution. But they are not always the right answer.
In short: Custom objects let you model data that does not fit HubSpot's standard objects, such as properties, subscriptions or machines. They require Enterprise. Before you create a custom object, check whether a property, an association or one of HubSpot's newer standard objects is enough.
A custom object is a new type of record in HubSpot with its own properties, its own pipeline if you want, and associations to contacts, companies, deals and other objects. It works in lists, reports and workflows just like the standard objects.
Many create custom objects unnecessarily. Ask yourselves first:
Custom objects are your own types of records in HubSpot with their own properties and associations, for data that does not fit the standard objects contacts, companies, deals and tickets.
In HubSpot's new pricing model, custom objects are included from Professional. On older hub-based subscriptions they require Enterprise.
Yes. Custom objects can be used in custom reports, lists and workflows just like standard objects.
There are limits on the number of objects, properties and records that depend on your edition. See HubSpot's technical limits for current numbers.
No. A custom property is a field on an existing object. A custom object is an entirely new type of record with its own fields and associations.
Custom objects are powerful when your business has data that does not fit HubSpot's standard objects. But they add complexity, so first check whether a property or a standard object is enough.
Wondering what your data model in HubSpot should look like? Get in touch with LeadLabs, CRM architecture is one of our specialties.