How to Create a Property in HubSpot Step by Step

TL;DR

To create a property in HubSpot, first decide which object should own the data, then choose the right field type, create the property, and test it on real records before rolling it out.

If you get the object wrong or choose the wrong field type, you do not just create a messy field. You create reporting friction, weak automation, and poor CRM Discipline.

What is a property in HubSpot?

A property in HubSpot is a field that stores information on a record.

For example:

• a contact can have a job title, email address, or service interest
• a company can have an industry, account priority, or annual revenue
• a deal can have an amount, close date, or estimated commission
• a ticket can have a category, status, or resolution date

Every property belongs to an object. That means the first decision is not the field name. The first decision is where the data belongs.

Why property creation matters more than most teams think

Most teams treat custom properties like a small admin task. It usually starts with a simple request: “We need one more field.”

That is rarely the full story.

A property affects how your team filters records, builds reports, triggers workflows, maintains Pipeline Hygiene, and manages customer information across the CRM. If the property is poorly designed, the damage spreads quietly.

Before you create a property

Before you build anything, check these four things first:

1. Confirm the property does not already exist

HubSpot includes default properties for standard objects. In many portals, teams create custom fields for information that already has a usable home.

Duplicate fields create confusion fast. One team fills in one field. Another team fills in a different one. Reporting splits. Automation breaks. Nobody fully trusts the data.

2. Decide which object should own the data

A simple rule:

• use contact properties for person-specific information
• use company properties for organization-level information
• use deal properties for revenue or transaction information
• use ticket properties for service or issue-related information

If you put the data on the wrong object, the rest of the system becomes harder to manage.

3. Decide how the field will be used

Ask:

• Will this field be used in reports?
• Will this field trigger workflows?
• Will users pick one value or several?
• Will the value be entered manually or calculated automatically?

Your answers should guide the property type.

4. Name the property clearly

The label should make sense to the people using the CRM every day. If the purpose is vague, the property will be used inconsistently.

A clear label reduces friction. A vague label creates interpretation problems that show up later in reports, workflows, and follow-up processes.

How to create a property in HubSpot from Properties

For most admins, this is the most direct way to create and manage properties.

Step 1: Go to Properties

In Settings, open Properties.

Step 2: Choose the right object

Select the object where the property should live, such as Contact properties, Company properties, Deal properties, or Ticket properties.

This matters because the object determines where the field appears and how it can be used in records, filters, automation, and reporting.

Step 3: Create the property

Create a new property and complete the setup details.

At a minimum, you will define:

• the property label
• the object
• the property group
• the field type

Step 4: Choose the correct field type

The field type should match how the business will actually use the data.

Some practical examples:

• Use single-line text for short entries such as branch code or referral source detail.
• Use number for values you want to measure or calculate.
• Use date picker when timing matters.
• Use dropdown select when a user should choose one defined option.
• Use multiple checkboxes when one record can legitimately have several selections.
• Use calculated property when the value should be derived from other fields instead of typed manually.

Step 5: Add options or calculation logic

If you are creating a select-type property, define the options clearly.

If you are creating a calculated property, make sure the formula reflects a real business rule.

Step 6: Save and test the property

After saving, check the property on real records.

Make sure:

• the property appears on the right object
• the label is clear
• the field type behaves as expected
• the values will support the report, workflow, or process you had in mind

How to create a property in HubSpot from Data Model

The Data Model view is useful when you want to create a property while thinking about the wider CRM structure, including objects and associations.

Step 1: Open Data Model

Go to Data Management > Data Model, then click Edit data model.

Step 2: Expand the object you want to update

Select the CRM object and expand its properties so you can review what already exists.

Step 3: Review the existing properties first

Before you create anything new, check what is already there.

HubSpot lets you review existing properties so you do not keep adding new fields for information that already has a home. Most property sprawl does not come from complex CRM architecture. It comes from people creating new fields because they did not stop to check what was already there.

