I Have Salesforce CPQ. How Do I Move to Revenue Cloud Advanced (RCA)?

If you run Salesforce CPQ, the move to Revenue Cloud Advanced (RCA) is no longer a question of if, but when and how. Salesforce placed CPQ into end-of-sale in 2025 and pointed new investment at RCA, the platform it rebranded as Agentforce Revenue Management (ARM) at Dreamforce 2025. This guide explains how to move from Salesforce CPQ to Revenue Cloud Advanced (RCA): what the migration actually involves, how long it takes, and the one part most teams underestimate.

A quick note on names, because they have changed several times. Revenue Cloud Advanced (RCA) and Agentforce Revenue Management (ARM) refer to the same underlying platform. Salesforce moved from "Revenue Cloud" to "Revenue Lifecycle Management," then to "Revenue Cloud Advanced," and then to "Agentforce Revenue Management" at Dreamforce 2025. This article uses RCA and ARM interchangeably to mean that platform.

Why is Salesforce CPQ end-of-sale forcing the move to RCA?

Salesforce CPQ reached end-of-sale in 2025, which means Salesforce stopped selling it to new customers and shifted product development to Revenue Cloud Advanced (RCA), now branded Agentforce Revenue Management (ARM). Existing customers can still use and renew CPQ, but the roadmap and new capabilities now live on RCA.

End-of-sale is not end-of-life. Your current CPQ instance keeps working, and you can renew licenses. What changes is direction: feature development, AI capabilities, and Salesforce's own attention move to RCA. Industry watchers generally expect an end-of-life milestone several years after end-of-sale, which puts realistic planning horizons in the 2029 to 2030 range. That gives most teams runway, but not unlimited runway.

It helps to read this as a modernization, not a penalty. Salesforce rebuilt its revenue platform on standard objects and added AI-native capabilities that CPQ was never designed to carry. The Salesforce quoting layer (CPQ today, RCA and Agentforce Revenue Management going forward) is getting stronger. The practical task in front of you is planning a controlled move while your CPQ investment is still fully supported, rather than waiting until the clock forces a rushed one.

What is Revenue Cloud Advanced (RCA), and how is it different from CPQ?

Revenue Cloud Advanced (RCA) is Salesforce's rebuilt revenue lifecycle platform, now branded Agentforce Revenue Management (ARM). The key difference from CPQ is architectural: CPQ is a managed package running on custom objects, while RCA is built on standard Salesforce platform objects, with a new pricing engine, a business rules engine, and headless APIs.

That architectural gap is the reason the move is more than a version bump. In CPQ, your quoting logic lives in custom objects, Quote Calculator Plugins (QCP), price rules, and product rules inside a package. In RCA, the equivalent concepts map to standard objects like Quote, Order, and Contract, with pricing handled by the Business Rules Engine and Product Configuration Model (PCM). The two systems speak different languages under the hood.

Here is a simplified comparison of what changes:

The takeaway is straightforward. You are not upgrading CPQ. You are adopting a different platform that happens to do a similar job, and your existing configuration does not carry over automatically.

Is moving from CPQ to RCA an upgrade or a full reimplementation?

Moving from CPQ to RCA is a full reimplementation, not an in-place upgrade. There is no automated, one-click migration tool. Because CPQ runs on custom objects and RCA uses standard platform objects, product bundles, price rules, and QCP scripts are rebuilt in the new model rather than copied across.

This is the single most important expectation to set with leadership. Teams that budget for a "migration" in the copy-and-move sense are the ones that get surprised. What you are really doing is redesigning your quoting and pricing configuration on a new foundation, then moving your active data into it.

The upside of a reimplementation is that it forces a cleanup you probably needed anyway. Most long-lived CPQ orgs accumulate what practitioners call "zombie rules," pricing logic and scripts that no longer do anything but still slow the system down, along with dead SKUs and duplicate products. Treating the move as a rebuild lets you retire that technical debt instead of carrying it forward into a fresh platform.

How do you move from Salesforce CPQ to Revenue Cloud Advanced (RCA)?

To move from Salesforce CPQ to Revenue Cloud Advanced (RCA), work through five phases: assess and clean your catalog, map data from custom to standard objects, rebuild pricing logic in the Business Rules Engine, reconnect downstream billing and ERP integrations, then run parallel testing before cutover. Most teams phase the switch rather than flipping everything at once.

Here is the sequence in practical terms:

1. Assess and clean. Audit your CPQ org before you touch RCA. Identify active versus dormant products, flag zombie rules and unused QCP scripts, and consolidate duplicate SKUs. A leaner catalog makes every later step faster. This is also where you document the pricing behavior you actually need to preserve.
2. Map the data model. CPQ custom objects do not have one-to-one equivalents in RCA. Build a field-level map from old objects to standard ones (for example, CPQ quote lines become Transaction Line Items) so historical quotes, orders, and contracts stay accurate after the move.
3. Rebuild pricing and configuration. Recreate bundles, attributes, and pricing logic using the Product Configuration Model and Business Rules Engine. QCP JavaScript will not run in the new engine, so any custom calculation logic has to be re-expressed. This is usually the largest single workstream.
4. Reconnect downstream integrations. Your quotes and orders feed billing and your ERP. Every integration that read from CPQ objects now has to read from RCA's standard objects. This includes the handoff into finance systems for invoicing and revenue recognition, which is the step teams most often shortchange and the one that most affects finance after go-live.
5. Test in parallel, then cut over. Rebuild and validate in a sandbox, run RCA alongside CPQ, and reconcile results before go-live. Many companies use a bridge approach: start all new deals in RCA immediately, keep existing contracts in CPQ, and migrate those contracts as they come up for renewal. Keeping CPQ in read-only mode during the transition preserves a reference.

