HubSpot lookup properties make relationships usable

HubSpot's new lookup property turns one labeled, 1-to-1 association into a field. That changes more than the record page. It lets a specific relationship, such as "original deal" or "primary contact," enter the forms, segments, workflows, reports, and views that admins already build around properties.

What is a HubSpot lookup property?

A HubSpot lookup property references another CRM record as its value. It is built on an existing custom association label, so the value is still a real relationship between records. The difference is that users can select and see that related record through a property field.

HubSpot already lets admins use association labels in segments, workflows, and custom reports. A label explains the relationship: a contact is the decision maker for a deal, one company is the headquarters of another, or one deal is an amendment of another. The lookup property gives one of those labeled relationships the familiar surface of a property.

The feature is currently in beta and supports 1-to-1 lookups. That limit is useful. It forces an admin to decide whether a relationship has one valid answer or a set of valid answers.

A relationship becomes useful when its role is explicit

An ordinary association answers, "Which records are connected?" A labeled association answers, "What does each connection mean?" A lookup property answers, "Which one record plays this role?" Those are different questions, and a clean HubSpot data model needs all three.

Business question	Best model
Which contacts are involved in this deal?	A contact-to-deal association
Which contacts are decision makers or billing contacts?	Labeled contact-to-deal associations
Who is the single primary contact for this deal?	A lookup property built on a 1-to-1 label

This is why the beta matters. CRM users spend most of their day reading and editing fields. Workflows, views, forms, and reports also start from fields. When one relationship has an operational role, exposing it as a property removes the translation step between "these records are related" and "this is the record the process needs."

One live HubSpot build shows the boundary

We built an in-HubSpot deal-creation flow for a professional services company that manages every engagement as a deal. Change orders and renewals were created as new deals, but the CRM did not reliably connect them to the work they continued. A legacy renewal stage also assigned an 85% win probability before the team had made that judgment.

For a change order, the relationship had one clear answer: the original deal being amended. We created a labeled "amendment of" association and made the original deal selectable during creation. A lookup property is a natural fit for that model. The user needs one field called "Original deal," and automation needs the same unambiguous reference.

The renewal flow exposed the limit. One renewal could combine several prior deals and selected line items from each. A 1-to-1 lookup cannot represent that honestly. Those source deals must remain a set of labeled associations. Flattening them into one property would throw information away.

The lesson from that build is simple: cardinality comes before interface. Decide how many related records can be true, then choose how HubSpot should expose the relationship.

Use the smallest model that tells the truth

Choose the data type by asking what the value represents. The record page should make the correct model easy to use, but convenience should not change the model.

Use	When it fits	Example
Ordinary property	The value is a fact about the current record.	Renewal type or anticipated close date
Lookup property	One other CRM record fills one named role.	Original deal or primary contact
Labeled association	Several related records may fill the same or different roles.	All decision makers or all deals included in a renewal

A lookup should not duplicate a relationship in a text field. If the value is another HubSpot record, keep the association as the source of truth and let the lookup expose it. That preserves the connection and its label instead of creating a second value that someone must keep synchronized.

Check four things before creating a lookup property

A good lookup starts with a stable relationship rule. Before adding one, test the model against four questions:

1. Can you name the role in the singular, such as "original deal" or "primary contact"?
2. Can only one related record hold that role at a time, including edge cases?
3. Does the association label already describe the relationship in language users understand?
4. Will a form, segment, workflow, report, or custom view become clearer when that relationship appears as a field?

If the second answer is uncertain, keep the labeled association. "We usually have one" is not the same as a 1-to-1 rule. The first exception will either block valid data or push the team back to notes, copied IDs, and other workarounds.

Start with one relationship that people currently have to interpret by opening association cards. Set the label and its limits, test existing records for conflicts, and then expose the lookup where the team already works. A small migration makes the behavior easier to validate than a portal-wide redesign.

The dropdown is only the visible part

Lookup properties close a long-standing gap between HubSpot's properties and associations. Their value comes from making one relationship explicit enough for users and automation to act on it without guessing.

Keep the distinction sharp: properties describe a record, associations connect records, labels explain the connection, and lookups expose one named connection as a field. If you are redesigning a HubSpot data model around renewals, parent accounts, or buying roles, bring us the relationship your team keeps working around.

FAQ

What is a lookup property in HubSpot?

A HubSpot lookup property is a property whose value references another CRM record through an existing custom association label. It lets users work with one labeled relationship through a familiar field.

Do lookup properties replace HubSpot associations?

No. The association remains the relationship between the records, and its label explains the role. A lookup property exposes one labeled relationship as a field so it is easier to select and use.

Are HubSpot lookup properties 1-to-1?

In the current beta, lookup properties support 1-to-1 relationships. Use a labeled association when several records can validly fill the role, such as multiple decision makers on one deal.

When should I use a lookup property?

Use one when a single related record fills a stable, named role and your users or automation need that relationship in a property surface. Original deal, primary contact, and headquarters company are good model shapes.

Can a lookup property hold all decision makers on a deal?

Not in the current 1-to-1 beta. Keep all decision makers as labeled contact-to-deal associations, and reserve a lookup for a role that allows only one record.