You are here:
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.
Understand the specific data dependencies involved if you’re migrating from Salesforce CPQ or Salesforce Billing, or both.
| Migration Source | Migration Target | Data Dependencies |
|---|---|---|
| Salesforce CPQ | Revenue Management excluding Billing features | Focus on migrating historical asset data to support the amendment, renewal, and cancellation logic in Revenue Management. See Migrate Asset Data to Revenue Management. Typically, invoicing is handled through a manual finance process or a CPQ-to-ERP export. Moving to Revenue Management creates an opportunity to automate that process, going from a signed order to a posted invoice without manual intervention or external system dependencies. |
| Salesforce CPQ and Salesforce Billing | Revenue Management including Billing features | Apart from migrating historical asset data, this migration also requires a comprehensive migration of billing transaction history or an additional mapping for billing schedules to ensure accurate invoice generation in Revenue Management. See Migrate Asset Data to Revenue Management and Migrate Billing Data. |

