HubSpot Association Labels vs. Custom Properties: How to Model Relationships

HubSpot association labels and custom properties solve different data-modeling problems. An association label describes the relationship between two CRM records. A property stores information about one record itself. Choosing the right one keeps reports understandable and prevents relationship details from being copied into the wrong object.

What an association label describes

An association connects two records—for example, a contact and a company. A label adds meaning to that particular connection. A contact might be a billing contact for one company and an implementation contact for another. The label belongs to the relationship, so the same person can have different roles across different companies or deals.

Labels are useful when users need to distinguish several valid connections between the same object types. They also make CRM records and relationship-based workflows easier to interpret. Available label features and limits can vary by object pair and HubSpot subscription, so check the options in the target portal before designing around them.

What a custom property describes

A custom property belongs to a single CRM record. Examples include a contact’s preferred language, a company’s employee band, or a deal’s implementation quarter. The value follows the record wherever it is used; it does not change according to which other record the user is viewing.

A property such as “Primary company role” can be misleading when a contact has different roles at different companies. It collapses multiple relationships into one record-level answer and can become difficult to report accurately.

A practical decision rule

Before migrating data, map each existing field to the record or relationship it actually describes. Check whether workflows, lists, reports, imports, and integrations depend on the current property. Then test a small sample with several records connected in different ways.

• If the value answers “What is true about this record?”, use a property.
• If it answers “What is the role or context of this connection?”, use an association label.
• If the information changes by deal, company, or service relationship, avoid storing it as a single contact-wide value.

Keep the model maintainable

Use a small, consistent set of labels with definitions that users can apply the same way. Do not create labels for distinctions that never affect routing, reporting, or day-to-day work. For properties, record the object, allowed values, owner, and source of truth.

After the change, validate records with multiple associations and inspect reports that group by relationship. A sound model makes the CRM clearer without duplicating the same fact across contacts, companies, and deals.