Architecture | Entry 6 of 11
HubSpot object associations connect related CRM records. They help nonprofit teams see how people, households, organizations, donations, volunteer activities, events, programs, and other records relate without storing every detail in one place.
Objects organize different types of information in HubSpot. Records are the individual entries stored within those objects. Associations are the connections between those records.
For example, a contact record for one constituent might be associated with:
HubSpot supports associations between different object types, such as a contact and a company, as well as certain associations between records of the same object type. Staff can view and manage associated records from record pages, including through cards that display related records or selected information from them.
A constituent rarely has only one relationship with a nonprofit. The same person may be:
When those relationships are disconnected, each team sees only part of the person’s history. Associations bring the details together while keeping every record type organized.
This supports clearer constituent histories, better staff coordination, stronger segmentation, more accurate reporting, useful workflow automation, and fewer disconnected records.
A nonprofit has a contact record for Jordan. Jordan belongs to the Jordan-Lee household, works for a corporate sponsor, gives monthly, volunteers at two annual events, and is registered for an upcoming fundraiser.
The CRM keeps separate records for Jordan’s contact, household, employer, donations, volunteer assignments, and fundraiser registration. Associations connect them.
When a development employee opens Jordan’s contact record, they can see the connected household, employer, donations, volunteer history, and event registration. The household record shows Jordan, other household members, and household donations. The corporate sponsor’s record shows Jordan’s relationship with the company and related sponsorship opportunities.
Each record has its own purpose, but the associations connect the full story.
A supported record-creation form can let staff select related records. A new donation, for example, could be associated with a contact and household as it is created.
Staff can add or remove associations from a record when a relationship changes or needs correction.
When enabled, HubSpot can create companies and associate contacts with them based on email domains. This setting requires careful review because a domain-based relationship may not fit every nonprofit use case.
Supported workflows can create or manage associations and update association labels. Available actions depend on the account’s HubSpot products and subscription.
Properly formatted imports, connected apps, and HubSpot’s Associations API can create associations during migrations, integrations, or high-volume record management.
Creating associations is only part of the work. The nonprofit also needs clear rules for how records should connect.
Before building associations, decide:
Automatic association settings should be used carefully. Connecting a contact to a company by email domain can help with corporate relationships, but shared, personal, university, government, or consulting-company domains can create misleading connections.
Association features vary by object type, HubSpot subscription, user permissions, and the tools used to create or manage the relationship.
Before implementation, confirm:
The exact setup should be confirmed for the nonprofit’s HubSpot account and data model.