What This Update Actually Is
HubSpot shipped a new native association between two record types: contracts and projects. Before this update, those two objects lived in separate corners of your portal. There was no built-in way to connect them.
Now you can link them directly. You can also use the data model builder to adjust how many associations are allowed or to create custom labels that describe the relationship on your team's terms.
This is available to Revenue Hub Professional and Enterprise accounts only. If you don't have access to both contract and project objects, this update won't surface for you yet.
Why HubSpot Shipped This
Here's the pattern we've seen across dozens of portals. A deal closes. A contract gets signed. A project kicks off. And then those three things exist in three different records with no thread connecting them.
The humans doing the delivery work can't easily see what was promised in the contract. The humans managing the contract can't quickly pull up where the project stands. Everyone ends up toggling between records, searching manually, or relying on memory.
That's not a visibility problem. It's a structural problem. HubSpot addressed it by making the association native, so the relationship lives in the data model itself, not in a sticky note or a Slack message.
Custom labels take it further. If your team needs to distinguish between a "master services agreement" tied to a project versus a "statement of work" tied to the same project, you can define that distinction right in the data model. No workarounds. No extra custom properties to fake the relationship.
How to Use It Step by Step
- Open a contract record in HubSpot. Navigate to the associations panel on the right side of the record.
- Click "Add" and select "Project" as the record type you want to associate. Search for the project by name and confirm the link.
- To create a custom association label, go to Settings, then Data Model, then the Associations section. Find the contract-to-project pair and add the label you need (for example, "Covers" or "Governs").
- To adjust association limits, stay in the data model builder. Increase the maximum number of contract records a single project can be linked to, or vice versa, depending on how your contracts are structured.
- Test the association by opening a linked project record and confirming the contract appears in the associations panel there as well. The link is bidirectional.
- Document your label conventions in a team wiki or your HubSpot portal documentation so all humans follow the same naming pattern going forward.
What It Touches in Your HubSpot Strategy
This update has a bigger footprint than it might appear at first glance. Let's walk through what actually shifts.
Your data model gets more honest. When contracts and projects are linked, your CRM actually reflects how your business operates. That matters for reporting, automation, and onboarding new team members who need to understand the customer journey at a glance.
Reporting becomes more powerful. You can build reports that pull data across both record types. Think about a view that shows contract value alongside project status. That's a meaningful RevOps signal you couldn't surface cleanly before.
Key Takeaway
Linking contracts to projects in HubSpot isn't just a convenience. It's a data model decision that affects how you report, automate, and hand off work between sales and delivery teams.
Workflows get smarter. Once these records are associated, you can use HubSpot workflows to trigger actions based on the linked object. A contract moving to "Signed" could kick off a project task. A project hitting "Complete" could notify the contract owner.
If you've been using workflows to manage associations elsewhere in your portal, this fits naturally into that pattern. The Copy Associations workflow action is a good complement here, especially if you need to propagate linked records across object types automatically.
Your CRM record views become more useful for delivery teams. Instead of a project record that only shows task data, it can now surface the relevant contract. Scope creep conversations get easier when everyone can see the original agreement in two clicks.
Key Takeaway
Custom association labels are where this update earns its weight. Generic links are fine. Labels like "Governs," "Supersedes," or "Covers Phase 2" give your team shared vocabulary baked into the data model itself.
Keep your data clean as you build these associations. If your CRM records have messy property values, now is a good time to review them. The updated property history table makes it easier to spot and restore bad data without leaving the record.
Who Should Care Most
This update is most valuable for a specific kind of company: one that sells AND delivers inside HubSpot. If your revenue model involves signed contracts followed by scoped project work, this directly reduces friction for your team.
- RevOps leaders who want cleaner data relationships across the full customer lifecycle
- Account managers who own both the contract relationship and the project outcome
- Project or delivery leads who need contract context without bugging the sales team
- HubSpot admins and CRM architects building out a data model that mirrors real-world operations
- Professional services firms, agencies, and SaaS companies with implementation or onboarding projects attached to contracts
If your team currently tracks contract-project relationships in spreadsheets, sticky notes, or a secondary tool, this is the update that lets you bring that context home to HubSpot.
George's Take
“A CRM should reflect how your business actually works, not force your team to work around how the tool is structured. Contract-to-project associations are a small update with a big signal: HubSpot is serious about being the system of record for the full customer lifecycle, not just the sale.”
We've worked with companies where the contract lives in DocuSign, the project lives in Asana, and HubSpot only knows about the deal. That's three sources of truth, which means it's actually zero sources of truth. When I see an update like this, I don't just think about the feature. I think about the team member who's been manually copy-pasting contract details into project notes for two years. This update gives those humans their time back. The custom label support is what makes it genuinely useful rather than just technically possible. If you're on Revenue Hub Professional or Enterprise and you're managing project-based delivery, don't sit on this one.
Once your contracts and projects are linked, consider pulling both into a unified dashboard view. HubSpot now lets you embed live CRM record pages directly on dashboards, which pairs nicely with this association update if your team wants a single screen for delivery oversight.
If you want help thinking through how this fits your data model or setting up the right association labels for your team, book a strategy call with Sidekick Strategies. We've done this work across hundreds of portals and we'll help you get it right the first time.
Frequently Asked Questions
What HubSpot plan do I need to associate contract records with project records?
You need Revenue Hub Professional or Revenue Hub Enterprise. This association is not available on free, Starter, or hub-specific plans that don't include both contract and project objects. If you don't see the option in your portal, check your subscription tier first.
How do I create a custom association label between contracts and projects in HubSpot?
Go to Settings, then Data Model, then Associations. Find the contract-to-project pair and add a custom label that describes the relationship. Examples include "Governs," "Covers," or "Supersedes." Labels are visible on both the contract and project record once the association is made.
Can I use HubSpot workflows to trigger actions based on linked contract and project records?
Yes. Once a contract is associated with a project, you can build workflows that reference the linked record. For example, a workflow could trigger a project task when a contract status changes to Signed, or notify a contract owner when a linked project reaches a certain milestone.
Is there a limit to how many project records I can associate with a single contract in HubSpot?
HubSpot sets default association limits, but you can adjust them using the data model builder. Go to Settings, then Data Model, then Associations, and update the limit for the contract-to-project pair. This is useful if one master contract covers multiple related projects.
Does associating a contract with a project affect reporting in HubSpot?
Yes, in a useful way. Once the records are linked, you can build cross-object reports that surface data from both. This lets RevOps teams track contract value alongside project status, giving leadership a cleaner view of delivery health tied to specific agreements.
What's the difference between a standard association and a custom association label for contracts and projects?
A standard association simply links two records together. A custom label adds context to that link, describing the nature of the relationship. Instead of just seeing a contract attached to a project, your team sees that the contract "Governs" or "Covers Phase 1," which reduces ambiguity across sales and delivery handoffs.
