The CPQ End of Sale Is a Revenue Architecture Decision — Not a Migration Project
What the EOS announcement actually means for your Lead-to-Cash stack — and why the answer isn't as obvious as everyone is telling you.
Your Salesforce AE probably made it sound urgent. Maybe alarming. And if you’ve been searching for what the Salesforce CPQ end of sale actually means — not the spin, not the pitch — you’ve likely found the same thing we have: a wave of blog posts from Salesforce partners explaining why Revenue Cloud Advanced is your obvious next step.
This isn’t one of those posts.
We implement both Salesforce and ServiceNow. We don’t have a platform to sell you. What we do have is a clear-eyed view of what’s happening in the market right now — and the honest read is that the CPQ end-of-sale announcement landed in the middle of a genuine strategic crossroads.
Not a migration project. A revenue architecture decision.
What “End of Sale” Actually Means for Salesforce CPQ
On March 27, 2025, Salesforce officially moved CPQ to End of Sale status. That phrase does specific work — and it’s worth being precise about it.
End of Sale does not mean your CPQ stops working tomorrow. It does not mean your contracts are void. What it means: Salesforce is no longer selling new CPQ licenses. No new features are being built. The product is in maintenance mode.
Renewals are a different question. Salesforce AEs are currently quoting August 2026 as the end of renewal window — that’s the community signal, not an official Salesforce statement, and it’s worth verifying against your actual contract terms. But the directional message is consistent: the runway is shorter than you think.
Here’s the part people miss on both ends of the spectrum.
Some teams hear “end of sale” and panic. They’re ready to rip and replace before they understand what they’re replacing it with. Others hear it and shrug — “CPQ still works, we’ll deal with it later.” Both responses miss the real issue. The problem with staying put isn’t that CPQ breaks. It’s that CPQ becomes a ceiling. Companies remaining on Legacy CPQ are locked out of Agentforce integration. That’s not a minor limitation in 2026. That’s a strategic constraint on where your revenue operations can go.
The clock is ticking. It’s just not the fire alarm everyone is treating it as.
The Salesforce Path: Real, But Honest
If you’re a pure Salesforce shop, the natural path is Revenue Cloud Advanced — or, in the latest naming iteration, Agentforce Revenue Management (ARM). Let’s be direct about both what’s compelling and what isn’t.
What’s compelling: ARM is architecturally built into the Salesforce core. It’s not an appended product. It’s native. That matters for data integrity, and it matters significantly for Agentforce readiness. If your long-term roadmap involves AI-assisted quoting, contract intelligence, or autonomous revenue workflows, you need a quoting layer that can actually participate in those architectures. ARM is designed to do that.
What’s less clean: the naming alone should give you pause. This product went from Revenue Lifecycle Management to Revenue Cloud Advanced to Agentforce Revenue Management in short succession. That kind of naming churn usually reflects something real happening in the product — prioritization shifts, capability consolidation, strategic repositioning. It doesn’t mean avoid it. It means go in with clear eyes.
The architecture itself represents a genuine shift. Salesforce CPQ was rule-based. ARM runs on constraint-based logic. The migration isn’t just a data migration. It’s a re-engineering of how your pricing and quoting logic works. For orgs with complex configurations — and most enterprise CPQ orgs have more undocumented logic than documented — that’s a significant undertaking.
Implementation timelines are running longer than partners are currently quoting. That’s a pattern we’re seeing consistently.
We have successfully deployed 2 projects!
The Market Context Nobody Is Writing About
Here is what is completely absent from the conversation happening in the Salesforce ecosystem right now.
On April 3, 2025 — one week after the CPQ end-of-sale announcement — ServiceNow acquired Logik.ai, one of the more capable AI-native CPQ platforms in the market. In October 2025, ServiceNow launched its own CPQ product built on that acquisition.
That timing is not coincidental. ServiceNow watched the CPQ market open up and moved immediately.
This doesn’t mean ServiceNow CPQ is the right answer for your organization. It launched six months ago. It’s not fully mature. We’re not here to pitch it. But if you run both Salesforce and ServiceNow — or if you’re one of the organizations actively questioning whether your Lead-to-Cash stack should consolidate onto a single platform — the conversation looks different than it did eighteen months ago.
The CPQ market just opened up. There is now more than one credible path.
Every other post you’re reading right now was written by someone who has already picked a side. Their answer is already determined before they start writing. We haven’t picked a side, and that’s not a weakness — it’s the only way to give you advice worth taking.
The Lead-to-Cash Question Everyone Is Skipping
Here’s what the CPQ-focused conversation consistently misses.
CPQ is not a standalone tool. It sits inside a process. Quoting touches pricing approvals, order management, billing, ERP, and fulfillment. It’s the middle of the revenue motion — upstream from legal, downstream from pipeline, and connected to systems that may not be on your Salesforce AE’s radar at all.
When organizations treat an EOS event as a migration project, they pick a new quoting tool and move the configurations over. The L2C process itself doesn’t get examined. And that’s exactly where migrations create lasting risk.
A CPQ migration that doesn’t account for what happens to contract terms downstream, how pricing changes flow to billing, or how orders connect to fulfillment isn’t a modernization. It’s a lateral move with fresh technical debt.
More than 70% of CPQ logic in enterprise orgs is undocumented. That’s not an exaggeration — it’s a pattern that’s been confirmed consistently by teams doing CPQ discovery work across the industry. When you’re scoping a migration, you’re scoping a process that most of the people involved haven’t fully mapped.
This is where an advisor who knows the full stack earns their fee. Not by picking the right tool. By helping you understand what the right question actually is before you start.
How to Frame the Decision
The wrong question: which CPQ tool should we migrate to?
The right question: what does our Lead-to-Cash architecture need to look like in three years — and what’s the cleanest path to get there?
Here’s how we think about it for three common org types:
Pure Salesforce shop. Your data lives in Salesforce. Your teams are trained on Salesforce. Your future roadmap includes AI-assisted workflows. For you, ARM is probably the right destination — but the timeline and complexity of getting there is likely being undersold. Start the discovery process now. Map what’s documented and what isn’t. Don’t let urgency push you into a scoping conversation before you understand what you actually have.
Salesforce + ServiceNow. You’re running both platforms, and there’s a real question about where L2C should live long-term. ServiceNow CPQ is new enough that you shouldn’t treat it as a proven enterprise solution — but you also shouldn’t ignore it. The acquisition of Logik.ai was a signal about where ServiceNow is investing. If you’re already consolidating workflows onto ServiceNow, that conversation is worth having before you lock into a Salesforce migration.
Overbuilt CPQ org needing a reset. Your CPQ configuration has accumulated ten years of band-aids. Nobody knows why half the rules exist. Your quoting process is slower than it should be, and everyone knows it. For you, this EOS moment is actually an opportunity — but only if you treat it as a chance to redesign, not just re-platform. The goal isn’t to move your complexity to a new system. It’s to build something cleaner.
Mountain Point’s Read
Here’s what we’d tell a client in a kickoff meeting.
Don’t let the end-of-sale timeline drive a rushed decision. The urgency is real — you have a finite window before staying on Legacy CPQ starts closing doors — but not so real that you should skip the architecture conversation.
Understand your current state before you scope a future state. If you don’t know what logic is documented and what isn’t, any timeline you’re given is a guess.
Be honest about which platforms you’re actually running. If you’re on both Salesforce and ServiceNow, the answer to “where does CPQ live?” is a revenue architecture question, not a feature comparison exercise.
And be skeptical of any partner who gives you an implementation timeline without first doing the discovery or a Proof of Concept. This work takes as long as it takes to do correctly. The partners who are telling you otherwise are either inexperienced with ARM or optimistic for reasons that serve them.
The CPQ end of sale is not the end of the world. It’s a forcing function. Used right, it’s an opportunity to get cleaner about your revenue process than you’ve ever been.
That’s the work. We’re here if you want to do it.
Frequently Asked Questions
Is Salesforce CPQ dead?
Not dead — but sunsetted. Salesforce CPQ moved to End of Sale on March 27, 2025, which means no new licenses and no new features. Existing CPQ customers can continue running it through the end of their renewal windows, with community signals suggesting August 2026 as the likely cutoff for renewals. The more meaningful issue: organizations staying on Legacy CPQ are locked out of Agentforce integration, which makes it a strategic ceiling, not just a technical liability.
What is Agentforce Revenue Management?
Agentforce Revenue Management (ARM) is Salesforce’s current name for its next-generation CPQ and revenue platform. It was previously called Revenue Cloud Advanced (RCA) and before that Revenue Lifecycle Management (RLM). It’s architecturally native to Salesforce core — designed to support AI-assisted quoting and revenue workflows through Agentforce. No certifications for ARM currently exist; implementation experience is the only reliable qualification signal when evaluating partners.