Glossary

Explore Meshline

Products Pricing Blog Support Log In

Start with your goals.

Book a call
Autonomous Operations

Create the Contract From an Accepted Quote or Import It? Decide Before You Record the Deal

Should a signed deal start from an accepted quote or an import? See which path fits your billing setup so you can choose the right contract route before recording the deal.

A database icon beside a document icon.

You have a signed deal and a decision to make before anyone touches HubSpot.

Should the contract be created automatically when the buyer accepts a quote, or should you import an existing agreement?

The two paths produce different records with different billing behavior.

Picking the wrong one can leave a contract that cannot bill, or an invoice sent earlier than expected.

This article gives a two-question decision procedure for one live deal, grounded in HubSpot's own documentation.

Choose the path before wiring up billing and renewal follow-up.

Question one: must the buyer accept a quote first?

Start with the buying process, not the tool.

If the buyer must review and accept a quote first, HubSpot documents a quote-based path.

After acceptance or signing, a contract is automatically created and associated with the quote, deal, contact, and company (HubSpot documentation).

This path has documented prerequisites.

Creating contracts from accepted quotes requires a Revenue Hub subscription and a Revenue Hub seat.

The person creating the contract also needs Super Admin or Create permissions for contracts.

Accepted quotes can create contracts whether the billing setting is turned on or not, but the billing setting changes what happens next (knowledge.hubspot.com).

If the billing setting is on, quote acceptance does more than create a record.

HubSpot generates the first invoice immediately after quote acceptance.

It sends that invoice to the buyer right away.

This happens regardless of the invoice's scheduled date or due date.

HubSpot also creates an order associated with the contract (knowledge.hubspot.com).

That is a real tradeoff: the quote path changes billing timing, not just record creation.

If your finance team expects the first invoice on a specific date, an immediate send on acceptance may not match their expectation.

If the billing setting is off, payment collection stays tied to the existing quote or standalone invoice experience.

No contract-driven billing starts (HubSpot documentation).

So the first question resolves cleanly.

If the buyer must accept a quote first and you have the required subscription, seat, and permissions, let acceptance create the contract.

You do not need to import anything; the record appears automatically with its associations in place.

Question two: must HubSpot run the billing?

If the agreement already exists — signed in another system, on paper, or in a legacy CPQ tool — the quote path does not apply.

There is no quote for the buyer to accept.

Your decision then hinges on a second question: does HubSpot need to generate invoices and collect payments, or does billing stay where it is today?

If billing stays in your legacy system: standard import

When you want to track and report on existing contracts in HubSpot while billing continues in your legacy system, the documented path is a standard contract import.

Imported contracts are non-billable records.

HubSpot does not generate invoices or charge payment methods, and your existing billing system remains in control (HubSpot documentation).

This import has its own prerequisites.

You need Import permissions and Edit permissions for contracts.

Before importing, create a custom contract property as a unique identifier.

The documentation suggests a single-line text property, such as contract_import_id, with Require unique values selected.

Your import file must include that property as a column, and for contracts with more than one line item, additional line items go on separate rows alongside the unique identifier.

The deal goes on its own row, with the deal's record ID in a column so it associates to the contract during import (knowledge.hubspot.com).

The failure mode here is worth naming plainly: if you choose import when HubSpot actually must run billing, the contract arrives as a non-billable record.

HubSpot will not generate invoices for it.

Fixing that later means moving to the migration route described below, which carries its own constraints.

If HubSpot must bill: migration, not import

To transfer future invoicing to HubSpot, with optional automatic payment collection, the documented route is a billing migration, currently in beta — not the standard import.

Migrated contracts are billed through HubSpot, while imported contracts are non-billable (knowledge.hubspot.com).

The migration path has documented conditions you should weigh before committing.

Your HubSpot account must use Stripe as a payment processing option.

Once a contract is activated, HubSpot becomes the system of record for billing, and the migration cannot be undone.

Migration also does not automatically stop billing in your legacy system, so you still own that shutdown (knowledge.hubspot.com).

