September 2026 | Reading time: 7 min
If you manage a Salesforce CPQ implementation, you've probably asked yourself: what are we doing about it?
The platform is in maintenance mode. Active development has stopped. The push toward Revenue Cloud Advanced has been consistent enough that the question is no longer whether to move, but when, and to what.
This article cuts through the positioning to answer what RevOps leaders are actually asking: what's happening to Salesforce CPQ, what the real alternatives are, and how to figure out which path makes sense for your organization.
Is Salesforce discontinuing CPQ?
Yes, effectively.
Salesforce CPQ (originally Steelbrick, acquired in 2015) is in maintenance mode. Bug fixes and security patches continue, but feature development has stopped. Salesforce is no longer investing in the platform as a product.
The official successor is Revenue Cloud Advanced. Salesforce has been clear about this direction for years, and the messaging has only gotten more consistent. If you're running Salesforce CPQ today, you're running a platform without a forward roadmap.
That's not the same as end-of-life. The platform won't stop working on a specific date. But it won't get better. And as Agentforce capabilities become more central to how Salesforce customers sell, the gap between what Salesforce CPQ can support and what Revenue Cloud Advanced can do will keep widening.
What is replacing CPQ in Salesforce?
Revenue Cloud Advanced (RCA) is Salesforce's answer. It's a rebuilt revenue platform, not an upgrade of Salesforce CPQ. It consolidates quoting, contracts, billing, and revenue lifecycle management in a single architecture, with native Agentforce compatibility and tighter integration with Salesforce Data Cloud.
For organizations that need to handle complex revenue models — subscription billing, usage-based pricing, milestone billing, or multi-party revenue management — RCA offers capabilities that legacy CPQ was never designed for.
The key distinction: RCA is not Salesforce CPQ with new features. It's a new architecture built for how B2B revenue management works today. Getting from one to the other is a migration, not an upgrade.
How is Revenue Cloud Advanced different from Salesforce CPQ?
The differences go deeper than feature lists. Here's where they actually diverge.
Architecture. Salesforce CPQ was built as an acquisition and layered onto the Salesforce CRM. Configuration rules, pricing logic, and the front-end interface are tightly coupled - changing one tends to require touching the others. Revenue Cloud Advanced was architected from the ground up to separate these concerns.
Revenue models. CPQ was designed around transactional quoting: configure a product, set a price, send a quote. RCA handles that, plus subscription management, usage-based billing, contract amendments, renewals, and lifecycle revenue recognition. If your business has moved toward recurring revenue or consumption-based pricing, CPQ's architecture is already working against you.
AI readiness. Salesforce CPQ predates AI as a practical selling tool. Agentforce, Salesforce's AI agent framework, is built for Revenue Cloud Advanced. Running AI-assisted quoting or AI-driven revenue management on top of legacy CPQ means working around the platform rather than with it.
Migration path. There isn't a clean one. Custom configuration rules, product catalogs, pricing logic, and approval workflows built in Salesforce CPQ don't port directly to RCA. Organizations that have treated Salesforce CPQ as a documentation system for their pricing and product rules are in a stronger position. Those who have let institutional knowledge accumulate outside the platform are facing a discovery exercise before they can scope anything.
What are the Salesforce CPQ alternatives?
Revenue Cloud Advanced is not the only option. The market has moved, and a growing number of enterprise organizations are evaluating paths that don't require staying inside the Salesforce ecosystem for their quoting layer.
Composable CPQ is the category drawing the most serious attention.
The core idea: instead of replacing one platform with another, you decouple the configuration and pricing engine from any single system of record.
The CPQ logic runs separately and is consumed by whatever front ends need it — a Salesforce-based sales rep interface, a dealer portal, a self-service commerce experience, an Agentforce agent. One set of rules, multiple consumers.
This architecture matters for a few reasons. First, most complex B2B organizations are no longer quoting through a single channel. A CPQ designed to live inside one CRM starts creating inconsistencies the moment you add a second touchpoint. Second, AI-driven selling requires configuration logic that can be accessed programmatically. A composable CPQ makes that native. A monolithic one makes it hard.
ServiceNow CPQ is the most prominent composable option in the market right now. It was built by the founder of BigMachines and Logik.ai — the people who shaped the CPQ category — and is explicitly designed to work alongside existing CRM and ERP rather than replacing them. It's drawing serious attention from organizations that don't want to rebuild their entire revenue stack to move off Salesforce CPQ.
Should you stay on Salesforce CPQ for now?
This is the option no vendor will recommend, and it's probably right for more organizations than they'd admit.
Salesforce CPQ is in maintenance mode, not end-of-life. If your implementation is stable, your customizations are documented, and your team's bandwidth is already stretched, committing to a major migration before you're ready to do it properly is worse than waiting.
Staying put makes sense when your CPQ is working, you have a realistic window to make the migration decision properly, and you're not trying to use AI-driven quoting capabilities that the current architecture can't support.
It stops making sense when you're already fighting the platform, your pricing logic lives in tribal knowledge and spreadsheets outside the system, you're quoting across multiple channels and running into consistency problems, or you're planning an Agentforce rollout that depends on a modern quoting layer underneath it.
The risk of waiting isn't a cliff. It's a slow drift. Configuration complexity grows. The gap between what your team knows and what's actually documented widens. The people who understand how the system really works leave the company. Maintenance mode means the platform won't break tomorrow, but it also won't solve any of those problems.
How do you decide which path is right?
The most useful work you can do before making this decision is understanding what you actually have.
Most organizations underestimate their CPQ complexity. The configuration rules, pricing models, and approval flows that make quoting work exist partly in the platform and partly in the heads of the people who built it.
Before you can evaluate any migration path, you need to answer one question: where does a quote go after it leaves CRM, and what breaks at each handoff?
The answer tells you how much of your configuration is documented, where your integration dependencies are, and how much of your logic is genuinely portable versus built around Salesforce-specific constructs. That's the foundation any migration decision should rest on.
A few other inputs that change the answer:
Your revenue model. If you're selling subscriptions, usage-based products, or complex bundles with lifecycle billing, RCA's capabilities matter more and the investment in migration makes more sense. If your quoting is primarily transactional, a composable CPQ may give you more flexibility with less risk.
Your channel footprint. If quotes are generated through multiple channels - a direct sales team, partner portals, self-service, or automated systems - a composable architecture gives you one logic layer powering all of them. If quoting is single-channel and rep-driven, the case for composability is weaker.
Your Agentforce plans. If AI-assisted quoting or agent-driven revenue management is on your roadmap, your CPQ architecture is a dependency. The CPQ decision and the Agentforce decision need to be made together, not sequentially.
Your migration capacity. A CPQ migration that goes wrong affects revenue velocity directly. How much disruption can your sales and operations teams absorb while a new system is being stood up? That's not a reason to avoid migrating - it's a reason to scope it honestly before you start.
What does a CPQ migration actually involve?
Less than you might fear if you've done the documentation work. More than anyone's proposal will tell you if you haven't.
The organizations that get CPQ migration right treat it as a process clarity exercise before it becomes a technology project. That means surfacing the configuration rules, pricing logic, and approval flows that currently live outside the system. It means identifying which product rules are stable and which need to be rethought before they're rebuilt. And it means creating a real feedback loop so the new system reflects how the business actually works, not just how the old one happened to be configured.
The organizations that struggle treat it as a technical project. They scope the platform work without addressing the process gaps underneath it. They automate configuration logic that was never correct to begin with. Three years later, the same operational problems are back - just with a newer interface.
The difference between those two outcomes is almost never the platform. It's whether the underlying processes were understood before the build started.
How Zaelab helps with CPQ migration
We work with complex enterprises on CPQ modernization: migrating to Revenue Cloud Advanced, moving to a composable architecture on ServiceNow, or figuring out what the right path actually is before committing to either.
The most common starting point isn't a platform decision. It's a diagnostic: mapping what you have, where the complexity actually lives, and what a migration would realistically take for your organization. That work usually changes the scope estimates significantly, and it tends to surface risks that don't show up in a standard vendor proposal.
If you're working through a CPQ decision, we're happy to talk through what we're seeing in the market and what tends to work for organizations in your situation. Let’s talk.
