The timing still matters because Salesforce says a typical migration can run 3 to 6 months from discovery through go-live, with longer timelines for complex catalogs, custom logic, data issues, or multiple integrations. That makes early diagnostic work more useful than a rushed build. Salesforce's current help material also calls the destination Revenue Management, while many teams still use the Revenue Cloud name in planning and search.
Step 1: Run a readiness assessment before choosing a migration path
Start by documenting how a normal quote moves from product selection through price calculation, approvals, contract creation, renewals, billing handoffs, and connected systems. Then inventory the current CPQ org, including active products, old products, price rules, custom scripts, approval logic, quote templates, integrations, and historical data. A CPQ migration readiness assessment should show which elements are still required and which exist because the old system accumulated workarounds. The output should be a decision record rather than a raw configuration export, with each item marked for retention, redesign, retirement, archiving, or more testing. If the team can't explain the current process before building, it will be forced to discover business rules while configuring the new system.
Step 2: Treat catalog and pricing cleanup as design work
Product and pricing problems often look like migration defects even when they started years earlier in CPQ. Salesforce's common migration issues guidance identifies skipped catalog rationalization and inactive pricing rules as common transition issues, so copying configuration without review can preserve obsolete behavior. The evidence to collect should include duplicate SKUs, unused bundles, exception pricing, manual approvals, custom scripts, and product relationships. A rule can be technically valid while serving a business process that no longer exists. If the team can't explain why a rule should survive, it shouldn't move automatically.
Step 3: Map the new architecture instead of copying CPQ objects
Revenue Management uses a different architecture from the managed-package model behind Salesforce CPQ. The migration therefore needs a mapping between current business behavior and the destination model, covering products, prices, quotes, assets, orders, contracts, billing records, and connected data flows. A Salesforce CPQ migration partner is most useful when the internal team needs help separating current business requirements from legacy configuration. Teams should document what process replaces each important CPQ behavior, what changes for users, and which customizations can be retired. Finding a design gap here prevents the same issue from forcing later build and testing work.
Step 4: Choose the migration strategy from evidence
Salesforce documents 4 migration strategies for moving from CPQ to Revenue Management, with different tradeoffs around speed, business disruption, redesign, and access to Revenue Management capabilities. The strategy should follow the assessment findings rather than precede them. A simple org with low process debt may tolerate a closer recreation, while a heavily customized org may need selective redesign or a staged transition. This decision has a direct effect on CPQ to Revenue Cloud migration cost because scope grows when teams rebuild custom logic, clean catalog data, manage parallel systems, or rework integrations. Cost estimates should show the assumptions behind cleanup, data conversion, testing effort, user training, and cutover support so later changes can be traced.
Step 5: Map data dependencies before moving records
Historical assets, subscriptions, amendments, renewals, and billing history can carry dependencies that aren't obvious in a simple export. Salesforce warns that migration requirements differ according to the source system and selected path, and overlooking those differences can cause asset errors after migration. The team should define which historical records must remain operational, which can be archived, and how key relationships will be preserved. Testing should then confirm that an active customer can renew correctly, an amendment produces the expected commercial result, and downstream systems receive the values they need. If a migrated record exists but can't support the next transaction, the migration isn't functionally complete.
Step 6: Test integrations as business handoffs
ERP, billing, tax, e-signature, finance, and other connected systems can fail even when Revenue Management itself appears to work. MuleSoft's September 2025 migration guidance recommends mapping current integrations and deciding which should move first, while warning about the disruption created by big-bang replacement. Test each interface with normal cases and exception cases, then reconcile the result at the receiving system. The team should verify identifiers, converted values, timing, error handling, retry behavior, and ownership when a handoff fails. Integration testing is finished only when the business process reaches its intended downstream result.
Step 7: Set a cutover threshold before go-live
Go-live should depend on evidence collected during testing rather than a date that was chosen months earlier. Define pass criteria for pricing accuracy, approval behavior, renewal handling, asset integrity, billing handoffs, user acceptance, and rollback readiness. Revenue Cloud migration consulting becomes useful when the team can't produce a reliable dependency map, can't explain legacy pricing logic, or keeps finding defects across connected workstreams. Open defects should be classified by business impact so decision-makers can see which issues can wait and which could affect active revenue work. The threshold for action is simple: if you can't prove that the highest-risk quote-to-cash paths work before cutover, keep the system in validation.
Frequently asked questions
Does Salesforce CPQ end of sale mean we must migrate now?
No forced migration has been announced for existing Salesforce CPQ customers. Salesforce says current customers can continue renewing licenses and receiving support, while new product investment has moved toward Agentforce Revenue Management. The practical decision should therefore be based on business requirements, CPQ complexity, and the amount of change the current setup can still support.
How long does a CPQ to Revenue Cloud migration take?
Salesforce says a typical move may take about 3 to 6 months, though complex implementations can take longer. Catalog size, custom logic, integrations, data quality, and testing scope can all change the schedule. A readiness review should happen before the project team commits to a final date.
Can we use a lift-and-shift approach?
Salesforce includes a full migration or l
