Migrate Salesforce CPQ data without breaking lookups
Salesforce CPQ has a complex object hierarchy. Price Books, Products, Pricebook Entries, Price Rules, Discount Schedules — each depends on the previous. SwiftPort migrates them in the correct dependency order automatically, with full field mapping and deduplication.
Ordered
Dependency-aware
No code
Visual builder
Re-runnable
Save & reuse
CPQ objects SwiftPort can migrate
Standard CPQ objects and any custom objects in your org. The template pre-populates the common ones — you adjust for your specific configuration.
Products
SBQQ__Product2__c
Base product catalog with CPQ-specific attributes
Standard Products
Product2
Salesforce standard Product2 records referenced by CPQ
Price Books
Pricebook2
Standard and custom price books
Pricebook Entries
PricebookEntry
Product-to-pricebook relationships with unit prices
Price Rules
SBQQ__PriceRule__c
Conditional pricing logic applied during quoting
Price Actions
SBQQ__PriceAction__c
Actions triggered by Price Rules
Discount Schedules
SBQQ__DiscountSchedule__c
Volume and partner discount structures
Subscription Pricing
SBQQ__SubscriptionPricing__c
Recurring pricing configurations
Plus any custom CPQ-related objects in your org — SwiftPort fetches your full schema.
Why CPQ migrations are hard — and how SwiftPort helps
CPQ has more interdependencies than almost any other Salesforce product. Most migration tools don't account for this.
Dependency ordering is critical
CPQ data has strict parent-child relationships. Price Book Entries depend on both Price Books and Products. Discount Schedules reference Products. If you migrate in the wrong order, lookups break and records fail to insert. SwiftPort's migration engine handles this automatically.
Field mapping between environments
Your sandbox and production orgs may have different field configurations, custom fields at different API versions, or picklist values that don't match. SwiftPort's field mapper shows you every field from both sides and flags type mismatches before you run.
No duplicates on re-run
CPQ migrations often need to be run multiple times — once to test, once to go live, once for incremental updates. SwiftPort's match strategy links existing records by a field like Product Code or External ID so re-runs update records instead of creating duplicates.
Critical-fail chain stops execution
If Price Book migration fails, SwiftPort stops the chain. It won't attempt to migrate Pricebook Entries that would reference non-existent Price Books and flood your logs with meaningless errors.
When to use CPQ migrations
Production → Sandbox refresh
Your sandbox's CPQ configuration has drifted from production. Push the full product catalog, price books, and pricing rules from production into sandbox to get a realistic testing environment.
Org consolidation after acquisition
Two companies merge, each with their own Salesforce CPQ setup. Migrate one org's product catalog into the other, mapping fields to the surviving schema.
Dev → UAT → Production promotion
New products and pricing are configured in a dev org. Promote that configuration up the chain — dev to UAT, UAT to production — using the same saved migration job.
CPQ implementation migration
Migrating from a legacy quoting system to Salesforce CPQ. Use SwiftPort to bulk-load your product catalog and pricing structures into the new org.
How it works
Select CPQ template
Choose the CPQ migration template when creating a new job. It pre-populates the recommended object order and common field mappings.
Review and adjust object order
The template orders objects by dependency. You can add, remove, or reorder steps based on what's in your specific org.
Configure field mappings per step
Each object step has independent field mapping. Auto-map handles name-matching fields; you handle schema differences manually.
Set match strategies
For each object, define how SwiftPort identifies existing records. Typically Product Code for Products, Name for Price Books.
Add filters if needed
Optionally scope each step — e.g. only active products, only custom price books, only non-expired discount schedules.
Review AI warnings
SwiftPort flags required fields that are unmapped, type mismatches, and picklist values that exist in source but not target.
Run and monitor
Execute the job. Each step runs in sequence. View per-step progress, per-record results, and full error details in the run history.
Also using Revenue Cloud Accelerator?
SwiftPort also has an RCA migration mode for Revenue Cloud (formerly Billing) objects. Same dependency-aware engine, pre-built templates for RCA object hierarchies.
Ready to migrate your CPQ data?
Start free. Connect your orgs and build your CPQ migration job in minutes.