What This Update Actually Is
Lookup Properties are a brand-new property field type inside HubSpot's CRM. Instead of storing a text string, number, or date, a Lookup Property stores a reference to another CRM record.
In practice, it works like this: an admin creates a Lookup Property on, say, a Deal. They configure it to reference a Contact object using a custom 1:1 labeled association. From that point on, reps see a dropdown on the Deal record. They pick the related Contact directly from the property field, no associations panel required.
One important caveat to know upfront: this release only supports 1:1 custom association labels. Many-to-many relationships and default HubSpot association types aren't in scope yet. If you need to map a relationship where one record connects to many others, this specific field type won't cover that case right now.
Why HubSpot Shipped This
Here's the real friction this solves. HubSpot has always had two ways to capture relationships between records: properties for data, and associations for connections. Those two systems don't talk to each other in a way that feels natural to most humans working inside a portal every day.
A rep editing a Deal record has to know: "Is this thing I need to capture a property or an association?" That's a CRM architecture question, not a sales question. It creates errors. It slows adoption. Admins end up fielding the same support question on loop.
Lookup Properties collapse that distinction. Admins configure the relationship the same way they configure every other property. Reps see a dropdown they already know how to use. The relationship data now lives in the properties framework, which means it's queryable, filterable, and reportable exactly like any other property.
How to Use It Step by Step
Admins set up Lookup Properties from the standard Properties settings page. Here's the exact path:
- Go to Settings > Properties.
- Select the object you want to add the Lookup Property to (for example, Deals or Tickets).
- Click Create property.
- Enter a property label that will make sense to the humans filling it in.
- Under Field type, select Lookup.
- Under Associated object, choose the CRM object type you want to reference. Remember: this must be based on an existing custom label with a 1-to-1 limit.
- Enter a label for the association under New association label.
- Click Create property.
Once out of beta, Lookup Properties will be on by default. No opt-in required. The property shows up on record pages as a standard dropdown, so reps don't need any extra training to start using it.
What It Touches in Your HubSpot Strategy
This isn't a small cosmetic change. Lookup Properties ripple into almost every layer of how you structure and use your CRM data. Here's where you'll feel it.
Record pages: Reps see and fill in the relationship directly on the record. No detour to the associations panel.
Lists and views: You can now filter and segment records based on which related record is referenced in a Lookup Property. That's a meaningful jump in list-building flexibility.
Workflows: Lookup Properties are available as workflow triggers and conditions, which opens up automation paths that previously required workarounds or custom code.
Reports: Because this relationship now lives as a property, you can include it in report filters and breakdowns. That gives RevOps teams cleaner data slices without building complex cross-object custom reports from scratch.
Forms: Lookup Properties surface in forms, which means you could expose relationship selection to the humans submitting the form, not just the admins and reps inside HubSpot.
If your team has been building out association logic to keep activity history clean, this pairs well with HubSpot's auto-association updates for Contracts, Orders, and Marketing Events. Together, they push CRM data quality in the same direction: less manual work, more structured relationships.
Key Takeaway
Lookup Properties don't replace associations. They add a property-layer interface on top of a specific type of association (1:1 custom labeled). Your existing association data and architecture stays intact.
Key Takeaway
If you have custom objects or complex object models, Lookup Properties are worth auditing now. The relationships you've been capturing through workarounds or free-text fields may have a cleaner home here.
Sales teams building tighter record linkage across the pipeline will also want to look at Sequence Task Associations, which auto-link tasks to every related record. It's a different mechanism, but the underlying goal is the same: reduce the gaps between CRM records so nothing falls through.
Who Should Care Most
Not every HubSpot update hits every team equally. Here's where this one lands hardest.
- HubSpot admins managing complex CRM architectures who've been maintaining both properties and association setups separately. This reduces the cognitive load and the maintenance surface.
- RevOps leaders who want relationship data to show up cleanly in reports and workflow logic without writing workaround formulas or layering on extra automation steps.
- Sales and service managers struggling with rep adoption. If your team keeps missing the associations panel, a familiar dropdown on the record page solves the behavior problem at the source.
- Companies using custom objects or those with non-standard CRM structures where relationships between objects are core to how the business runs, not just a nice-to-have.
If you're on a Free or Starter plan, this one isn't available yet. All tiers that get Lookup Properties start at Professional.
George's Take
We've audited a lot of HubSpot portals, and one of the most common pain points we see is this exact split: admins who understand associations, reps who don't use the associations panel, and a gap in between where important relationship data just disappears. Lookup Properties feel like HubSpot finally closing that loop in a way that respects how humans actually work inside a CRM, not how CRM architects think they should work. The 1:1 limitation is real and worth planning around, but don't let that stop you from identifying which relationships in your portal deserve to be Lookup Properties right now. Start there, build the habit with your team, and be ready to expand when HubSpot broadens the scope.
“Admins who understand associations and reps who never use the associations panel are two different problems. Lookup Properties solve both at once.”
While you're thinking through how data shows up for your team, it's worth noting that inline report descriptions on HubSpot dashboards are another recent change that helps humans understand what they're looking at without extra hand-holding from admins.
If your CRM architecture needs a fresh set of eyes, or you want help mapping which relationships in your portal are ready for Lookup Properties, that's exactly the kind of work we do at Sidekick Strategies. Book a strategy call and let's look at your portal together.
Frequently Asked Questions
What are HubSpot Lookup Properties?
Lookup Properties are a new property field type in HubSpot that lets you reference another CRM record as the value of a property. Instead of using the associations panel, reps select the related record from a standard dropdown directly on the record page. They're currently available for 1:1 custom labeled associations only.
How are Lookup Properties different from regular HubSpot associations?
Regular associations live in their own panel and require users to know the association exists. Lookup Properties surface that same relationship inside the properties framework, so it shows up on record pages, forms, lists, workflows, and reports just like any other property. It's the same underlying connection, but with a much more accessible interface.
What HubSpot plans include Lookup Properties?
Lookup Properties are available on Professional and Enterprise tiers across Marketing Hub, Sales Hub, Service Hub, Content Hub, Smart CRM, Revenue Hub, and Data Hub. They're not available on Free or Starter plans.
Can Lookup Properties be used in HubSpot workflows and reports?
Yes. Because Lookup Properties live in the standard properties framework, they're available as triggers, conditions, and filters in workflows, lists, and reports. This is one of the biggest advantages over the associations panel, which isn't directly queryable in the same way.
What's the current limitation of HubSpot Lookup Properties?
The current release only supports 1:1 custom association labels. You can't use Lookup Properties for many-to-many relationships or for HubSpot's default association types yet. HubSpot has indicated broader support is planned as the feature moves out of beta.
Do I need to opt in to use HubSpot Lookup Properties?
No opt-in is required. Once Lookup Properties are out of beta, they'll be on by default for all eligible portals. Admins create them from Settings > Properties the same way they'd create any other property, selecting Lookup as the field type.
