Salesforce CPQ End of Sale: What It Actually Changes, and What It Doesn't

In March 2025, Salesforce confirmed the Salesforce CPQ end of sale: the product stopped selling to new customers, full stop. Nothing else happened that week - no shutdown date, no forced migration, no change to a single contract already in force. Eighteen months on, plenty of CPQ customers still haven't decided what, if anything, that means for them, and a long line of migration vendors has found a dependable business explaining to those customers, loudly, that the sky is falling faster than Salesforce itself has ever said it is.

If your org is one of them, the decision in front of you isn't "migrate or don't" - it's whether the CPQ build you're running today is light enough to wait, or custom enough that waiting is itself a decision with consequences. That's the same judgment call behind most Salesforce build vs. buy choices: the risk was never the licensing line, it's who ends up owning the rules once the platform underneath them changes.

The short answer

In brief: the CPQ end of sale is a sales-motion change, not a product shutdown. Salesforce's own page on this is titled "End of Sale (Not End of Life)," and current customers keep support, renewals, and the right to add seats. Nothing in the announcement forces a migration this year. What should actually drive your timeline is three things that have nothing to do with the announcement itself: how much custom price and product rule logic your CPQ build is carrying, when your contract next renews, and whether CPQ is already causing operational pain independent of any of this news. If the honest answer to all three is "not much, not soon, not really," this is a watch-and-revisit decision, not a line item for next year's budget.

What the Salesforce CPQ end of sale actually changed

Salesforce stopped taking new CPQ orders - confirmed in reporting from Salesforce Ben and echoed across implementation partners since. Existing customers kept everything: support, critical fixes, renewal rights, and the ability to add users under their current contract. What Salesforce redirected was new product investment - new CPQ features stopped shipping, and new engineering effort moved to Salesforce's newer quoting line. That's the entire scope of the announcement. On its own, it doesn't obligate an existing CPQ customer to do anything differently before their next renewal conversation.

End of sale, not end of life - so far

Salesforce draws this distinction itself, in its own CPQ lifecycle messaging: end of sale, not end of life, with no forced migration path to the newer product. No official end-of-life date exists for Salesforce CPQ. The 2029-2030 range quoted across migration-vendor blogs is analyst extrapolation from a typical four-to-five-year gap after an end-of-sale announcement elsewhere in enterprise software - not a Salesforce commitment, and not something to put on a calendar. What Salesforce has committed to, repeatedly, is that current customers retain support and renewal rights for now. "For now" is doing real work in that sentence, which is exactly why it's worth confirming at your next renewal rather than trusting any one article's timeline, including this one.

The name keeps changing. That's not your deadline.

CPQ's successor has been rebranded at least twice in under two years: Revenue Lifecycle Management, then Revenue Cloud Advanced, now also marketed in some places as Agentforce Revenue Management. Vendor write-ups don't agree on the exact order, and Salesforce's own regional pricing pages still use more than one of these names side by side. None of that is a reason to move faster. A product whose own marketing hasn't settled on a name yet is not a product to build a 2026 migration deadline around - it's a reason to confirm the current name, edition, and per-user price directly with your account team before any internal business case cites a figure from a blog post, including the ones linked below.

Why "just migrate" undersells the work

CPQ runs on managed-package custom objects; Revenue Cloud Advanced is built on standard platform objects. That's not a packaging footnote - it means price rules, product rules, bundle logic, and approval flows don't move with a data export, because the object model they're written against doesn't exist on the other side. No Salesforce-provided automated migration tool carries that logic across for you. Every price rule and product rule gets re-evaluated and effectively rebuilt against the new data model, which is why informed estimates of migration cost and duration disagree by an order of magnitude - from a few weeks to several months, from the cost of a bounded Fix Sprint to six figures - depending almost entirely on how much custom rule logic a given org is carrying. Anyone quoting you a single number before asking how many price rules you have is quoting from a template, not from your org.

What to do, by situation

What to check before your next renewal conversation

1. Count your active price rules and product rules, and note how many were added in the last 18 months versus inherited from the original build.
2. Ask your account executive for Revenue Cloud Advanced's current name, edition, and per-user price in writing - not from a slide deck.
3. Confirm whether any CPQ limitation you're already working around (approval bottlenecks, slow quote generation, rule conflicts) would still exist on the new platform, or is specific to CPQ itself.
4. Get a migration-scope estimate from someone who has actually counted your rules, not a flat quote based on seat count alone.

If nobody in your org can currently answer the first question without opening a sandbox and counting, that's the kind of inventory gap a Salesforce Health & Roadmap assessment is built to close before a vendor conversation starts, not during one.

What not to do yet

Don't sign a Revenue Cloud Advanced contract because a vendor's slide says CPQ is "going away." It isn't, not on any timeline Salesforce has published. Don't let renewal-cycle pressure turn into a rushed reimplementation of pricing logic nobody has fully documented - that's a worse version of the exact fix, rebuild, or reimplement decision most orgs already struggle to make calmly. And don't assume a competitor's analyst placement settles anything for you: ServiceNow's own announcement names it a Leader and a "Customer Favorite" in Forrester's Q4 2026 CPQ Wave, built partly on its Logik CPQ acquisition - but a vendor's self-reported placement in an analyst report is marketing, not due diligence on your specific requirements, and Salesforce's own position in that same Wave isn't something we could independently confirm.

Questions worth answering before the next renewal

Is Salesforce CPQ actually shutting down?

No. Salesforce stopped selling it to new customers in March 2025, but existing customers keep support, critical fixes, and renewal rights, and there's no published end-of-life date. Salesforce's own messaging explicitly frames this as end of sale, not end of life.

What's the difference between CPQ, Revenue Cloud Advanced, and Agentforce Revenue Management?

CPQ is the legacy, managed-package product no longer sold to new customers. Revenue Cloud Advanced is its intended successor, built on standard platform objects; Agentforce Revenue Management appears to be a later rebrand of the same line in some of Salesforce's own marketing. The naming has moved more than once in under two years, so confirm the current name and packaging with your account team rather than relying on any third-party summary.

How long does a CPQ to Revenue Cloud Advanced migration actually take?

There's no reliable single figure - published estimates range from a few weeks to several months, because duration tracks almost entirely with how many price and product rules your org has accumulated, not with license size. Treat any fixed-weeks quote you receive before a rule count has been done as a sales estimate, not a scoped one.

Do we need to decide before our next renewal?

No - but use the renewal conversation to get real numbers in writing (current product name, pricing, and whether anything in your contract changes), rather than signing anything under the pressure of an end-of-sale date that, on its own, changes nothing about your current usage rights.

The bottom line

The Salesforce CPQ end of sale is eighteen months old, hasn't been followed by an end-of-life date, and doesn't obligate anyone to act this year. What should drive your timeline is the same thing that should always drive a platform-migration decision: how much custom logic you're actually carrying, not how urgently someone else needs you to move. If you're not sure how much custom price and product rule logic your own CPQ build has accumulated, that's a scoping question worth answering before the next renewal conversation, not during it - talk to us if you'd rather get an outside count before the number comes from the vendor selling you the migration.