Salesforce CPQ to HubSpot
Moving from Salesforce CPQ to HubSpot?
Whether you are evaluating HubSpot or already migrating, your Salesforce CPQ configuration is the part that does not come with you. Bundles, price rules, approval chains, and quote templates stay behind. This guide shows what happens to each part, where native HubSpot stops, and where Quotivity fits.
Free analysis · Runs locally on your machine · Open source
Already mid-migration? Book a scoping call.
Can your team migrate to HubSpot and continue quoting effectively?
That's the core question this guide will answer. HubSpot's native quoting is sufficient for many companies. But companies with configurable products and complex pricing often need more — which is where Quotivity fits in.
Run the free CPQ migration analysis to find out
It reads your Salesforce CPQ configuration and shows you how it maps to a HubSpot and Quotivity configuration.
It's private. You don't share credentials with us.
It's local. Run it on your machine and nothing is shared with us until and unless you say so.
It's quick. You'll have an answer in 2 minutes.
How the analysis runs
- Install the plugin. It is a Salesforce CLI plugin and the source is public, so you can read it before you run it.
- Run it against your org. It uses your own Salesforce session. There is no connected app to approve and no credentials to hand over.
- Read the report. It is written to your machine. Nothing reaches us unless you send it.
It is a command line tool for one reason: that is what lets it read your org from your side of the wall. A hosted version would mean granting a third party access to your Salesforce data before you had decided anything.
What it reads
It inventories the Salesforce CPQ configuration in your org and counts it, construct by construct.
- Bundles and options — product options, product features, option constraints, and how deep your bundles nest
- Pricing — price rules and the conditions on each one, summary variables, lookup queries, block prices, contracted prices
- Discounting — discount schedules, including slab type and group aggregation scope, and quote line groups
- Guided selling — configuration attributes
- Approvals — approval rules, chains, approvers and tracked fields, and which approval system you are actually on
- Quote documents — templates, template sections, line columns and quote terms
- Subscriptions and contracts — subscription products, contracts, and multi-dimensional pricing
- Custom code — quote calculator plugins, Apex on CPQ objects, custom actions and validation rules, listed by name
What you get back
A report that maps each construct to where it lands in HubSpot and Quotivity, with your counts beside it. It is a map of your configuration, not a readiness score.
- A verdict per construct — clear path, partial path, or no path — with structural change reported separately from behavior that is genuinely lost
- The numbers that actually size the work: conditions per price rule, bundle nesting depth, template count, script count
- Flags on the parts that need a person: discount schedules that aggregate by group, lookups whose shape has to be inspected, and scripts we cannot classify from the outside
We do not read your JavaScript. A quote calculator plugin is listed and flagged rather than interpreted, and working out which ones become configuration is what the free consultation is for.
What happens to your Salesforce CPQ setup
| What you have in Salesforce CPQ | Where it lands in HubSpot | What to expect |
|---|---|---|
|
Bundles and options
|
Configurable products in Quotivity
|
Native HubSpot does not have a bundle object.
|
|
Price rules and formula logic
|
Calculated pricing and roll-ups
|
Tiered pricing can be native. Calculated pricing needs more.
|
|
Approval chains
|
Native approvals or Quotivity approvals
|
The approval layer is usually fine. The values underneath it are the real question.
|
|
Quote templates and terms
|
Rebuilt templates and conditional document logic
|
The document survives as a rebuild, not as an export.
|
|
Guided selling and attributes
|
Guided selling flows in Quotivity
|
There is no native guided selling feature in HubSpot.
|
|
Custom scripts and plugins
|
Configuration, automation, or review work
|
Some code becomes configuration. Some code needs a closer look.
|
|
Your full org
|
The free analysis output
|
That is where you stop guessing and count what is actually there.
|
The pages in this guide
What HubSpot's native quoting does and doesn't do
The trust anchor for where native quoting works and where it stops.
Can HubSpot handle our pricing?
The pricing and discounting page for formulas, tiers, and roll-ups.
Can HubSpot handle configurable products?
The bundles and options page for the most common capability doubt.
Can HubSpot handle multi-step approvals?
The approvals page for readers whose real blocker sits underneath routing.
Can HubSpot handle amendments and renewals?
The contracts and lifecycle page for subscription changes after signature.
Can HubSpot produce the quote document we need?
The page for styled quote documents, templates, and proposal-style output.
How to use this guide
Start here
Check the native limit first
If your quoting is straightforward, native HubSpot may already cover you. That is the first branch in the decision.
Then compare
Map what you already built
Look at bundles, pricing logic, approvals, documents, and scripts as separate constructs. They do not all move the same way.
Use the tool
Count the real migration surface
The analysis tells you how many rules, bundles, templates, and scripts are in your org so the project gets scoped from evidence.
Use the result
Decide with the numbers in hand
Once the counts are visible, you can judge whether native HubSpot is enough, whether you need Quotivity, or whether the migration should pause.
One guide, two stages of the same decision. Research first, migration second.
Who this guide is for
A fit if
- You use Salesforce CPQ today and are evaluating or migrating to HubSpot
- You need to understand what happens to bundles, pricing logic, approvals, or quote templates
- You want the quoting question answered before the migration is scoped loosely
- You need a native-to-HubSpot path rather than a second quoting system
This guide is less useful if
- Your quoting is a single product with list pricing and light approvals
- You are not moving to HubSpot and only need a Salesforce optimization project
- You are comparing generic CPQ platforms without a HubSpot decision in view
If native HubSpot already fits, the right answer may be to configure native and stop there.
Questions teams ask before running the analysis
No. Your Salesforce CPQ configuration lives inside Salesforce. The useful question is where each construct lands when you rebuild the quoting workflow in HubSpot.
That is the assumption worth testing rather than settling on a demo. Native HubSpot genuinely does not do configurable products, calculated pricing, or guided selling, so the observation behind the doubt is usually correct. What does not follow is the conclusion: that is a limit of native quoting, not of HubSpot. Run the analysis and you will be working from counts instead of impressions.
Sometimes, and we will say so if it is true for you. Native HubSpot can be enough for standard products, list pricing, and straightforward approvals. If that sounds like your quoting, start with the native limits page rather than the analysis — it may answer the whole decision.
Yes, and the spread is wide. Bundles, price rules, approval chains and quote templates have known routes, even where the structure changes shape on the way. The parts that need judgement are discounts that aggregate across a quote or a product group, deeply nested bundles, and custom scripts — which is why the analysis reports those separately rather than counting them alongside everything else.
Then you are in the normal place. Most teams find the quoting question after the CRM migration work is already in motion. The guide is meant for that moment too.
Salesforce CPQ to HubSpot
You can answer the quoting question before the decision hardens
Read the spoke that matches your blocker, or run the free CPQ migration analysis and see how many rules, bundles, templates, and scripts are actually in your org.
Need to talk through your case? Book a scoping call.