Salesforce stopped selling CPQ to new customers in March 2025. Existing orgs keep running — but there is no upgrade path, which changes the maths on every alternative.
Salesforce announced the end of sale for Salesforce CPQ — the SteelBrick-based managed package — in March 2025. It is no longer sold to new customers.
If you are already running it, nothing broke. You keep your licences, you keep support, and you can renew. There is no announced end-of-life date. What you do not get is new functionality, and over time you will find fewer specialists who know it well.
There is no migration path from Salesforce CPQ to Revenue Cloud. You do not upgrade; you reimplement — rebuilding your product catalogue, pricing rules, approval logic and document templates from scratch.
That single fact matters more than anything else, because it removes the argument that usually keeps companies where they are. Switching costs normally protect an incumbent. Here there is no incumbent to protect: whatever you choose, you are rebuilding.
So the question stops being "should we move?" and becomes "given that we are rebuilding anyway, what should we rebuild on?"
Perfectly reasonable for a while. The product works and it is supported.
The cost is not immediate, it is gradual: no new capability, a shrinking pool of people who know the product, and a migration that still happens eventually — just later, and probably under more time pressure than you would choose.
Salesforce's own answer, and the right one for genuinely complex businesses. It handles multi-ramp deals, usage-based billing and revenue treatment that most mid-market companies never need.
Salesforce publishes the licence pricing: Revenue Cloud (formerly Revenue Lifecycle Management) sits at 150 to 200 US dollars per user per month depending on edition. For thirty quoting users that is roughly 54,000 to 72,000 US dollars a year in licences alone, before implementation — which is a partner-led project measured in months, not weeks.
If you are a five-thousand-person enterprise, that is proportionate. If you are a hundred-person software company, it is a board-level decision to solve a problem that used to cost you a fraction of that.
DealHub and Conga are both good products with real strengths. Two things to weigh.
The first is architectural: their data lives outside Salesforce and synchronises back. That means two systems that can disagree, and a reconciliation problem that becomes somebody's job.
The second is scope. Both are strongest up to the signed document; beyond it, their coverage thins out. Subscription management, renewal automation and revenue reporting need another tool, which means another contract, another integration and another place your numbers can diverge.
For European companies there is a third consideration: these platforms often host data in the United States by default, which can turn a software purchase into a data protection conversation.
This is the option that did not really exist until recently, and it is why we built Revligent.
The argument is simple. The thing you liked about Salesforce CPQ was that it was native — one system, one security model, no synchronisation. The thing you did not like was that changing anything required a specialist.
So keep the first and fix the second: a managed package that installs in your own org, configured by your revenue operations team rather than a consultancy, covering quoting and approvals and then carrying on through subscriptions, renewals and ARR reporting.
Three questions, in this order.
Do you need usage-based billing today? If yes, look at Revenue Cloud or a specialist. That is genuinely hard and we do not do it yet.
Does your quoting stop at the signature? If the answer is no — if you also need to know what customers are paying eighteen months later — then a quoting-only tool leaves you assembling the rest yourself.
Who will own it after go-live? If the honest answer is "a consultancy on retainer", price that in. It is usually the largest number in the comparison and the one nobody puts on the slide.
Whatever you choose, start by exporting your current CPQ configuration — product catalogue, price rules, approval logic, templates — while the people who built it are still around. You will need it for the rebuild regardless of the destination, and it is much harder to reconstruct later.
Figures cited are from Salesforce's published pricing and third-party implementation benchmarks as at September 2026. Vendor pricing changes; verify before you decide.
Thirty minutes in your Salesforce sandbox. We install it, configure your pricing, and quote a real opportunity end to end.