Beta Closing: Associations as Lookup Properties
Tuesday, August 25, 2026
What it is
Lookup properties were a property type that referenced another CRM record directly inside a property field, coupled to a custom one-to-one association label. They are now being rolled back and can no longer be created. As of August 24, 2026 you cannot create any new lookup properties, and existing lookup properties lose access on Friday, August 28, 2026. Associations created while these properties were filled remain available, but the properties themselves can no longer be interacted with.
Why it matters
The first iteration required lookup properties to be coupled with custom one-to-one association labels. HubSpot wants the functionality to be available and useful to all customers regardless of whether they use labels, and has opened a survey for input on how the system should ideally work.
The Take
Heaven forbid we ask customers to use association labels.
It is rolling back. As of August 24 you cannot create new lookup properties, and the ones you have lose access on Friday, August 28. Associations that got created while those properties were filled stay put, the properties themselves just stop working. If you built anything on this, that is a four-day runway.
HubSpot's stated reason is that the first release tied lookup properties to custom one-to-one association labels, and they want this to work for everyone whether or not they use labels. That is a fair goal and a slightly deflating one, because the label requirement was the honest part. A lookup property only means something if the relationship underneath it is defined.
That is the conversation this rollback should start. Association labels are not a configuration detail you switch on to make a property type work. They are a statement about how your business actually works, and they need to be an intentional, org-level decision. No lookup property was ever going to paper over a team that has not had that conversation. Once you have had it, everything downstream opens up: sync properties, automated associations, roll-up and calculated properties, filtered record cards on index pages, and agents that can reason about which record you actually mean.
What is actually broken is the interface, not the model. Associate a contact, then find the label, then wait through that whole flow, is not built for a rep in a hurry, and that is a UI problem a well-made card can solve today without waiting on HubSpot. If you are on Pro or Enterprise: fill out their survey, and use the next four days to check whether anything in your portal was leaning on a lookup property.
Watch Us Discuss This
The full segment from the show, us working through this update start to finish.
FAQ
Does this replace association labels, or do I still need them?
You still need them. A lookup property displays a labeled association inside the properties framework — it doesn't replace the work of defining clean associations and labels underneath. Skip that and you just get a dropdown of records with no way to tell them apart.
What's the biggest setup risk?
Naming conventions. The dropdown search-and-select space is small, so if your record names aren't intentional — ideally built dynamically from other properties on the record — and your data isn't clean, finding the right record in the lookup field gets hard fast, especially on objects where the primary property wasn't chosen carefully.
Where will operators feel this fastest?
Forms. Native lookup-property support in forms, especially internal forms, closes one of the most common and most painful HubSpot customizations teams have been building around manually.
Is this live yet?
No — it's in private beta as of this recording. Request access if you want hands-on time before general availability.
Produced by Value-First Media