On this page
What HubSpot supports natively
A custom object is a new record type, with its own properties, associations and, optionally, pipelines. HubSpot’s rules:
| Topic | What HubSpot says |
|---|---|
| Subscription | Enterprise tier of Marketing, Sales, Service, Data, Content Hub, Smart CRM or Revenue Hub |
| Permissions | Account access permissions to create, edit and manage custom objects |
| Where | Data Management > Data Model > Edit data model, then add a custom object |
| Required setup | Singular and plural names and a primary display property, which names each record |
| Fixed after creation | The internal name |
| Limits | Depend on the subscription; shown on the Limits tab of the data model |
| Deleting | Can’t be restored, and blocked while other tools use the object |
HubSpot also asks you to check first whether an existing object and its properties can hold the data. It gives two examples of misuse: creating “Parents” and “Teachers” objects instead of contacts with a contact-type property, and building a “Notes” object instead of using activities.
Custom object, property or association label?
| You need to track | Use | Example |
|---|---|---|
| A fact about one contact, company or deal | Property | Contract renewal date on a company |
| A type of person or company | Property on the existing object | Contact type: Parent, Teacher, Partner |
| How two existing records relate | Association label | Contact is the Billing contact for this company |
| A thing that has many instances per company or contact, each with its own data | Custom object | Shipments, subscriptions, vehicles, properties for sale |
| A thing that moves through stages independently of deals | Custom object with a pipeline | Onboarding projects, applications |
| A one-off interaction | Activity (note, task, call) | Site visit notes |
A quick test: if you’d otherwise create numbered properties (Vehicle 1 make, Vehicle 2 make), you need an object. If each record would only ever have one value, a property is enough.
How to set up a custom object well
- Write down the relationships first. Which standard objects does it associate with, and how many on each side? Map it in the data model overview.
- Pick a stable internal name. It can’t change later, and integrations will use it.
- Choose a primary display property people recognise, such as an order number or a policy name.
- Add only the properties you’ll report on at launch. More can come later.
- Create associations and labels before importing records, so the import can link them.
- Add a pipeline only if the object really moves through stages.
Where Jetstack AI fits
To set up a new custom object, use Jetstack AI’s Projects. Describe the object, its properties, association labels and pipeline in a brief; Jetty, the Projects assistant, turns it into a plan you approve, builds the object before anything that depends on it, and deploys after a separate approval, with a receipt checked by reading each asset back from HubSpot. Projects is currently in limited release; see what Projects can build. To reuse an object you’ve already designed in another portal (see copying custom objects), Portal reuse imports the full schema with its pipelines and user-defined association labels, deploys the object before anything that depends on it, and reuses a matching object if the destination already has one. See how custom objects are deployed.
Sources
- Create custom objects (HubSpot Knowledge Base)
- Track CRM data limits (HubSpot Knowledge Base)
- Custom objects (Jetstack AI documentation)
Checked October 29, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.
HubSpot admin
Turn the brief into approved HubSpot assets.
Projects plans the build against the client portal, generates the assets and deploys them only after you approve.
Explore Projects