Blog
Is Salesforce CPQ End of Life? End of Sale Status, Timeline, and What It Means for SaaS Teams

Updated: February 2026
Searches for “Salesforce CPQ end of life” have increased following Salesforce’s shift toward Revenue Cloud Advanced.
So what’s actually happening?
Short Answer:
Salesforce CPQ is not End of Life. It is in End of Sale, meaning new customers cannot purchase it, but existing customers can renew and receive support. Salesforce’s long-term innovation focus has shifted to Revenue Cloud Advanced, now known as AgentForce Revenue Management
Salesforce CPQ Status at a Glance
Current Status: End of Sale
End of Life: Not announced
New Customers: No longer available for purchase
Existing Customers: Renewals and support continue
Strategic Focus: Revenue Cloud Advanced (AgentForce Revenue Management)
Salesforce CPQ is not currently End of Life. However, it is no longer Salesforce’s primary innovation focus. In practical terms, Salesforce CPQ has entered a transition phase — not an immediate shutdown, but no longer a long-term innovation priority.
For SaaS companies running Salesforce CPQ today, that distinction matters.
This guide explains:
The difference between End of Sale and End of Life
What Revenue Cloud Advanced (AgentForce Revenue Management) replaces
Expected long-term timelines
Migration considerations
When it makes sense to evaluate alternatives
What Is “End of Sale”?
End of Sale means the product can no longer be purchased by new customers. Existing customers can continue renewing licenses and receiving support.
When a product reaches the End of Sale milestone, innovation ends as the vendor shifts investment elsewhere.
What Is “End of Life”?
End of Life means the product is fully discontinued. Renewals and support end, and customers must migrate to a replacement platform.
Salesforce CPQ is currently End of Sale, not End of Life.
That means it remains supported, but it is no longer Salesforce’s long-term strategic investment.
Is Salesforce CPQ Being Discontinued or Sunset?
Salesforce has not announced a formal End of Life date.
However:
Salesforce CPQ entered End of Sale
Salesforce is positioning Revenue Cloud Advanced (AgentForce Revenue Management) as its long-term revenue platform.
Industry analysts anticipate eventual migration pressure over the next several years.
Salesforce has not publicly used the term “sunset” to describe Salesforce CPQ. However, the shift in innovation investment to Revenue Cloud Advanced (AgentForce Revenue Management) indicates that Salesforce CPQ is no longer the long-term strategic revenue platform.
What Replaces Salesforce CPQ?
Salesforce is actively promoting Revenue Cloud Advanced (AgentForce Revenue Management) as its strategic successor, expanding quoting into:
Subscription billing
Revenue lifecycle orchestration
Advanced billing automation
AI-driven revenue insights
Salesforce CPQ, CPQ+, Revenue Cloud, Revenue Cloud Advanced (AgentForce Revenue Management), and Revenue Lifecycle Management — What’s the Difference?
Over the years, Salesforce sold CPQ in several packaging variations:
Salesforce CPQ (standalone): The original managed package (formerly SteelBrick).
CPQ+: Bundled CPQ with document generation, advanced approvals, limited contract lifecycle management, and advanced order management.
Revenue Cloud: Expanded packaging including Salesforce Billing, Subscription Management, and Contracts.
Revenue Lifecycle Management: Introduced in 2024 as a native (non–managed package) CPQ architecture built directly on the Salesforce platform.
Revenue Cloud Advanced (AgentForce Revenue Management): Salesforce’s strategic revenue platform, which includes Revenue Lifecycle Management and broader billing and lifecycle capabilities.
The key shift: Salesforce CPQ was a managed package. Revenue Lifecycle Management and Revenue Cloud Advanced (AgentForce Revenue Management) are native platform architectures. Unlike Salesforce CPQ, which operates as a managed package inside Salesforce, Revenue Lifecycle Management and Revenue Cloud Advanced (AgentForce Revenue Management) are native platform architectures designed to replace, not extend, the original CPQ model.
That distinction matters because native platform rebuilds typically require reimplementation — not simple upgrades.
This is not a simple feature upgrade. It represents architectural evolution.
Salesforce CPQ Timeline: What We Know
Salesforce has shifted its revenue product strategy toward Revenue Cloud Advanced (AgentForce Revenue Management) and its newer architecture.
What this means today:
Salesforce CPQ (the legacy managed package, formerly SteelBrick) is no longer the primary focus of innovation.
Net-new investment and product development are centered on Revenue Cloud Advanced (AgentForce Revenue Management).
Existing Salesforce CPQ customers can continue renewing licenses.
Salesforce has not publicly announced a formal End of Life date.
At this time, there is no published End of Life timeline.
However, historically in enterprise software, once a formal End of Sale announcement is made, transition windows can compress quickly, especially for mission-critical revenue systems.
Revenue infrastructure migrations are rarely simple. Waiting until an official End of Life declaration can create resource constraints, budget pressure, and implementation timelines driven by necessity rather than strategy.
For organizations running complex quoting environments, early evaluation preserves optionality and reduces execution risk.
Roadmap Risk: The Hidden Factor
When a product reaches the End of Sale milestone, innovation velocity typically shifts.
For revenue systems like CPQ, this introduces long-term considerations:
Reduced feature investment
Slower architectural modernization
Increasing divergence from subscription billing innovation
Growing complexity around integration with newer revenue tools
For SaaS companies that frequently evolve pricing models, roadmap alignment matters.
Why SaaS Companies Were Re-Evaluating Salesforce CPQ Even Before End of Sale
The End of Sale announcement accelerated evaluation, but many teams were already reassessing their CPQ architecture.
Common drivers include:
1. Managed Package Architecture
Salesforce CPQ operates as a heavy managed package inside Salesforce.
This can introduce:
Complex Apex dependencies
Upgrade friction
Admin overhead
Difficult troubleshooting
Over time, complexity compounds.
2. Subscription Lifecycle Complexity
Modern SaaS deals often include:
Multi-year ramp pricing
Co-terming
Midterm expansions
Extensions
Hybrid subscription + usage pricing
Salesforce CPQ can support these models, but often requires significant configuration and custom logic.
When subscription logic spills outside the CPQ, reporting and renewals become fragile.
3. Consultant Dependency
Many organizations report that:
Pricing changes require specialized consultants
Subscription amendments require development work
Admin overhead increases year over year
When pricing evolves faster than system configurability, sales velocity slows.
4. Revenue Cloud Advanced (AgentForce Revenue Management) Migration Cost
For organizations considering Revenue Cloud Advanced (AgentForce Revenue Management) migration typically involves:
Re-implementation
Data restructuring
Billing redesign
Cross-functional realignment
Revenue Cloud Advanced (AgentForce Revenue Management) is not a toggle switch – it’s a strategic re-platforming decision.
For some SaaS companies, End of Sale triggered a broader question:
Should we migrate within Salesforce — or evaluate modern CPQ architectures altogether?
Salesforce CPQ vs Revenue Cloud Advanced (AgentForce Revenue Management)
Revenue Cloud Advanced (AgentForce Revenue Management) is not a feature upgrade to Salesforce CPQ.
It is a different architecture built on Salesforce’s newer Revenue Lifecycle Management framework. For most organizations, moving from Salesforce CPQ to Revenue Cloud Advanced (AgentForce Revenue Management) is not a toggle — it is a reimplementation.
The table below summarizes the high-level differences.
Questions That Actually Matter | Salesforce CPQ | Revenue Cloud Advanced (AgentForce Revenue Management) |
|---|---|---|
Is this a managed package? | Yes | No |
Is Salesforce investing net-new innovation here? | Limited | Yes |
Is this Salesforce’s long-term revenue architecture? | No | Yes |
Can you upgrade in-place? | N/A | Migration is probably required |
Migration complexity varies significantly, especially for organizations with custom pricing logic, approvals, billing integrations, or downstream revenue workflows. In many cases, the shift to Revenue Cloud Advanced (AgentForce Revenue Management) resembles a fresh CPQ implementation rather than a simple upgrade.
Salesforce CPQ Decision Framework
End of Sale does not require immediate action, but it does justify evaluation.
You may choose to stay if:
Your implementation is stable
Pricing changes are infrequent
Subscription complexity is manageable
You have strong in-house Salesforce expertise
You may evaluate options if:
Reps avoid CPQ for complex deals
Subscription amendments require manual work
Pricing changes require outside help
Revenue Cloud Advanced (AgentForce Revenue Management) migration costs feel substantial
You are planning major pricing model changes
Roadmap shifts create natural evaluation windows.
When evaluating timing, consider this:
If Salesforce CPQ supports your current pricing model but not your next pricing model, End of Sale is the right time to evaluate — not End of Life.
Re-platforming under deadline pressure introduces operational risk.
Early evaluation preserves negotiation leverage and architectural choice.
What About Salesforce CPQ Alternatives?
Some SaaS companies are using this transition to evaluate modern CPQ architectures.
Emerging CPQ models emphasize:
Native subscription lifecycle handling
Deterministic pricing guardrails
Faster implementation cycles
Reduced consultant dependency
For subscription-heavy SaaS teams, architecture flexibility often matters more than feature count.
If you’re evaluating Salesforce CPQ alternatives, it’s important to compare:
Managed package complexity
Subscription lifecycle support
Implementation speed
Pricing governance control
Integration depth
(You can explore a deeper breakdown of Salesforce CPQ alternatives for SaaS here.)
Frequently Asked Questions
Is Salesforce CPQ end of life End of Life?
No. Salesforce CPQ is currently in End of Sale, not End of Life. Existing customers can renew and receive support.
Is Salesforce CPQ deprecated?
Salesforce CPQ is not fully deprecated, but it is no longer Salesforce’s primary innovation focus.
Is Salesforce CPQ still supported in 2026?
Yes. Existing customers continue to receive renewals and support.
When will Salesforce CPQ reach End of Life?
Salesforce has not announced an official End of Life date. Long-term migration toward Revenue Cloud Advanced (AgentForce Revenue Management) is expected over time.
What happens to existing Salesforce CPQ customers?
Existing customers can continue renewing licenses. However, new feature investment has shifted to Revenue Cloud Advanced(AgentForce Revenue Management) .
Is Revenue Cloud Advanced (AgentForce Revenue Management) the same as Salesforce CPQ?
No. Revenue Cloud Advanced (AgentForce Revenue Management) is a broader revenue management platform that includes CPQ functionality alongside billing and lifecycle orchestration.
Final Takeaway
Salesforce CPQ is not disappearing overnight.
But it has entered a strategic transition phase.
For SaaS organizations, the question is not: “Is Salesforce CPQ dead?”
The question is: Does your quoting architecture support both control and velocity as your pricing evolves?
If your current system:
Handles subscription lifecycle complexity cleanly
Allows pricing changes without heavy development
Maintains trust between sales and finance
You may not need to move urgently.
If not, End of Sale may be the right milestone to evaluate your long-term revenue infrastructure strategy.
End of Sale does not necessarily mean urgency is required, but it does mean the roadmap has changed and should be taken seriously.
Read more

Blog
Why CPQ Implementations Fail (And What SaaS Companies Get Wrong)
Most CPQ implementations fail due to rigidity, subscription complexity, and misaligned sales workflows. Learn what SaaS companies should do differently.
Feb 18, 2026

Blog
Configure Price Quote Tools: A Beginner’s Guide for Modern Sales Teams
As B2B sales models become more complex, many teams reach a point where spreadsheets, static templates, and manual approvals simply stop scaling. That’s where configure price quote tools—often called CPQ tools—come in.
Feb 10, 2026
