You are here:
Common Issues and Recommended Practices
This table describes issues that commonly arise during a transition from Salesforce CPQ to Revenue Management (formerly Revenue Cloud), along with the underlying causes and recommended practices for avoiding them.
| Issue | Cause | Recommended Practice |
|---|---|---|
| Approaching the project as a migration rather than a redesign | Teams focus on replicating Salesforce CPQ functionality instead of rethinking processes. | For each process, consider the purpose behind its current design before designing Revenue Management equivalents. |
| Skipping catalog rationalization | Teams underestimate product catalog bloat and defer rationalization. | Define the distinction between your commercial and technical product taxonomy before any technical configuration begins. |
| Migrating inactive pricing rules | Teams move Salesforce CPQ pricing rules that are inactive or redundant without review. | Audit all pricing rules during the assessment phase. Archive rules that no process actively enforces. |
| Underestimating Quote Calculation Plug-ins (QCP) complexity | Teams often poorly document QCP logic. QCP logic is invisible in pricing output. | Map every QCP to its business purpose by using AI explainability tools. Validate outputs by using a small set of quotes that cover a range of representative scenarios. |
| Ignoring data quality prerequisites | Inconsistent attribute naming, duplicate products, and orphaned records carry over into Revenue Management. | Invest in data quality remediation before migration begins. Run normalization passes on all attribute values. |
| Insufficient reporting redesign | After go-live, teams discover that they must recreate Salesforce CPQ reports built on custom objects for Revenue Management's data model | Identify critical reports before go-live. Rebuild them on Revenue Management objects in a sandbox and validate before cutover. |
| Underinvesting in change management and training | Technical teams focus on the system while end users aren't prepared until go-live. Migration teams underestimate the substantial architectural differences between CPQ and Revenue Management, assuming existing knowledge transfers directly. | Start end-user enablement well before go-live. Practical workshops that use real data are effective. Ensure all team members managing the migration complete foundational Revenue Management training before configuration begins. Ideally, have certified team members available for production maintenance. Revenue Management's architecture requires new mental models, not just UI familiarity. |
Did this article solve your issue?
Let us know so we can improve!
