Skip to content
Techila Global Services
Techila/Insights/Salesforce Revenue Cloud vs CPQ: What Changed and When to Move

Salesforce · 13 min read

Salesforce Revenue Cloud vs CPQ: What Changed and When to Move

Category

Salesforce

Read time

13 min read

Author

Techila Salesforce Practice

Published

22 Nov 2026

Last updated

22 Nov 2026

A plain-English explainer of Salesforce CPQ and Revenue Cloud (Revenue Cloud Advanced, RLM): current names, a side-by-side comparison, what Salesforce says about CPQ's status, when to stay or move, and a migration planning checklist.

Salesforce CPQ is the configure-price-quote managed package that came from Salesforce's 2016 acquisition of SteelBrick. Revenue Cloud, whose top edition is Revenue Cloud Advanced (RCA), is its successor: a revenue lifecycle management (RLM) product built into the core Salesforce platform that covers catalog, pricing, quoting, contracts, orders and assets, with Revenue Cloud Billing alongside. CPQ is end of sale for new customers but not end of life, so existing customers can stay on it while they plan a move.

This guide explains the two products and their names, compares them side by side, and gives a checklist for planning a migration. If you want the detail on how CPQ itself works, read our Salesforce CPQ guide. Every product fact below comes from Salesforce's own pages, read on 22 November 2026.

What is Salesforce CPQ?

Salesforce CPQ is a managed package that adds product configuration, pricing rules, discount approvals and quote documents to Sales Cloud. Salesforce completed its acquisition of SteelBrick on 1 February 2016, which is why many admins still call CPQ "Steelbrick".

The key word is package. Salesforce's migration page says CPQ "was built as a managed package, sitting on top of the Salesforce platform". Its objects, price rules and quote calculator live inside that package. That design works, but it means CPQ's logic sits apart from the platform's own data model and APIs. Salesforce now describes it, on its Revenue Cloud explainer, as "a previously managed product with powerful but limited functionality".

What is Salesforce Revenue Cloud (Revenue Cloud Advanced, RLM)?

Revenue Cloud is Salesforce's revenue lifecycle management product, built natively on the Salesforce platform rather than as a package. In July 2025 Salesforce said it had "rebuilt its CPQ solution as the all-new Revenue Cloud", and launched Agentforce for Revenue inside it as part of the Summer '25 release.

Salesforce describes Revenue Cloud as running on the Agentforce 360 Platform, native to Data 360, and sharing the same data model, security and user interface as Sales Cloud and Service Cloud. It is API-first: the migration page says RCA's logic is exposed through APIs and standard objects, with more than 150 APIs and invocable actions. A Salesforce blog calls it "built headless", meaning the pricing, configuration and quoting logic lives in the APIs, not in a screen. In practice, the same pricing engine can serve a sales rep, a partner portal, a self-service storefront or an AI agent.

On Salesforce's product page and in its Trailhead overview, Revenue Cloud covers:

  • Product catalog: one attribute-based catalog across channels, managed in Product Catalog Management, with integration to PIM, PLM and ERP systems.
  • Pricing: a configurable pricing engine with pre-built pricing frameworks and visibility into how each price was calculated.
  • Configure and quote: the Product Configurator, with a Constraint Builder for configuration rules, bundles and add-on suggestions.
  • Assets and subscriptions: tracking what each customer owns so sellers can amend, renew or cancel, with ARR, MRR and NRR visibility.
  • Contracts: contracts created from opportunities, legal-managed templates and clause libraries, approvals, e-signature integration and obligation management.
  • Orders: a design canvas that breaks a commercial order into technical fulfillment orders and triggers downstream steps such as fulfillment, revenue recognition and billing.
  • Billing and usage: invoicing, payments, credit and debit memos and usage management, delivered through Revenue Cloud Billing.
  • Analytics: pricing, subscription, order and billing dashboards powered by Tableau Next.

What is Revenue Cloud called now?

Salesforce's naming has moved several times, which is why search results mix four or five names for one product. Here is what each name means, as Salesforce uses it today:

Salesforce revenue product names, as used on Salesforce pages read on 22 November 2026
Name you will seeWhat it refers to
Revenue CloudThe product name in the heading of Salesforce's US and Canada revenue pages
Revenue Cloud Advanced (RCA)The higher edition of Revenue Cloud, and the name Salesforce uses on its CPQ end-of-sale and migration pages
Revenue Cloud GrowthThe entry edition: quoting and configurator, order capture and subscriptions
Revenue lifecycle management (RLM)The category; Salesforce says a revenue cloud is "more commonly referred to as a revenue lifecycle management solution", and its product URLs still use the term
Agentforce Revenue ManagementA name Salesforce has used for Revenue Cloud, for example in Trailhead module titles and earlier regional page titles
Agentforce for RevenueThe AI agent capabilities embedded in Revenue Cloud, launched in July 2025
Revenue Cloud BillingThe complementary billing product: usage rating, invoicing, payments and collections
Salesforce CPQ (SteelBrick)The older managed package, now end of sale for new customers