None of these phases is optional, and the order matters. Skipping the assessment step, in particular, is how a six-month program turns into a twelve-month one.

How long does a CPQ to RCA migration take?

A CPQ to RCA migration timeline depends on complexity. Moderate CPQ environments commonly run about 4 to 6 months of implementation, while heavily customized enterprise orgs with advanced pricing rules, legacy bundles, and billing dependencies often run 9 to 18 months. Add roughly 3 to 6 months of discovery and planning before the build contract is signed.

Plan the timeline backward from two dates: your next major CPQ renewal and the expected end-of-life horizon. If enterprise builds can take a year and a half, and prudent teams want margin for testing and change management, then a program that "starts now" in the 2029 to 2030 EOL window still leaves comfortable room. Waiting two more years compresses that margin quickly.

Complexity drivers that push you toward the longer end include the number of custom QCP scripts, the volume of active SKUs and bundles, multi-currency and multi-entity requirements, and how many downstream systems consume your CPQ data. The more integrations that read from CPQ, the more surface area you have to rebuild and retest.

What do most teams underestimate in a CPQ to RCA migration?

The most underestimated part of a CPQ to RCA migration is the handoff from the Salesforce quoting layer to the ERP where revenue is recognized. RCA modernizes quoting and pricing, but a closed deal still has to become accurate invoices and ASC 606-compliant revenue in your ERP. That CRM-to-ERP boundary is where migrations stall.

The reason is structural, not a fault of any product. The Salesforce stack (CPQ today, RCA and ARM going forward) is built to configure, price, and close the deal. Recognizing that deal's revenue lives in the ERP, in systems like NetSuite Advanced Revenue Management. When you rebuild your quoting layer on new objects, every commercial event that used to flow into finance now originates from a different data model, and the logic that translates a sales event into a correct accounting outcome has to be rebuilt with it.

Consider the classic pattern: the same deal shows up as three different numbers. A booking of $500K in the CRM becomes $420K in billing and $180K in recognized revenue in a given period. Those are not errors, they are the normal result of ramps, proration, usage, and revenue schedules. But if the handoff between the quoting layer and the ERP is not designed deliberately, that translation becomes manual reconciliation, cancel-and-rebill cycles, and spreadsheets at quarter-end. A CPQ to RCA migration is the moment to fix that translation on purpose, not to rebuild the same gap on newer software.

Modern pricing makes this sharper. As more companies add usage, consumption, credits, and hybrid structures on top of subscriptions, the distance between "what sales sold" and "what finance recognizes" grows. RCA gives sales the agility to quote those models. The finance side still has to receive them cleanly. You can see how the new Salesforce quoting layer handles usage-based pricing and why the downstream connection matters more, not less, once you modernize.

How do you keep revenue recognition clean during and after the move?

Keep your ERP as the system of record for invoicing and revenue recognition, and connect the new Revenue Cloud Advanced quoting layer to it so commercial events map to correct ASC 606 outcomes automatically. The goal is that a deal closed in Salesforce becomes accurate revenue in your ERP without manual translation.

In practice, that means three things during the migration. First, treat the CRM-to-ERP integration as a first-class workstream in the project plan, not a task you bolt on after go-live. Second, define how each commercial event (new business, amendment, renewal, cancellation, usage) should land in the ERP before you rebuild the pipes. Third, validate revenue outcomes in parallel, comparing what RCA produces against what finance expects, before you retire CPQ.

This is the layer we spend our time on at Continuous: rather than bolting on middleware, we embed revenue infrastructure natively inside Salesforce and NetSuite. Salesforce stays the source of truth for the deal, NetSuite stays the source of truth for revenue, and commercial events flow cleanly between them without custom code or manual cleanup. If you are scoping a CPQ to RCA move, it is worth designing the finance handoff at the same time, rather than discovering it at your first quarter-close on the new platform.

What should you do before you start the CPQ to RCA migration?

Before you start a CPQ to RCA migration, do three things: inventory your current CPQ configuration and integrations, confirm your renewal and end-of-life runway, and decide who owns the finance handoff. The migration succeeds or fails on preparation, not on the build itself.

Start with an honest inventory. List every product, price rule, QCP script, and downstream integration, and mark what is active versus dormant. This inventory becomes your cleanup list and your rebuild scope in one document. Next, confirm the dates that constrain you, your renewal timing and the EOL horizon, so the program is scheduled with margin rather than urgency. Finally, name an owner for the CRM-to-ERP handoff. When that ownership is ambiguous, the finance connection is the piece that quietly slips, and it is the hardest one to fix after cutover.

Handled this way, the move off CPQ is a controlled modernization rather than a fire drill. You retire technical debt, adopt a platform Salesforce is actively investing in, and rebuild the finance handoff correctly while you have time to test it.

Key takeaways

Moving from Salesforce CPQ to Revenue Cloud Advanced (RCA) is a full reimplementation on a new, standard-object platform, not an upgrade, and there is no automated migration tool. Plan for a phased program of roughly 4 to 18 months depending on complexity, use the rebuild to retire technical debt, and treat the CRM-to-ERP revenue handoff as a first-class part of the project. Design how closed deals become recognized revenue before you cut over, keep your ERP as the system of record, and you turn an end-of-sale deadline into a clean modernization.

If you want a second set of eyes on the finance side of your migration, talk to our team about connecting the new Salesforce quoting layer to NetSuite, or request a demo to see the handoff work end to end.