Salesforce CPQ Is Sunsetting: What It Means for Your Revenue Operations
Salesforce confirmed CPQ has entered End of Sale status in March 2025, with all innovation shifting to Revenue Cloud Advanced. Here's what current CPQ customers need to know — and what to do next.
On March 19, 2025, Salesforce officially confirmed what many in the ecosystem had been anticipating: Salesforce CPQ has entered End of Sale (EOS) status. While this isn't an immediate shutdown, it marks the beginning of the end for one of the most widely adopted configure-price-quote solutions in the Salesforce ecosystem.
For the thousands of organizations running their revenue operations on Salesforce CPQ, this announcement demands attention — and a plan.
What End of Sale Actually Means
It's important to distinguish between End of Sale and End of Life. Salesforce's official statement was clear:
"Current customers will continue to receive full access — including support — and can renew and add licenses. For new customers, we now offer Revenue Cloud Advanced and Revenue Cloud Billing."
In practical terms, this means:
No new customers can purchase Salesforce CPQ as of March 2025
Existing customers retain full access, support, and the ability to renew
No new features or significant R&D investment in the legacy CPQ package
Bug fixes and security patches will continue during the support period
All innovation is now directed at Revenue Cloud Advanced and Revenue Cloud Billing
Based on typical enterprise software lifecycle patterns, industry analysts project a full End of Life around 2029–2030, giving current customers roughly 4–5 years to transition.
Why Salesforce Is Making This Move
Salesforce CPQ was built as a managed package — essentially a third-party app running on top of the Salesforce platform. While powerful, this architecture created limitations:
Performance bottlenecks on large or complex product catalogs
Governor limits that constrained advanced pricing logic
Technical debt from years of iterative development on an aging architecture
Limited AI integration compared to native platform capabilities
Revenue Cloud Advanced is built natively on the Salesforce core platform, meaning it benefits from the same infrastructure, security model, and — crucially — AI layer (Einstein / Agentforce) as the rest of the Customer 360 suite. It launched in the Spring '25 release with an API-first, composable architecture designed for modern revenue operations.
Revenue Cloud Advanced vs. Legacy CPQ
Revenue Cloud Advanced isn't just a renamed CPQ — it's a fundamentally different product:
Dynamic Product Catalog: More flexible product modeling that supports subscription, usage-based, and hybrid revenue models natively
Flexible Pricing Engine: Built to handle complex pricing without hitting governor limits
Product Configurator: Modernized configuration experience with better UX
Contract Lifecycle Management: Integrated CLM capabilities that were previously separate
AI-Ready Architecture: Native integration with Einstein GPT and Agentforce for intelligent quoting and forecasting
The Migration Reality Check
Here's the part nobody wants to hear: there is no automated migration path from CPQ to Revenue Cloud Advanced. Organizations cannot simply upgrade their existing CPQ implementation. This is a full reimplementation that requires:
Complete re-architecture of product catalog and pricing rules
Rebuilding of approval workflows and discount structures
Re-creation of quote templates and document generation
Migration of historical data (quotes, orders, contracts)
Integration re-work for ERP, billing, and other downstream systems
Cross-team coordination across IT, sales operations, finance, and legal
Typical go-live timelines are 18–24 months for enterprise implementations. That's not a weekend project — it's a major program of work that needs executive sponsorship, dedicated resources, and careful change management.
What You Should Be Doing Now
If you're currently on Salesforce CPQ, here's the recommended action plan for 2026:
1. Audit your current CPQ implementation. Document your product catalog complexity, custom Apex triggers, pricing rules, approval chains, and integrations. Understand the true scope of what needs to migrate.
2. Evaluate Revenue Cloud Advanced. Request a sandbox environment and assess feature parity with your current setup. Identify gaps early.
3. Engage an experienced SI partner. This migration requires deep expertise in both legacy CPQ and Revenue Cloud. The right SI partner can help you avoid costly mistakes and compress your timeline.
4. Start planning now, even if you're not ready to migrate. Organizations that begin evaluation in 2026 have a significant advantage — they can learn from early adopters' experiences while there's still ample SI capacity in the market. Waiting until 2028–2029 means competing with every other CPQ customer for migration resources.
5. Consider a phased approach. Not everything needs to migrate at once. Many organizations are starting with new product lines on Revenue Cloud Advanced while maintaining legacy CPQ for existing catalogs during the transition period.
The Bottom Line
The sunset of Salesforce CPQ isn't a crisis — it's a planned transition with a multi-year runway. But the organizations that treat this as a strategic opportunity rather than a compliance checkbox will come out ahead. Revenue Cloud Advanced offers genuine architectural improvements that can accelerate your quote-to-cash cycle, improve sales productivity, and unlock AI-driven revenue intelligence.
The clock is ticking. Start the conversation with your team and your SI partners now — your future revenue operations will thank you.