CPQ to Revenue Cloud: How to Plan Your Migration
What changes, a six-step migration plan, and the pitfalls we see most.
Why plan now
Salesforce CPQ is end of sale, not end of life. Since March 2025, Salesforce no longer sells CPQ to new customers. Existing customers can keep using it, add users, renew licenses, and still get support and critical fixes.
What has stopped is new feature work. Salesforce is putting that into Revenue Cloud Advanced (RCA) and Revenue Cloud Billing, which it now markets as Agentforce Revenue Management. You will still see "Revenue Cloud" in the app and in the documentation.
There is no forced migration date. But every new price rule, script or workaround you add to CPQ today makes the eventual move bigger. Planning now lets you migrate on your schedule, with a cleaner catalog, instead of under pressure later.
What actually changes
Revenue Cloud Advanced is not CPQ with a new name. It is rebuilt on the core Salesforce platform, so most CPQ designs need to be rethought rather than copied.
- Architecture: Salesforce CPQ uses managed package, quote-centric; Revenue Cloud Advanced uses native to core Salesforce, API-first and composable.
- Product catalog: Salesforce CPQ uses sKU-based bundles and options; Revenue Cloud Advanced uses attribute-based catalog.
- Pricing: Salesforce CPQ uses price rules plus custom scripts (QCP); Revenue Cloud Advanced uses declarative pricing procedures.
- Configuration: Salesforce CPQ uses rules-based; Revenue Cloud Advanced uses constraint-based.
- Revenue models: Salesforce CPQ uses one-time and subscription, limited usage; Revenue Cloud Advanced uses one-time, subscription, usage and hybrid.
- Subscriptions: Salesforce CPQ uses subscription records, contract-based changes; Revenue Cloud Advanced uses asset-based amendments, renewals and cancellations.
- Channels: Salesforce CPQ uses mainly direct sales; Revenue Cloud Advanced uses direct, partner, ecommerce and self-service through APIs.
Billing is a separate product. Revenue Cloud Billing handles billing schedules, usage, invoicing and payments, and is usually paired with RCA.
Source: Salesforce, CPQ end of sale overview
A six-step migration plan
Salesforce puts a typical migration at 3 to 6 months, and longer for complex orgs. These six steps keep that timeline realistic.
- Inventory what you have. List products, bundles, price rules, scripts, approvals, quote templates and integrations. Count live contracts and subscriptions, because those become your migration volume.
- Decide what to keep, simplify or retire. Most CPQ orgs carry years of one-off rules. Don't move anything nobody can explain.
- Redesign the catalog around attributes. Replace long SKU lists with products described by attributes, such as size, tier or region.
- Rebuild pricing declaratively. Pricing in RCA runs on context definitions, pricing procedures and decision tables. Map each business rule to these, not each old price rule.
- Migrate live subscriptions into assets. Amendments and renewals in RCA run on assets, so this step decides whether day-two changes work. Run trial loads and reconcile totals such as ARR before go-live.
- Roll out in phases. Go live by region, business unit, channel or selling model to limit risk. Then plan for a hypercare period with your support team.
Pitfalls we see most
- Copying CPQ one-to-one. Translating every price rule into a pricing procedure rebuilds your old technical debt on a new platform.
- Underestimating subscription migration. In-flight contracts with mid-term changes, ramps and co-terminated renewals take the most time to move cleanly.
- Forgetting what sits downstream. Billing, ERP, tax and ARR reporting all read from quotes and orders. Test them end to end, not just the quote.
- Treating it as an IT project. Sales, Finance and Legal need to own catalog and pricing decisions. Set up that governance before the build starts.
- Skipping rehearsals. Practice the cutover at least once with production-sized data before the real weekend.
Get a migration plan
Amwintech has spent more than 10 years on Salesforce quote-to-cash, with current certifications as a Revenue Management Consultant and CPQ Administrator. We can review your CPQ org and give you a phased migration plan. Book a free consultation.
Sources
- Salesforce: CPQ is end of sale, not end of life
- Trailhead: Configure pricing for products
- Trailhead: Get started with Billing
Salesforce, Revenue Cloud, Agentforce and Trailhead are trademarks of Salesforce, Inc.
Amwintech's Blog

