If you run Salesforce CPQ, your CFO or CIO has probably asked you a direct question: are we being forced off this product, and what happens at our next renewal? The short answer is that Salesforce CPQ reached end of sale in March 2025. That is not the same as Salesforce CPQ end of life. This article explains the difference in plain terms and what it means for your license renewal, support, and budget. It also shows how to use your renewal cycle as a planning checkpoint rather than a panic button.
TL;DR
- Salesforce stopped selling Salesforce CPQ to new customers in March 2025. That is end of sale, not end of life.
- Salesforce has not announced an end-of-life date for Salesforce CPQ. Existing customers can keep using the product, renew licenses, add users, and receive support.
- What changes is investment, not entitlement. Salesforce has moved its strategic development to Revenue Cloud Advanced (RCA), now part of Agentforce Revenue Management. Salesforce CPQ is effectively in maintenance mode, with little meaningful new feature development.
- Moving from Salesforce CPQ to Revenue Cloud Advanced is a reimplementation on a different data model, not an upgrade. Treat it as a redesign project with its own budget and timeline.
- Bottom line: your next CPQ renewal is a decision checkpoint, not a deadline. Use it to compare three paths: renew and stay, plan an RCA reimplementation, or keep Salesforce CRM and replace only the quoting layer.
What "end of sale" actually means for Salesforce CPQ
End of sale means new customers can no longer buy the product. It does not mean the product stops working, loses support, or can no longer be renewed. Most of the anxiety about Salesforce CPQ end of life comes from mixing up these two terms, so this distinction matters more than any other point in this article. For background on the announcement itself, see what Salesforce CPQ users should know about end of sale.
Here is how the terms differ in practice:
- End of sale: new customers can no longer buy Salesforce CPQ. Existing customers keep their entitlements.
- End of life: the vendor sets a date after which the product is no longer supported or operable. Salesforce has not announced an end-of-life date for Salesforce CPQ.
- Maintenance mode: the product keeps running and keeps receiving support, but strategic engineering investment has moved elsewhere. This is the best description of Salesforce CPQ today.
So the configure-price-quote (CPQ) engine you run tomorrow is the same one you ran yesterday. What has changed is where it is headed.
What this means for your CPQ renewal and license renewal
Your CPQ renewal is still a normal commercial renewal. Existing Salesforce CPQ customers can renew, add users, and keep receiving support. The end-of-sale announcement does not block a license renewal or put you on a vendor-imposed migration clock.
What changes is the value you get for the money. When you renew a product in maintenance mode, you pay for stability and continuity, not for a roadmap. That can be a sound purchase, especially if your quoting process is stable and your product catalog is not getting more complex.
Before you sign, ask a few concrete questions:
- What is our renewal term, and does it line up with any CPQ replacement or redesign we are considering?
- What new capability did we receive in the last two renewal cycles, and what do we expect in the next one?
- How much of our annual CPQ spend goes to consultants, admins, and custom development rather than licenses?
- Which upcoming commercial initiatives, such as new revenue streams, new regions, or new product lines, would stress our current configuration?
A shorter renewal term gives you more room to change course. A longer term may give you price stability. Neither choice is wrong. What matters is choosing on purpose instead of renewing by default.
Support, stability, and the real risk of staying
Support continues, so staying on Salesforce CPQ does not put you at risk of an outage. The risk is accumulation. Over time, the gap between what your business needs and what a product in maintenance mode delivers tends to grow quietly.
In practice, that gap shows up as:
- Business requirements met with custom code instead of configuration, including Quote Calculator Plugin (QCP) customizations that only a specialist can safely change.
- Product rules and price rules so intricate that routine catalog changes need a consultant.
- Managed package constraints that limit how far you can extend the quoting experience inside Salesforce CRM.
- Slow performance on very large quotes and deeply nested bundles.
- More and more middleware to keep enterprise resource planning (ERP) data, pricing, and bills of materials (BOMs) aligned with the quote.
None of these is a reason to drop the product on short notice. They are reasons to know your own numbers before your next renewal.
Where Salesforce CPQ still earns its keep
Salesforce CPQ remains a reasonable fit for low to moderate quoting complexity. That means catalogs that do not change constantly, stable approval workflows, and a quote-to-cash process that lives entirely inside Salesforce. If that describes you, it is a sound plan to renew and revisit the question in twelve or twenty-four months.
Salesforce CPQ struggles when the business runs on complexity. Examples include thousands of product permutations, hardware, services, labor, and subscription revenue mixed on one quote, or quoting that depends on live ERP data for inventory, cost structures, and BOMs. In those environments, middleware, spreadsheets, and developer tickets start to pile up.
Your three paths after the Salesforce CPQ end of sale
There are three realistic paths, and the end-of-sale news does not choose one for you. Each is summarized below. For a deeper evaluation, see the three paths compared.
Path one: renew and stay
Keep Salesforce CPQ, your support, and your current process. This works best when quoting complexity is modest, the configuration is stable, and other projects rank higher for budget and attention. The cost is a roadmap that stands still while your requirements change.
Path two: reimplement on Revenue Cloud Advanced
Revenue Cloud Advanced is where Salesforce is investing, and it now sits within Agentforce Revenue Management. It uses an attribute-based, API-first architecture with a different data model, so moving to it is a reimplementation and redesign, not a version upgrade. This path fits best if you are committed to a single-vendor revenue platform that covers pricing, billing, and lifecycle management, and you are prepared for a redesign project.
Path three: keep Salesforce CRM and replace only the quoting layer
You can change CPQ without changing CRM. This path keeps Salesforce CRM as your system of record, along with your existing accounts, opportunities, reporting, and user habits. Only the configure-price-quote engine is replaced, with one suited to your level of complexity. For a full look at this option, see how you can keep Salesforce CRM and replace only the quoting layer.
Experlogix CPQ is one option on this path. It integrates natively with Salesforce CRM and runs inside the Salesforce workflow, so business users configure, price, and quote without leaving the opportunity and account context they already know. Quoting works with your CRM data where it lives. That helps you avoid the costs of copying records into a separate platform and syncing them back: stale or mismatched records, sync failures, duplicate data, reporting based on a copy instead of the source, and extra middleware to maintain.
If complexity is why you are looking, Experlogix CPQ supports:
- Logic-driven product models with a rule engine
- Guided selling and workflow automation
- Multi-level BOM generation, routing validation, and ERP handoff for production
Administration is low-code, so business users and admins can maintain rules and product logic with less reliance on developers or consultants.
This path is not for everyone. One of the other two paths probably fits better if your catalog is simple, you run a pure self-service SaaS model, or your organization has already committed to a Revenue Cloud Advanced reimplementation.
The bottom line on Salesforce CPQ end of sale versus end of life
Salesforce CPQ is end of sale, not end of life. Existing customers keep their licenses and support, can renew and add users, and have no announced end-of-life date to plan around. The product is effectively in maintenance mode while Salesforce invests in Revenue Cloud Advanced. Moving to Revenue Cloud Advanced is a reimplementation on a different data model, not an upgrade.
So your CPQ renewal is a planning checkpoint, not a forced march. Use it to compare the three paths honestly: renew and stay, plan an RCA redesign, or keep Salesforce CRM and replace the quoting layer. Base the decision on four things: your quoting complexity, how much you depend on custom code and consultants, your total annual cost of ownership, and the commercial initiatives on your two-year roadmap. If timing is the open question, this guide on whether to migrate now or wait can help.
A practical next step: before your next license renewal date, take an inventory of your Salesforce CPQ footprint. Include:
- Product bundles
- Product and price rules
- QCP scripts
- Approval workflows
- Quote templates
- Integraties
- The open quotes, contracts, and renewals that depend on them
That inventory is useful whichever path you choose. It turns an abstract question about Salesforce CPQ end of life into a decision you can back with evidence.
Veelgestelde vragen
Is Salesforce CPQ end of sale or end of life?
Salesforce CPQ is end of sale. Salesforce stopped selling it to new customers in March 2025. End of life would mean a date after which the product is no longer supported or operable, and Salesforce has not announced one.
Can existing Salesforce CPQ customers still renew licenses and add users?
Yes. Existing customers can renew their licenses, add users, and keep using the product. The end-of-sale announcement does not block renewals or force a migration.
Has Salesforce announced a Salesforce CPQ end-of-life date?
No. Salesforce has not announced an end-of-life date for Salesforce CPQ. Its strategic investment has moved to Revenue Cloud Advanced, now part of Agentforce Revenue Management, and Salesforce CPQ is effectively in maintenance mode.
Is Salesforce CPQ still supported?
Yes. Existing Salesforce CPQ customers continue to receive support. The practical change is that the product gets little meaningful new feature development, so the main risk of staying is a growing gap between your needs and the product's capabilities, not a loss of support.
What should we ask before renewing Salesforce CPQ?
Ask whether your renewal term lines up with any CPQ redesign or replacement you are considering. Ask what new capability you received in recent renewal cycles and how much of your annual CPQ spend goes to consultants, admins, and custom development. Also ask which upcoming initiatives, such as new revenue streams, regions, or product lines, would stress your current configuration.
Make your next Salesforce CPQ renewal a real decision
