Approvals
Yes, HubSpot can handle multi-step approvals.
HubSpot CPQ Enterprise handles approvals well. The useful decision is not whether approvals exist. The useful decision is which quoting stack you are on, and whether the values underneath the approval rules already exist.
Short answer · Native works · Revenue Hub Enterprise required · Trigger logic still matters
When native is enough
If approvals are the only gap in your quoting workflow, HubSpot CPQ Enterprise is usually the direct. You buy the Enterprise tier, configure the approval routing, and keep the rest of your quoting process inside HubSpot.
Approvals are not a separate menu item
You cannot lift HubSpot approvals out of the native quoting stack and place them on Quotivity quotes. Approvals come with the quoting stack you choose. That is what makes the decision clearer.
If you stay native, you use HubSpot approvals. If you move to Quotivity for pricing, configuration, or guided selling, Quotivity brings approvals with it.
The real question is what approvals depend on
An approval based on discount percentage is straightforward in either stack. An approval based on margin after freight, a bundle total, or a rolled-up quote value only works once that value exists and is reliable.
The approval layer is usually fine. The pricing layer underneath it is what changes the recommendation.
| If approvals are... | The answer is | Why |
|---|---|---|
|
The only gap
|
HubSpot CPQ Enterprise
|
You do not need Quotivity when native quoting already fits the rest of your process.
|
|
One of several gaps
|
Quotivity
|
Approvals come with the quoting stack, so you are not giving them up when pricing, configuration, or guided selling need more than native can offer.
|
|
Dependent on calculated values
|
Inspect pricing logic first
|
Approval routing only works when margin, bundle totals, or rolled-up values exist before the rule fires.
|
|
Dependent on the Salesforce approval model
|
Map the current system
|
Many teams do not know whether they use Advanced Approvals or native Salesforce approval processes today, and that changes the migration path.
|
Need the pricing side of that decision? See the cost breakdown.
What to inspect before you migrate approvals
- Approval rules and chains. Count the stages, the routing steps, and the people involved.
- Tracked fields and derived approvers. Check whether the route depends on a field lookup rather than a fixed approver.
- Calculated trigger values. Find every rule that depends on margin, freight, bundle totals, or rolled-up quote values.
- Exception paths. Note any bypass, escalation, or fallback logic that keeps deals moving when an approver is unavailable.
When you should run the analysis
- You are leaving Salesforce CPQ and need to identify the approval model before migration.
- Your approval rules depend on calculated values that may not exist yet in HubSpot.
- You know native approvals are good, but you need to see whether pricing logic or configuration pushes the decision beyond approvals.
Questions buyers ask about approvals
No. If native HubSpot quoting already fits the rest of your process, HubSpot CPQ Enterprise is the direct answer for multi-step approvals. The decision changes only when approvals sit alongside pricing, configuration, or guided selling requirements that need a fuller quoting workflow.
No. Quotivity includes its own approval capability inside the quoting workflow. The tradeoff is not approvals versus no approvals. The tradeoff is whether your pricing logic, product configuration, and approval routing are better handled by the native stack or by a fuller CPQ workflow inside HubSpot.
Teams often say they use advanced approvals when the routing is built with native Salesforce approval processes, or the other way around. That difference changes the migration plan because the objects, dependencies, and rebuild effort are not the same.
The hard part is rarely the route itself. The hard part is the value that triggers the route. A discount threshold is simple. Margin after freight, a bundle-level total, or a rolled-up quote value only works when that calculation exists and is trusted before the approval fires.
The analysis counts your approval rules, chains, tracked fields, and approver logic, identifies whether you are using the Advanced Approvals package or native Salesforce approvals, and shows whether your routing depends on values that need to be rebuilt before migration.
Approvals matter, but they are not the whole decision
These results came from broader quoting workflow changes. They are useful here because they show what improves once approval routing, pricing logic, and configuration accuracy work together in one system.
Sales reps are incentivized to stick to price book because they can get their deal out the door much faster.
Renée Durrance
Senior Director of Business Systems, Aptarro
Most of our junior reps just grabbed it, and they love it because they do not have to remember all of the different subtypes.
Kalee Nichols
Manager, True North
5.0 from 18 published reviews and 400+ installs on the HubSpot marketplace, as of August 2026.
Approval migration analysis
Map the approvals before you move the quoting stack
We count your approval rules, chains, tracked fields, and approver logic, identify which Salesforce approval system you are actually using, and show whether your routing depends on values that need to be rebuilt first.
Need the pricing side of this first? See the CPQ Pricing page.