Guide

Salesforce CPQ to Revenue Cloud Advanced migration: what it involves

Revenue Cloud Advanced is built on core Salesforce objects with a different data model from the SBQQ package. Salesforce says CPQ-specific objects, rules, and scripts “don’t map directly” and that there is no first-party tool — only partner accelerators. A full rebuild runs 12–18 months in practice. Licenses are $150 or $200 per user per month. Here is the work, in order.

Open the ROI calculator →
12–18 mo
Full rebuild, in practice
$150–$200
Per user per month
~15%
Of RCA customers came from CPQ
0
First-party migration tools

What Salesforce itself says

From Salesforce’s end-of-sale page: “A typical migration runs 3–6 months from discovery through go-live, but complex implementations with extensive custom logic, large product catalogs, and multiple integrations can take longer.” Treat that 3–6 months as a best case; a full rebuild runs 12–18 months in practice. And: CPQ-specific objects, custom fields, pricing rules, and scripts “don’t map directly — a structured migration and data transformation process is required.” Source: salesforce.com.

Salesforce also publishes a side-by-side of the two architectures: CPQ is a managed package with SKU-based bundles, price rules and Quote Calculator Plugin scripts, a rules-based configurator, and a Subscription custom object; RCA is native to core with an attribute-based catalog, declarative pricing procedures, a constraint-based configurator, and asset-based amendments and renewals. Every one of those rows is a rebuild.

The steps

  1. Assess the current implementation

    Inventory products, bundles, price rules, discount schedules, QCP and Apex scripts, quote templates, approval chains, and integrations. Salesforce’s advice is to identify where CPQ creates friction before deciding timing and approach (source).

  2. Rationalize the catalog

    RCA uses an attribute-based catalog rather than SKU-based bundles. Most teams collapse SKU variants into attributes. This is design work, not data loading.

  3. Rebuild pricing as procedures

    Price rules, discount schedules, and QCP scripts become declarative pricing procedures and elements. Advanced discount schedules and price rules need manual handling even with partner tooling (Prodly).

  4. Choose a tool and a partner

    Salesforce names Forsys RevRamp, IdeaHelix, and Prodly, and says they “work best when paired with a certified Salesforce partner” (source). Compare them in migration tools.

  5. Migrate the install base

    SBQQ Subscriptions and Contracts become RCA assets; renewals and amendments become asset-based. Test a renewal end to end before cutover.

  6. Re-point integrations and templates

    ERP, billing, e-signature, and document generation all reference SBQQ objects today. Each needs the new object model.

  7. Pilot, then cut over

    Run one business unit or product line first. Keep CPQ licensed until the last renewal has been processed in RCA.

What it costs

Licenses are published: $150 per user per month for Revenue Cloud Growth (quoting and configurator, order capture, subscriptions) and $200 for Advanced (adds contracts and orders, consumption and invoicing, AI and analytics), billed annually, on an annual contract (Salesforce pricing). Implementation is not published; it is scoped by the partner. Our calculator uses a labeled estimate for a 50-user SI-led rebuild. Salesforce Premier Success is listed at 30% of net license fees if you want expedited support.

Details on tiers and add-ons: Revenue Cloud Advanced pricing.

The alternative path

Because RCA is a re-implementation either way, some teams use the moment to compare it against a Salesforce-native CPQ that keeps standard Products and Price Books. Kugamon migrates from SBQQ in 4–8 weeks at $65 per user per month; the playbook shows what moves. Neutral comparison of the two Salesforce products: Salesforce CPQ vs Revenue Cloud Advanced. What RCA actually is: explainer on kugamon.com.

Common questions

CPQ to Revenue Cloud — FAQ

All migration questions →

No. Salesforce describes different architectures: CPQ is a managed package, RCA is native to the core platform with a new data model. CPQ objects, rules, and scripts do not map directly (Salesforce). It is a migration with data transformation.

a full rebuild runs 12–18 months in practice (source). Forsys claims 6–8 weeks for the data-transformation portion with its RevRamp tool (Forsys); that is a vendor claim about one phase, not the whole program.

$150 per user per month for Growth and $200 for Advanced, billed annually on an annual contract, per Salesforce’s pricing page. It is a paid add-on to Sales Cloud. Implementation is quoted by partners. See RCA pricing, explained.

Salesforce says approximately 15% of Revenue Cloud Advanced customers migrated from Salesforce CPQ (source). It does not publish the absolute number.

Yes. There is no forced migration. Salesforce-native alternatives such as Kugamon keep your standard Products and Price Books and typically migrate in 4–8 weeks (playbook); external platforms such as DealHub or Nue are also options. Overview: migration hub.

Next step

See your migration plan

Published timelines by source platform, a fixed implementation fee, and a calculator that labels every estimate.

Open the migration checklist →