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, until the migration assistant Salesforce has announced for December 2026 ships. A full rebuild runs 12–18 months in practice. Licenses are $150 or $200 per user per month. Here is the work, in order.
The short answer
- You expect the tools to do the migrationThey move catalog and price books; rules, scripts, integrations and templates are rebuilt by people.
- You read “3–6 months” on the marketing pageTreat it as a best case; full rebuilds run 12–18 months in practice.
- You want the successor anywayRationalize the catalog first; it is the longest pole.
What Salesforce itself says
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.
How long it takes, by source
Every source you will read gives a different number, because each measures something different. Side by side:
| Source | What it says | What it measures |
|---|---|---|
| Salesforce, end-of-sale page | A typical migration runs 3–6 months from discovery through go-live; complex implementations take longer. | Salesforce’s stated figure. Treat it as a best case. |
| Forsys, a Revenue Cloud partner | A manual CPQ migration typically runs about twelve months; its RevRamp tool claims 6–8 weeks for the data move. | The 6–8 weeks is one phase, not the program. |
| Workday’s CIO, Dreamforce 2026 keynote | Workday reimplemented Salesforce with Revenue Cloud in seven months with Accenture; such a transformation generally takes a year to 18 months. | Remarks on stage; no written case study. |
| Salesforce Help | Treat the migration as a redesign rather than a direct migration of existing configurations. | No duration given. |
| Our planning figure | A full rebuild runs 12–18 months in practice. | Catalog, pricing, configuration, templates, integrations, testing and training. |
Plan to the long figure, contract to a fixed date, and treat anything shorter as upside.
The steps
- 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).
- 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.
- 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).
- Choose a tool
Salesforce’s own migration assistant, announced at Dreamforce 2026, has a December 2026 target; check whether it has shipped and what it covers. Until then, Salesforce names Forsys RevRamp, IdeaHelix, and Prodly (source). Its Help page is explicit about what they cannot do: Apex and Quote Calculator Plugin logic, integrations, document templates, page layouts, permissions and custom fields all move by hand (Salesforce Help). Compare them in migration tools.
- 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.
- Re-point integrations and templates
ERP, billing, e-signature, and document generation all reference SBQQ objects today. Each needs the new object model.
- Pilot, then cut over
Run one business unit or product line first. Keep CPQ licensed until the last renewal has been processed in RCA.
Salesforce’s four migration paths and four rollout models
Salesforce’s CPQ Migration page (salesforce.com) gives the move a vocabulary worth adopting, because your implementation team and your executive sponsor will both use it. Four paths describe how much you change; four rollouts describe how you switch.
| Path | What it means | When it fits | Watch for |
|---|---|---|---|
| Lift and shift | Move the catalog, rules and data across with minimal redesign. | Small catalog, few rules, no QCP. | Salesforce’s own Help says to “treat your migration as a redesign rather than a direct migration” (Help); a true lift and shift is rare. |
| Selective transformation | Move most as-is; redesign the parts that hurt (pricing, bundles). | A working CPQ with two or three known problems. | Scope creep — every “while we are in there” adds weeks. |
| Full rationalization | Redesign catalog, pricing and process from first principles. | Catalog sprawl, legacy discounting, many integrations. | This is the 12–18 month project. |
| New BU or product line | Start RCA on something new; leave CPQ on the old book. | A launch that needs a different selling model. | Two systems of record until the old book is retired. |
| Rollout | What it means | When it fits |
|---|---|---|
| Big bang | Everyone switches on one date. | Small teams; one quote cycle of parallel run first. |
| Pilot-first | One team or region proves it, then the rest follow. | Most mid-market orgs. |
| Bridge | CPQ and RCA run together with a defined hand-off for some time. | Long contract terms; renewals must finish on CPQ. |
| Cohort-based | Segments move in waves. | Many business units or regions with different catalogs. |
Our phased migration and parallel run pages cover the same ground from the admin’s side, and apply to any destination.
What the marketing page says, and what the Help docs say
Read both before you plan. The CPQ Migration page offers “lift and shift” with minimal redesign (salesforce.com). The Help documentation for the same move says CPQ objects, fields, rules and scripts do not map directly, that the migration should be treated as a redesign, and that the partner tools cannot migrate Apex, Quote Calculator Plugin logic, integrations, document templates, layouts, permissions or custom fields (differences · tools). The Help version is the one to budget against. It runs to roughly forty pages — phases, org-complexity evaluation, strategy selection, architecture changes by domain, cutover planning, per-data-set procedures — and is the deepest first-party migration reference Salesforce publishes (Migrate to Revenue Management). It contains no cost figure and no object-by-object map; for those see RCA pricing and the object mapper.
What migrates automatically, with help, or by hand
Prodly’s founder, who built the original SteelBrick CPQ, sorts the work into three buckets in a public webinar (Prodly). Combined with Salesforce’s own list of what tools cannot do (Help), the picture is:
| Bucket | What falls in it | Who does the work |
|---|---|---|
| Automatic | Products, price book entries, bundle structure, product selling models. | The migration tool, with validation. |
| Assisted | Product rules (validation, selection), simple price rules, discount schedules, install base (subscriptions and assets consolidate into managed assets). | Tool proposes; an admin reviews and corrects. |
| By hand | Advanced discount schedules, complex price rules, Quote Calculator Plugin and Apex, integrations, quote document templates, page layouts, permission sets, custom fields. | Admin, developer or SI — this is where the months go. |
Historical transactions are the one thing every source agrees on: do not migrate closed quotes and orders; archive them read-only and migrate the active install base completely. Our quote and subscription data migration page has the cutoff rule and the reconciliation procedure. The object mapper now shows the bucket for every SBQQ object.
Running CPQ and RCA in one org
Salesforce documents a coexistence mode: the CPQ package and Revenue Cloud Advanced can run in the same org during the transition, with an RCA licence, and a feature matrix describes what works in each (Salesforce Help). Keep CPQ licensed until the last renewal has been processed on the new side; the parallel run procedure applies unchanged.
What it costs
Licenses are published: $150 per user per month for Revenue Cloud Growth (which already includes order management, subscription and asset lifecycle, advanced approvals, document generation and usage selling) and $200 for Advanced (adds Contract Lifecycle Management, Revenue Management Intelligence and Agentforce templates), billed annually, on an annual contract (Salesforce pricing). Invoicing needs Invoice Management (an add-on) or Revenue Cloud Billing, a separate, quote-only product. Implementation is not published; it is quoted per project. Our calculator estimates about $375,000 to implement a 50-user rebuild and $63,000 a year of admin; with the license at the midpoint of the $200 list and a discounted case, Revenue Cloud Advanced comes to about $897,000 over three years at 50 users. Each is an estimate: the midpoint of the low and high cases in our October 2026 competitor research. Salesforce Premier Success, with 24/7 support for business-stopping issues, is 30% of net license fees on the Enterprise edition.
Details on tiers and add-ons: Revenue Cloud Advanced pricing.
Questions to ask before you sign
- Will the migration assistant cover our org?
Salesforce announced it at Dreamforce 2026 with a December 2026 target. Ask whether it has shipped, whether it is included in your licence, and for the list of what it will not convert in your org.
- What will the implementer fix in price and date?
Ask your implementer (Salesforce Professional Services or a partner) for a fixed-fee, fixed-date statement of work covering catalog, pricing, configuration, templates, integrations and the install base.
- What is the all-in licence cost during the move?
CPQ and Revenue Cloud may both be licensed while renewals finish on CPQ. Ask what you pay for each, and for how long.
- Is Premier Success in the quote?
It is 30% of net licence fees on the Enterprise edition. Ask whether it is included, and on which licences it is calculated.
- Who owns pricing procedures and CML after go-live?
Name the person, and the training they need, before the project starts.
- Who has done this at our size?
Ask for two customers your size live on Revenue Cloud, with their go-live dates.
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.
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.
Not as of November 2026. Salesforce announced a migration assistant for the CPQ managed package, configuration included, at Dreamforce 2026 with a December 2026 target (Salesforce+), and has not published what it will leave behind or how it is licensed. Until it ships, Salesforce names partner tools from Forsys, IdeaHelix and Prodly (Salesforce).
$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 per project. See RCA pricing, explained.
Salesforce (2026) 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 or hybrid platforms such as DealHub or Nue are also options. Overview: migration hub.
How long would yours take?
Readiness check
Twelve questions about your catalog, pricing logic, approvals and integrations. Returns a timeline range.
Take the check →Object mapper
Where every Salesforce CPQ, Conga, Revenue Cloud Advanced, DealHub and Nue object lands — and what has no equivalent.
Look up an object →3-year cost
Published prices where they exist, labelled estimates where they do not, at your user count.
Open the calculator →Nothing is submitted and no email is asked for — all three run in your browser. 135 public AppExchange reviews are on the reviews page.
See your migration plan
Published timelines by source platform, a fixed implementation fee, and a calculator that labels every estimate.