CPQ to Revenue Cloud Migration
Salesforce CPQ rebuilt on Salesforce Revenue Cloud by architects who know what each construct was built to do
Two decades of Salesforce Quote to Cash, now on Revenue Cloud
Our architects know what each Salesforce CPQ construct was built to do and how to rebuild it on Revenue Cloud.
What Salesforce CPQ end of sale means
Salesforce's end-of-sale announcement sets no deadline, so the timing of a move is a business decision.
End of sale, not end of life
Salesforce CPQ is no longer sold to new customers; existing customers retain licenses and support, with no forced migration.
A re-implementation, not an upgrade
The data models differ significantly; catalog, pricing, configuration and install base are rebuilt on the standard data model.
Coexistence has limits
Both products can run in one org. Salesforce Billing is the billing product for Salesforce CPQ and depends on it; Revenue Cloud Billing is Revenue Cloud's own.
Migration paths and rollout options
How Acellas consultants run a CPQ to Revenue Cloud migration
Pricing, configuration and data in detail
CPQ Price Rule Migration
Price rules, product rules and the Quote Calculator Plugin rebuilt as pricing procedures, decision tables and constraint models.
CPQ Data Migration
Contracts and subscriptions carried across with their amendment history intact.
Platform decisions and Salesforce CPQ migrations led by Acellas
Netskope: Quote to Cash Assessment
22 Quote to Cash complexities mapped to inform the platform decision
Viewpoint Construction Software: Revenue Cloud
From 4,085 legacy items to one governed quoting catalog
Trimble: Billing and Revenue Recognition
165,764 legacy subscriptions realigned for billing and revenue recognition
Questions about CPQ to Revenue Cloud migration
Is Salesforce CPQ end of life?
No. Salesforce CPQ is end of sale, not end of life: Salesforce no longer sells it to new customers and has announced no end-of-life date. Existing customers keep their licenses and support, and no migration is forced, so the real question is when a move to Revenue Cloud serves the business.
Should we migrate from Salesforce CPQ now or wait?
Migrate when a business need calls for Revenue Cloud, not because of a deadline: usage or hybrid pricing, a catalog redesign, billing on the platform, or agents that need one data model. If none applies yet, Salesforce CPQ keeps working, although taking an inventory of rules and dependencies now makes the later decision clearer.
Can we run Salesforce CPQ and Revenue Cloud at the same time?
Yes. Both products can run in one org, and a pilot or cohort-by-cohort rollout lets each group move when it is ready. Billing needs the most care, because each product has its own: Salesforce Billing works with Salesforce CPQ, and Revenue Cloud Billing works with Revenue Cloud. Salesforce Billing depends on Salesforce CPQ, which must be installed before or alongside it. Where Salesforce Billing is already active without CPQ, or CPQ must be upgraded or reinstalled in a live org with billing in use, our consultants follow safe procedures that prevent data corruption and validation rule failures.
Questions on scope and data
What is the difference between Salesforce CPQ and Revenue Cloud?
Salesforce CPQ is a managed package with its own objects; Revenue Cloud runs on the standard Salesforce data model, with an attribute-based catalog, pricing procedures, decision tables and constraint models. Assets with state periods record what each customer owns, and order orchestration, usage rating and billing share the same data.
Does anything migrate from Salesforce CPQ automatically?
No. Nothing in the Salesforce CPQ pricing and configuration layer ports automatically. Price rules, product rules, discount schedules and twin fields each need a redesign or a rebuild, and contracts and subscriptions move through a planned data migration rather than a copy. That is why our architects begin every migration with an inventory of what the org holds.
What happens to renewals that are in flight during the migration?
In-flight renewals continue through the move. Our team sequences open quotes, renewal opportunities and co-termed contracts so no renewal is lost or duplicated, and each subscription and its amendments become an asset with state periods. Before go-live, our team runs renewals and amendments through the interface in test cycles.
Plan your CPQ to Revenue Cloud migration
Talk with the architects who would lead the work.