You are here:
Transactional Data Migration Scope and Approaches
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.
- Determine Your Data Migration Scope
One of the most strategic decisions in data migration is determining scope. More data isn't always better. - Compare Transactional Data Migration Approaches
Compare four ways to handle transactional data at go-live to weigh simplicity and speed against dual-system work, ongoing effort, and unified reporting. - Architecture Changes and Technical Considerations
The migration from Salesforce CPQ to Revenue Management is an architectural shift. The migration team, including architects, functional leads, and business owners, should understand the data model changes and its impact on contracts, orders, assets, and integrations. Review these system architecture changes and technical considerations to plan your migration, avoid common issues, and ensure data integrity across all components. - Automation Scope for Data Components
Use this table to understand the level of automation for each data component during migration, and the data component that requires manual effort or expert review.

