Skip to content
ancilAn INSIDEA company
HubSpot glossary

What are custom objects in HubSpot?

A custom object is a record type you define in HubSpot to store data that the standard objects, such as contacts, companies, deals and tickets, do not fit. It has its own properties, associations and records, and can be used in lists, workflows and reports like a standard object.

Standard objects cover most sales, marketing and service needs, but many businesses track something else: properties a real estate firm manages, vehicles a fleet company services, enrollments a school processes, or locations a franchise runs. A custom object gives that thing its own records instead of squeezing it into a contact or company property. Custom objects are available depending on your subscription, usually at Enterprise level.

When you create a custom object you define its schema: its name, a primary display property, which properties are required, which are searchable, and which other objects it can associate with. These choices are hard to change later, so they deserve planning. A custom object with no associations is an island, and one with no searchable properties is hard to find.

Before building one, ask whether a property, an association label or a standard object would do the job. Custom objects are the right choice when the thing has its own lifecycle, many records per contact or company, or its own properties that would otherwise clutter another object.

Treat custom objects as part of your data model. Document what each one represents, who owns it, which integration writes to it, and how it associates with contacts, companies and deals.

Example

A property management firm stored each building as a company record, which mixed buildings with real client companies. They created a Property custom object with address, unit count and status, associated it with owner contacts and with service tickets, and could finally report on tickets per building.

Common mistakes

  • Creating a custom object for data that a simple property or association label would handle.
  • Leaving the object without associations to contacts, companies or deals, so records cannot be reported on in context.
  • Choosing a primary display property that is not unique or meaningful, which makes records hard to tell apart.
  • Building several objects that overlap in meaning because nobody owned the data model.

Related checks

Frequently asked questions

When should I use a custom object instead of a property?

Use a custom object when the thing has its own records, properties and lifecycle, or when one contact or company can have many of them. Use a property when it is a single fact about an existing record.

Can custom objects be used in workflows and reports?

Yes, depending on your subscription and the tool. Custom objects can generally be used in lists, workflows and reports, which is a main reason to use them instead of storing data in notes or text fields.

Related terms

See how your portal measures up.

Ancil connects to HubSpot read-only in about 60 seconds. Nothing changes in your portal without your approval.