CPQ to Revenue Cloud: How to Plan Your Migration

November 17, 2026

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.


  1. 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.
  2. Decide what to keep, simplify or retire. Most CPQ orgs carry years of one-off rules. Don't move anything nobody can explain.
  3. Redesign the catalog around attributes. Replace long SKU lists with products described by attributes, such as size, tier or region.
  4. 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.
  5. 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.
  6. 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, Revenue Cloud, Agentforce and Trailhead are trademarks of Salesforce, Inc.


Amwintech's Blog

By looka_production_187211612 • November 17, 2026
How pricing procedures, decision tables and billing schedules fit together.
By looka_production_187211612 • November 17, 2026
How assets work, and a go-live checklist for day-two changes.
March 10, 2025
Revenue Cloud Billing product from Salesforce provides the following key capabilities: Accounting Foundations: Allows the configuration of legal entities, accounting periods, and general ledger accounts to establish the necessary accounting framework. Provides "accounting awareness" by integrating the billing system with core financial processes. Flexible Product Configuration: Supports a wide range of product types, including subscriptions, one-time purchases, professional services, and usage-based offerings. Enables granular control over billing policies, tax configurations, and usage rating for these different product types. Automated Billing Workflows: Tracks customer purchases through billing schedule groups and schedules. Enables automated invoice generation on a scheduled basis (daily, weekly, monthly). Allows invoices to be produced and emailed directly from within the Salesforce platform. Accounting Integration: Generates the necessary journal entries and general ledger postings based on the invoices processed. Ensures tight alignment between the billing operations and the financial reporting. Revenue Cloud Advanced Billing product provides a comprehensive, Salesforce-native solution for managing complex billing requirements, from establishing the accounting foundations to automating the end-to-end billing process and integrating with financial systems Observations of a demo: I. Set Up Legal Entities and Accounting Foundations A. Configured legal entities - Legal entities represented different operating companies (e.g., US, Japan, Canada) in the system. - Each legal entity was able to have its own set of accounting periods, such as 445 model or monthly, allowing for flexibility. B. Established general ledger accounts - The system allowed for the setup of general ledger accounts within Salesforce, similar to an ERP system. - This provided the necessary "accounting awareness" for the billing system by setting up accounts for receivables, deferred revenue, cash, and other financial elements. II. Flexible Product Configuration A. Subscription-based products - Billing policies, such as advanced billing, was defined for subscription products. - Tax policy integration was also configured, with support for Avalara and Vertex tax providers. B. One-time/equipment products - The system was able to handle one-time purchases or equipment-related charges. C. Professional services products - Milestone-based billing for professional services, allowed for percentage-based or fixed-amount charges at defined project milestones. D. Usage-based products - The system provided the ability to configure usage grants, rate cards, and other parameters to handle consumption-based billing. - Validity terms, refresh policies, and rollover policies could be defined for usage-based offerings. III. Order Management and Billing Workflows A. Order creation and decoration - Orders could originate from various sources, such as Revenue Cloud Advanced or Commerce. - Billing details, including payment terms and legal entity, were added to the orders. B. Billing schedule groups and schedules - The system tracked customer purchases and created the necessary billing data in the form of billing schedule groups and schedules. - Detailed billing information was made accessible from the asset record. C. Automated invoice generation - Billing batch schedulers were set up to allow for scheduled invoice runs on a daily, weekly, or monthly basis. - Invoices could be generated and emailed directly from the customer account within Salesforce. IV. Accounting Integration A. Journal entries and general ledger postings - The system generated the necessary dual-entry accounting entries based on the invoices, ensuring accurate financial tracking and reporting. B. Aligning billing operations with financial reporting