Custom Objects are one of the features that make people seriously consider HubSpot Enterprise - and one of the clearest lines in HubSpot’s pricing that never seems to move.

The short version: if you are on Professional, you do not have them. On Starter or Free, definitely not. Only Enterprise portals can create and use Custom Objects, and the same is true of every workflow, list, or report that sits on top of one.

What HubSpot subscription do I need for Custom Objects?

You need Enterprise on at least one Hub.

HubSpot’s documentation is direct: “An Enterprise subscription is required to use custom objects.” The Create and edit custom objects article lists the qualifying subscriptions:

• Marketing Hub Enterprise
• Sales Hub Enterprise
• Service Hub Enterprise
• Data Hub Enterprise (formerly Operations Hub)
• Content Hub Enterprise
• Commerce Hub Enterprise
• Smart CRM Enterprise

One Enterprise seat on any of those Hubs unlocks Custom Objects across the whole portal. You do not need Enterprise on every Hub - just one.

What does not qualify: any Professional, Starter, or Free tier on any Hub. The Smart CRM Starter plan includes a line about “storing almost any type of data”, which gets read as Custom Object access by people skimming the pricing page. It is not. The Smart CRM wording refers to HubSpot’s standard objects and custom properties on them, not Custom Objects as a feature.

Why Professional does not include Custom Objects

This is one of HubSpot’s clearest tier gates and it has not moved in years. No Spring 2026 Spotlight change, no announced roadmap shift, no new Professional tier access. The community idea thread for “Custom Objects for Professional plans” is still open without an official commitment.

The structural reason: Custom Objects touch every part of the portal. They need workflow support, list support, report support, API support, Data Model Builder access, association handling, and Marketing/Content Hub surfaces. Gating each of those individually would be messy. Gating the underlying feature to Enterprise keeps the tier story clean.

From a practical point of view, if you are shopping tiers, it helps to know exactly what you unlock and what you do not.

Can I use Custom Objects in HubSpot workflows on Professional?

No. This is one of the cleanest gates in HubSpot’s product.

HubSpot’s workflow object types article lists Custom Object workflows under Enterprise Only, alongside Goals. Every other workflow object type available on Professional is a standard object.

What Professional portals do get for workflows:

All Hubs (Pro and Enterprise):

• Contact-based workflows
• Company-based workflows
• Deal-based workflows
• Conversation-based workflows
• Subscription-based, Payment-based, Invoice-based, Quote-based workflows
• Task, Call, Project, Goal, User, Media workflows

Hub-specific (Pro and Enterprise):

• Leads workflows (Sales Hub Professional+)
• Ticket workflows (Service Hub Professional+)
• Feedback submission workflows (Service Hub Professional+)
• Campaign workflows (Marketing Hub Professional+)

Enterprise only:

• Custom Object workflows
• Goal workflows with custom object scope

The downstream effect matters more than the list. Workflows that can run on Custom Objects, or create/update them from a contact or deal workflow, all require Enterprise. So does the “Create custom object record” action inside a parent-object workflow.

What can I do in Professional without Custom Objects?

Three realistic workarounds. None of them is a true Custom Object, but between them they cover a lot of ground.

Custom association labels on standard objects

Available on Professional and Enterprise. HubSpot documents that “in accounts with a Professional or Enterprise subscription, you can create custom labels.”

This is the workaround people reach for most. Instead of building a Custom Object to represent a relationship type (like “primary decision maker” or “renewal owner”), you add a labelled association between two standard objects. You lose the ability to store data specific to that relationship on its own record, but you can model the structure of the relationship.

Custom properties on standard objects

Professional portals can add custom properties to Contacts, Companies, Deals, and Tickets. For many use cases that people assume need Custom Objects - tracking contract start/end dates, licence counts, renewal owners - a handful of custom properties on the Deal record does the job.

Where this falls over: when you need a one-to-many relationship and the child side needs its own lifecycle. A deal has one close date. A contract has many renewal events. Custom properties on Deals cannot model that cleanly; you end up with pattern-named properties like renewal_1_date, renewal_2_date, and the schema gets ugly fast.

Custom reports on standard objects

HubSpot’s custom report builder is available from Professional upward. You can report across Contacts, Companies, Deals, Tickets, and their properties, build funnel and attribution reports, and expose everything your team needs to see - without ever touching a Custom Object.

Reports that require joining to a Custom Object, of course, need Enterprise to exist.

When is the upgrade to Enterprise worth it for Custom Objects?

A few genuine signals:

You are stuffing a 1:many relationship into Deal properties. If you have named things subscription_1_id, subscription_2_id, renewal_1_date, you have outgrown what Deals can model. Custom Objects are the right shape.

You are running multi-product or multi-contract accounts. Each product or contract needs its own lifecycle, owner, end date, and history. Custom Objects give every one of those records a proper home.

You need to report across the “child” side. “How many contracts closed this quarter” is different from “how much closed-won revenue this quarter”. Reports over children need the children to be first-class objects.

You are hitting the association limits of your current model. Standard objects have association types and limits; when you need a particular relationship to carry its own data, you need a Custom Object.

The inverse is also true: if your team is thriving on Contacts + Companies + Deals and never hits the shape-of-data problems above, Enterprise is a lot of money to spend for Custom Objects you do not need.

Designing Custom Objects faster once you are on Enterprise

If you have already made the call and you are on Enterprise, the problem shifts.

Custom Objects take a while to design well. The schema choices (properties, associations, pipeline stages, lifecycle), the workflows that sit on top, the lists that drive reporting - all of it is configurable, and all of it is slow to build click-by-click through HubSpot’s UI.

This is where AI-assisted configuration helps. Daeda AI’s Plan Mode lets you describe the Custom Object and its supporting workflow/list structure in conversation, reads your live portal to avoid duplicates and collisions, and drafts a complete execution plan you can review top to bottom before anything touches production. The plan document becomes your own documentation - shareable, replayable on another portal when the next reorg lands.

Previous coverage: Plan Mode 200 clicks to 2, and how Custom Objects fit the automation picture.

Not every team needs this. If you are building two Custom Objects for a team of five, the clickthrough path is fine. If you are building across multiple portals, or inheriting a tangled production portal, the time maths changes.

FAQ

You can also see what Daeda AI adds on top of HubSpot Enterprise or browse the full Daeda AI hub.