The Salesforce CPQ Sunset Is a Strategy Decision. Treat It Like One.
Salesforce CPQ went End-of-Sale in March 2025. For most companies we talk with, it reads like an IT ticket. Swap one quoting tool for another. Move on.
Six months into migration, they see it differently. This is not a CPQ replacement. It is a rebuild of your revenue operations architecture. And a rebuild is the moment to ask a bigger question than "what replaces CPQ?"
The bigger question: if you are rebuilding everything anyway, does deeper Salesforce consolidation serve your business?
We have guided European mid-market companies through 50+ forced migrations. The ones who come out ahead ask that question before they pick a tool.
ON THIS PAGE
This is not a tool swap
Your CPQ does not work alone. It connects your CRM to your ERP, your billing, your contract management, and your document generation. When CPQ sunsets, every one of those integration points breaks and needs rebuilding.
Revenue Cloud does not change that. It is a complete reimplementation, not an upgrade. Same timeline. Same disruption. Same user retraining as moving to any other platform.
So the real choice is not "rebuild or not." You rebuild either way. The choice is what you rebuild on.
What the sunset forces you to decide
You have two paths.
Path 1: Consolidate deeper into Salesforce. Migrate to Revenue Cloud Advanced. Rebuild your CPQ logic, pricing rules, and workflows. Accept the licensing increase. Run quoting, billing, contracting, and revenue operations inside one vendor's ecosystem.
Path 2: Use the rebuild as a strategic exit. Move to HubSpot or another CRM. Pair it with a specialised CPQ that connects to both your new CRM and your existing ERP. Keep platform independence and renewal leverage.
Most companies skip Path 2 without examining it. They assume changing CRM is harder than changing CPQ. It rarely is, because you are already rebuilding CPQ in full. Revenue Cloud asks for the same configuration effort, the same timeline, and the same process redesign as any alternative. The difference is whether you stay locked to one vendor or regain flexibility.
The platform independence alternative
Across our implementations, one pattern holds: companies that keep CRM and CPQ independent carry more flexibility and often a lower long-term cost.
The architecture looks like this. Your customer data lives in HubSpot. Your product data stays in your ERP, whether SAP, Microsoft Dynamics, or Oracle. Your specialised CPQ sits between them with native connectors to both.
When Salesforce makes a strategic change, you are not exposed. When a CPQ vendor raises prices, you switch CPQ without touching CRM or ERP. The dependency that forced this migration stops being a single point of control.
What we see when companies take this path:
- Faster adoption. A simpler interface lowers sales resistance, and migrations finish faster when users want the new system.
- Lower lock-in risk. A vendor's strategy change hits one system, not your whole revenue stack.
- Renewal leverage. Independence keeps competitive pressure on every contract.
What this looks like in practice
Consider the pattern we see most in SAP environments. A mid-market manufacturer runs Salesforce CRM, Salesforce CPQ, and SAP ERP. They use Sales Cloud but not Service Cloud or Marketing Cloud. The sales team finds Salesforce heavy. Product data and pricing logic live in SAP. Salesforce has grown expensive for what they actually use.
CPQ goes End-of-Sale. Salesforce proposes Revenue Cloud: a higher licensing cost and a full rebuild. The CTO asks the question that changes the project. "If we rebuild anyway, why stay with the vendor that forced this?"
The alternative on the table: HubSpot CRM with a specialised CPQ connected natively to SAP. Same rebuild effort. A different long-term architecture. Sales reps adopt faster because the interface fits how they work. Native connectors remove manual data entry between systems. Integration upkeep drops because vendor-maintained connectors replace custom code.
The lesson is not "leave Salesforce." It is that a forced rebuild is a rare chance to re-examine the whole architecture, while the cost of switching is already on the table.
How to tell which path fits you
Revenue Cloud fits if:
- You use several Salesforce clouds, so consolidation genuinely simplifies your stack.
- You need Salesforce's native billing and revenue recognition.
- Your team prefers Salesforce despite the complexity, and change resistance outweighs cost.
- Your strategy is committed to the Salesforce platform.
Platform independence fits if:
- You use mainly Sales Cloud, and your other revenue operations run outside Salesforce anyway.
- Your SAP or ERP integrations matter more than native CRM-CPQ integration.
- You want protection from the next vendor-forced migration.
- Your sales team complains about Salesforce complexity, and your CFO is questioning the cost trajectory.
The question to ask before you decide
What happens when the next Salesforce product sunsets in five years?
Consolidation means the vendor's roadmap decides your hand. Independence means you control timing and selection. This is not hypothetical. You are living it right now with CPQ.
Then run the numbers. Calculate the five-year total cost of ownership for both paths. Include licensing, implementation, training, integration maintenance, and the cost of a future forced migration. Add the hidden costs: productivity loss during transition, integration rebuilds, process redesign, and parallel operation.
Independence often lands at a lower five-year cost, driven by licensing and reduced lock-in. The stronger argument is strategic control, not the cost line alone.
How we help
We start by mapping your real architecture. Where does your customer data live? Where does your product data live? How do your systems actually connect today?
Then we evaluate both paths honestly. Revenue Cloud with realistic costs and timelines. Platform alternatives with realistic costs and timelines. We show you both and let you decide. For SAP environments, we usually recommend DealHub. For document-heavy workflows, GetAccept.
Book a Strategic Architecture Assessment. You'll receive an honest evaluation of both paths, a map of where your data lives and how systems connect, a risk assessment for each migration approach, timeline estimates based on your real configuration, and a cost comparison you can share with your executive team.
Some companies should stay on Salesforce. We will tell you if you are one of them.