One caution: older articles, job posts and vendor decks sometimes use "Revenue Cloud" loosely for CPQ-based setups. When someone says "Revenue Cloud", ask whether they mean the CPQ managed package or the platform-native product. In this guide, Revenue Cloud always means the platform-native product.

Salesforce CPQ vs Revenue Cloud: side-by-side comparison

The short version: CPQ is a quoting package; Revenue Cloud is a revenue platform. The table compares them on the points that matter in a buying decision.

Salesforce CPQ vs Revenue Cloud, from Salesforce's own pages (read 22 November 2026)
AreaSalesforce CPQRevenue Cloud (Growth and Advanced)
ArchitectureManaged package on top of the Salesforce platformBuilt natively into the core platform; logic exposed through APIs and standard objects (150+ APIs and invocable actions)
Product catalogProducts and bundles defined inside the packageOne attribute-based catalog across channels, with PIM, PLM and ERP integration
PricingPrice rules and the package's quote calculatorA configurable pricing engine with pre-built frameworks and price-calculation visibility
Configuration and quotingProduct rules, bundles, discounts, approvals and quote documentsProduct Configurator with constraint-based and rules-based logic; Salesforce says it handles quotes with more than a thousand line items
Contracts, orders and assetsContracts and orders generated from quotesContract lifecycle with clause libraries and obligation management; order decomposition into fulfillment; asset lifecycle for amend, renew and cancel
BillingNot part of CPQ; handled by a separate billing productRevenue Cloud Billing, separate but complementary: usage rating, invoicing, payments and collections
Agentforce and AINo new features; CPQ is in a maintenance phaseAutomatic Quoting with Agentforce, a quoting agent, AI-assisted clause generation and redlining, and agents in Slack and on records
AnalyticsStandard Salesforce reports on package objectsRevenue dashboards powered by Tableau Next
LicensingExisting customers only: renewals and additional usersTwo editions, priced per user per month and billed annually (see below)
Who can buy itNot sold to new customersNew and existing customers

What does Revenue Cloud cost?

Salesforce's pricing page listed two editions when we read it on 22 November 2026:

  • Revenue Cloud Growth: USD 150 per user per month, billed annually. Includes quoting and configurator, order capture and subscriptions.
  • Revenue Cloud Advanced: USD 200 per user per month, billed annually, with an annual contract. Includes everything in Growth plus contracts and orders, consumption and invoicing, and AI and analytics.

These are list prices for the licenses. They exclude implementation, data migration and any add-ons, and enterprise agreements are negotiated. For what a project costs to deliver, see our Salesforce implementation cost guide.

Is Salesforce CPQ end of life?

No. On a page dated 10 July 2026, Salesforce says CPQ "is end of sale, not end of life". In summary, Salesforce says:

  • It has not announced an end-of-life date for CPQ, and there is no forced migration.
  • Existing customers can keep using CPQ, buy additional users, renew licenses and receive support under their current contract terms.
  • CPQ is in a maintenance phase: support and critical fixes continue, but there are no new features. Innovation is focused on Revenue Cloud Advanced and Revenue Cloud Billing.
  • About 15% of Revenue Cloud Advanced customers migrated from CPQ, and a typical migration takes 3 to 6 months from discovery to go-live.

Be wary of any article that gives a CPQ retirement date. As of 22 November 2026, Salesforce has not published one. Our CPQ guide covers what end of sale means day to day.

Should you stay on CPQ or move to Revenue Cloud?

There is no deadline, so make this a business decision, not a panic one. These are the signals we look for with clients.

Staying on CPQ for now is reasonable when:

  • Your catalog and pricing are stable, quotes are fast, and users are not working around the system.
  • You have no near-term plans for usage-based pricing, new sales channels or AI quoting.
  • Your CPQ customizations are well documented and your team can support them.
  • A bigger program, such as an ERP change, would compete for the same people this year.

Planning a move to Revenue Cloud makes sense when:

  • Quote calculation is slow, or price rules and custom scripts have become hard to change safely.
  • You are adding subscriptions, consumption or usage pricing, or need amend-renew-cancel on assets.
  • You want one pricing engine behind sales, partner, self-service and agent channels.
  • You want Agentforce to create or change quotes, which Salesforce is building on Revenue Cloud, not CPQ.
  • Billing, contracts or order fulfillment are manual hand-offs today.
  • A renewal, re-organization, new product line or pricing redesign gives you a natural moment to change.

If you are new to Salesforce quoting, the choice is made for you: CPQ is not sold to new customers, so start with Revenue Cloud. If you are weighing whether Salesforce should also run finance processes, read is Salesforce an ERP? first, because Revenue Cloud stops where your ERP's general ledger begins.

CPQ to Revenue Cloud migration planning checklist

