Operational Considerations

Before any migration work begins, review the operational and licensing considerations. These are not design decisions but practical requirements that apply regardless of your migration strategy. We recommend that the migration project lead, Salesforce admin, and IT or licensing owner review these considerations before any configuration or migration activity starts.

• Retain at Least One Active Salesforce CPQ License
  Retain at least one active CPQ license throughout the entire migration period in both production and any sandbox where Revenue Management is being configured or tested. Retaining the CPQ license ensures that the team can reference, validate against, or roll back to CPQ data when needed.
• Determine Your Deployment Model and Org Strategy
  Where you deploy Revenue Management is part of the broader Salesforce platform strategy of your company, not just a migration decision. Many companies run multiple Salesforce clouds, including Sales Cloud, Service Cloud, Experience Cloud, and Field Service. Determine the Salesforce org in which you want Revenue Management to deploy within that wider context rather than in isolation. If your company has a defined Salesforce org strategy, such as a plan to consolidate clouds into a single org or a deliberate multi-org model by region or business unit, align the Revenue Management deployment decision to that strategy. Involve your Salesforce account executive and platform architect early in this conversation, as the decision has implications beyond the migration from CPQ to Revenue Management.
• Managing Coexistence During the Transition Period
  Regardless of whether you choose to use the same org or a new org, there will be a period during which CPQ and Revenue Management are both in active use. This is expected, but it requires deliberate planning.