HubSpot New Quotes vs Legacy Quotes: What Changed and How to Plan the Transition

What changed between HubSpot new quotes and legacy quotes?

The main difference is operational. Legacy quotes may reflect an older quoting model and older template assumptions, while the newer experience is intended to provide a more structured way to create and manage quote documents within the CRM. The exact capabilities available to your team depend on your portal, permissions, subscription, and current HubSpot product configuration.

For a sales representative, the change may appear to be a different quote creation flow. For operations, it can affect data ownership, template maintenance, line item accuracy, workflow triggers, reporting, and the treatment of existing documents.

New quotes and legacy quotes: the important differences

1. Quote creation follows a different operating model

Legacy quotes often sit inside a familiar, relatively linear creation process. The newer experience may separate quote details, products, content, settings, and presentation more clearly. That can make the process easier to govern, but it also means that old instructions and assumptions may no longer map directly to the new workflow.

Before training users, document the decisions a rep must make. For example:

• Which deal is the quote associated with?
• Which products or services are included?
• Which customer, billing, and payment details are required?
• Which terms or approvals apply?
• Who owns the quote after it is sent?

This list is more useful than a screenshot-based training guide because it defines the business logic behind the quote.

2. Templates and branding need governance

Quote templates are often treated as design assets, but they are also operating controls. They determine what information is shown, what users can change, and which commercial terms appear consistently across documents.

When comparing the two experiences, review more than logos, colors, and fonts. Check the placement and behavior of:

• Customer and company information
• Product and line item descriptions
• Prices, discounts, taxes, and totals
• Payment terms and expiry dates
• Signature or approval elements
• Legal or contractual language

A template that looks correct in a sample quote can still fail operationally if data is missing, editable content is uncontrolled, or the wrong fields are mapped to the document.

3. Products and line items affect data quality

Quotes depend on the relationship between the deal, products, line items, pricing, and the final document. A transition is an opportunity to check whether those relationships are being used consistently.

Ask whether sales users select approved products, enter free-text descriptions, override prices, or apply discounts in different places. Also determine which values finance and management rely on for reporting. If a quote contains one value while the deal or line item record contains another, the business may have a document that looks accurate but produces unreliable reporting.

Do not assume that moving to a newer quote experience will correct inconsistent product data. The underlying catalog, pricing rules, permissions, and user behavior still need to be reviewed.

4. Existing quotes require a separate policy

A common transition mistake is to define a process for new quotes but not for quotes that already exist. Legacy quotes may remain relevant for active opportunities, renewals, amendments, customer reference, or audit purposes.

Create explicit rules for at least three situations:

• New opportunities: decide when all newly created quotes must use the new experience.
• Existing opportunities: decide whether an open legacy quote remains valid or must be recreated.
• Renewals and amendments: define whether the team continues the original format or creates a new quote using the current process.

The correct answer depends on commercial, operational, and record-keeping requirements. The important point is that users should not have to decide case by case without guidance.

How to assess whether your team is ready to switch

Readiness is not measured by whether an administrator can create one successful test quote. It is measured by whether the new process produces reliable results across the situations your sales team actually handles.

Use a representative test set rather than a single simple quote. Include a standard sale, a discounted sale, a multi-line sale, a renewal, and any scenario involving special terms or approval. The purpose is to expose differences before users encounter them with customers.

A practical transition sequence

What to review in HubSpot workflows and reporting

Quote changes can have consequences outside the quote itself. Operations teams should identify every workflow, report, notification, and integration that refers to quote properties, deal stages, line items, or payment events.

Useful review questions include:

• Does a quote event update the deal, and is that still the intended behavior?
• Do reports distinguish between a quote being created, sent, accepted, and paid?
• Are workflow triggers based on a meaningful business state or simply on record activity?
• Can finance identify the commercial values that were actually presented to the customer?
• Are users notified when a quote needs attention, and is ownership visible?

A workflow should not be retained just because it has always existed. If the new process changes the meaning or timing of a field, the automation may need to be redesigned.

For wider CRM architecture, ownership, and automation decisions, see HubSpot consulting services or CRM consulting services.

Common transition mistakes

Rebuilding appearance without rebuilding logic

Copying the visual layout of a legacy template does not guarantee that the new quote contains the right data or supports the right approval process. Recreate the business requirements first, then make the document look familiar where that is useful.

Allowing both processes to continue indefinitely

Temporary coexistence can reduce disruption, but an undefined dual process creates inconsistent training, reporting, and support. Set an owner and an end condition for legacy use.

Automating before the new states are understood

Automation should follow a clear definition of what each quote status means. Otherwise, teams may trigger notifications or update deals based on activity that does not represent a real commercial decision.

Training users only on buttons

Users need to know not only where to click, but also when to use a template, when to request approval, which fields matter, and what to do when a legacy quote needs attention.

When to involve CRM operations support

Some teams can manage a straightforward template change internally. More complex transitions deserve a broader CRM review when quotes feed reporting, approvals, finance processes, renewals, or multiple sales motions.

The useful question is not whether an external consultant can configure a quote. It is whether the quoting process is connected to a wider operating system that needs to remain consistent. If ownership is unclear, data is duplicated, or users rely on manual corrections, configuration alone will not solve the underlying problem.

A process-first review can clarify what should happen, which records should hold the authoritative data, where automation is appropriate, and where a human decision is still required.