feature highlights
Metadata + CPQ data migration
Products
Price rules
Price books
Configuration data
Related records
Salesforce CPQ is highly interconnected: products, price books, pricing rules, bundles, and dependencies all rely on each other
why CPQ deployments are so difficult
Products, rules, or related records lose their connections after deployment, causing CPQ functionality to break
Broken references
Missing dependencies
Required components are often skipped or deployed in the wrong order, resulting in incomplete configurations
Metadata alone is not enough for CPQ, since critical configuration data also needs to be migrated together
Incomplete migrations
Unexpected fixes
Teams frequently have to reconnect records manually, recreate data, or troubleshoot issues manually after deployment
Identify corresponding records even when they were created separately in different environments
match existing records across orgs
One of the biggest CPQ migration challenges is record ID mismatch between environments.
For example, after cloning a sandbox from production, records may later diverge or be recreated independently. Standard deployment tools rely heavily on Salesforce IDs, which often leads to broken references, duplicate records, and deployment inconsistencies.
For example, after cloning a sandbox from production, records may later diverge or be recreated independently. Standard deployment tools rely heavily on Salesforce IDs, which often leads to broken references, duplicate records, and deployment inconsistencies.
The challenge
mtdt solves this with intelligent record matching.
Instead of relying only on record IDs, mtdt matches existing CPQ records across orgs using business logic and relationship-aware comparison. This allows the platform to correctly identify corresponding records even when they were created separately in different environments.
Instead of relying only on record IDs, mtdt matches existing CPQ records across orgs using business logic and relationship-aware comparison. This allows the platform to correctly identify corresponding records even when they were created separately in different environments.
The solution
Automatic dependency handling
mtdt automatically detects and deploys dependencies in the correct order, ensuring migration completeness and consistency
Relationship preservation
All relationships between records stay intact, so everything continues to work correctly after deployment without broken references or the need to reconnect records manually
what mtdt handles automatically
Predictable deployments
Reduce manual work and make CPQ deployments significantly more reliable and repeatable across environments
Common CPQ migration scenarios
use cases
Promote CPQ changes safely and consistently into production
Sandbox → Production Deployments
Multi-Org Replication
Replicate CPQ setups across multiple Salesforce orgs with minimal manual effort
Create reliable backups of CPQ configurations and restore them when needed
Backup & Restore
Environment Synchronization
Keep CPQ configurations aligned across development, QA, staging, and production orgs
contact us
Have questions? We’re here to help!