Migrate to Agentforce Revenue Management

Revenue Management is a native platform that brings together your entire revenue lifecycle. Transitioning from Salesforce CPQ and Salesforce Billing to Agentforce Revenue Management requires updates to the system architecture that manages your revenue lifecycle. This architecture changes the way you model data, design business processes, and govern data.

This section covers the guidance for Salesforce CPQ and Salesforce Billing users who are planning to migrate to Agentforce Revenue Management with any of the licenses. It covers each phase of the migration journey, starting with understanding your current implementation and evaluating migration strategies, through to building readiness by addressing technical prerequisites, data migration, and integration requirements. This guidance makes sure that you can plan and execute a well-prepared transition.

• Get Ready to Migrate to Agentforce Revenue Management
  Revenue Management is a unified platform that enables companies to rethink how they manage the entire revenue lifecycle, from product catalogs to invoicing. It's not just the next version of Salesforce CPQ. Migrating to Revenue Management requires careful planning and a clear business case. This topic outlines Revenue Management capabilities to help your team assess where Revenue Management fits in your broader revenue strategy.
• Key Differences Between Revenue Management and Salesforce CPQ
  Before planning your migration, review the various aspects of Revenue Management and how this platform differs from Salesforce CPQ.
• Prepare to Migrate to Revenue Management
  A well-prepared migration team makes better decisions and avoids common pitfalls. Before you begin the migration to Revenue Management, assess your company's readiness in phases. Complete all the tasks of each phase in the mentioned sequence before moving to the next phase. There’s no set time frame. Progress at a pace that fits the business needs and complexity of your company.
• 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.
• Evaluate and Select a Migration Strategy
  There’s no single correct migration strategy. The right approach depends on what you found in your assessment in Phase 1, the risk tolerance of your company, and the scope of your future-state design. Use this section to translate your CPQ complexity profile into a strategy that fits your situation.
• Rollout and Cutover Strategy
  The way you sequence your go-live is as important as the way you design the solution. Make rollout strategy decisions early in the program. These decisions directly affect your data migration scope, integration design, cutover approach, and change management plan.
• Transactional Data Migration Scope and Strategy
  The data models between CPQ and Revenue Management differ significantly. Migrate object relationships, field mappings, and the business logic governing data validity in a structured manner.
• Reporting and Analytics After Migration
  CPQ and Revenue Management use different data models and different objects. Reports, dashboards, and analytics built on CPQ objects must be recreated by using Revenue Management's standard objects. Plan for this work early in your migration project to avoid surprises after go-live.
• Data Dependencies Based on Source System
  Data migration requirements for Revenue Management vary based on your source system and migration path. Before you migrate data, identify and document your migration path because each path carries unique data dependencies and field requirements.
• Migration Implementation Considerations
  Follow these deployment standards when migrating large volumes of historical records to ensure system stability and data accuracy.
• Migrate Product Data to Revenue Management
  Migrating your product catalog from Salesforce CPQ to Revenue Management is more than a data transfer. It's an architectural evolution from a metadata-heavy configuration to an attribute-driven model. By transitioning to Revenue Management, you can eliminate catalog bloat, simplify bundle maintenance, and decouple how a product is defined from how it is sold.
• Migrate Asset Data to Revenue Management
  Migrate existing asset data to Revenue Management by either generating assets from historical initial-sale orders, or by directly creating asset data. We recommend that you start by migrating orders so that a complete history of all the prior purchases is available in Revenue Management. Having this history enables accurate amendments, renewals, cancellations, and billing after the previous order system is decommissioned.
• Migrate Billing Data
  If you were using your legacy system for billing and want to preserve the full billing history in Agentforce Revenue Management, generate billing schedules and billing schedule groups for the previously billed periods in Agentforce Revenue Management.