Migration guide

    Revenue Cloud can wait five minutes while you find the quote history

    A Salesforce CPQ migration starts with the product, price and quote data you still need, and a decision on whether Revenue Cloud or another CPQ is the destination. Inventory catalogues and quote history, map them, run both in parallel, then cut over. Check Salesforce’s current CPQ status before you set a date. Platforms like Rig handle that mapping and cutover.

    By Toby Mather · Published

    Key takeaways

    • Salesforce says CPQ is end of sale, with no end-of-life date announced, and existing customers can keep using it, add users, renew and get support.
    • There is no forced migration, so set the date by your own quote-to-cash needs and contract terms.
    • Scope three things first: the product catalogue, the price rules and the quote and subscription history.
    • Revenue Cloud covers pricing, quoting, contracting and billing on one data model, and moving to it involves redesigning the process as well as mapping data.
    • Reporting on bookings, renewals and discounting needs the old quote history to stay queryable after the move.
    1. 01Salesforce CPQ

      Products, price rules, quotes, subscriptions

    2. 02Inventory catalogues and quotes

      Plus the flows and reports that read them

    3. 03Revenue Cloud or another CPQ

      Process redesigned, data mapped

    4. 04Parallel run and cutover

      Quote totals and dates compared

    Salesforce CPQ data moves to Revenue Cloud or another CPQ, with a parallel run.

    Is Salesforce CPQ at end of life?

    Salesforce’s own explanation says CPQ is end of sale and that it has not announced an end-of-life date. It no longer sells new CPQ licences to new customers, and CPQ is in a maintenance phase without new feature development. Existing customers can continue using it, buy more users, renew licences and receive support, and Salesforce states there is no forced migration to Revenue Cloud. Its investment has moved to Revenue Cloud Advanced. Check the page again before you plan, because the status can change.

    What is in scope?

    Most CPQ estates have grown for years, with custom fields on quote lines, price rules that reference other price rules, and flows that fire on quote approval. Map the dependencies before you map the data. One education software company we worked with planned to switch off a large share of its custom Salesforce fields, and Rig mapped every field and the rules, flows and views that read it, on read-only access, so the cleanup could run in a safe order.

    • Products, bundles, features and options.
    • Price books, price rules, discount schedules and product rules.
    • Quotes, quote lines, approvals and quote templates.
    • Contracts, subscriptions, amendments and renewals.
    • Flows, validation rules, reports and integrations that read CPQ objects.
    • Billing and order handoffs downstream.

    Revenue Cloud or another CPQ?

    Revenue Cloud is Salesforce’s successor, and Salesforce describes it as unifying pricing, quoting, contracting and billing on a single data model. Its data model differs from CPQ’s managed package, so the move includes redesigning the configuration and pricing logic. Some teams choose another CPQ that integrates with Salesforce, and some stay on CPQ for now while they clean up. Whichever you pick, the inventory and the quote history work are the same.

    What is the migration plan?

    Split the work by product line or region.

    1. Inventory products, price rules, quotes, subscriptions and the flows, reports and integrations that depend on them.
    2. Agree the destination, and who owns product configuration and pricing rules during and after the move.
    3. Map catalogues, prices and open subscriptions to the destination, and decide where closed quote history will live.
    4. Run new sales, amendments, renewals and cancellations through both systems in a sandbox and compare quote totals and subscription dates.
    5. Cut over when sales operations and finance sign off, then switch off CPQ automation and keep the history reportable.

    What does reporting need afterwards?

    Bookings, renewal and discount reports reach back years. If the old quotes and subscriptions stay only in CPQ objects you plan to retire, those reports stop working. Load the quote and subscription history in the warehouse with the new system’s data, define bookings and renewals once, and the board pack keeps its trend lines.

    CPQ migration checklist

    Use these as the exit checks for each wave.

    • Current CPQ status and your contract terms checked with Salesforce.
    • Dependencies mapped for every CPQ object and field.
    • Owner agreed for product configuration and pricing rules.
    • Catalogues, prices and open subscriptions mapped and reviewed.
    • Quote totals and subscription dates match in sandbox tests.
    • Approvals, orders and billing handoffs tested end to end.
    • Quote history reportable in the warehouse or the new system.

    Where does Rig fit?

    Rig is an AI-native data and systems integrator. Salesforce implementation partners run most Revenue Cloud programmes, and Salesforce’s own help covers the product. Platforms like Rig handle the mapping, parallel run and cutover of that commercial data, and leave a governed semantic layer on the warehouse you already run.

    Rig Map traces the fields, flows and reports that depend on CPQ, Rig Migrate agrees a fixed delivery price after scoping, and Gateway controls who and which agents can query the history. The CPQ migration page describes the service.

    Tools and approaches

    Salesforce: CPQ end of sale explained
    Salesforce’s explanation of CPQ’s end-of-sale status, support for existing customers and the move to Revenue Cloud Advanced.
    Salesforce Revenue Cloud
    Salesforce’s product for pricing, quoting, contracting and billing on one data model.

    Common questions

    Is Salesforce CPQ at end of life?

    Salesforce says CPQ is end of sale and has not announced an end-of-life date. Existing customers can keep using it, add users, renew and receive support, and there is no forced migration. Check Salesforce’s current page before you plan.

    How do you migrate Salesforce CPQ to Revenue Cloud?

    Inventory products, price rules, quotes, subscriptions and their dependencies, redesign the configuration and pricing in Revenue Cloud, map the data, run sales, amendments and renewals through both in a sandbox, then cut over with finance and sales operations sign-off.

    What happens to quote history in a CPQ move?

    Decide where closed quotes and subscriptions will live, in the new system or in the warehouse, and reconcile them against CPQ. Reporting on bookings and renewals depends on that history staying queryable.

    Can we move to something other than Revenue Cloud?

    Yes. Some teams choose another CPQ that integrates with Salesforce, and some stay on CPQ while they clean up. The inventory and history work are the same either way.

    Who runs the mapping?

    Platforms like Rig handle mapping, parallel runs and cutover, and leave a governed semantic layer on the warehouse you already run. Salesforce partners also run these programmes.

    Sources

    Vendor documentation checked on 20 November 2026. Confirm current features and terms with the vendor.

    About the author

    Toby Mather, Co-founder and CEO, Rig. Toby co-founded Rig after seeing how hard it was for business teams and AI to work with complex internal data. He was previously co-founder and CEO of Lingumi and CPO at Novakid.

    Talk to Rig

    Check the migration before you commit to it

    An engineer sends a short written view of the scope, systems and risks, then offers a call to go through it.