ChatGPT
Claude
PerplexitySalesforce CPQ Features and What Replaces Each in 2026
Salesforce CPQ is end of sale, not end of life. Salesforce states that directly and adds that there is no forced migration to its successor, so existing customers keep running and keep getting support. That answer belongs at the top of a features page in 2026, because most people asking what CPQ does are really asking whether it still has a future.
It does, for now. What has changed is that every capability below now has a successor built differently, and that changes which features are safe to invest in.
Ten CPQ features do the work
Feature | What it does | Where teams feel it |
|---|---|---|
Product configuration and bundling | Multi-level bundles with rules enforcing valid combinations | Fewer invalid quotes reaching approval |
Pricing and discount management | Volume, tiered, block, contracted and promotional pricing | Margin control without manual policing |
Guided selling | A question set that filters the catalogue to a fitting product | New reps quoting correctly sooner |
Advanced approvals | Conditional routing by discount, value or terms, with an audit trail | Quarter-end bottlenecks |
Quote documents and e-signature | Templated proposals assembled from quote data | Turnaround from days to same day |
Subscription and renewal management | Recurring terms, amendments, co-terming, renewal quote generation | Renewal revenue protected rather than chased |
Contracted pricing | Negotiated rates remembered and reapplied per account | Consistency across repeat business |
Einstein pricing guidance | Discount ranges suggested from historical outcomes | Fewer reflex discounts |
Multi-currency and localisation | Rates, rounding and tax handling per market | Quoting across regions from one catalogue |
Reporting on quote data | Win rates, discount distribution, quote velocity | Pricing decisions grounded in evidence |
Three of these carry most of the value in practice. Configuration prevents quotes that cannot be fulfilled. Approvals is where deal cycle time is won or lost. And renewal management is the feature that quietly protects the largest revenue number in a subscription business.
Revenue Cloud Advanced rebuilds each capability differently
Salesforce publishes a direct comparison, and it is worth reading before making any further CPQ investment. The successor is Revenue Cloud Advanced, also referred to as Agentforce Revenue Management following the 2025 rename.
Area | Salesforce CPQ | Revenue Cloud Advanced |
|---|---|---|
Architecture | Managed package installed on top of Salesforce, tightly coupled and quote-centric | Native to Salesforce core, API-first, headless and composable |
Composability | Monolithic, adopted all or nothing | Modular, adopt pricing, quoting, ordering or billing independently |
Product model | SKU-based bundles and options | Attribute-based product catalogue |
Pricing engine | Price rules, custom scripts such as QCP and PSP, custom code | Declarative pricing procedures and elements |
Configurator | Rules based | Constraint based |
Quoting | Custom object in a managed package, logic tied to the UI and sequential steps | Standard data model with API-first composable logic |
Sales channels | Primarily direct | Direct, partner, ecommerce, self-service and in-product |
Revenue models | One-time and subscription, limited consumption | One-time, subscription, consumption and hybrid |
Orders and assets | Quote-to-order flow | Order decomposition, orchestration and full asset lifecycle |
Subscription management | Subscription custom object, contract-based amendments | Asset-based amendments, renewals and cancellations |
AI readiness | Limited native support | Built for Agentforce, APIs and headless workflows |
Source: Salesforce, Salesforce CPQ end of sale.
Two rows carry the most weight. The move from a managed package to native core is why the successor can be composed rather than adopted wholesale. And the move from contract-based to asset-based subscription management changes how amendments and renewals behave at a data level, which is the single largest conceptual difference for anyone who has built around CPQ’s subscription object.
CPQ feature choices carry different migration risk
This is the practical consequence and it is why the two tables belong on the same page. Not every CPQ feature you build on today ports at the same cost.
CPQ feature you invest in now | Migration risk | Reason |
|---|---|---|
Standard bundles and product rules | Lower | Configuration intent transfers, even though the model becomes attribute-based |
Approval routing and templates | Lower | The logic is expressible in both, and much of it lives outside the package |
Price rules built declaratively | Moderate | Concepts map onto pricing procedures, but the implementation is rewritten |
Quote document templates | Moderate | Content transfers, assembly mechanics do not |
Custom quote calculator scripts and plugins | Higher | Replaced by declarative pricing rather than ported |
Anything built on the subscription custom object | Higher | The successor is asset-based, so the data model differs |
Heavy custom code around quote objects | Highest | The quoting object model itself changes |
The rule that follows: prefer declarative where a declarative option exists. That has always been sensible advice on Salesforce and it now carries a second benefit, because declarative intent survives a platform change far better than custom script does.
Custom quote calculator scripts are the hardest to carry forward
Quote Calculator Plugins and price script customisations are where mature CPQ orgs keep their hardest-won logic, and they are explicitly the thing the successor replaces rather than reproduces. Declarative pricing procedures cover much of what those scripts were written to do, but the translation is a redesign rather than a lift.
If you are running CPQ today, this is the inventory worth compiling now regardless of whether you plan to move: every custom script, what business rule it implements, and whether that rule could be expressed declaratively. That document is useful immediately for maintenance and becomes the migration scope later.
CPQ decisions go wrong in six predictable ways
Decision | Why it goes wrong | Better move |
|---|---|---|
Treating end of sale as end of life | Panic migration on someone else’s timetable | No forced migration; plan on your own cycle |
Building new custom scripts | Deepening the hardest thing to migrate | Exhaust declarative options first |
Assuming feature parity in reverse | The successor is not CPQ with a new badge | Compare capability by capability |
Ignoring the subscription model change | Amendment and renewal logic behaves differently | Understand asset-based before designing |
Delaying the script inventory | Migration scope unknowable when it matters | Compile it while the authors are still available |
Reading guidance written before 2025 | Names and architecture have both moved | Check the date on anything you rely on |
The last row is worth checking on anything you read about CPQ, including feature lists. Guidance published before the end-of-sale announcement describes a product with a different future.
Salesforce CPQ features and status, condensed
Item | Detail |
|---|---|
Product status | End of sale, not end of life, with no forced migration |
Successor | Revenue Cloud Advanced, also called Agentforce Revenue Management |
Architecture change | Managed package to native core, API-first and composable |
Product model change | SKU-based bundles to attribute-based catalogue |
Configurator change | Rules based to constraint based |
Subscription change | Contract-based amendments to asset-based |
Highest-value CPQ features | Configuration, approvals, renewal management |
Highest migration risk | Custom quote calculator scripts and subscription-object customisation |
The rule to apply now | Prefer declarative wherever a declarative option exists |
For the underlying product definition and how quote-to-cash fits together, CPQ explained covers the fundamentals.
An org inventory precedes any CPQ migration estimate
Whether to stay on CPQ, when to move, and what a move would cost are all downstream of one thing: an accurate picture of what has actually been built in your org. Most CPQ estates have accumulated scripts, rules and customisations that nobody has inventoried, which is why migration estimates for CPQ vary so wildly between vendors.
That inventory is the first thing the AI-native delivery team produces, reading the org’s configuration and custom code to establish what exists before anyone estimates what it would take to change it.
Questions teams ask about Salesforce CPQ features
Is Salesforce discontinuing CPQ?
No. Salesforce states that CPQ is end of sale rather than end of life, meaning it is no longer sold to new customers while existing customers continue to run and be supported. Salesforce also states there is no forced migration to the successor.
What is replacing Salesforce CPQ?
Revenue Cloud Advanced, referred to as Agentforce Revenue Management following the 2025 rename. It is a native, API-first, composable rebuild rather than a new version of the managed package, with an attribute-based catalogue and asset-based subscription management.
What are the main Salesforce CPQ features?
Product configuration and bundling, pricing and discount management, guided selling, advanced approvals, quote documents with e-signature, subscription and renewal management, contracted pricing, Einstein pricing guidance, multi-currency support and quote reporting.
Should we still build on Salesforce CPQ?
For run-the-business changes, yes, since there is no forced migration. For significant new investment, prefer declarative configuration over custom scripts, because declarative intent survives a platform change considerably better than custom code does.
What is the biggest difference between CPQ and Revenue Cloud Advanced?
Architecture. CPQ is a managed package installed on top of Salesforce and adopted as a whole; the successor is native to the core and modular, so pricing, quoting, ordering and billing can be adopted independently.
How hard is migrating from CPQ?
It depends almost entirely on how much custom script and subscription-object customisation you have. Standard bundles, rules and approvals transfer in intent. Quote calculator plugins and asset-model differences are where the real effort sits, which is why an inventory should come before any estimate.
