Salesforce stopped selling CPQ to new customers in March 2025. It still runs, it's still supported — but every dollar of R&D now lives on the native stack. Here's what actually changed, what you can and can't do yet, and how to decide: stay, migrate, or build greenfield.
CPQ isn't dying — it's frozen. Existing orgs are safe for years. But it will never get another new feature, so the question is never "if." It's "when," and "greenfield or migrate."
Half the bad advice online cites the wrong product. "Revenue Cloud" has meant three different things. When someone says "move to Revenue Cloud," they mean the native rebuild — RLM / RCA — not the old bundle.
Salesforce CPQ
Legacy · SteelBrickThe managed package (SBQQ namespace) you've implemented
for years. Now End of Sale — frozen but supported.
Revenue Cloud (old)
Retired nameA pre-2024 umbrella bundle of CPQ + Billing + CLM. This meaning is gone — which is exactly why old articles confuse people.
RLM
The new engineRevenue Lifecycle Management — the native, API-first revenue architecture Salesforce rebuilt from scratch on the core platform.
RCA ← the successor
Buy thisRevenue Cloud Advanced — the richer commercial SKU sold on the RLM stack. This is the actual replacement for CPQ.
ARM
AI rebrandAgentforce Revenue Management — Salesforce's current AI-forward brand for the same platform. Same engine, newer marketing.
Revenue Cloud (today)
UmbrellaThe current umbrella brand over all of the above. Precise enough for a slide; too vague for a scoping conversation.
This is the part clients panic about — and the facts are calmer than the noise. No one gets kicked off CPQ in 2026 or 2027. But the roadmap is over.
CPQ reaches End of Sale
New customers can no longer buy Salesforce CPQ. Existing customers keep full access — support, renewals, and the ability to add new user licenses — all continue.
Frozen, supported, and no longer evolving
Salesforce has confirmed CPQ "will not receive new features or innovations." Maintenance continues; investment has moved entirely to RCA. There is no forced migration — and only ~15% of RCA customers today came from CPQ.
Estimated End-of-Life window
No formal EOL date has been announced by Salesforce. A 2029–2030 window is a consultant estimate, not a commitment — treat it as planning runway, not a deadline.
Sources: Salesforce CPQ End-of-Life page (salesforce.com); Salesforce Ben; Rithom (quoting Salesforce); servicePath (2029–2030 estimate). End of Sale ≠ End of Life.
Frame it as
CPQ is a frozen-but-supported asset with years of runway. You won't be forced off it soon — but you will never get a new feature, and the entire AI / Agentforce story lives on the other side.
The two products don't share a data model. Nothing lifts-and-shifts. This table is the "why" behind every 12–24 month migration estimate.
SBQQ namespace)SBQQ__Quote__cThe hard part
QCP JavaScript cannot be ported to server-side Pricing Procedures. Price Rules, Product Rules,
and Discount Schedules don't auto-map. SBQQ__Quote__c and
SBQQ__ProductOption__c have no automated migration path — only conceptual
equivalents that must be rebuilt by hand.
01 · The headline
Metered and consumption pricing with monitoring, reporting, and invoicing — out of the box. In CPQ this needed custom logic or a third-party tool.
02 · CPQ's most-hated gap
Winter '26 Asset Amendments let you push out an asset's end date and handle amendment logic automatically — plus CPI-based price adjustments on amendments.
03
Segment a multi-year deal into time-based ramp tranches, now supporting usage-based and bundled products. Long-requested; genuinely hard in CPQ.
04
Contract Lifecycle Management and Advanced Approvals are bundled in, not the separate paid add-ons they were in the CPQ era.
05
Quote → contract → order → billing → renewals in one data model, versus CPQ's "value ends at close" plus a separate Salesforce Billing product.
06 · The strategic one
Dedicated APIs (Product Discovery, Expression Set, Pricing Procedure) and catalog version control. CPQ's batch, monolithic, CRM-locked design structurally can't feed AI agents real-time pricing.
The part competitors won't tell your client. It's the most decision-relevant section on this page.
01 · Maturity
Practitioners are blunt: gaps are being closed "with each release," and a senior voice pegged full feature parity at "at least a couple of years" out (stated late 2024). You're implementing a moving target.
02 · Ecosystem
CPQ has a decade of docs, Trailhead, and Stack Exchange answers. RCA doesn't. Your architects will hit undocumented edges — a real delivery-risk and staffing cost.
03 · DevOps
RCA couples configuration data to metadata (PCM, pricing rules) with complex dependencies that don't behave like standard metadata. Sandbox refreshes can overwrite active dev work.
04 · Cost & curve
Longer implementation cycles, meaningful upskilling, and materially higher license + maintenance cost than plain CPQ. Salesforce has moved the price floor up.
Both show up in blogs and both are false. If your team cites them, someone technical in the room will catch it.
Myth · corrected
"CPQ can't do tiered / volume pricing without custom code."
Wrong. Legacy CPQ does tiered and volume pricing natively via Block Pricing and Discount Schedules (Range + Slab types). What CPQ actually lacks natively is usage / metered consumption pricing — not tiered. Get the distinction right.
Myth · corrected
"CPQ stores product attributes as JSON on the line item."
Wrong. SteelBrick CPQ uses Twin Fields — real typed columns on the Quote Line (documented on Salesforce's own Trailhead). The JSON-blob pattern belongs to Industries / Vlocity CPQ, a different product entirely.
List figures below (blog-sourced — real deal pricing varies). Treat as directional.
Watch for
RCA is materially pricier than plain CPQ was. A client who only ever needed lightweight CPQ now faces a premium platform or a third-party alternative (Logik.io, Nue.io, DealHub). As one practitioner put it: "for smaller companies just wanting the CPQ… they may be out of options."
There is a future for CPQ the concept. Not so much a future for Salesforce CPQ.
Practitioner · Salesforce Ben comments
There are large gaps between the two. Feature parity is on the roadmap but it will take time to deliver.
Senior consultant · late 2024
End of Sale does not require immediate action — but it does justify evaluation.
Migration guidance · consensus view
The "CPQ isn't dying, it's evolving" line is marketing — its own comment sections say Salesforce stopped adding features.
LeanScale read on vendor-blog framing
And note
The smartest voices frame the post-CPQ decision as not automatically RCA. Logik.io (config), Nue.io, and others are legitimate contenders depending on the use case. RCA is the default — not the only answer.
The framework we put in front of a client. Default for stable existing orgs is wait. Default for anything net-new is RCA.
Option A
Stay on CPQ
…for now
When it fits
These clients have years of runway. Don't manufacture a fire drill.
Option B
Plan the migration
reimplementation, not upgrade
When it fits
Treat as greenfield. Document all pricing logic first. QCP & catalog get rebuilt.
Option C · default for net-new
Build greenfield on RCA
the only forward-looking choice
When it fits
Only ~15% of RCA customers have migrated. The tooling is immature and the docs are thin — which is exactly where a specialist earns margin. The firms that build a repeatable CPQ→RCA reimplementation playbook now will own a multi-year motion as End-of-Sale pressure builds.