Salesforce CPQ vs Revenue Cloud Advanced: side-by-side comparison, with sources
Salesforce CPQ (SBQQ) is a managed-package quoting product Salesforce stopped selling to new customers in March 2025; existing customers can still renew and get support. Revenue Cloud Advanced is its successor, built on core Salesforce objects with a new data model at $150 or $200 per user per month. Moving between them is a migration, not an upgrade — a 12–18 month rebuild in practice.
Which one is right for you
- You want Salesforce’s own roadmap, and have the budget for a full rebuildChoose Revenue Cloud Advanced — $150–$200/user/mo, 12–18 month rebuild in practice
- You want to keep standard Products and Price Books, admin-ownedChoose a Salesforce-native alternative — published $65/user/mo, 4–8 weeks
- Your contract renews soon and nothing is brokenYou can stay on CPQ — it is supported, renewable, and has no end-of-life date
What actually differs
The difference that matters is architectural, not cosmetic: these are two products with different data models, and Salesforce says so itself.
| Dimension | Salesforce CPQ (SBQQ) | Revenue Cloud Advanced | Source |
|---|---|---|---|
| Commercial status | End of sale since March 2025 — not sold to new customers. Not end of life; no end-of-life date announced. | Actively sold. Salesforce’s current CPQ product; billing is the separate Revenue Cloud Billing. | salesforce.com |
| Existing customers | Can renew, add users, and receive support for the duration of existing contracts. No forced migration. | Standard subscription terms; annual contract required. | salesforce.com |
| Architecture | Managed package (SBQQ) installed into the org, with its own CPQ objects. Quote-centric and tightly coupled. | Native to Salesforce core; Salesforce calls it API-first, headless and composable. Configuration needs specialist skills (Constraint Modeling Language, pricing procedures, context definitions). | salesforce.com |
| Product model | SKU-based bundles and options. | Attribute-based product catalog. | salesforce.com |
| Pricing engine | Price rules, discount schedules, and Quote Calculator Plugin scripts. | Declarative pricing procedures and elements. | salesforce.com |
| Configurator | Rules-based. | Constraint-based. | salesforce.com |
| Subscriptions | Subscription custom object; contract-based amendments and renewals. | Asset-based amendments, renewals and cancellations. | salesforce.com |
| List price per user / month | Not sold to new customers (no published price). not sold new | $150 Growth · $200 Advanced published | salesforce.com |
| New features | None — maintenance phase. | Ongoing releases; Salesforce’s investment focus. | salesforce.com |
| Documentation | Online help retired July 2026 in favour of a single PDF. | Current online documentation. | help.salesforce.com |
| Upgrade path between them | None — different data model. Moving to RCA is a re-implementation. | No first-party migration tool yet (a Salesforce migration assistant is on the roadmap for December 2026); Salesforce names Forsys, IdeaHelix and Prodly. | salesforce.com |
| Typical migration time | — | A full rebuild runs 12–18 months in practice; Salesforce’s FAQ quotes 3–6 months — treat that as a best case. in practice | salesforce.com |
What Salesforce’s Help documentation adds
Salesforce’s Help documentation for the migration has its own comparison table, and it goes further than the marketing page. It opens with a warning worth repeating: treat the move as a redesign, not a direct migration of existing configurations (Salesforce Help).
| Area | Salesforce CPQ | Revenue Cloud (Help’s description) |
|---|---|---|
| Where pricing runs | In the browser, rules executed in sequence. | On the server, as pricing procedures executed as a price waterfall. |
| Pricing models | Price books, discount schedules, block pricing through rules. | Pricing procedures and elements; one-time, subscription and consumption pricing on one transaction; several selling models on one product. |
| Contract and account pricing | The ContractedPrices custom object and account-specific workarounds. | ContractItemPrice on standard objects, plus account, partner and channel pricing. |
| Configuration | The quote line editor. | Screen flows, a headless API, and a constraint engine written in Constraint Modeling Language (CML). |
| Contracts | Limited. | Salesforce Contracts, with AI clause generation (Contract Lifecycle Management is included in Advanced, extra on Growth). |
| Orders | Orders created from quotes. | Order decomposition and fulfilment orchestration with downstream systems (Dynamic Revenue Orchestration, bought separately). |
| Billing | The separate Salesforce Billing managed package. | Billing and rating on the platform, sold as the separate Revenue Cloud Billing. |
| Customization | Quote Calculator Plugin, Apex plug-ins, execution-order dependencies, custom objects. | Declarative pricing procedures and elements, with Apex pre- and post-hooks, flows and CML constraints. |
| AI | Not available. | Agentforce agents that create and manage quotes and answer billing questions. |
The bracketed notes on packaging are ours, from Salesforce’s pricing page (Salesforce).
Where each one runs
Both live inside your Salesforce org. The distinction is which objects hold your data — package objects or core ones.
SBQQ__ package objects; Revenue Cloud Advanced uses core Salesforce objects with a different model. That is why moving between them is a re-implementation, not an upgrade.Salesforce CPQ is a managed package: quotes are SBQQ__Quote__c records, bundles are SBQQ__ProductOption__c, and pricing runs through price rules and Quote Calculator Plugin scripts. Revenue Cloud Advanced is built on core Salesforce objects with an attribute-based catalog and declarative pricing procedures. Nothing leaves your org in either case — but almost nothing transfers between them untouched either.
What moves, and what gets rebuilt
Three object types move as-is. Everything else is a rebuild.
SBQQ__ prefix is package data with no direct equivalent in Revenue Cloud Advanced.Where Revenue Cloud has caught up, and where the limits are
Some objections to Revenue Cloud that were true in 2025 are not true now. Others have limits worth knowing before a demo.
| Capability | Where it stands | Source |
|---|---|---|
| Cloning a whole quote or order | Deep Clone shipped in Summer ’26. Salesforce Help sets a limit of 6,000 records per cloned transaction; for more than 1,000 lines, customers contact their account executive. | Salesforce Help |
| Attributes per product | Up to 200, raised from 15 in Summer ’25. | release notes |
| Agentforce quoting | Quotes created and updated in plain language in Salesforce or Slack since Summer ’25; Salesforce reports 75% less quoting time on its own sales team. | Salesforce |
| Buyer, partner and renewal quoting by agents | Winter ’27 (October 12, 2026), in Revenue Cloud, not in Salesforce CPQ. | Salesforce |
| Consumption billing at volume | Salesforce bought m3ter (closed July 1, 2026); partners’ recaps put its first Revenue Cloud capabilities in the first half of 2027. | Salesforce · Atrium |
| A free trial | None. Salesforce offers hands-on workshops instead. | Salesforce |
| Moving from CPQ in one step | Not yet. The first-party migration assistant has a December 2026 target; partner tools cannot move Apex, Quote Calculator Plugin logic, integrations, templates, layouts, permissions or custom fields. | Salesforce Help |
What it costs over three years
The licence gap is published and large; the implementation gap is where the real money is, and only one vendor publishes a number.
Revenue Cloud Advanced is $150 per user per month for Growth and $200 for Advanced, billed annually on an annual contract, as a paid add-on to Sales Cloud (salesforce.com). Salesforce publishes no implementation figure; a full rebuild runs 12–18 months in practice; it points to partner accelerators. Kugamon publishes $65 per user per month and a fixed implementation fee of $15,000–$30,000 set by the edition, $5,000 less on a two- or three-year term (appexchange.salesforce.com).
From SteelBrick to Revenue Cloud
| When | What happened | Source |
|---|---|---|
| December 2015 | Salesforce agrees to buy SteelBrick, the package that becomes Salesforce CPQ. | SEC filing |
| November 2020 | The Revenue Cloud brand launches as a bundle of CPQ, Billing and other products. | Salesforce |
| June 2024 | Revenue Lifecycle Management launches on the core platform. | Salesforce |
| September 2024 | Revenue Lifecycle Management is renamed Revenue Cloud (Winter ’25). | release notes |
| March 2025 | Salesforce CPQ goes end of sale for new customers; existing customers renew and get support. | Salesforce (status) |
| July 2026 | Salesforce CPQ’s online help is replaced by a single PDF. | KB 005388761 |
| September 14, 2026 | Salesforce restores the Revenue Cloud name after a year as Agentforce Revenue Management. | The Next Web |
| September 16, 2026 | Dreamforce: a migration assistant for the CPQ managed package announced, December 2026 target. | Salesforce+ |
| October 12, 2026 | Winter ’27: new agent quoting ships in Revenue Cloud, not in Salesforce CPQ. | Salesforce |
Running both in one org
You do not have to switch on one day. Salesforce documents a coexistence mode in which the CPQ package and Revenue Cloud run in the same org during a transition, with a Revenue Cloud licence, and publishes a feature matrix of what works where (Salesforce Help). One pattern: new business or one product line on Revenue Cloud, renewals finishing on CPQ, and CPQ licensed until the last renewal has gone through the new side. Budget for both licences for that period, and for reports that have to read from two models. The CPQ to Revenue Cloud playbook has the rollout options.
If you are on Salesforce CPQ today
Three paths, and no deadline forcing any of them.
Questions to ask before you decide
- Which of our CPQ features exist in Revenue Cloud today?
Ask for a list against your own org: bundles, price rules, discount schedules, contracted prices, amendments, renewals and templates, each marked available now or roadmap.
- Who will own pricing after go-live?
Ask to see a price change made live by your admin, not a partner, in pricing procedures and CML.
- What will the migration assistant convert, and what will it leave?
It has a December 2026 target. Ask for the list of unconverted items for your org before you commit, and whether it is included in your licence.
- What is the fixed fee and the date?
Salesforce quotes 3–6 months as typical; a full rebuild runs 12–18 months in practice. Ask your implementer (Salesforce Professional Services or a partner) for both in a statement of work.
- What happens to our CPQ renewal if we wait?
Salesforce’s own page says you can renew, add users and get support. Ask for any different answer in writing.
No. It is a separate product with a different data model. Salesforce has no first-party migration tool yet (one is on its roadmap for December 2026); moving from CPQ to Revenue Cloud Advanced is a re-implementation that runs 12–18 months in practice. Salesforce points customers to partner accelerators from Forsys, IdeaHelix and Prodly. Source: Salesforce
Salesforce CPQ is a managed package with SKU-based bundles, price rules and Quote Calculator Plugin scripts, and pricing that runs in the browser. Revenue Cloud runs on the core platform with an attribute-based catalog, pricing procedures that run on the server, a constraint-based configurator and asset-based renewals. Salesforce’s own Help says to treat a move between them as a redesign (Salesforce Help).
No. Salesforce says there is no forced migration. CPQ is end of sale, not end of life: existing customers can renew, add users, and receive support, and no end-of-life date has been announced. The practical pressure is that CPQ gets no new features and, since July 2026, has no online documentation. Source: Salesforce · KB 005388761
Revenue Cloud is $150 per user per month (Growth) or $200 (Advanced) on Salesforce’s pricing page. Salesforce CPQ is not sold to new customers and has no published list price; existing customers renew on their contract terms. For comparison, Kugamon’s Salesforce-native CPQ is $65 per user per month on its AppExchange listing.
In practice a full rebuild runs 12–18 months. Salesforce’s own page quotes 3–6 months; treat that as a best case. A migration to a Salesforce-native alternative such as Kugamon typically runs 4–8 weeks because it reuses standard Salesforce Products and Price Books. Source: Salesforce · Migration playbook
Salesforce (2026) says approximately 15% of Revenue Cloud Advanced customers migrated from Salesforce CPQ. It does not publish the absolute number. Source: Salesforce
Yes. Salesforce documents a coexistence mode for running the CPQ package and Revenue Cloud in one org during a transition, with a Revenue Cloud licence, and publishes a feature matrix of what works in each (Salesforce Help). Plan for two licences and two data models until the last CPQ renewal has moved.
Not on any announced date. Salesforce CPQ is end of sale, not end of life: no end-of-life date has been announced, existing customers can renew, add users and receive support, and there is no forced migration (Salesforce). It gets no new features, and its online help moved to a single PDF in July 2026 (KB 005388761).
Pricing procedures: declarative steps that run on the server and build a price waterfall, with Apex pre- and post-hooks where needed (Salesforce Help). Discount schedules become price adjustment schedules, and contracted prices become ContractItemPrice records (object mapper). None of them convert automatically; complex price rules and Quote Calculator Plugin logic are rebuilt by hand (Salesforce Help).
What Salesforce admins say on AppExchange
Quoted verbatim from the Kugamon listing on AppExchange. Reviewer names and dates as published there. Read all 135, including the critical ones →
★★★★★A new bar for RevOps
“As someone who has set up Salesforce CPQ before, I found Kugamon to be much more straightforward and easier to use. It took us just a few weeks to get going, rather than the few months or even years required by other systems.”
★★★★★Easy to understand, easy to implement
“This SFDC-native platform is lightweight but powerful, bringing the entire sales process onto one pane of glass. No more disconnected Opportunities and Quotes/Orders, no more fractured approval processes, just more control over everything. Implementation is a breeze.”
★★★★★Great Salesforce Native CPQ Tool
“Kugamon is an awesome tool that I found to be easy to understand and configure for our complex use case. Not to mention, they have a fantastic onboarding process that does a great job of covering every feature.”
Published prices, your team size
The calculator uses Salesforce’s published Revenue Cloud Advanced price and Kugamon’s published AppExchange price. Competitor implementation figures are labeled estimates.