Salesforce CPQ end of sale: should you migrate to Revenue Cloud Advanced?
What actually changed
Salesforce CPQ was built as a managed package sitting on top of the Salesforce platform. Revenue Cloud Advanced is built into the core platform. Salesforce's own migration page puts the difference this way: CPQ's business logic lived inside its UI components, while RCA exposes 150+ APIs and invocable actions on standard core objects, so quoting, pricing and ordering can be automated and called from anywhere, not just the Salesforce quote screen.
Salesforce also positions RCA for things CPQ was never designed for: selling through channels and outside Salesforce, hybrid and consumption-based pricing, and automation with AI agents. That's where its roadmap is going.
Migrate now, or wait?
Migrate now if…
- You sell usage, consumption or hybrid models that CPQ handles awkwardly.
- Partners, dealers or customers need to quote outside the Salesforce UI.
- Your CPQ is so customized that every change is a project.
- You're already planning a major quote-to-cash change (new ERP, new billing, an acquisition to integrate).
Wait and plan if…
- CPQ works for how you sell today.
- Your catalog and pricing are stable.
- There's no near-term driver beyond the announcement.
- You can't yet staff a reimplementation properly. A rushed migration is the expensive kind.
Waiting isn't doing nothing. Use the time to document your pricing logic, clean the catalog, and find out what your current setup is getting wrong — the next section explains why that last part matters most.
Why it's a reimplementation, not an upgrade
| Area | Salesforce CPQ | Revenue Cloud Advanced |
|---|---|---|
| Architecture | Managed package on top of the platform | Built into the core platform |
| Where logic lives | Largely in package UI components and custom code | Standard core objects, 150+ APIs and invocable actions |
| Rules and pricing | Product rules, price rules, custom scripts | Rebuilt in RCA's own catalog, pricing and configuration model — no one-to-one port |
| Where you sell | Built for direct sales in Salesforce | Positioned for selling anywhere, including channels |
| Revenue models | One-time purchases and standard subscriptions | Hybrid and consumption models |
Because the rules are rebuilt rather than moved, the honest migration estimate depends on how much custom logic you have. A clean catalog with standard pricing moves in weeks; years of accumulated product rules, price rules and custom code take quarters, phased.
The step most migrations skip
A migration is the one time you rebuild every price rule, discount schedule and approval from scratch. Most projects use that moment to port today's logic as faithfully as possible — including whatever it's been getting wrong.
Before we design anything in RCA, we run a Leak Ledger on the current setup: join quotes, orders, invoices and claims on one deal ID and itemize what's slipping. Discounts running deeper than peer deals. Orders entered at a different price than the accepted quote. Invoices billed off the contract. Required options left off quotes. Each finding becomes a design requirement for the new system instead of a habit you migrate.
Don't migrate your leaks. The rebuild is the cheapest moment you'll ever have to fix them.
Our engagement-derived planning rates — not survey statistics — put configuration and discounting errors at about 3% of quoted value for configure-to-order manufacturers. On a migration budget, finding even part of that pays for the discovery. The argument behind this approach is in A ledger, not a dashboard.
A migration plan that holds up
- Inventory the logic. Every product rule, price rule, discount schedule, approval and custom script, with an owner who knows why it exists.
- Run the ledger. Find what the current setup is leaking, so the new design fixes it instead of copying it.
- Clean the catalog. Retire dead products and bundles before they're rebuilt.
- Design in RCA's model, not CPQ's. Rebuild pricing and configuration the way the platform expects; don't recreate the package in custom code.
- Connect the ERP and billing so orders and invoices reconcile to the quote — a read-mostly connection where possible.
- Run both in parallel on real deals, compare outputs line by line, then cut over by segment.
Who's writing this
Nteli is a Salesforce Premier Partner headquartered at Capital Factory in Austin. We implement both Salesforce CPQ and Revenue Cloud Advanced and Billing, and MuleSoft for the CRM-to-ERP connection — 58 certifications across the team and a 4.93-star average across 10 AppExchange reviews. Before Nteli, our team built product configurators and pricing systems at Cisco, Dell and IBM. Texas customers get us in person: Salesforce consultants in Texas.
Find your leaks before you migrate them.
The Leak Ledger Workshop: one day with your CPQ, order and invoice data — a dollar ledger of what your current setup is getting wrong, ready to become your RCA design requirements.