- Salesforce CPQ end of sale does not require immediate migration, but it does require intentional planning
- There is no direct upgrade path from CPQ to ARM — Revenue Cloud Advanced is a reimplementation with a different architecture
- Most organizations succeed by modernizing in phases, extending CPQ where it makes sense while avoiding disruption
- Fragmenting quote-to-cash systems to "test" usage or consumption pricing often creates long-term reconciliation and data integrity issues
- Teams that plan now gain flexibility later
In early 2025, Salesforce announced that CPQ would be end-of-sale. The news immediately raised questions across RevOps, Sales, and Product teams about what comes next. To explore what CPQ EOS really means in practice, John Banks, CEO and Founder of Continuous, sat down with John Garvens, Salesforce Revenue Cloud expert, for a live Quote-to-Cash Conversations discussion.
Rather than fueling alarm, the conversation surfaced a more grounded reality. CPQ end-of-sale is not a cliff. It's a runway. CPQ is still supported, the lights are not turning off tomorrow, and most teams have more time than they think.
CPQ EOS is not a crisis, but it is a forcing function
End-of-sale does not mean end-of-life. CPQ is not disappearing overnight. The real risk is letting uncertainty turn into inertia, then finding yourself forced into a rushed decision later. This period is best used as a planning window — a chance to understand what actually lives inside your Salesforce org, how much of your revenue process relies on custom workarounds, and where friction has quietly turned into tech debt.
Most companies are choosing one of three paths
1. Stay on CPQ for now. Some teams will remain on CPQ for a period of time because budget, bandwidth, or organizational readiness make a near-term change unrealistic.
2. Start fresh in a contained scope. Others will implement newer tooling for a new product line, a new business unit, or a recent acquisition — allowing progress without disrupting the broader organization.
3. Take a phased bridge approach. Many teams will modernize incrementally, keeping the business running while gradually transitioning their quote-to-cash architecture.
The important distinction: moving from CPQ to Revenue Cloud Advanced is not an upgrade. It's a reimplementation with a different operating model and a much higher premium on process clarity and architectural discipline.
Fragmentation is the fastest path to future pain
One of the strongest warnings from the conversation: when teams try to test consumption or usage-based pricing by bolting on a separate billing system "just for a pilot," the complexity rarely stays contained. Over time, those experiments often create a second customer record, a second product catalog, and a second transaction engine. Reconciliation becomes manual. Reporting becomes unreliable.
The safer long-term approach: extend what you already have without breaking the integrity of your architecture. Protect a single customer view, a single source of product truth, and clean lifecycle management even as monetization evolves.
The bridge matters because revenue cannot stop
Moving from CPQ to ARM requires a merge lane. Most companies cannot pause quoting, selling, amending, and invoicing while they rebuild their revenue stack. A phased transition allows teams to modernize transactionally, reduce risk, and avoid a single high-stakes cutover. When done well, migration becomes a controlled progression rather than a disruptive reset.
ARM success depends on people as much as product
The platform is evolving quickly, which creates opportunity but also risk for enterprise teams that need stability and governance. Projects tend to struggle when teams build against the product's intent, compensating with custom workarounds that become permanent. Domain expertise matters — successful teams have experienced quote-to-cash practitioners who understand not just what is possible, but what should be avoided.
A realistic planning window for CPQ EOS transitions
For many organizations, a six- to twelve-month preparation window is realistic, once remediation, catalog cleanup, process clarity, and cross-functional alignment are factored in. That time is not about delay — it's about laying the groundwork that prevents expensive mistakes later. Measured planning now leads to faster, more predictable outcomes when change does happen.
Final Thought
CPQ EOS does not demand immediate action, but it does reward intentional planning. Teams that use this period to clarify their processes, clean up their architecture, and modernize thoughtfully will have far more flexibility when the next decision arrives.
CPQ EOS: Common Questions Revenue Leaders Are Asking
Do we need to replace Salesforce CPQ now that it's end-of-sale?
No. End-of-sale means CPQ is no longer sold to new customers — not that it stops working. Existing customers will continue to receive support, giving teams time to plan instead of reacting under pressure.
Is moving from CPQ to ARM an upgrade?
No. ARM introduces a different operating model with fewer guardrails and greater architectural responsibility. Treating it as a lift-and-shift often leads to delays, rework, and avoidable complexity.
Can we experiment with usage or consumption pricing without breaking our architecture?
Yes — but only if experimentation happens within a unified quote-to-cash model. Adding separate billing or usage tools for pilots frequently leads to duplicate data, manual reconciliation, and reporting gaps.
How long should teams plan for a CPQ EOS transition?
For most organizations, six to twelve months of preparation is realistic, including catalog cleanup, process alignment, cross-functional readiness, and architectural planning.