The documentation also flags a data-quality consequence: if incorrect data is imported, you cannot correct historical data in MRR waterfall reports.

If you use revenue continuity, the guidance recommends testing the import in a sandbox environment first (knowledge.hubspot.com).

Those are permanent-enough consequences that the test step deserves a place in your plan, not a footnote.

One more documented limitation applies across both creation paths: it is not currently possible to migrate HubSpot subscriptions to contracts (knowledge.hubspot.com).

If the committed revenue lives in an existing HubSpot subscription, neither the quote path nor the import path directly converts it.

An illustrative example

Suppose — as a clearly labeled illustration, not a real customer result — your team closes a renewal where the buyer asked for a formal quote to route through procurement.

The buyer must accept before anything is final, and your account has a Revenue Hub subscription with a seat assigned and a Super Admin ready to configure contracts.

Question one answers itself: build the quote, share it, and let acceptance create the contract with its associations to the quote, deal, contact, and company.

But before sharing, check the billing setting.

If billing is on, acceptance sends the first invoice immediately.

Confirm with finance that this is acceptable, or turn billing off and keep collection in the quote experience.

Now flip the situation.

The same renewal was signed weeks ago in a legacy CPQ tool, and finance wants billing to stay there for the rest of the term.

There is no quote to accept, so question one is settled: import.

Because billing stays in the legacy system, the standard import fits.

It uses non-billable records, Import and Edit permissions, a unique contract_import_id property, and a multi-row file with the deal on its own row.

If finance later wants HubSpot to take over invoicing mid-term, that is not an import tweak.

It is the separate migration beta, with its Stripe requirement and one-way activation.

What each path gives you afterward

Contracts serve as the centralized source of truth for committed revenue.

You can record existing agreements, bill buyers manually or automatically, update contracts over time, renew them, and report revenue (HubSpot documentation).

Both creation paths land you in that same management surface — the difference is how the record is born and who bills.

A few contract-record details are worth knowing before you create anything.

If a line item automatically renews until canceled, no contract end date is set.

If all line items have a fixed term, the end date is set to the latest line item's end date.

If the contract only has one-time line items, no contract end date is set (knowledge.hubspot.com).

These defaults affect how renewals and reporting behave later, so check your line-item structure against them before the contract exists.

After a quote-created contract, you can view it from the quote's preview panel under the Contracts card, or on the contract index page (knowledge.hubspot.com).

For imported contracts, the documentation points next toward managing invoices and payments and reporting revenue in HubSpot (knowledge.hubspot.com).

A short decision checklist

  • Does the buyer need to accept a quote before the agreement is final? If yes and you hold the required Revenue Hub subscription, seat, and contract permissions, use the quote path — acceptance creates the contract automatically. If no quote is part of the process, move to the next question.
  • Must HubSpot generate invoices and collect payments for this contract? If no, use the standard import: non-billable records, with Import and Edit permissions and a unique identifier property prepared. If yes, the standard import will not bill — the documented route is the migration beta, which requires Stripe, cannot be undone once activated, and does not stop legacy billing automatically.
  • Is the committed revenue an existing HubSpot subscription? If yes, note that direct conversion of subscriptions to contracts is not currently supported, so neither path applies directly and you should plan around that limitation.

One caution on sequencing: decide the path before you build renewal follow-up or reporting around the contract.

A workflow triggering on quote acceptance will never fire for an imported record.

A billing report built on non-billable imports will not reflect invoicing HubSpot is not doing.

The record's origin shapes what downstream automation can see.

Weighing this for a deal in flight?

A second pair of eyes on the quote-to-contract handoff is worth talking through.

Related reading if your decision touches neighboring workflow choices:

How Meshline can help. Connect automation, Organic Marketing (demand generation), and customer lifecycle management (Revenue Intelligence).

Bring topic planning, content publishing and performance feedback into the conversation about your workflow. Book a Meshline demo.

Revenue Intel

Ask us about this workflow.

Tell us what you want to fix or automate. We'll reply with the most useful next step.

See how we can help

Implementation decisions

Put this into practice

Before choosing a solution, define the problem, the available data and who will review the outcome.