Salesforce's migration page says the right strategy depends on CPQ complexity, data quality, pricing logic and your appetite for change, and lists four paths (lift and shift, selective transformation, full rationalization, new business unit) and four rollout models (big bang, pilot-first, bridge and cohort-based). Our CPQ guide explains each one. Whichever you pick, work through this checklist before you commit to dates.

  1. Inventory what CPQ does today. List products, bundles, product rules, price rules, discount schedules, approval chains, quote templates and every custom script or Apex class that touches the package.
  2. Separate the rules you need from the history. Many CPQ orgs carry rules for products that are no longer sold. Decide which logic moves, which is redesigned and which is retired.
  3. Map to the Revenue Cloud model. Revenue Cloud uses its own catalog, pricing and transaction objects rather than the package's. Map each CPQ object and field to its target, and note where there is no one-to-one match.
  4. Choose a path and a rollout model. Agree how much redesign you want, and whether you switch over at once, by pilot, by cohort or through a bridge where new business goes to Revenue Cloud while existing contracts run to renewal.
  5. Decide what happens to open quotes, contracts and subscriptions. Plan amendments and renewals of contracts signed in CPQ: migrate them as assets, or let them run to renewal in CPQ.
  6. Plan billing at the same time. Decide whether invoicing moves to Revenue Cloud Billing, stays in your ERP, or changes later, and draw the hand-off.
  7. List every integration. ERP, tax, e-signature, PIM or PLM, data warehouse and any portal that reads prices. Each needs to be re-pointed to the new APIs.
  8. Check data quality early. Run trial loads of products, price books and active contracts, and reconcile totals against CPQ. Our data migration strategies guide covers trial loads and reconciliation.
  9. Agree the licensing. Choose Growth or Advanced by the capabilities you need, and plan how CPQ and Revenue Cloud licenses overlap during a bridge period.
  10. Test with real deals. Rebuild a sample of recent quotes, including your most complex, and compare prices line by line before go-live.
  11. Train and change-manage. Sales, deal desk, legal and finance all change how they work. Plan training by role, not one session for everyone.
  12. Add Agentforce last, not first. Get catalog, pricing and data right, then add quoting agents on top, with clear limits on what they may change.

How Techila helps

Techila Global Services is a Salesforce Summit Partner headquartered in Frisco, Texas, with 700+ projects delivered and 500+ Salesforce certifications across our team. Our Revenue Cloud practice runs CPQ health checks, Revenue Cloud implementations and CPQ-to-Revenue Cloud migrations, and our Salesforce implementation team covers the wider Sales Cloud and integration work around them. We start with a written assessment of your CPQ org, so you can decide when to move with the facts in hand.

Frequently asked questions

Is Salesforce Revenue Cloud the same as Revenue Cloud Advanced and RLM?

They describe the same product family. Revenue Cloud is the product name on Salesforce's US site. Revenue Cloud Advanced (RCA) is the higher of its two editions and the name Salesforce uses on its CPQ migration pages. Revenue lifecycle management (RLM) is the category: Salesforce says a revenue cloud is more commonly referred to as a revenue lifecycle management solution.

What is Agentforce Revenue Management?

It is a name Salesforce has used for Revenue Cloud. A Trailhead module is titled "Agentforce Revenue Management" and some regional Salesforce pages have carried the title "Agentforce Revenue Management (formerly Revenue Cloud)". When we checked on 22 November 2026, the US and Canada product pages used "Revenue Cloud" as the heading. It is the same product either way.

Is Salesforce CPQ being discontinued?

Salesforce says CPQ is end of sale, not end of life. Its page dated 10 July 2026 says it has not announced an end-of-life date, there is no forced migration, and existing customers can keep using CPQ, buy more users, renew and get support. CPQ is in a maintenance phase with support and critical fixes but no new features.

How much does Salesforce Revenue Cloud cost?

Salesforce's pricing page, read on 22 November 2026, lists Revenue Cloud Growth at USD 150 per user per month and Revenue Cloud Advanced at USD 200 per user per month, both billed annually; Advanced requires an annual contract. Implementation, Revenue Cloud Billing and any add-ons are separate, so get a quote for your scope.

Can Salesforce CPQ and Revenue Cloud run in the same org?

Salesforce's own migration page describes a bridge rollout, where new business goes to Revenue Cloud Advanced while existing CPQ contracts run to renewal, which means both run side by side for a period. Salesforce Help publishes coexistence guidance for this; read the version for your release, because it sets out which objects and features overlap.

How long does a CPQ to Revenue Cloud migration take?

Salesforce puts a typical migration at 3 to 6 months from discovery to go-live, and says complex implementations can take longer. The main drivers are the number of products and price rules, the quality of your quote and contract data, integrations to ERP and billing, and whether you redesign or copy your current model.

Next steps

If you run CPQ, start with the inventory in step 1 of the checklist; it is useful whether you move this year or in three. If you are buying Salesforce quoting for the first time, plan for Revenue Cloud from day one. To talk it through with our revenue team, book a discovery call.

Talk to an expert about Salesforce Revenue Cloud services

All fields are required unless marked optional.

We save these details on this device to fill them in next time.

Add project details (optional: clouds, users, start date, role)
Salesforce clouds (optional, choose any)Which Salesforce clouds are involved?
Salesforce users (optional)How many Salesforce users?
Start date (optional)When do you want to start?
Your role (optional)What is your role?

We reply within 1 business day.

By sending this form, you agree that Techila Global Services may contact you by email or phone about your request. We do not sell your personal information. See our Privacy Policy.

Working on something like this?

We reply within 1 business day · +1 617-777-9873

See case studies