Architecture Changes and Technical Considerations

The migration from Salesforce CPQ to Revenue Management is an architectural shift. The migration team, including architects, functional leads, and business owners, should understand the data model changes and its impact on contracts, orders, assets, and integrations. Review these system architecture changes and technical considerations to plan your migration, avoid common issues, and ensure data integrity across all components.

• Data Model Changes
  Salesforce CPQ uses custom objects whereas Revenue Management uses standard objects. This shift has several implications.
• Product Catalog Architecture Changes
  One of the key architectural decisions in the migration is the approach to the product catalog.
• Pricing Architecture Changes
  Pricing is one of the most architecturally significant differences between Salesforce CPQ and Revenue Management. If not explored early, it's one of the areas where complexity can emerge later. We recommend that the migration team develop a clear understanding of the pricing model changes, and its impact on configuration and migration before design decisions are finalized.
• Order Architecture Changes
  A key question that many customers consider is whether to rearchitect the modeling of orders in Revenue Management to better use new capabilities.
• Contracts Architecture Changes
  A key question that many customers explore is whether to rearchitect the modeling of contracts in Revenue Management to better use new capabilities.
• Dynamic Revenue Orchestrator as the Integration Orchestration Layer
  CPQ integrations are typically point-to-point, with direct connections from CPQ to an Enterprise Resource Planning (ERP) system, a billing system, or a provisioning platform. Each connection is independently maintained, monitored, and subject to breaking when there are changes. As part of the Revenue Management migration, treat the integration landscape as a dedicated workstream. Take the opportunity to rethink the architecture rather than just remap the connections.
• Billing Architecture Changes
  During migration, assess whether Billing in Revenue Management can replace a separate billing system or manual invoicing. Generate invoices for orders based on configuration in Revenue Management, rather than custom integrations to an external billing platform.
• Key Business Process Changes
  Based on pilot learnings and partner implementations, these themes represent the most common process changes that companies make during a Revenue Management migration.