You are here:
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.
Core Differences between Salesforce CPQ and Revenue Management
In Salesforce CPQ, bundles are defined strictly through product options and product features. Revenue Management builds bundles using a hierarchy of components.
| Element | Salesforce CPQ | Revenue Management |
|---|---|---|
| Structure | A parent product is related to child products through Product Option records. | A bundle is defined by its structure. You add product related components, which can be specific products or product classifications. |
| Grouping | Options are grouped visually using product features. For example, Hardware, Software. | Components are organized into product component groups. |
| Dynamics | To create dynamic bundles, you must use Filter Product Rules to query specific fields on the Product object. | You can add a product classification component to a bundle. The bundle automatically includes all products tagged with that classification, eliminating the need for complex filter rules. |
| Logic | Product rules, such as Selection, Validation, and Alert, control which options can be selected. | Configuration rules are managed through the Business Rules Engine or Constraint Rules Engine to handle exclusion, requirements, and validation. |
Migration Mapping
Use this table to map your existing Salesforce CPQ bundle elements to Revenue Management structures.
| Salesforce CPQ Configuration | Revenue Management Equivalent | Migration Logic |
|---|---|---|
| Product Option record | Product Related Component record | Migrate individual option records to Product Related Component records. Define cardinality directly on the component relationship. |
| Product Feature record | Product Component Group record | Features translate to component groups. See Add Components to a Configurable Product Bundle. |
| Dynamic Bundle or Filter Rule | Product Classification Component record | Instead of creating a rule to filter products, associate products with a classification and add that classification as a single component to the bundle. See Create a Product Classification. |
| Option Constraints | Constraint Rules Engine or Business Rules Engine | Use Constraint Rules Engine for large and complex product configuration rules and constraints. Use Business Rules Engine for simple product configuration rules. See Configure Your Products in Revenue Management. |
| Configuration Attribute | Product Attribute | Attributes are defined at the catalog level and inherited by the bundle or specific components. See Manage Dynamic Attributes in Revenue Management. |
After you understand about product structures and attributes, and product bundles in Revenue Management, learn about product selling models before you migrate product data.
