Quick answer: Use a HubSpot custom object when you need to track a business entity that no existing HubSpot object can hold. Before building one, check HubSpot's data model: Services, Listings, Appointments and Courses can be activated by a Super Admin without an Enterprise subscription. Custom objects require Enterprise. Loncom Consulting, a HubSpot Diamond Solutions Partner, helps B2B teams make that call before they build.
Most HubSpot portals don't run out of objects. They run out of room on the objects they already have.
You can spot it on a single record: properties called Product 1 Serial and Product 2 Serial, renewal dates kept in a spreadsheet, a single Training Date field overwritten every time a contact attends another session. The data model has outgrown the standard objects. But the fix isn't always a custom object. This guide shows how to tell what you need, what to check first, and how to build without creating a new data quality problem.
When Should You Use Custom Objects in HubSpot?
Use a custom object when what you are tracking is a thing, not a field. A field describes a record, such as a company's contract end date. A thing has its own lifecycle, can exist more than once per record, and needs its own history. Fields belong in properties. Things belong in objects.
HubSpot itself draws a clear line here. Its own guidance warns that a custom object shouldn't replicate an existing CRM object, such as separate objects for parents and teachers who are all contacts, or replace activities. HubSpot automatically sets up associations between custom objects and emails, meetings, notes, tasks, calls and conversations, so activities can be logged against custom object records.
Want an expert review of your HubSpot data model?
Explore HubSpot CRM Audit
Before You Build: Does HubSpot Already Have the Object You Need?
Often, yes. As of October 2026, subscriptions, orders and carts are built-in HubSpot objects, and Services, Listings, Appointments, Courses and Projects, sometimes called HubSpot's object library, sit switched off until a Super Admin activates them.
HubSpot's setup guide asks the same thing: can you use an existing CRM object instead? It also won't let a custom object share a name with a HubSpot-defined object.
| What you want to track | HubSpot object | How you get it |
|---|---|---|
| Recurring payments and subscriptions | Subscriptions | Built-in HubSpot object |
| Confirmed purchases from ecommerce | Orders | Built-in (often synced from ecommerce) |
| Onboarding, consulting, repairs, maintenance | Services | Activated by a Super Admin |
| Properties or units to buy, sell or rent | Listings | Activated by a Super Admin |
| Encounters or services booked for an individual | Appointments | Activated by a Super Admin |
| Training programmes and course enrolments | Courses | Activated by a Super Admin |
| Project delivery and project tasks | Projects | Activated by a Super Admin |
| Anything unique to your business | Custom object | Built by a Super Admin (Enterprise) |
Object availability and some features depend on your HubSpot subscription, so check your account's data model before planning around a specific object.
To activate one, go to Data Management, then Data Model, open the Manage tab and click Activate object. According to HubSpot's data model documentation, it can then be used in workflows and segments.
If a native object covers most of what you need, extend it with custom properties instead of building from scratch.
How Do You Know Standard HubSpot Objects Aren't Enough?
When the data model is under strain, it shows up as workarounds everyone has quietly accepted. These are common patterns in HubSpot portals.
| Symptom | Fix |
|---|---|
|
!Numbered properties (Product 1, 2, 3)
|
✓One record per item in an object
|
|
!Same values retyped on many records
|
✓Create the entity once, then associate it
|
|
!A spreadsheet next to the CRM
|
✓Activate or build an object, then import
|
|
!Only the latest value survives
|
✓Store each event as its own record
|
|
!Integration data with nowhere to land
|
✓Use a custom object as the landing zone
|
|
!Hundreds of unexplained properties
|
✓Audit and move groups into an object
|
Integrations make this urgent. When an ERP sends contracts or assets into HubSpot with no object to map to, the data gets squeezed into company or deal properties and the numbers stop reconciling, as we cover in why CRM-ERP integrations fail. The same question applies to connected tools such as Jira (see our HubSpot Jira integration comparison) and to migrations: in our Attio to HubSpot migration guide, list entries that carry their own data need a home before anything is imported.
HubSpot Custom Object Examples by Industry
Typical starting points, with the standard objects each one connects to:
| Industry | Custom object | Associated with |
|---|---|---|
| Manufacturing | Equipment or installed assets | Companies, Tickets |
| Renewables | Sites or installations | Companies, Deals, Tickets |
| Tech and SaaS | Licences or environments | Companies, Deals |
| Education | Applications | Contacts (consider the native Courses object for programmes) |
| Ecommerce and retail | Warranties | Contacts, Companies |
| Media and events | Sponsorship packages | Companies, Deals |
What to Know Before You Commit
Custom objects can be used in marketing emails, workflows and reports. But a few rules catch teams out after the build, when changes are expensive.
- Associations come first. HubSpot's knowledge base notes that for custom objects, you must configure association settings before records can be associated.
- Workflows depend on those associations. According to HubSpot's workflow documentation, a workflow can only create custom object records if the custom object is associated with the workflow's object type.
- Undoing a build is slow. HubSpot's developer documentation states that a custom object can only be deleted after all of its records, associations and properties have been deleted.
Missing associations are also a common reason workflows misfire, as we explain in why HubSpot workflows stop triggering. And once the object exists, decide who can see and edit its records. Our guide to HubSpot permissions and user roles explains why records end up exposed or locked.
How Do You Plan a HubSpot Custom Object Without Breaking Your Data?
A custom object is a structure you will live with for years. Planning it takes an afternoon. Rebuilding it takes a project.
- Define the entity in one sentence. If you can't say what one record represents, it is probably a property, not an object.
- Give every record a unique identifier. When you create the object, HubSpot lets you require unique values on the primary display property, so users can't enter the same value twice.
"Contacts have an email address and companies have a domain, but most custom objects have no natural name at all. That's why the first thing we define is a unique identifier, something as simple as APP-0001 for an Application object. Without it, you can't stop duplicates, you can't match records coming in from other systems, and you can't trust the reports built on top of them," says Stefan Loncar, CEO of Loncom Consulting.
- Map associations before loading data. Decide what it connects to, which labels you need, and whether a record links to one company or many.
- Match field types to the systems that feed it. Workflows only copy values between compatible property types, so keep dates as dates and dropdowns as dropdowns.
- Decide who owns the data. Agree who creates and updates records, and how. Our CRM data quality framework includes an ownership model you can reuse.
- Test with a small import. Load a sample, check associations, reports and workflows, then migrate the rest. For a real migration example, see our Mailchimp to HubSpot migration guide.
HubSpot's Breeze Assistant can now create a custom object from a plain request such as "Create a jobs object". That speeds up the build, not the planning.
Bottom Line
The costliest data models aren't the ones missing a custom object. They're the ones where one was built too early, duplicated something HubSpot already had, or went live without an identifier and associations. Get the structure right and reporting, automation and integrations follow.
That's why our HubSpot implementation and optimisation work starts by mapping your processes and data architecture before anything is built.
In Short
HubSpot custom objects track entities that standard objects can't hold, and they require Enterprise. Check first whether a property, an association label or an activatable HubSpot object solves the problem. If you build, set a unique identifier and configure associations before loading data.
Not sure whether your HubSpot needs a custom object?
Book a Free Consultation
FAQ
What is a custom object in HubSpot?
A custom object is an object you define yourself for data that doesn't fit contacts, companies, deals or tickets, such as equipment or applications. It has its own records, properties and associations.
Do you need HubSpot Enterprise to use custom objects?
Yes. Creating custom objects requires an Enterprise subscription. HubSpot's activatable objects, such as Services and Listings, have no Enterprise requirement.
How do I create a custom object in HubSpot?
With Super Admin permissions, go to Data Management, then Data Model, open the Manage tab and click the plus icon next to All objects. Add the object details, then click Create.
What is the difference between a custom object and a custom property?
A custom property stores one value on a record, such as a renewal date. A custom object stores a separate entity that can exist many times per record, such as several pieces of equipment linked to one company.
Can Loncom help?
Yes. Loncom Consulting is a HubSpot Diamond Solutions Partner with 150+ CRM implementations. We review your data model and build the right structure, from a property to a custom object, with identifiers and associations planned from day one.
Share:
Leave a comment