You are here:
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 Products and Product Attributes to Revenue Management
When migrating from Salesforce CPQ to Revenue Management, understanding the way product structures and attributes are defined is critical for a successful transition. Product Catalog Management in Revenue Management enables you to consolidate your catalog while simplifying maintenance through an attribute-driven data model. - Migrate Product Bundles to Revenue Management
When migrating from Salesforce CPQ to Revenue Management, the fundamental concept of bundling, that is selling multiple items together as a single unit, remains. However, Revenue Management shifts configuration from a purely relationship-based model to a structured, component-based model that leverages product classifications for dynamic inclusion. - Migrate Product Selling Models to Revenue Management
When migrating from Salesforce CPQ to Revenue Management, the method for defining how a product is sold, such as one-time, subscription, or evergreen, changes significantly. Revenue Management uses product selling models, decoupling the selling method from the product definition. This shift allows a single Product record to support multiple selling strategies simultaneously, reducing catalog duplication. - Create Products and Price Book Entries
Before you migrate asset data, create Product and Price Book Entry records that the asset data references. Use the composite graph and sObject API to create these records.
Did this article solve your issue?
Let us know so we can improve!
