How to replace a legacy CPQ system without a year-long project
The common mistake in a CPQ replacement is treating it like the original implementation, a year-long workshop-driven rule rebuild. The right approach is parallel-run: extract the existing product schema, reimplement one product family in the new system in under three weeks, run both systems side by side for a quarter while quote quality is verified, then cut over. With AI-native CPQ, this approach compresses a typical 12-month replacement into roughly 8 to 12 weeks.
Step 1: extract instead of rebuild
Your existing CPQ already contains the product schema, so do not reinvent it. Export what you can:
- Salesforce CPQ: use the Product2 and PricebookEntry tables, plus the Product Option and Configuration Attribute objects
- Oracle CPQ: export BML scripts and the data dictionary; the schema is in the Product Admin area
- Tacton: export the constraint model as an .sta file; rules are in the constraint-based modeling language
- SAP CPQ: export from the Quote and Product Catalog modules
Step 2: load the new system, in a slice
Do not try to migrate the whole catalog at once. Pick the simplest product family that still exercises real rule complexity (typically 10 to 30 SKUs with 5 to 15 constraint types). In Sailsrep, upload the extracted pricelist and rules, and the system drafts a schema you approve in hours.
Get this family to a working end-to-end quote in the new system before touching the next one.
Step 3: parallel-run for a quarter
Run both systems for 90 days. Every quote generated in the legacy system is also generated in the new system and compared. This surfaces rule discrepancies cheaply: if the two systems disagree, one of them is wrong, and you have a ticket.
Parallel-run is what turns a scary migration into a routine one, and it only works if the new model is legible; how Sailsrep works describes the model both systems are compared against. Skipping it is the single biggest reason CPQ replacements fail.
Step 4: cut over one family at a time
Do not flip the whole catalog on one day. Migrate one product family per sprint. Sales teams learn the new UI incrementally, the help desk is not overwhelmed, and rollback per family is trivial.
A realistic replacement timeline for a mid-market B2B with 5 product families: 2 weeks for slice one, 8 weeks for parallel-run, 4 weeks to migrate the remaining families. The CPQ buyer's guide puts that timeline next to what the alternatives cost. Total: roughly 14 weeks. Legacy-to-legacy replacements routinely take 12 to 18 months.
Frequently asked questions
Do I need to keep my legacy CPQ running during migration?
Yes, for at least a quarter. Parallel-run is how you prove the new system produces the same quotes as the old one. Cutting over without parallel-run is the single most common cause of failed CPQ replacements.
What if my legacy CPQ has thousands of BML rules?
Extract them, feed them to the new system, and let AI-assisted schema building draft a structured equivalent. You review and approve the draft. This is vastly faster than hand-translating BML into a new language, which is what legacy-to-legacy migrations require.
Can I migrate off Salesforce CPQ without leaving Salesforce CRM?
Yes. Sailsrep works alongside Salesforce CRM via API. You keep your accounts, opportunities, and pipeline in Salesforce and run configuration and quoting in Sailsrep.
What data is hardest to migrate?
Pricing waterfalls and approval workflows. Product structure and basic rules migrate cleanly; multi-level discount approval chains and volume-tier pricing edge cases are the parts that need careful verification during parallel-run.