Step 4: Create the property

Click Create property, complete the fields in the right panel, then save it.

Step 5: Finalise the setup

You are still making the same core decisions:

• what the property should be called
• which group it belongs to
• what field type it should use
• whether the field needs options, rules, or calculation logic

The difference is context. Data Model helps you think about the property as part of a wider CRM structure, not just as a standalone field.

Properties vs. Data Model

Both paths work. The better choice depends on what you are trying to do.

Use Properties when:

• you already know which object needs the field
• you want the fastest route to create or edit a property
• you are managing labels, options, validation, or field settings

Use Data Model when:

• you want to see how the object fits into the wider CRM structure
• you are reviewing associations and existing architecture before adding fields
• you are cleaning up or redesigning how data is organized across objects

Who can create a property in HubSpot?

To create a custom property, you typically need permission to edit property settings. Super admins can also create properties.

If the create option is missing, the issue may not be the CRM. It may be access.

Examples of useful HubSpot properties

Example 1: Multiple checkbox property for service interest

Property label: Services of Interest
Object: Contact
Field type: Multiple checkboxes

Use this when one person may be interested in more than one service, such as:

• HubSpot Implementation
• Sales Enablement
• CRM Strategy
• Reporting & Dashboard Development

Example 2: Calculated property for commission tracking

Property label: Estimated Commission
Object: Deal
Field type: Calculated property

A calculated deal property can be used to derive an estimated commission value from fields such as deal amount and commission ratio.

Example 3: Dropdown property for company priority

Property label: Account Priority
Object: Company
Field type: Dropdown select

A controlled dropdown works well when the business needs one defined classification per company, such as:

• Healthy
• Watchlist
• At Risk

Common mistakes when creating properties in HubSpot

Creating duplicate properties

You create a new field for information that already exists somewhere else.

That usually leads to split reporting, inconsistent filtering, and weak automation because different users choose different fields for the same information.

Putting data on the wrong object

A company-level fact gets stored on the contact. A deal-level fact gets stored on the company. A service issue ends up on the deal.

That is not a small setup mistake. That is a reporting and automation problem waiting to happen.

Choosing the wrong field type

If you use free text where a controlled dropdown should exist, reporting becomes messy.

If you use multiple checkboxes when the business process requires one clear answer, you create ambiguity.

If you use text instead of a number or date, you make calculations harder than they need to be.

Creating properties before defining the process

If you have not defined how the team qualifies leads, tracks handoffs, or measures a stage outcome, creating new properties will not fix that.

The property will simply mirror the underlying operational confusion.

FAQ: Creating properties in HubSpot

What is the difference between a default property and a custom property in HubSpot?

A default property is created by HubSpot and comes built into the platform. A custom property is one your team creates to store information specific to your process, reporting, or customer journey.

Should I create a new property or use an existing one?

Start by checking whether a usable property already exists. If the information already has a clear home, use it. Creating a duplicate field usually creates friction instead of clarity.

What is the difference between an object and a property in HubSpot?

An object is the category of record, such as a contact, company, deal, or ticket. A property is the field that stores information on that record.

Which HubSpot object should own a property?

The object should match where the information is actually true. If the data describes a person, use a contact property. If it describes a company, use a company property. If it describes a transaction, use a deal property. If it describes a service issue, use a ticket property.

Why does property setup affect reports and workflows?

Because properties are part of the structure of your CRM data. Reports, workflows, segmentation, and record management all depend on the quality and design of those fields.

When should I use multiple checkboxes in HubSpot?

Use multiple checkboxes when one record may need more than one value selected at the same time.

When should I use a calculated property in HubSpot?

Use a calculated property when the value should be based on other fields instead of being entered manually.

Final checklist before you save

Before you create any new property, make sure you can answer these three questions clearly:

1. What information are we trying to capture?
2. Which object should own it?
3. How will this field be used after it is created?

If those answers are clear, the property setup usually becomes much easier.