HubSpot Contracts vs. Subscriptions and how they relate to Stripe:
HubSpot Contracts is an object within HubSpot Revenue Hub that is built to contain HubSpot's record of your committed revenue, including: the line items, terms, MRR, ARR, renewals and mid-contract changes for each customer. Contracts are built to be flexible, supporting one or multiple termed or evergreen subscriptions in addition to one-time items. They can be created from HubSpot quotes, imported or integrated data, or manually in the UI.
HubSpot Subscriptions are another object within HubSpot Revenue Hub that will eventually be sunset. You can think of them as the “V1” of HubSpot Contracts that are more limited (subscription data only) and were more deeply integrated with HubSpot’s internal billing engine rather than supporting external billing data.
Migrating Stripe into HubSpot Contracts effectively moves your billing engine from Stripe to HubSpot: once a migrated contract is activated, HubSpot becomes the system of record for billing, the migration can't be undone, and Stripe stays on only as the payment processor. Teams that want Stripe Billing to continue owning their billing and subscription data should sync Stripe data into HubSpot instead of migrating. ClearSync currently does this with two HubSpot app objects: ClearSync Stripe Subscriptions and ClearSync Stripe Events.
Where the confusion comes from: In HubSpot's docs, "Stripe" almost always means the potential for using Stripe as payment processor for HubSpot Billing, and very rarely means “for Stripe Billing customers”, which is the Stripe product that likely manages your invoices and subscriptions today.
HubSpot Contracts: the new Core Object in Revenue Hub
HubSpot Contracts are the object in HubSpot Revenue Hub that holds your committed revenue. A single HubSpot contract can hold one or more recurring subscriptions, termed or evergreen, alongside one-time items, and HubSpot calculates total contract value (TCV), annual contract value (ACV), MRR and ARR on each one.
How Contracts differ from Deals: A HubSpot Deal tracks one potential sales opportunity until it closes. A HubSpot contract picks up from a closed/won Deal and covers the customer relationship over time: the agreement itself and how it changes over time. Each Contract can be associated with other standard objects including: contacts, companies, deals, quotes, line items, invoices, payments and subscriptions.
How a contract gets into HubSpot: There are three ways to create one:
From a HubSpot quote. With Revenue Hub, the Connected CPQ, Billing, and Payments beta and automatic contract creation turned on, HubSpot creates a contract when a buyer accepts a quote.
Imported or integrated. Contracts can come in through a CSV import, which is HubSpot's migration path, or through the Contracts API, which has been in public beta for all hubs and tiers since August 3, 2026.
Manually in the UI. Through the Direct Create, Edit, and Renew HubSpot Contracts beta, any HubSpot account can create a contract from a deal, contact, company or ticket record, or from the contracts index page.
Built to hold revenue billed elsewhere: Every HubSpot contract has a setting for whether HubSpot handles its billing. The Contracts API can create a contract with HubSpot billing turned off, so a contract can record committed revenue that another system invoices. That setting is fixed once the contract is created.
How contracts change over time: You can edit a contract directly (in beta) or send a change quote for the buyer to accept. You can renew a contract from the contract record (in beta) or with a renewal quote, which creates a new contract linked to the old one once it's accepted. Change quotes and renewal quotes have to be associated with a deal. Evergreen contracts renew until canceled and have no end date, so HubSpot skips TCV and ACV on them but still calculates MRR and ARR.
How proration works: HubSpot prorates mid-term changes with a hybrid method, where full billing months count equally and partial months count by exact days. In HubSpot's own example, a $3,000 quarterly line item that starts March 15 and is replaced on April 18 by a $4,500 quarterly line item bills $1,100 for the old item and $2,850 for the new one.
Why Contracts matter for reporting: Every contract action generates two revenue events, e_contract_booking and e_contract_revenue_scheduled, and those events power HubSpot's MRR Waterfall, Net New MRR, Booked MRR and Booked TCV reports. Nobody can write those events directly. They only come from contract actions, so revenue that never lands on a HubSpot contract never shows up in those reports.
What you need for each setup:
You want HubSpot Contracts that... | What you need | Compatibility with Stripe Billing |
|---|---|---|
Record payments manually | Any HubSpot version + Direct Create beta | Yes - you can manually sync your Stripe revenue data if your transaction volume is low enough |
Send invoices automatically | Any HubSpot version + Direct Create beta | Not compatible - invoices still come from Stripe Billing |
Send invoices and collect payments automatically | Direct Create beta + HubSpot payments (Starter or above) or Stripe connected as a payment processor | Not compatible - invoices and payment collection are still done by Stripe Billing |
Are created from accepted quotes | Revenue Hub + Connected CPQ, Billing, and Payments beta | Not compatible - you can use HubSpot quotes and manually create Stripe customer, invoice, and subscription data |
Run quote to invoice to payment automatically | Revenue Hub + Connected CPQ, Billing, and Payments beta + HubSpot payments or Stripe as a payment processor | Not compatible - these only connect within HubSpot if you migrate from Stripe Billing to HubSpot Billing |
In short: HubSpot Contracts work on any HubSpot version through the Direct Create beta. Contracts created from accepted quotes need Revenue Hub and the Connected CPQ beta, and collecting payments automatically needs HubSpot payments or Stripe connected as a payment processor, and won’t work if you need to stay on Stripe Billing.
Where HubSpot Contracts stop: Despite the name, HubSpot Contracts don't replace signed legal agreements or MSAs. Buyers only see quotes, invoices and receipts.
Which to choose: Migrate to HubSpot Contracts if you want HubSpot to become the source of truth for committed revenue and you're ready for HubSpot to own renewals, changes and billing.
If Stripe Billing is staying (often due to deep integrations with SaaS products or more advanced features that HubSpot billing lacks), ClearSync supports keeping your billing in Stripe and syncing Stripe subscriptions, payments, and MRR change events into HubSpot as two app objects, ClearSync Stripe Subscriptions and ClearSync Stripe Events. ClearSync uses HubSpot’s native Payment object to sync subscription payment data into HubSpot.
A note on naming: Revenue Hub is the product HubSpot called Commerce Hub until June 2026, so older guides and docs still use the old name.
HubSpot Contracts vs HubSpot Subscriptions: what's the difference?
HubSpot Subscriptions are the older, more limited object. You can think of them as the "V1" of HubSpot Contracts: a HubSpot Subscription holds subscription data only and was built around HubSpot's own billing engine, while a HubSpot Contract holds the whole agreement and can also record revenue that's billed outside HubSpot.
How HubSpot Subscriptions and Contracts work together today: HubSpot is already moving billing onto Contracts. With the Connected CPQ, Billing, and Payments beta, adding recurring line items to a quote still creates a Subscription record, but billing for it is managed through the Contract.
Where HubSpot is headed: When we asked Arun Gunari, HubSpot's PM for Billing and CPQ strategy, during a September 2026 Revenue Hub webinar with ProcessPro Consulting, he confirmed that new customers should use Contracts rather than Subscriptions, and that Subscriptions will eventually be sunset. HubSpot has also said usage-based line items are coming to Contracts, alongside the termed, evergreen and one-time items they support today.
HubSpot Subscriptions | HubSpot Contracts | |
|---|---|---|
What it is | Recurring billing record | Committed-revenue agreement |
What it holds | Subscription data only | Termed and evergreen subscriptions plus one-time items |
Created from | Payment links, legacy quotes, manual entry, a Stripe subscription migration, or quotes under the Connected CPQ beta | HubSpot quotes with the Connected CPQ beta, CSV import, the Contracts API, or manually through the Direct Create beta |
Revenue metrics | MRR, ARR and churn reports, on Professional or Enterprise | TCV, ACV, MRR and ARR, plus the revenue events behind the MRR Waterfall |
Changes and renewals | Edit the Subscription | Contract edits, change quotes, renewal quotes and proration |
Compatibility with Stripe Billing | None | Partial - Contracts can be created manually or through the API with HubSpot billing turned off. HubSpot's Contracts migration and quote-to-cash flows rely on moving billing to HubSpot rather than integrating with Stripe billing. |
Migrating from Stripe Billing | Pauses your Stripe subscriptions and expects HubSpot to take over invoicing, subscription management, and payments | Can't be undone, and doesn't stop Stripe billing on its own |
HubSpot Subscriptions run recurring billing, while HubSpot Contracts can hold multiple line items and more complex scenarios, handle changes and renewals, and feeds into HubSpot's MRR Waterfall.
A Stripe migration into HubSpot Subscriptions can be reversed by resuming the subscriptions in Stripe (you'd then cancel the HubSpot Subscriptions, which emails customers unless you turn notifications off). A migration into HubSpot Contracts can't be reversed. Teams that want Stripe Billing to keep billing skip both migrations and sync Stripe data into HubSpot instead, which is what ClearSync does with ClearSync Stripe Subscriptions and ClearSync Stripe Events.
Four different things called "subscriptions" in a Stripe and HubSpot stack
Part of the confusion is that four different records share the same name, and only one of them bills from HubSpot.
Name | Where it lives | Who bills the customer |
|---|---|---|
Stripe subscription | Stripe Billing | Stripe |
HubSpot Subscription | HubSpot Revenue Hub | HubSpot, charging through HubSpot payments or using Stripe simply as a payment processor |
Subscriptions from HubSpot's Stripe app | A HubSpot custom object, which requires HubSpot Enterprise and doesn’t sync over MRR/ARR data | Stripe; HubSpot only reads the data |
ClearSync Stripe Subscriptions | A HubSpot app object from ClearSync, on any HubSpot version with no Enterprise required | Stripe; HubSpot only reads the data |
In short: Of the four records called subscriptions in a Stripe and HubSpot stack, only a HubSpot Subscription bills from HubSpot. The Subscriptions custom object from HubSpot's Stripe app and ClearSync Stripe Subscriptions are read-only copies of Stripe subscriptions, so Stripe Billing keeps billing with either one installed.
Which to choose: Choose HubSpot Contracts if you want to consolidate on HubSpot Revenue Hub and migrate away from Stripe Billing. Choose ClearSync if Stripe Billing keeps billing and you want Stripe subscriptions, payments and MRR change events as reportable HubSpot records without HubSpot Enterprise.
Who bills the customer after a HubSpot migration: Stripe Billing or HubSpot?
After a migration onto HubSpot Contracts or HubSpot Subscriptions from Stripe, HubSpot bills the customer and Stripe only charges the card. Stripe plays two separate roles next to HubSpot, and a migration keeps only one of them:
Stripe Billing is the billing engine that owns your subscriptions, invoices, proration and payment retries.
Stripe payment processing is the card charge itself. Migrating into HubSpot Contracts or HubSpot Subscriptions replaces Stripe Billing but keeps Stripe payment processing.
Job | Keep Stripe Billing and sync to HubSpot | Migrate into HubSpot Contracts or Subscriptions |
|---|---|---|
Holds the subscription or contract | Stripe Billing | HubSpot |
Sends invoices and receipts | Stripe Billing | HubSpot |
Prorates changes and runs renewals | Stripe Billing | HubSpot |
Retries failed payments | Stripe Billing | HubSpot |
Charges the card | Stripe | Stripe, or HubSpot payments, which runs on Stripe |
Shows subscriptions, payments and MRR in HubSpot | A sync app such as ClearSync | HubSpot natively |
In short: After a migration into HubSpot, every billing job moves to HubSpot and Stripe keeps one job: charging the card.
Why the wording trips teams up: HubSpot's Contracts migration requires "Stripe as a payment processing option," which reads like "you get to keep Stripe." It means connecting your Stripe account so HubSpot can charge cards through it while HubSpot runs billing. Teams that pick HubSpot payments instead are still on Stripe underneath, because HubSpot payments is built on Stripe's infrastructure. A HubSpot account can connect HubSpot payments or a Stripe account as its processor, but not both.
Which to choose: Keep Stripe Billing if your product is deeply integrated with Stripe, or if Stripe's billing logic, Stripe Tax or usage-based pricing carries real weight in your business; ClearSync then syncs your Stripe subscriptions, payments and MRR change events into HubSpot. Move billing to HubSpot if you want quotes, invoices and renewals run from HubSpot and you're comfortable with Stripe becoming the payment processor only.
What happens when you migrate Stripe subscriptions into HubSpot Contracts?
Migrating into HubSpot Contracts effectively moves your billing engine from Stripe to HubSpot. HubSpot requires HubSpot billing to be turned on for every migrated Contract, and once a Contract is activated, HubSpot is the system of record for billing and the migration can't be undone. Stripe stays connected only as the payment processor: for Contracts set to automatic payments, each Contract stores a Stripe payment method ID so HubSpot can charge the saved card.
What HubSpot's Contracts migration requires
A beta. A Super Admin opts the account into the Billing Migrations onto Revenue Hub Contracts beta.
Stripe as the payment processor. The HubSpot account has to use Stripe as a payment processing option. Teams on HubSpot payments who want to move cards from an external Stripe account fill out a request form.
Revenue Hub, unless the account is in the Direct Create beta.
A CSV import. Every Contract row sets hs_hubspot_billing_enabled to TRUE, a collection process of manual or automatic payments, a future billing start date override, and a custom import_unique_id. Automatic payments also need the Stripe payment method ID in hs_external_payment_method_reference_id.
How the migration runs: Imported Contracts land as drafts. HubSpot validates them, flags errors to fix, and only starts billing once you confirm the migration. Before that final step, HubSpot asks you to review the last invoice from the old system, the first HubSpot invoice, open receivables, cancellation of the old subscriptions, dunning, invoice emails and your QuickBooks Online or Xero connection.
Two HubSpot migration settings to double-check: The billing start date override doesn't reset a customer's billing cycle; if it falls between two cycle dates, HubSpot waits for the next scheduled date. And if the CSV leaves out hs_net_payment_terms, every migrated invoice defaults to due on receipt, whatever your account's invoice settings say.
Three things the Contracts migration doesn't do
The HubSpot Contracts migration doesn't stop billing in Stripe. HubSpot's documentation says so directly, and its final checklist includes cancelling the legacy subscriptions. Cancel your Stripe subscriptions before HubSpot's first billing date, or Stripe will keep billing customers alongside HubSpot.
The HubSpot Contracts migration doesn't recreate historical invoices or payments. The revenue continuity option uses ramp keys to group line items into phases, which rebuilds MRR change events such as expansions and contractions for the MRR Waterfall. Past invoices and payments stay in Stripe, so teams that want that history in HubSpot without migrating use a sync such as ClearSync, which imports historical Stripe subscription data.
The HubSpot Contracts migration can't be corrected in place. If historical MRR data imports wrong, the only fix HubSpot documents is deleting the Contract and importing it again, which is why HubSpot tells you to test revenue continuity imports in a sandbox first.
Migrating into HubSpot Contracts vs migrating into HubSpot Subscriptions
HubSpot offers a second, older route for Stripe customers: migrating Stripe subscriptions into HubSpot Subscriptions. The HubSpot Subscriptions route and the HubSpot Contracts route behave very differently.
Into HubSpot Subscriptions | Into HubSpot Contracts | |
|---|---|---|
How | In-app migration from Stripe > Subscriptions | CSV import, in beta |
What happens in Stripe | Stripe subscriptions are paused, not deleted | Nothing; Stripe keeps billing until you cancel them |
Reversion | Resume the subscriptions in Stripe | Can't be undone easily; you’d need to escalate a case with HubSpot to attempt to transfer out your data, including payment methods and any history. |
Not eligible | Usage-based or metered billing, Stripe automatic tax, trials, subscriptions that haven't reached their first billing date, discounts on recurring line items, line-item taxes, subscriptions created by third-party apps; some become eligible if HubSpot strips the discount or tax rate | Not documented yet, although HubSpot's Contracts API supports flat, volume, graduated and stairstep pricing |
Volume Considerations | Over 1,000 subscriptions needs a request form | Not stated |
In short: HubSpot's Stripe subscription migration (which will likely be sunset) pauses Stripe subscriptions and can be reversed by resuming them, but it excludes usage-based billing, Stripe automatic tax, trials and most discounted subscriptions.
HubSpot's Contracts migration leaves Stripe subscriptions running until you cancel them, and it can't be undone.
Which to choose: Migrate to HubSpot Contracts if HubSpot should own billing, renewals and change quotes from now on, and your Stripe pricing maps to flat or tiered line items. Stay on Stripe Billing if you have a complex billing model or deep integrations with your product or other systems like accounting or taxation; ClearSync then syncs your Stripe subscriptions, payments and MRR change events into HubSpot without moving billing.
What changes for your team when HubSpot bills instead of Stripe Billing?
When HubSpot replaces Stripe Billing, your team gives up the ability to use much of Stripe's functionality, including Smart Retries, the customer portal and Stripe Tax, in exchange for having quotes, Contracts, invoices and your CRM in one system. Teams usually stay on Stripe Billing for one of two reasons: their product is deeply integrated with Stripe (signups, plan changes and usage all flow through Stripe), or they rely on billing features HubSpot doesn't have yet.
Capability | Stripe Billing | HubSpot Contracts and Subscriptions |
|---|---|---|
Failed payments | Smart Retries, which uses AI to time retries, or a custom schedule | Card payments retried automatically up to 4 times within 30 days, plus manual retry; bank debits aren't retried |
Customer self-service | Stripe's customer portal for plan and payment changes | Payment method update links sent by email |
Usage-based pricing | Supported | Not eligible for the Subscriptions migration; the Contracts API lists flat and tiered models; HubSpot has said usage-based line items are coming to Contracts |
Sales tax | Stripe Tax or other integrated systems like Avalara | HubSpot automated sales tax, for U.S. businesses and Canadian businesses in British Columbia, Quebec and Manitoba, on Revenue Hub Professional or Enterprise with a Revenue Hub seat |
Quotes, renewals and change quotes tied to HubSpot Deals | Limited native quoting and HubSpot Deal integration | Built in with Revenue Hub, with Deal pipelines for renewals and expansions |
MRR Waterfall in HubSpot | Needs a tool like ClearSync | Built-in, driven by Contract revenue events |
Two more checks before moving billing to HubSpot: If your product creates subscriptions through Stripe Checkout or the Stripe API, those self-serve flows were built for Stripe Billing, so plan how new signups will reach HubSpot. And HubSpot's Stripe payment processing isn't available in 13 countries, including Brazil, India, Indonesia, Malaysia, South Africa, Thailand and the United Arab Emirates.
Where HubSpot billing makes the most sense: Sales-led teams that don’t have in-app self-service billing powered by Stripe. When reps already live in HubSpot, a change quote updates the Contract, the invoice schedule and the MRR Waterfall in one step, which removes a lot of manual work.
If you sell both self-serve and sales-led on Stripe and HubSpot
Many SaaS companies run two motions: self-serve signups through Stripe and sales-led deals through quotes. Billing them in two places leaves you with two partial MRR numbers and one of the systems disconnected from your product in terms of access and entitlements.
HubSpot's MRR Waterfall only counts revenue on HubSpot Contracts, so self-serve customers billed in Stripe Billing are missing from it unless their data reaches HubSpot some other way. Decide which system holds the full MRR picture before you split billing.
Which setup fits: Stripe Billing with a HubSpot sync, HubSpot Subscriptions or HubSpot Contracts?
The right setup depends on which system should send the invoice. Stripe Billing with a HubSpot sync such as ClearSync fits teams that want Stripe to keep billing, HubSpot Subscriptions fit simple flat-rate plans billed from HubSpot, and HubSpot Contracts fit quote-driven agreements with renewals and change quotes.
If your team... | Setup | Compatibility with Stripe Billing | Tools |
|---|---|---|---|
Keeps Stripe Billing and wants subscriptions, payments and MRR in HubSpot | Stripe Billing + sync | Yes | ClearSync, starts at $149/month, works with any HubSpot version |
Closes Deals in HubSpot and wants Stripe Billing to create the subscription | HubSpot Deals into Stripe Billing | Yes | Finrite |
Wants Stripe revenue analytics in a separate dashboard | Stripe Billing + analytics tool | Yes | ChartMogul, Baremetrics |
Sells through quotes and wants HubSpot to own quote to cash | HubSpot Contracts | No - billing moves to HubSpot | Revenue Hub + the Contracts migration beta |
Bills on usage, relies on Stripe Tax, or has deep integrations between Stripe and your product | Stripe Billing | Yes | Any sync above for HubSpot visibility |
In short: Teams staying on Stripe Billing choose some combination of: ClearSync, HubSpot's Stripe app, and Finrite depending on what they need in HubSpot. Teams moving billing to HubSpot choose HubSpot Contracts for quote-driven agreements.
What each Stripe and HubSpot tool does:
ClearSync is a HubSpot app that syncs Stripe subscriptions and MRR change events into HubSpot as two app objects, ClearSync Stripe Subscriptions and ClearSync Stripe Events, and syncs subscription payments into HubSpot's native Payment object, working with any version of HubSpot. ClearSync starts at $149/month and imports full historical Stripe subscription data.
HubSpot's Stripe app is HubSpot's free data sync for Stripe customers, invoices and products, with Stripe subscriptions synced as custom objects on HubSpot Enterprise (although it lacks any MRR/ARR data).
Finrite is a HubSpot app that moves HubSpot Deals into Stripe Billing.
ChartMogul and Baremetrics are subscription analytics tools that report on Stripe data in their own dashboards.
FAQ about HubSpot Contracts and Stripe
Can I use HubSpot Contracts and keep Stripe Billing?
Yes, in a limited way. You can create HubSpot Contracts manually through the Direct Create beta, or through the Contracts API with HubSpot billing turned off, and record your Stripe revenue on them, which works if your transaction volume is low enough to keep in sync by hand or if you want to custom-develop your own integration.
HubSpot's Contracts migration and quote-to-cash flows all move billing to HubSpot, and HubSpot's own Stripe app doesn't write to Contracts.
Are HubSpot Subscriptions being replaced by HubSpot Contracts?
Yes, over time. When we asked Arun Gunari, HubSpot's PM for Billing and CPQ strategy, during a September 2026 Revenue Hub webinar with ProcessPro Consulting, he confirmed that new customers should use Contracts rather than Subscriptions, and that Subscriptions will eventually be sunset. HubSpot Subscriptions still work today, and with the Connected CPQ, Billing, and Payments beta, billing for Subscription records is already managed through the Contract.
Does migrating to HubSpot Contracts cancel my Stripe subscriptions?
No. HubSpot's documentation says the migration doesn't stop billing in the legacy system, so you cancel your Stripe subscriptions yourself before HubSpot first bills the customer.
Can I undo a HubSpot Contracts migration?
No. Once a migrated Contract is activated, HubSpot is the system of record for billing and the migration can't be undone. A migration back to Stripe is possible but painful and could take weeks or months - you would need to escalate a support case with HubSpot to have payment methods and the current subscription footprint securely transferred to a new Stripe account.
A migration into HubSpot Subscriptions is different: Stripe subscriptions are paused, and you can resume them in Stripe and then cancel the HubSpot Subscriptions.
Do I need Revenue Hub to use HubSpot Contracts?
Not always. Any HubSpot version can create Contracts through the Direct Create, Edit, and Renew HubSpot Contracts beta, but creating quotes requires paid Revenue Hub seats, and Contracts created automatically from accepted quotes also need the Connected CPQ, Billing, and Payments beta.
Is HubSpot Revenue Hub the same as Commerce Hub?
Yes. HubSpot renamed Commerce Hub to Revenue Hub in June 2026, so older HubSpot docs and guides still say Commerce Hub.
Does HubSpot's Stripe app sync Stripe subscriptions into HubSpot Contracts?
No. HubSpot's Stripe app syncs Stripe subscriptions into custom objects, which requires HubSpot Enterprise. ClearSync syncs them into two app objects, ClearSync Stripe Subscriptions and ClearSync Stripe Events, on any HubSpot version with no Enterprise required.
Additionally, the free HubSpot Stripe App does not sync any MRR/ARR data at all, even if you use the subscription object. See this article for a full teardown.
Can I sync Stripe payments into HubSpot without migrating my billing?
Yes. ClearSync syncs Stripe subscription payments into HubSpot's native Payment object, alongside ClearSync Stripe Subscriptions and ClearSync Stripe Events, while Stripe Billing keeps billing.
What's the difference between HubSpot payments and Stripe payment processing in HubSpot?
HubSpot payments is HubSpot's own payment processor, built on Stripe's infrastructure and available on Starter and above for businesses based in the U.S., U.K. and Canada. Stripe payment processing connects your existing Stripe account instead (an account would either use “HubSpot Payments” for processing which is Stripe behind the scenes, or Stripe Payment Processing directly, but can’t use both).
Does HubSpot retry failed payments like Stripe Billing does?
Yes, on a fixed schedule. HubSpot retries failed card payments up to 4 times within 30 days and lets you retry manually, while Stripe Billing offers Smart Retries, which uses AI to choose retry times.
How does HubSpot prorate a Contract change?
HubSpot counts each full billing month equally and counts partial months by exact days. When proration is turned off, mid-term changes take effect at the next billing cycle.
Does a HubSpot Contract replace my signed contract or MSA?
No. Despite the name, HubSpot says Contracts don't replace legal agreements. You can link a signed PDF to a Contract through a custom file or URL property.
Related ClearSync Guides:
Stripe Billing vs HubSpot Payments: What's Actually Different? · ClearSync vs HubSpot's Stripe App · How to Rebuild Accurate Stripe MRR History in HubSpot
