Let me be upfront: if you’re searching for Salesforce CPQ alternatives because you think Salesforce is getting rid of CPQ, that hasn’t happened … yet. There are good reasons to look at DealHub, Conga, Nue, Revenue Cloud, and others now, so you’re ready when Salesforce does announce an end-of-life date. There’s also a scenario where staying put makes sense.
I’ve spent 15+ years in quote-to-cash implementations and we bring 75+ years’ experience in the space across our company - there’s a consistent pattern we’ve seen in the quote to cash space. You pick a platform, migrate, and only then discover your data wasn’t ready and that you’ve built another mess.
So while yes, I want to cover what to consider migrating to, this article also covers what’s happening to CPQ, whether you should move today, what your options are, and how to choose between them.
One clarifying definition: Configure, Price, Quote software is one piece of quote-to-cash, which is the full process that carries a deal from the first quote through contracts, billing, invoicing, and revenue recognition. So any choice impacts much more than sales.
Click to jump to a section:
- Is Salesforce discontinuing CPQ?
- What is replacing Salesforce CPQ?
- Should you migrate from Salesforce CPQ?
- The main Salesforce CPQ alternatives
- How to choose
- What a CPQ migration puts at risk
- You need a data-first approach that’s platform agnostic
- Budget for more than CPQ migration and re-implementation
- Questions to ask any migration partner, including us
- Where to go from here
- Frequently Asked Questions
Is Salesforce discontinuing CPQ?
Not yet. Salesforce stopped selling new CPQ licenses in March 2025, but:
- It’s not end of life. Existing customers keep their licenses, can add users, and continue to renew. Salesforce hasn’t announced a shutdown date.
- Updates are minimal. CPQ still gets security updates and critical fixes, but new development has gone to its successor, Revenue Cloud, for two years or more.
- New customers can’t buy Salesforce CPQ. If you’re evaluating a quote-to-cash platform today and don’t already have CPQ, you’re choosing between Revenue Cloud and alternatives like DealHub, Conga, and Nue.
You’ll hear people on LinkedIn (and likely your Salesforce AE, if you’re a current customer) say you need to migrate now. I’ll respectfully disagree that you have to, though there are many scenarios where you want to.
What is replacing Salesforce CPQ?
Salesforce’s answer is Revenue Cloud, which has been built natively on the Salesforce platform rather than as a managed package the way CPQ was around Steelbrick.
You’ll see it under a few different names: Revenue Lifecycle Management, Revenue Cloud Advanced (RCA), Agentforce Revenue Management, and, as of this fall, Revenue Cloud again. They are all the same platform, and as of November 2026 Salesforce’s own pages still use more than one of them.
I want to flag something very specific here: moving from CPQ to Revenue Cloud is a full reimplementation - this is NOT a lift-and-shift because the two are built on different architectures (rules-based in CPQ, data-model-driven in Revenue Cloud). I’ve heard stories of RevOps teams being told it’s an upgrade, but we’ve walked through this ourselves - thinking of it as Salesforce’s brand-new v2 instead of some sort of spiritual successor is the right framing.
More on RCA here, if you’re curious: Salesforce Revenue Cloud Advanced? Start With Your Data, Not Your Configuration.
Should you migrate from Salesforce CPQ?
It depends on how you sell today.
As much as I’d love to say “yes, and we help with that,” that would go against everything we stand for.
Stay on Salesforce CPQ if you have:
- A relatively simple, single-channel (inside sales) process
- Simple renewals, or few of them
- A small team managing the instance
- No near-term plans for eCommerce or partner and self-service selling
If quote times are fast and accurate and your quote-to-cash process isn’t a barrier, why fix something that isn’t broken? That’s especially true if you’ve layered in Salesforce Billing for invoicing built off standard sales objects - your entire FP&A may be disrupted by a move.
Start evaluating migrating if you:
- Sell across multiple channels (a direct sales team plus eCommerce, self-service, or partner portals)
- Plan to add a digital or partner channel in the next year or two, since the architecture decision has to happen before that investment, not after
- Struggle with mid-term add-ons or customer upgrades
- Have a new pricing model that will force an overhaul of your pricing catalog anyway
- Fight CPQ’s custom-object complexity on a regular basis
If you’re facing a CPQ renewal, I’d advise you to run the numbers before deciding.
Look at each team it touches:
- Revenue operations: How much time goes to maintaining a system that will eventually go away, or to chasing and fixing quoting problems?
- Accounting: Time to invoice, time until payment arrives, and manual fixes driven by invoicing and billing errors.
- IT: How many Salesforce support requests do you log, and how much time goes to break/fix work?
- The C-suite: How quickly leadership gets accurate, trustworthy reporting when it asks.
Your answer may well be “this is fine for now.” And that’s okay!
If so, keep a migration on the horizon since nobody knows when Salesforce will announce an end date (despite many rumors floating out there; we haven’t seen a confirmed date as of publishing this).
But if you’re pouring time into making a 10+ year old system work, there’s a chance it’s not worth the hassle.
Staying on CPQ is a legitimate option until Salesforce announces an end date.
The main Salesforce CPQ alternatives
Candidly, I’m not going to rank these - ranking platforms without knowing your business is how people end up making a decision based on whichever demo they saw last and ignores the right data-first approach that embraces architecture before activation.
So these are all very much worth considering and we’re happy to help guide you here.
Salesforce Revenue Cloud
I’ve already touched on this above, so two callouts: this may fit if your organization really wants to keep everything within Salesforce and you run several channels at once, such as inside sales plus eCommerce, partner portals, or self-service.
One pricing engine runs across all of them instead of duplicating logic in separate systems. It’s built to handle complex renewals and amendments, and in our experience those still took the most configuration effort, so test them early.
The tradeoff is complexity: we’ve led a CPQ to Revenue Cloud migration for a client and ran into bugs and gaps firsthand. The two years since have been a ton of development and break-fix updates by Salesforce. Is it far better than it was upon launch? Yes, but you want to work with someone who’s seen the gremlins.
DealHub
DealHub sits alongside your CRM (Salesforce, HubSpot, or Microsoft Dynamics) rather than inside Salesforce as a package and covers quoting, contracts, subscriptions, and billing in one place. It tends to suit growing teams that want quote-to-revenue handled in one system and a lighter implementation than a Revenue Cloud rebuild; it’s really strong for mid-market and enterprise SaaS and technology companies, though they also support telecommunications, manufacturing, and others. DealHub lists customers including Intuit, Deel, Gong, and HP’s 3D printing division.
DealHub also acquired Subskribe, a subscription management and billing platform, in November 2025 so worth asking about this roadmap around your entire quote-to-revenue stack.
Full disclosure: we’re a certified DealHub implementation partner and recommend it more often than people may expect. We really like their agentic-first approach to newer developments and excellent customer support - there’s a reason it’s a fast-growing CPQ platform.
Conga
Conga (formerly Apttus) is a Salesforce-native CPQ with contract lifecycle management behind it, and we’ve worked with it in multiple organizations.
Here, you’ll find continuity: move to a newer product from the same vendor without re-platforming. It’s usually considered for complex enterprise pricing and contract-heavy selling.
Conga also acquired PROS’s B2B business in February 2026, which includes PROS Smart CPQ and its pricing optimization as part of the AI development race in the quote-to-cash space right now. If pricing science is your biggest gap, it’s worth asking how their two products will sit together over time.
Nue
Nue is built for SaaS companies and houses CPQ in a Salesforce package with billing alongside it. It’s worth a look if you leverage usage- or credit-based pricing models and are in an earlier-stage high-growth motion, though some larger companies like OpenAI also lean on it today.
Tacton
Tacton is built for manufacturers of highly configurable products, such as industrial machinery. Its engine checks that a configuration can be built before it’s quoted, and it integrates with Salesforce. Expect more value, and more scope, from connecting it to engineering and ERP.
Experlogix
Experlogix is a configuration-focused CPQ for Salesforce, Dynamics 365, and NetSuite, suited to product-heavy businesses with strict configuration rules. It competes closely with Tacton.
Oracle CPQ and SAP CPQ
If quote-to-cash process is anchored in your ERP and you want quoting to share a data model with orders, inventory, and finance then these may be a fit.
My personal opinion is that if you aren’t already on Oracle or SAP, the integration overhead won’t pay off and you should pick another option that’s more modern.
How to choose
Avoid any vendor-led narratives or checklists … I find these questions narrow the field faster:
- What does your pricing model look like? Subscription, usage, hybrid models stress a platform differently than one-time product sales. How often do you have mid-term renewals or upsells, too?
- Where will your CRM live? If Salesforce is permanent, native options are simpler - though having worked with many an integration, they’re quite robust and easy to maintain. So how important is it to have everything in Salesforce for you?
- Do you want conversational or AI-assisted quoting? CPQ gets no new feature development, so building a quote by describing the deal in plain language isn’t coming to it. If that’s on your roadmap, put it in the evaluation now. Smart approvals and upsell insights depend less on the quoting tool and more on whether your data is accurate.
- Who runs it after go-live? A small admin team will feel a complex platform every day.
- What’s forcing your timeline? If I had to guess, probably a renewal date - we’re happy to help you pick something that’s best for you.
Before you commit, run the same test through your top two or three options. Give each vendor your three hardest quotes, one mid-term amendment, and one renewal, built from your own catalog instead of a demo dataset. Compare accuracy, how long each quote took to build, and what it took to configure. Then ask each vendor to price the same use cases, and add license fees, implementation, and ongoing admin to compare them. A vendor that will not run your data is telling you something.
What a CPQ migration puts at risk
Picking the platform is the easier decision. The harder one is what happens to the quotes, contracts, and subscriptions in flight while you switch. On our own Revenue Cloud engagement, new-business quotes priced correctly well before amendments and renewals did, and I’d expect that order on any platform.
| Risk | Decide before you start | How to test it |
|---|---|---|
| Customizations | Inventory price and product rules, flows, Apex, quote calculator code, approvals, templates, and integrations. Retire, replace, rebuild, or defer each, and count the pricing logic your design needs against platform limits. | Run each item through the Four Rs. Test every flow on new business, amendments, and renewals. Ask who fixes quotes by hand. |
| Historical quotes and contracts | Migrate active contracts and open quotes, archive closed ones read-only, and drop the rest. Finance and legal set retention. Keep an old-to-new ID map. | Can finance pull last year’s quote and an open renewal on day one without asking IT? |
| Subscriptions and amendments | Migrate current state and keep history as reference. Decide how co-terming and renewals in flight cut over. Budget more time here than for new business. | Test accounts that hold assets, including odd-day amendments and partial cancellations. Check that a start date plus a term gives the right end dates and that renewals don’t zero out lines. |
| Pricing accuracy | Build a regression set of real quotes, simplest to hardest. Write down intended differences first. | Run each quote through both systems and compare net price, discounts, approvals, and documents. Finance signs off on variances. Retest after every fix. |
| Testing, cutover, and parallel running | Phase by segment or channel, freeze CPQ changes, and keep it licensed through a renewal cycle and a quarter-end. Find out what loads and what must be rebuilt by hand. | Dry-run the production move and time it. Pause configuration work during test windows. Write exit criteria first. |
| Sales disruption and handoff | Avoid quarter-end. Train reps on their own deals. Write the admin guide before go-live. | Can your admin add a product within a quarter without us? Track time to quote and error rate before and after. |
| Platform fit and vendor support | Prove your hardest pricing scenario in a sandbox before committing a timeline. Get named vendor escalation contacts. Check license start dates against a realistic go-live. | Keep a dated log of platform questions and answers. A scenario you can’t prove is a finding, not a delay. |
You need a data-first approach that’s platform agnostic
Whichever CPQ platform you have will faithfully reproduce whatever you hand it, which means a product catalog with a separate SKU for every variant still carries the same complexity for a sales rep building a quote. And if pricing rules exist that nobody remembers writing or there’s a quote/invoice mismatch? Yep, you’re paying to recreate this, too.
If you name an account Acme Inc. in the ERP and Acme LLC in Salesforce and there’s no shared ID then you have duplication. Or, an amendment for an odd number of days prices wrong and someone in accounting quietly fixes it before it reaches the ERP (this happens more than you’d think, yes even today).
Five checks you can run this week
You don’t need us, or anyone, to find out whether your data is ready. Try these before you talk to a vendor or a partner:
- SKUs vs. real products. Count the SKUs in your catalog, then count how many are the same product with a different flavor, size, or region.
- Rules and lookup tables. Count your price rules and lookup entries, how many were touched in the last year, and whether anyone can explain the oldest ones. Lookup tables that have grown to tens of thousands of permutations usually signal a pricing strategy that outran the system.
- Manual overrides. What share of quotes has someone editing price or terms by hand?
- Quote-to-invoice mismatches. How many invoices did accounting correct last quarter?
- Hand-fixes and who does them. Ask finance and RevOps what they quietly fix before data moves on, and who would know if that person left.
If two or more of these look bad, that is your migration scope talking.
Start with the Four Rs
That’s why we run product, pricing, and quote data - in addition to the other of the eight domains - through the Four Rs (relevant, reliable, revealing, and reusable) before any platform decision.
This shows what data’s worth carrying forward and what will slow the migration down. Catalog rationalization is usually the first fix for your revenue lifecycle, in that you structure your catalog around one core product with configurable attributes instead of a SKU per variant. Then, move pricing logic into rules-based configuration so that you never need a sales rep or customer giving 15 pieces of information (again, this happens more than you’d think!).
Ignoring this step has massive costs; our research took Gartner’s enterprise benchmark for the annual cost of poor data and scaled it across U.S. businesses, which came to roughly $617 billion a year.
You can read the full breakdown in The Hidden Cost Of Dirty Data, and if you want the foundation work on its own, that’s our data architecture practice.
Budget for more than CPQ migration and re-implementation
Don’t treat go-live as the finish line. As products and pricing change, systems drift and fall back into break/fix. Plan to keep improving for one to two years after you migrate.
Questions to ask any migration partner, including us
Whoever you talk to, ask these. I’d rather you ask them of every firm on your list.
- Which of our CPQ customizations will you rebuild, which will you retire, and who decides?
- How do you handle our quote calculator plugin code and custom Apex?
- What happens to our historical quotes and contracts, and who owns the retention decision?
- How will you migrate subscriptions and amendments in flight, and how do you test cases like co-termed and mid-term changes?
- How will we prove pricing matches between the old and new systems before cutover, and who signs off?
- How do we run both systems in parallel, and what are the exit criteria?
- What is the rollback plan, and at what point can we no longer roll back?
- Have you led a migration to this exact platform before, and what went wrong?
- How much of your fee depends on outcomes we agree on?
Where to go from here
If you want an answer based on your data instead of a vendor pitch, that’s what our CPQ Migration Assessment does.
We look at whether you need to move, where to land (Revenue Cloud, DealHub, etc.), and what it’ll cost in real terms.
And it’s backed by our Success Guarantee, which ties part of the project fee to KPIs you agree on.
Want a quick read first? Try our free 844 Data Snapshot on your customer domain of data.
Frequently Asked Questions
Is Salesforce phasing out CPQ?
Gradually. Salesforce stopped selling new CPQ licenses in March 2025, but existing customers keep their licenses, can add users, and continue to receive support and critical fixes. No end-of-life date has been announced.
What is replacing Salesforce CPQ?
Revenue Cloud, also called Revenue Cloud Advanced, Revenue Lifecycle Management, and Agentforce Revenue Management, is Salesforce’s successor. Outside Salesforce, common alternatives include DealHub, Conga CPQ, and Nue. Existing CPQ customers aren’t required to move yet, though CPQ will reach end of life at some point.
Is Revenue Cloud better than CPQ?
Not necessarily. It depends on how you sell. Revenue Cloud is built for multi-channel selling, complex renewals, and eCommerce, which CPQ was not designed for. If you have a single channel and CPQ runs well today, you may have no reason to move yet, and a platform like DealHub may be easier to run.
Which CPQ is best?
It depends on your existing data readiness vs. the four Rs test and existing tech stack + sales motion. We take a platform-agnostic approach and help you evaluate fit instead of starting from a preference.
Is CPQ the same as quote-to-cash?
No. CPQ (configure, price, quote) covers building and pricing a quote. Quote-to-cash is the broader process that continues through contracts, orders, billing, invoicing, and revenue recognition, plus renewals and amendments. CPQ is one part of it.
What is the difference between quote-to-cash and order-to-cash?
Quote-to-cash starts earlier, at configuration, pricing, and quoting. Order-to-cash begins once an order is placed or a contract is signed and runs through fulfillment, invoicing, and collections.
Is CPQ owned by Salesforce?
Yes. Salesforce acquired the product, then known as SteelBrick, in 2015. It originally started as a third-party product before becoming Salesforce CPQ.
