Your HubSpot CRM is only as useful as the data inside it.
And underneath all of that data are your CRM properties.
Properties are the individual data points that tell HubSpot what you know about a contact, company, deal, ticket, or other CRM object. They might seem like a relatively minor part of your CRM configuration, but they have a huge impact on what your team can actually do with HubSpot.
Well-designed properties make it easier to build useful record views, segment your database, create reports, and trigger automation. Poorly designed properties can lead to inconsistent data, unreliable reporting, and a CRM that becomes increasingly difficult to manage.
That's why CRM property design should be treated as part of your overall data model, not just as an administrative task.
At a basic level, properties are the fields where information is stored in your HubSpot CRM.
Examples might include:
HubSpot also creates many properties automatically when you open an account. These include record creation date, last contacted date, source, and activity-related information.
The important distinction is that some properties should be controlled automatically by HubSpot, while others should be intentionally designed around your organization's processes.
Good CRM properties serve several important purposes.
When someone opens a CRM record, the properties displayed should help them understand the customer or prospect.
Instead of forcing your team to search through notes, emails, and different systems, relevant properties can put important information directly on the record.
You can use properties to create lists and segments.
For example, you might want to identify all companies that:
The better your underlying data, the more useful your segmentation becomes.
Properties also become the dimensions and filters you use in reporting.
You might want to report on revenue, client status, employee count, support activity, or another business-specific data point.
If you don't capture that information consistently, your reports won't be reliable.
Properties can also trigger workflows and other automation.
A change in a property might trigger:
In other words, your properties aren't just storing information.
They're helping HubSpot understand what is happening in your business.
One of the biggest mistakes companies make is creating properties one at a time without thinking about the larger data model.
Someone needs a field, so they create a field.
Then another team needs something else, so they create another.
Eventually, the CRM contains hundreds of properties with unclear names, duplicate concepts, inconsistent values, and little organizational structure.
A better approach is to start by thinking about the information your business actually needs.
What do you need to know about a company?
What do you need to know about a contact?
What information belongs on a deal?
What information should you capture during the sales process?
What information needs to be available after a customer closes?
Answer those questions first.
Then build the properties.
For B2B organizations, company properties are particularly important.
Company information often applies to multiple contacts associated with that company.
For example, a company's:
may be relevant regardless of which individual contact you're looking at.
Other CRM objects can also collect information that ultimately needs to be associated with the company.
A deal might capture information during the sales process that should eventually be reflected on the company's master record.
The same can be true for tickets, projects, and other objects.
Thinking about the company first can therefore provide a useful foundation for designing the broader CRM data model.
As your CRM grows, property management becomes increasingly important.
HubSpot allows you to organize properties into groups.
Groups don't change how a property behaves. They're primarily an organizational layer for CRM administrators.
You might create groups for:
This makes it easier for administrators to find and manage properties as the CRM grows.
When you create a property, decide what kind of data it will store.
The right property type depends on how you'll use that information.
For example, a field that needs standardized options might be better as a dropdown than a free-text field.
A numerical value may need to be formatted as:
Other property types may be more appropriate for phone numbers, dates, or other structured information.
The key principle is simple:
Use the property type to enforce the way your business actually handles the data.
One of the easiest ways CRM data becomes messy is through free-text fields.
Consider something as simple as a state.
If your CRM allows someone to enter a state manually, you could end up with:
Those values may all refer to the same thing, but they aren't necessarily treated as the same value when you're building reports or segments.
A standardized dropdown eliminates much of that ambiguity.
HubSpot also provides preset options for several types of dropdown properties, which can save time when creating standardized fields.
You can also reuse options from an existing property rather than recreating them manually.
HubSpot provides additional controls that can help you enforce data quality.
Depending on the property type, you can configure things such as:
These controls help your CRM reflect your actual business rules.
For example, if every customer has a unique internal company ID, you can configure the CRM to enforce uniqueness rather than relying on employees to remember the rule.
That's a small configuration decision that can meaningfully impact data hygiene.
HubSpot comes with many properties out of the box.
Some are extremely useful because HubSpot automatically maintains their values.
For example:
These properties provide valuable information without requiring your team to maintain them manually.
In general, you don't want humans responsible for information that HubSpot can reliably maintain itself.
At the same time, some default properties may not fit the way your business actually operates.
That can create an opportunity to introduce a more structured custom property.
This is perhaps the most important point.
A good CRM doesn't necessarily have more properties. It has better properties.
Before creating a new field, ask:
If you can't answer those questions, you may not need the property yet.
It's easy to focus on the exciting parts of HubSpot.
Automation.
AI.
Reporting.
Sales forecasting.
Marketing campaigns.
Customer service workflows.
But all of those capabilities depend on the data underneath them.
Your CRM properties are the building blocks.
When you design and maintain those properties thoughtfully and consistently, you can create better record views, segmentation, automation, and reporting.
That's why CRM property management may be one of the least exciting parts of HubSpot — but also one of the most important.
If you're trying to build a CRM that actually reflects how your business operates, start with the data model.
Get the ones and zeros right.
Everything else gets easier from there.