Having been part of multiple engagements and scoping calls, I'll say this plainly: most companies approaching Revenue Cloud Advanced (RCA) today are starting in the wrong place. (note: it's officially called Agentforce Revenue Management now, but many in the space still call this RCA; some still call it RLM, when it was previously named Revenue Lifecycle Management)
The conversation almost always begins the same way: "we need to replace Salesforce CPQ." That's an understandable reflex, but it's the wrong starting point, and it's worth being factual about why.
Salesforce moved CPQ to End-of-Sale status in March 2025, though existing customers can (and do) still use the product. If your CPQ instance is working and you have no near-term plans to expand into new sales channels, there's no factual reason to feel rushed.
So, take your time comparing CPQ vs. RCA, and read up with our expertise from being hands-on with both, though we also work with many other systems across data, AI, and your entire business:
Jump to a section:
- "Just Replace Salesforce CPQ" Is the Wrong Frame
- The Actual Starting Point Is Your Data, Not Your Configuration
- Where Salesforce RCA Changes the Equation vs. CPQ
- Approach Salesforce CPQ vs. RCA as a Data Decision
- Frequently Asked Questions: RCA vs. CPQ
"Just Replace Salesforce CPQ" Is the Wrong Frame
CPQ and RCA are architecturally different systems: CPQ is a rules-based, template-driven engine that evaluates rule sets in sequence to determine valid configurations. RCA uses a data-model-driven pricing framework, built to react to structured data rather than stitch together sequential rules.
That's a significant architectural shift - particularly around multi-channel consistency, where CPQ historically required duplicating pricing logic across every channel it touched.
If you rebuild your existing CPQ configuration line-by-line inside RCA, you inherit the same technical debt in a new system, at a higher cost, without any of the architectural benefit RCA is supposed to provide. It is not a lift-and-shift approach, and treating it as such is asking for a six-figure failure.
The Actual Starting Point Is Your Data, Not Your Configuration
Before you touch RCA's configuration or explore other quote-to-cash platform options, you need to know which parts of your current product, pricing, and quote data are actually worth carrying forward. Dirty data is a huge (silent) killer of businesses, so run the Four Rs test on your data by asking what's:
- Relevant; does this pricing rule, product attribute, or approval condition still map to a real business need, or is it a workaround for a problem that no longer exists?
- Reliable; is the data behind it complete and trusted, or does it require manual correction before anyone acts on it?
- Revealing; does it tell you something about how the business actually sells, or is it just historical noise?
- Reusable; will this still make sense in your RCA data model, or is it a CPQ-specific patch that shouldn't exist anywhere?
If a pricing rule or discount approval doesn't hold up under, it's a candidate to leave behind when you migrate. This is absolutely not the time for "but what if?" because you'll map out your edge cases later.
Salesforce CPQ can have pricing lookup tables that have grown to tens of thousands of permutations, but I've found these tables are often a workaround for a pricing strategy that evolved faster than resources could get the systems updated. If these taped-up measures pull forward, you're setting up a data migration and maintenance burden inside RCA (and it's expensive). After all, it's a massive amount of complex data!
The Four Rs test is what tells you whether that complexity reflects a business need or a legacy patch that should be simplified before you migrate.
Where Salesforce RCA Changes the Equation vs. CPQ
Revenue Cloud Advanced is worth serious consideration if your business needs, or is heading toward, multi-channel selling: e-commerce, partner channels, self-service buying, or consistent pricing across several sales motions at once.
Salesforce CPQ was built for inside sales; the moment you added another channel, it needs duplicated pricing logic across systems - that's the inconsistency and maintenance burden RCA's unified data model is designed to remove.
This is most-felt in e-commerce and self-service contexts where you need flexibility … after all, CPQ was originally built way back in 2009 (as QuoteQuickly, before it was eventually bought by Salesforce as an add-on from Steelbrick) and buying options were a bit different then. Self-service and e-commerce buyers expect easy. If you've built a checkout experience around dozens of configuration fields and you're asking for more than a few items from the customer, you've already set yourself up to fail.
If you sell exclusively through an internal sales team with no plans to add channels, CPQ may continue to serve you well. Plenty of CPQ implementations run efficiently for years with the right cleanup and governance, and there's no factual pressure forcing a move before you're ready.
Revenue Cloud Advanced vs. CPQ: Key Differences
Suffice to say, we're fans of the platform's potential. But for those using CPQ today, you'll find this valuable regardless of where you land on switching.
Originally coined as Revenue Lifecycle Management and then rebranded as RCA in 2024 — and now Agentforce Revenue Management, per the note above — this is a built-by-Salesforce module that's already achieved feature parity with CPQ. There's a robust roadmap with many exciting releases coming from Salesforce, as well, meaning that as the months go by RCA will only become more powerful.
Here's a few more things we like about RCA vs. CPQ's functionality:
Structure
If you want to build a partner or customer portal with a degree of self-service capability, RCA provides exactly what you're looking for.
That's because it's built on a headless architecture - in short, it'll play nicely on other platforms such as a Salesforce community, your website, etc. It means you don't have to re-work your back-end logic to make it work in other places.
In addition, CPQ locks you into specific object models - but RCA doesn't. Have a high-volume, low-touch process that involves Salesforce objects like Cases, Products, and/or Invoicing?
It's much simpler to build with Revenue Cloud Advanced.
Renewal Flows
Let's say you have a customer with a 12-month recurring agreement. A few months before they're set to auto-renew, they reach out wanting to add two new products and then reset the agreement for the next 12 months.
Previously in CPQ, this involves a lot of manual steps - including contract cancellation, which we've seen throw off invoicing processes if not setup properly. A lot of our clients have complained about this being a complex process that wastes a ton of time (and invites user error with all the manual steps).
RCA has an out-of-the-box way of handling this specific scenario and it's much easier. Goodbye, painful admin work!
Object Mapping
Because Revenue Cloud Advanced leverages the native Salesforce quote object - and not the outsourced Steelbrick object that CPQ is built on - you get a much simpler interface that resembles more of a "shopping cart" experience when building your quote.
This makes adding discounts and single-line editing so much easier than when doing so in CPQ, which ends us saving you countless hours of admin work over the course of a year. More time selling!
Contracts
RCA provides an advanced Contract Lifecycle Management capability right out of the box. Think redlining, document generation, signatures, etc.
This streamlines the entire process around contracts and reduces the time needed to get a deal done. It's also simpler to setup in RCA vs. in CPQ.
As a bonus, it's much easier to include images in these documents - a nice touch to help customers confirm they're getting the right products and services.
Which Products and Business Models Benefit Most From Revenue Cloud
This is the question we get asked most directly, so let's answer it head-on rather than burying it in an FAQ.
Any product with real complexity is a potential fit, but a few specific patterns benefit the most:
- Usage-based or consumption billing. If pricing changes based on what a customer actually uses month to month, RCA's data-model-driven engine handles that far more cleanly than CPQ's rule-stacking approach.
- Multi-channel sales motions. Inside sales plus any combination of e-commerce, self-service, or partner portals is the primary use case RCA was built for to deploy one pricing model consistently across every channel.
- Frequent mid-term upsells or amendments. If you're a SaaS company where customers regularly add seats or products mid-contract, that's a renewal / amendment scenario RCA was designed to simplify.
- High-configuration physical products. Manufacturing and industrial products with real option complexity (think a piece of equipment with 40+ possible accessory combinations) benefit from RCA's constraint-based configuration model vs. what Salesforce CPQ offers today.
- Telecommunications and financial services product lines, which often combine complex bundling, regulatory requirements, and multi-channel sales in ways that expose CPQ's rule-based limitations quickly.
- If you want to move as much as possible into Salesforce. It seems simple enough; one unified platform that includes contract lifecycle, billing, invoicing, and more. While there are many robust quote-to-cash options in the market (such as Dealhub, Nue, and Conga) that is an additional platform to manage.
Approach Salesforce CPQ vs. RCA as a Data Decision
Before any configuration work begins, that means revisiting:
- Which product bundles and pricing rules are actually still relevant
- What data is reliable enough to trust in a new system
- How sales, partners, self-service, and billing should interact going forward
- How FP&A consumes pricing data for forecasting and modeling
This is why we don't walk into an RCA engagement with pre-written assumptions about what should carry over. In fact, your data-first approach may identify that another platform is a better-fit for you; we take a platform-agnostic approach because your data layer isn't tied to a specific technology - you absolutely need to run something akin to our 844 Approach that tackles the data layer to design the right pricing and product infrastructure the first time.
This is the difference between getting this right the first time and spending the next two to three years patching a system you just paid to rebuild.
How To Migrate from Salesforce CPQ to Revenue Cloud Advanced
If you have Salesforce CPQ today, this section's for you.
This isn't a lift-and-shift approach, so here's three steps to attack this the right way:
Rationalize Your Product Catalogue: An ice cream data example
Product catalog rationalization is one of the highest-leverage steps you can take before or during any quote-to-cash migration (irrespective of the platform you're moving to).
Let's say you work for an ice cream company with dozens of flavors, toppings, and other factors from cone type to number of scoops. That's a lot of configurable options! And it's too much for a sales rep to browse through when building a quote.
They just need "ice cream," and then to add the right options fast.
Same idea here: A telecom client's catalog was complex because years of one-off SKUs had never been cleaned up. A distributed computing client had outgrown using Opportunity Record Types to track products entirely, with two dissimilar core product lines each running their own separate, undocumented process.
What does the customer need, and how can / should sales engage to get this to them? That's the driving question … for ice cream, it looks like letting your customer choose "ice cream" and then picking flavors, toppings, and even throwing in some sprinkles for their kids. The back-end systems should configure everything else automatically and sync the data downstream to Finance's systems.
This isn't theoretical - getting this right leads to 40%+ reduction in quote time, 50% reduction in pricing exemptions, 98% invoice accuracy on catalog and pricing architecture work broadly.
Start simple with pricing.
This can get complex very quickly, so take your simplest pricing options and build out the quoting, renewals, discounts, and document generation workflows based on that. You shouldn't have many exemptions you have to work though yet (those come later).
Then, go slowly with more complex situations where it gets messy and you get those one-offs. Remember, you're tyring to build this more like an eCommerce experience with a shopping cart when building your quotes, so it may take some time ensuring the right data flows into the right places.
This takes longer than you'll budget for - no, really, I'd double the time allocated to be super-sure you're getting this right.
Revisit your current sales process.
Where are current pain points and bottlenecks today? What should we improve, and what gains come of these improvements? What processes do we want to accelerate so they're more efficient?
Again, designing the system for who's actually going to use it is the goal here - not following some technical how-tos that might get the system up and running, but not contextually for you.
Want a taste? Try the free Data Snapshot on your customer domain of data right now.
Frequently Asked Questions: RCA vs. CPQ
I'm seeing a lot of chatter around these platforms, so here's a few answers:
Is Salesforce CPQ being discontinued? Salesforce CPQ entered End-of-Sale status in March 2025, meaning no new licenses are being sold to new customers, but it has not been discontinued (end of life) at this time. Existing customers retain full support and can continue renewing. We believe there's another few years left
Should I migrate from Salesforce CPQ to Revenue Cloud Advanced? Migrating depends on your channel strategy, but definitely not from licensing pressure. If you need genuine multi-channel selling such as e-commerce, partner portals, self-service alongside direct sales, then RCA's unified data model addresses a real limitation in CPQ. We'd also recommend looking into other CPQ options such as Dealhub, Nue, and/or Conga, though as always it depends on your specific use cases. If what you have today in Salesforce CPQ is running well and supports what you need in the next 12-24 months, we would recommend staying put.
Can I just move my Salesforce CPQ configuration directly into RCA? No, migrating from CPQ into RCA is not a lift-and-shift process - it's a fundamental re-write of your quote-to-cash engine because they use different architectures (rules-based versus data-model-driven). Starting at the data layer is an absolute must if you want to get this right, though it does not take months to do.
What should I do before starting an RCA migration? Before migrating to Revenue Cloud Advanced, run your product, pricing, and quote data through a data-quality assessment (ours is built around the Four Rs of data, determining what's relevant, reliable, revealing, and reusable) before any configuration work begins. This tells you what's actually worth carrying forward versus what's going to cause friction and slow down your migration.
Is RCA replacing CPQ? Not outright. It's the next evolution of Salesforce CPQ, but Salesforce is continuing service for existing customers for now; we expect at least a few more years of CPQ support.
How much does Revenue Cloud Advanced cost? As with anything, it depends on your organization's needs and if you adopt a data-first approach that gets this right at the outset. This also goes for Revenue Cloud Advanced implementations as service providers work through the platforms' intricacies. I can tell you, as someone who's hands-on with this platform today, that I expect offerings to evolve as Salesforce continues development of the platform.
What is Salesforce Revenue Cloud Advanced (RCA)? Revenue Cloud Advanced is Salesforce's next-generation configure, price, quote (CPQ) and billing platform. Originally called Revenue Lifecycle Management, it was rebranded as RCA in 2024 and again as Agentforce Revenue Management in late 2025. It is built natively on the Salesforce platform unlike CPQ, which was originally a third-party product (Steelbrick) acquired by Salesforce in 2015.
Is Salesforce CPQ still available? Salesforce stopped selling CPQ as of March 2025. Existing CPQ customers remain supported, but all new implementations use Revenue Cloud Advanced. Salesforce's development investment is now focused entirely on RCA.
What is the difference between Revenue Cloud and Revenue Cloud Advanced? There is no difference; they both reference the same platform.
Is Revenue Cloud Advanced worth it for companies already on CPQ? RCA may be worthwhile, but it largely depends on your current selling motion and upcoming product needs. You may find there are other, better-suited CPQ platforms that are faster to implement, so it's worth building out a few use cases and then getting multiple vendors to weigh in.
How long does a CPQ to RCA migration take? Timeline varies significantly, but at minimum this is a few months; those with heavily-customized CPQ environments should budget more time and expect the process to involve business process redesign, not just technical migration.
What happened to RLM? Revenue Lifecycle Management (RLM) was what Revenue Cloud Advanced was originally called, but it was rebranded in 2024 by Salesforce, then rebranded again to Agentforce Revenue Management in late 2025. The naming has shifted a few times as the platform matured; RCA still touches all parts of the revenue lifecycle and is what most people call it today.
We'd recommend starting at the data layer and getting your foundations right before any platform decision.
