A practical look at where CPQ ends, where Revenue Cloud Advanced begins, and how to plan a migration that doesn’t blow up your timeline.
If you work anywhere near Salesforce quoting, pricing, or billing, you’ve probably heard the question more than once this year: should we stay on CPQ, or start planning our move to Revenue Cloud Advanced (RCA)?
There’s no one-size-fits-all answer, but there is a clear way to think about it. Here’s the breakdown I put together after digging into both platforms.
First, what are we actually comparing?
Salesforce CPQ is a managed package that sits on top of core Salesforce. It’s mature, widely deployed, and familiar to most Salesforce admins — products and pricing live in a fairly fixed, list-based structure, and business rules are configured through point-and-click logic.
Note: Document generation capabilities are currently limited and may require an additional license to enhance functionality. Billing is an additional package designed to handle all billing-related tasks.
Revenue Cloud Advanced is built natively on the Salesforce core platform rather than as a package bolted on top. It’s a more modern architecture designed to handle complex pricing, subscriptions, and billing without stitching together several add-ons.
Where they actually differ
The differences aren’t cosmetic — they show up in how each platform handles the full quote-to-cash lifecycle:
The pattern across every row is the same: CPQ was built for simpler, quote-centric selling. RCA was built for the messier reality most companies live in now — usage-based pricing, evolving subscriptions, and systems that need to talk to each other.
So, CPQ or RCA?
Here’s the honest answer: it depends on where you are today.
- If you’re an existing CPQ customer with a working setup, there’s no urgency to switch. CPQ is mature, proven, and still fully supported.
- If you’re a new customer starting from scratch, RCA is the more forward-looking choice — you’re not carrying any migration debt, and you get the modern architecture from day one.
Will Salesforce discontinue CPQ?
Not anytime soon. A few things worth keeping in mind:
- CPQ remains a mature, widely adopted, proven choice for existing customers.
- RCA (part of the broader Revenue Lifecycle Management vision) is powerful, but a full migration wave across the ecosystem will take time.
- Existing CPQ customers don’t need to rush a switch.
- New customers, on the other hand, are generally better served starting on RCA directly.
If you are planning a migration, here’s a phased approach that works (high level):
Migrating quote-to-cash systems is not a lift-and-shift. It’s closer to open-heart surgery on a system that’s still running your revenue. A phased plan makes the difference between a clean cutover and an 18-month overrun.
1. Assess & Inventory current CPQ setup:
Document everything in the existing CPQ org: product bundles, price books, price rules, discount schedules, QCP (Quote Calculator Plugin) scripts, approval rules, quote templates, and any ERP/billing integrations. Flag ‘ghost’ products and unused rules nobody remembers building. Sort every item into three buckets: Automated (tools can migrate it), Assisted (needs manual review + tooling), and Manual (must be rebuilt by hand in RCA).
2. Map CPQ Objects to Revenue Cloud objects:
This mapping becomes your migration blueprint and is the single most time-consuming but important step.
3. Migrate product catalog & pricing first:
Move core product catalog, attributes, bundles, and price books into RCA’s catalog structure before touching transactional data. Rebuild complex price rules as Pricing Procedures/Decision Tables rather than trying to force a 1:1 copy — RCA’s pricing engine works differently, so this is usually a redesign, not a lift-and-shift.
4. Run a proof of concept on your hardest scenario:
Pick your most complex pricing/configuration scenario (not the simplest one) and rebuild it end-to-end in a scratch or sandbox org. If your hardest case works, the rest of the catalog is largely solvable. This step catches architectural gaps early, before they surface mid-rollout.
5. Migrate historical & transactional data:
Extract historical quotes, orders, contracts, and active subscriptions from CPQ. Convert active subscriptions into RCA Assets so they can be managed going forward (renewals, amendments, usage). Decide what history needs to be live in RCA vs. what can stay archived/read-only in the legacy org — migrating every historical quote is rarely necessary.
6. Pilot with a subset of customers:
Run RCA live for a limited group of customers or a single business unit while CPQ stays in read-only mode for everyone else. Run parallel regression testing across both systems, track quote turnaround time and error rates, and set clear go/no-go criteria before expanding further.
7. Full rollout, cutover & decommission CPQ:
Expand to all customers in phases rather than a single big-bang cutover. Give the team time to stabilize on RCA before layering in anything extra, like Agentforce automation.
The bottom line
CPQ isn’t going away, and there’s no need to panic-migrate if it’s working for you. But if you’re evaluating a new implementation, or your pricing and billing needs have outgrown what CPQ was designed for, RCA is where Salesforce’s investment — and the ecosystem — is headed.
The migration itself is very doable, but it rewards patience: assess thoroughly, pilot with your hardest scenario first, roll out in phases, and give your team time to stabilize before adding anything new on top.
Ready to take the next step?
Stretch Customer can help you assess your current setup, identify the right solution, and build a practical roadmap for Salesforce CPQ or Revenue Cloud Advanced.
Contact us for an initial conversation about your needs and how we can help.