Quick answer
The HubSpot Contracts object is a native CRM record (object type ID 0-721) that acts as the single source of truth for committed revenue. It's created automatically when a quote is accepted and tracks line items, ACV/ARR/MRR/TCV, term dates, billing schedule, and renewal status across the full agreement lifecycle. It shipped generally available on June 16, 2026 inside Revenue Hub (Professional and Enterprise, Revenue Hub seat required) — replacing the renewal-pipeline and spreadsheet workarounds RevOps teams have run for years.
Renewals slipping through the cracks? ARR living in a spreadsheet that never quite matches your CRM?
You're not alone. For years, every RevOps team on HubSpot has run the same workaround: a renewal pipeline full of deals pretending to be contracts.
That era just ended.
In June 2026, HubSpot shipped the Contracts object — a native CRM record built to be the single source of truth for committed revenue — inside the newly renamed Revenue Hub.
In this guide, you'll learn:
- What the HubSpot Contracts object is (and what it isn't)
- How it works: auto-creation, revenue metrics, statuses, and renewals
- How it compares to deals, subscriptions, and Salesforce
- What it costs, how to set it up, and the limitations nobody mentions
Let's get into it.
What is the HubSpot Contracts object?
Here's HubSpot's own definition:
"The centralized source of truth for committed revenue in HubSpot, detailing one-time and recurring products, revenue metrics, and changes over time."
And the key distinction, straight from the Knowledge Base:
"Unlike deals, which track individual sales opportunities, contracts are designed to support the entire customer agreement lifecycle, including amendments and renewals."
In plain English: a deal closes once. A contract lives on — through upsells, downgrades, and renewals.
Quick facts:
- Object type ID:
0-721 - Where to find it: More → Revenue → Contracts
- Associations: contacts, companies, deals, tickets, quotes, invoices, line items, payments, subscriptions — and other contracts (that's how renewal chains work)
- Requires: Revenue Hub Professional or Enterprise + a Revenue Hub seat
What the Contracts object is NOT
Two things trip people up. Let's clear them up now.
It's not a legal contract. Your MSAs and signed PDFs live wherever they live today. HubSpot itself suggests adding a custom property with a File or URL field to reference the legal document. No redlining, no clause libraries, no obligation management.
Your customers never see it. The contract object is internal. Customers get quotes, invoices, receipts, and billing notifications — the contract is what your team works from behind the scenes.
When did HubSpot launch the Contracts object?
HubSpot launched the Contracts object in public beta on April 14, 2026 (Spring Spotlight) and made it generally available on June 16, 2026 — the same day Commerce Hub was renamed Revenue Hub.
The full build-up took five years:
What do you need to use it?
Check your plan before you get excited:
- Revenue Hub Professional or Enterprise — Contracts isn't on Free or Starter
- A Revenue Hub seat — required to create/edit contracts and to create change or renewal quotes
- Super Admin — required for setup
- Granular permissions — View/Edit/Delete contract permissions (under Billing and adjustments) govern day-to-day access
Wondering whether your HubSpot setup is ready for Revenue Hub — or whether your renewal process is leaking revenue right now? Get in touch with Superwork for a quick assessment of your quote-to-cash setup and what adopting the Contracts object would actually take.
How does the HubSpot Contracts object work?
Here's the core loop.
A customer accepts a quote. HubSpot creates the contract automatically (with the "Automatically create contracts from accepted quotes" setting on), inheriting line items, terms, and details from the quote.
No manual data entry. No rep forgetting to log the terms.
Revenue metrics, calculated for you
From the line items, every contract auto-calculates the four numbers your leadership team actually asks about: TCV (Total Contract Value), ACV (Annual Contract Value), MRR (Monthly Recurring Revenue), and ARR (Annual Recurring Revenue).
One catch for evergreen contracts (recurring line items that auto-renew with no end date). Per the official KB:
"Because they don't have an end date, TCV and ACV aren't calculated. MRR and ARR are still calculated."
If a big chunk of your book is evergreen, build your reporting on MRR/ARR — not TCV.
The five contract statuses
Contracts don't use pipelines or stages. They move through five statuses:
- Scheduled — created with a future effective date; flips to Active automatically
- Active — currently in effect
- Completed — reached its end date
- Terminated — ended early (immediately or on a scheduled date)
- Draft — not finalized
Why does this matter? There's no "drag the contract to the next stage" motion. The status reflects reality — and the things that change reality (amendments, renewals) happen through quotes.
Inside the contract record
Three tabs:
- Overview — contract performance (value, recurring revenue, end date, amount billed), current and upcoming line items, and renewal status
- Activities — the familiar timeline
- History — the quietly valuable one: every change, renewal, recurring-revenue movement, and line-item add/remove over the contract's life
That History tab is the audit trail you used to reconstruct from deal notes and email threads.
Custom properties? Fully supported. But start with the standard ones, and add custom properties only for signals the standard record doesn't cover — contract type, customer tier, product line, territory. Every custom property should feed a workflow, a dashboard, or a decision.
How do change quotes, renewal quotes, and proration work?
Mid-term changes are where the old deal-based workaround hurt most. Here's how the native tooling handles them.
Change quotes modify an active contract — add, adjust, or remove products for upsells, expansions, downgrades, or add-ons. Each change quote must be associated with a deal. Once accepted, the contract updates automatically. (Note: line items on change quotes and contracts carry separate record IDs — relevant if you sync line-item data externally.)
Renewal quotes are created as a customer nears end of term. When accepted, HubSpot creates a new contract and auto-associates it with the existing one. That's your contract-to-contract chain across the customer's lifetime.
Proration handles the math. With proration on, mid-term changes are prorated daily based on days remaining in the billing term, applied from the change's effective date. Off? Changes wait for the next billing cycle. Admins set a portal default and can allow per-quote overrides. In the Connected CPQ, Billing, and Payments beta, a prorated mid-cycle change generates a prorated charge invoice plus a credit memo automatically.
One structural point that keeps forecasting clean: change and renewal quotes create associated deals — and those deals flow into dedicated expansion and renewal pipelines. The contract is the record of truth. The deal pipelines remain your forecasting surface.
Contracts vs. deals vs. subscriptions vs. quotes: what's the difference?
A deal tracks a single sales opportunity. A quote is the mechanism that creates and modifies contracts. A contract governs the whole commercial agreement. A subscription is the recurring billing relationship that executes invoicing. In short: the contract powers the subscription; the subscription executes the billing.
Here's the breakdown:
| Object | What it does | Relationship to the contract |
|---|---|---|
| Deal | Tracks one sales opportunity to close | Originating deal links to the contract; renewal/change quotes spawn new deals |
| Quote | The mechanism | Accepted quote → contract; change/renewal quotes modify or extend it |
| Contract | Governs the full agreement | The record of truth |
| Subscription | Runs the automated invoicing schedule | Powered by the contract |
An accepted quote with recurring line items creates both a subscription and a contract automatically. And in the Connected beta, invoices generate from the contract's billing schedule on each billing date, with payment collected via HubSpot Payments or Stripe.
Line items define the billing cadence — monthly, quarterly, annual, or mixed across products in a single contract.
The workarounds this replaces
Before Contracts, you had three options — and they all hurt:
- Spreadsheets (the ARR "source of truth" that never matched the CRM)
- A second deal pipeline with renewal stages, contract dates as deal properties, and workflows auto-creating renewal deals ~90 days out — HubSpot's own long-documented pattern
- An Enterprise-only custom object for contracts
They worked. But they required heavy manual configuration and disconnected ARR reporting from the live contract. The native object ships renewal quotes, ARR dashboards, and the supporting workflows out of the box.
One nuance for complex sellers: as of Spring 2026, line items can also link to custom objects. So the custom-object path remains the right call for things HubSpot doesn't model natively (license keys, complex entitlements) — while now connecting into the native commerce flow.
How to manage renewals with the Contracts object
This is the use case most RevOps teams will adopt Contracts for. Here's the playbook.
Step 1: Turn on renewal alerts. Configurable on the contract object — X days before end date, a custom window, or none. They display right on the record.
Step 2: Build a renewal-date workflow. Contract-based workflow enrollment is currently in beta for Revenue Hub Professional and Enterprise. Trigger it on the Renewal date property. The logic:
- No renewal quote? Renewal date = contract end date
- Renewal quote accepted? Renewal date = that quote's effective date
Trigger from the renewal date — not a rep's calendar reminder. And set planning windows from your actual notice periods, not a universal 90 days.
Step 3: Automate renewal deal creation. Configure Revenue Hub to auto-create a deal (in your chosen pipeline and stage) whenever a renewal or change quote is accepted. Your renewal pipeline stays current without anyone typing anything.
Step 4: Keep pipelines separate. New business in one pipeline, renewals in another. Blending acquisition and retention makes both numbers meaningless.
Bonus: HubSpot's native retention reports analyze churn, NRR, and GRR using contract renewal data — no more calculating retention off deal properties in a spreadsheet.
Setting up renewal automation for the first time — or migrating off a renewal-pipeline workaround? This is exactly where a half-day of expert configuration saves weeks of trial and error. Talk to Superwork about a Revenue Hub renewals setup tailored to your notice periods and pipelines.
What reporting do you get with the Contracts object?
Because every revenue movement flows through the contract, Revenue Hub ships native reports that previously required a BI tool: MRR waterfall, Net new MRR, Booked MRR, Booked TCV, retention (churn/NRR/GRR), and AR/cash reports including DSO.
The headliner is the MRR waterfall by month: opening MRR, new, upgrades, downgrades, churn, renewals, ending MRR.
Alongside it: Net new MRR by month, Booked MRR by month, Booked TCV by month (by revenue type), AR/cash reports (including DSO), retention reports, and attribution.
ACV, ARR, MRR, TCV, contract end dates, and renewal status are all reportable properties you can slice in custom reports.
On the AI side: Revenue Hub includes Breeze-powered quote generation, invoice prioritization, and a growing set of agents in beta — including a Customer Agent that completes payments via chat, email, or WhatsApp, and a Revenue Agent (private beta) for autonomous invoice collections. (Branding note: HubSpot has been repositioning "Breeze" toward "Agent Hub" since mid-July 2026 — we track that shift in HubSpot's agentic CRM pivot — so expect names to move.)
What integrates with the Contracts object?
E-signature: Native e-signature for quotes ships with CPQ, powered under the hood by Dropbox Sign. Allowances are tier-based — 25 e-signatures per user/month on Professional, 50 on Enterprise (per Method's 2026 pricing breakdown). For signing beyond quotes, teams pair HubSpot with DocuSign or PandaDoc.
Accounting and billing: Native bi-directional sync with QuickBooks Online and Xero (contacts, products, invoices, payments). Payment processing via HubSpot Payments or Stripe. To be precise: native billing replaces Stripe Billing, but Stripe as a payment processor still works underneath.
Where dedicated tools still win: Complex CPQ or true contract lifecycle management — redlining, clause libraries, obligation management — remains stronger in dedicated platforms (Salesforce CPQ/Revenue Cloud, Zuora, Icertis, Ironclad, Conga, Agiloft, Juro). HubSpot isn't trying to be a CLM. It's trying to be the system of record for commercial terms.
How to set up the HubSpot Contracts object (step by step)
Ready to turn it on? Here's the path:
- Go to Settings → Data Management → Objects → Contracts (Super Admin required)
- Toggle on "Create contracts from accepted quotes"
- Configure the Renewals tab: renewal alerts and windows
- Set your proration default — and decide whether users can override per quote
- Configure automatic deal creation for change/renewal quotes (choose pipeline + stage)
- Assign View/Edit/Delete contract permissions (under Billing and adjustments)
- Confirm everyone who creates or edits contracts has a Revenue Hub seat
Before you flip the switch: clean your product catalog and price books first. Garbage line items in means garbage revenue metrics out. And put shared truth in dashboards, not personal saved views.
Can you migrate existing contracts and subscriptions?
You can import contracts, but you cannot migrate subscriptions. Contract imports entered public beta in July 2026 (CSV upload of properties, contacts, line items, and deal associations). Subscription-to-contract migration is not supported.
HubSpot is explicit: "It isn't possible to migrate subscriptions to contracts at this time." If you run Commerce Hub subscriptions today, there's no convert button.
The recommended approach is phased:
- Route all new business through Revenue Hub with automatic contract creation from day one
- Transition existing customers onto contracts at their renewal
- Use the imports beta for active contracts you need in-system sooner
What are the limitations of the HubSpot Contracts object?
An honest adoption decision needs the full caveat list. Here it is:
- The Connected CPQ, Billing, and Payments layer is still in beta — and the initial Contracts public beta wasn't available to accounts already using HubSpot Payments or Stripe. Check eligibility in-product.
- Accepted legacy quotes don't create contracts. The automation only applies going forward.
- The Contracts API is read-only (GET and batch-read only), with OAuth scope availability gaps reported during rollout. Factor that into integration planning.
- Credit memos applied to an invoice aren't reflected on the contract (Connected beta).
- Contracts with billing can't be deleted — and deleted contracts can't be restored. Build a termination process, not a deletion habit.
- Billing was still rolling out globally through H2 2026, with a billing pricing model expected September 2026.
- Documentation gaps: there's no official "default contract properties" KB page yet. Only five internal property names are published (
hs_name,hs_contract_effective_date,hs_createdate,hs_lastmodifieddate,hs_object_id); pull the rest via the CRM Properties API on a live portal.
HubSpot Contracts vs. Salesforce Contracts: which is better?
Salesforce's Contract object is deeper on the record itself (document generation, clause libraries, obligation management, full APIs). HubSpot's advantage is bundling CPQ, billing, payments, and contracts into one connected quote-to-cash flow on the same CRM records — a better fit for mid-market SaaS (roughly 20–500 employees).
The honest tradeoff:
- Highly configurable pricing (multi-year ramps, usage-based tiers, guided selling)? HubSpot CPQ is positioned for standard product libraries, simple bundles, and fixed/percentage discounts. Complex configurations remain Salesforce CPQ/Revenue Cloud territory.
- Legal workflow depth? Neither native CRM contract object replaces a dedicated CLM.
How much does the HubSpot Contracts object cost?
Contracts requires Revenue Hub Professional ($85/seat/month billed annually, $95 monthly) or Enterprise ($140/seat/month). New customers attaching Revenue Hub to Sales Hub get a 30% discount — roughly $57 (Pro) or $98 (Enterprise) per seat/month. (Figures per UsagePricing's tracking of the July 30, 2026 pricing launch — verify with HubSpot.)
The tier breakdown:
| Tier | What you get |
|---|---|
| Free | Invoices, payment links, subscriptions, payment collection |
| Professional | + CPQ quoting, contracts, e-signature, revenue analytics |
| Enterprise | + Advanced quote approvals |
Other costs to model:
- Payments fees (confirmed on HubSpot's pages): 0.5% platform fee on HubSpot Payments (0.75% via Stripe processing). Cards run 2.9% + platform fee; ACH is 0.8% + 0.5%, each capped at $10. Available to Starter+ customers in the U.S., U.K., and Canada; 130+ currencies supported. Active promo: no platform fee for one year — verify terms before quoting your CFO.
- Billing add-on: currently included at no extra monthly cost; a billing pricing model is expected September 2026.
- Onboarding: $1,500 (Professional) / $3,500 (Enterprise) one-time fees on the paired Sales Hub tiers.
- EUR pricing: HubSpot hasn't published a confirmed EUR figure for Revenue Hub. Nordic/EU buyers should request a localized quote. (For how the rest of the platform is priced, see our full HubSpot pricing guide.)
Should you adopt the HubSpot Contracts object?
Adopt it now if you sell recurring or contract-based revenue, already run quotes in HubSpot, and are missing renewals or reconciling ARR in spreadsheets. Wait if you need complex CPQ, deep CLM, or can't go live on a partially-beta billing layer.
Already on HubSpot? Pilot Contracts on new business now. Turn on automatic contract creation, configure renewal alerts, and wire a renewal-date workflow tuned to your real notice periods. Run the phased migration. Keep new-business and renewal pipelines separate.
Evaluating HubSpot? The fit is strong for B2B SaaS and mid-market (20–500 employees) wanting quote-to-cash in one system. Weak fit for usage-based pricing, guided selling, or deep CLM — budget for Salesforce CPQ, Zuora, or a dedicated CLM there. Model the full cost: seats + Sales Hub + payment fees + billing pricing (from September 2026) + onboarding.
Thresholds that change the answer: multi-party MSAs, license keys, complex usage tiers, or many concurrent contracts per customer may still fit an Enterprise custom object better. And if the Connected beta hasn't reached GA by your go-live, keep billing on your existing system until it does.
Frequently asked questions
What is the HubSpot Contracts object?
A native CRM record (object type ID 0-721) that serves as the single source of truth for committed revenue — tracking line items, ACV/ARR/MRR/TCV, term dates, billing schedule, and renewal status across the full agreement lifecycle.
Which HubSpot plan includes the Contracts object?
Revenue Hub Professional and Enterprise. A Revenue Hub seat is required to create and edit contracts.
Does the Contracts object replace legal contracts?
No. It tracks commercial terms, not legal documents. HubSpot suggests a custom File or URL property to reference your signed MSA or PDF.
Can customers see the contract record?
No. Contracts are internal. Customers receive quotes, invoices, receipts, and billing notifications.
Can I migrate my HubSpot subscriptions to contracts?
No — HubSpot states subscription-to-contract migration isn't possible at this time. Use the phased approach: new business on contracts now, existing customers at renewal, and the contract imports beta (July 2026) for external contracts.
Is there a Contracts API?
Yes, but it's currently read-only (GET and batch-read). Write access and broader OAuth scope availability were still pending as of August 2026.
How is a contract different from a deal in HubSpot?
A deal tracks one sales opportunity and closes. A contract governs the entire agreement lifecycle — amendments, renewals, and revenue changes — and links back to the originating deal.
The bottom line
The HubSpot Contracts object is the piece HubSpot's commerce story was missing: a native record connecting the accepted quote to revenue metrics, the renewal motion, and (increasingly) billing — replacing the renewal-pipeline and spreadsheet workarounds RevOps teams have maintained for years.
It's production-ready today for the core use case: recurring-revenue B2B companies that want committed revenue, renewals, and MRR reporting living where their CRM data already lives.
Go in with eyes open, though. The connected billing layer and contract workflows are partly in beta. The API is read-only. Subscription migration doesn't exist. And pricing — especially billing, especially in EUR — is still settling.
The teams that win with the HubSpot Contracts object will pilot it on new business now, keep their renewal process disciplined, and migrate the back book on renewal rather than all at once.
Rather not figure out setup, migration sequencing, and renewal automation alone? That's what we do all day. Book a call with Superwork and we'll map your quote-to-cash setup against Revenue Hub — what to adopt now, what to wait on, and what it'll cost.
Note on sources: statuses, evergreen behavior, associations, seat and permission requirements, payments platform fees, and launch framing are confirmed against official HubSpot Knowledge Base and product pages. E-signature volume limits and Revenue Hub seat pricing come from partner blogs and pricing trackers (Method, UsagePricing) and should be verified with HubSpot before quoting. All figures are time-sensitive as of August 2026.