CPQ vs Revenue Cloud

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 · SteelBrick
• The managed package ( SBQQ namespace) you've implemented

for years. Now End of Sale — frozen but supported.

• Revenue Cloud (old)
• Retired name
• A pre-2024 umbrella bundle of CPQ + Billing + CLM. This meaning is gone — which is

exactly why old articles confuse people.

• RLM
• The new engine
• Revenue Lifecycle Management — the native, API-first revenue architecture Salesforce

rebuilt from scratch on the core platform.

• RCA ← the successor
• Buy this
• Revenue Cloud Advanced — the richer commercial SKU sold on the RLM stack. This is the

actual replacement for CPQ.

• ARM
• AI rebrand
• Agentforce Revenue Management — Salesforce's current AI-forward brand for the same

platform. Same engine, newer marketing.

• Revenue Cloud (today)
• Umbrella

The current umbrella brand over all of the above. Precise enough for a slide; too vague for

a scoping conversation.

Lifecycle

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.

• Mar 19, 2025 Announced
• 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.

• Today Jul 2026
• 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.

• 2029–2030 Projected
• 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.

Architecture & Data Model

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.

• Dimension
• Salesforce CPQ (legacy)
• Revenue Cloud / RCA
• Deployment
• Managed package bolted on ( SBQQ namespace)
• Native to the core platform — API-first, headless, composable
• Architecture
• Tightly coupled, quote-centric, monolithic (all-or-nothing)
• Modular — adopt pricing / quoting / ordering / billing independently
• Quote object
• Custom SBQQ__Quote__c
• Standard core Quote and Order objects
• Product catalog
• CPQ-specific Price Books
• Product Catalog Management (PCM) — unified product + attribute catalog
• Pricing engine
• Price Rules / Product Rules + QCP (browser-side JavaScript)
• Pricing Procedures + Decision Tables (server-side, declarative)
• Product attributes
• Twin / Target Fields (real typed columns on the Quote Line)
• Separate related records on transaction lines
• Post-sale lifecycle
• Value largely ends at close; renewals via Subscription records
• Asset-based — renew / amend / cancel directly from the Asset
• Fulfillment
• Not native

Dynamic Revenue Orchestrator (DRO) — order decomposition, fulfillment plans, jeopardy management

The 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.

What Revenue Cloud Can Do That CPQ Can't

01 · The headline

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 Honest Gap List

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

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

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.

Pricing & Licensing

List figures below (blog-sourced — real deal pricing varies). Treat as directional.

• $150 /u/mo
• Revenue Cloud · Growth
• 2026 list
• $200 /u/mo
• Revenue Cloud · Advanced
• 2026 list
• +$125 –200
• CLM Add-On /u/mo
• on top of RCA base
• ~6 %
• 2025 Price Increase
• 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."
• What The Experts Are Saying

"

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 Verdict

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
• Implementation is stable & meeting business needs
• Pricing changes are infrequent
• No near-term revenue-process redesign
• Re-architecture cost > near-term value

These clients have years of runway. Don't manufacture a fire drill.

• Option B
• Plan the migration
• reimplementation, not upgrade
• When it fits
• Outgrowing CPQ — need usage billing, ramp, clean amend-and-extend
• Want unified post-sale lifecycle or AI on quoting
• Already facing a major revenue redesign — do it once, on RCA
• Budget a phased parallel run: 12–24 mo

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
• Any net-new Salesforce revenue implementation
• Especially with advanced config, consumption, or ramp
• You can't buy CPQ anyway — and building new on a frozen product is malpractice
• Exception: tiny, cost-sensitive SMB → weigh a lighter 3rd-party CPQ
• The LeanScale angle

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.

LeanScale

LeanScale builds and runs the GTM and revenue systems behind high-growth B2B SaaS — including CPQ, Quote-to-Cash,

and the migration to Salesforce Revenue Cloud. This brief is a client-advisory reference, not Salesforce guidance.

Compiled July 2026 from 25 verified public sources. Feature availability and pricing change every

release (three per year) — verify current-release specifics before scoping. Projected EOL window is a third-party

estimate, not a Salesforce commitment.

• Salesforce official (CPQ EOL page · RLM Developer Guide)
• Salesforce Ben (6 articles)
• Gearset · Kicksaw · Nebula · CPQ Consultant
• servicePath · Dupont Circle · Rithom · StratusCarta
• www.leanscale.team