CPQ migration timeline: week by week, for every route
A CPQ migration is a sequence of five phases — discovery, catalog and pricing, quote and install-base data, integrations and documents, parallel run and cutover — and the length is set by three things: how much of your source data maps as-is, how much pricing logic lives in code, and how many integrations touch quotes. A CPQ-to-Revenue-Cloud-Advanced rebuild runs 12–18 months in practice. A move to Kugamon, which reuses standard Products and Price Books, typically runs 4–8 weeks from Salesforce CPQ and 4–10 weeks from other packages.
Typical lengths by route
- You are moving Salesforce CPQ to Revenue Cloud AdvancedPlan for 12–18 months for a full rebuild; longer with heavy custom logic, a large catalog or many integrations
- You are moving Salesforce CPQ to Kugamon4–8 weeks; Products and Price Books move as-is
- You are moving Conga, Nue or Subskribe to Kugamon6–10 weeks; the extra time is the Price List or external-catalog conversion
- You are moving DealHub or spreadsheets to Kugamon4–6 weeks; the catalog is small or already in Salesforce
The five phases
| Phase | What happens | What sets its length |
|---|---|---|
| 1. Discovery & scope | Inventory objects, rules, scripts, templates, integrations. Decide what is archived rather than migrated. | Number of active rules and integrations. |
| 2. Catalog & pricing | Move or rebuild products, bundles, price books, tiers, contracted prices. | Whether list prices are standard Price Book entries (move as-is) or vendor objects (convert). |
| 3. Quotes & install base | Migrate active subscriptions or assets; decide the quote-history cutoff. | Install-base volume and how clean the dates and quantities are. |
| 4. Integrations & documents | Re-point ERP, e-signature, billing; rebuild quote templates. | Count of systems that read or write quote objects. |
| 5. Parallel run & cutover | Reps quote in both; totals compared; then one cutover date. | One full quote cycle, usually 1–2 weeks. |
By route
| Route | Typical length | Long pole | Guide |
|---|---|---|---|
| Salesforce CPQ → Revenue Cloud Advanced | 12–18 months in practice | Re-expressing SBQQ rules and scripts as pricing procedures; new data model. | Guide |
| Salesforce CPQ → Kugamon | 4–8 weeks | Bundle and subscription mapping. | Playbook |
| Revenue Cloud Advanced → Kugamon | 4–8 weeks | Asset-to-subscription mapping. | Playbook |
| Conga CPQ → Kugamon | 6–10 weeks | Price List to Price Book conversion. | Playbook |
| DealHub → Kugamon | 4–6 weeks | Exporting the authoritative quotes from DealHub. | Playbook |
| Nue / Subskribe → Kugamon | 6–10 weeks | External catalog and subscription export. | Nue · Subskribe |
| Spreadsheets → Kugamon | 3–6 weeks | Deciding the catalog structure for the first time. | Playbook |
The three things that set the length
- How much maps as-is. Standard
Product2andPricebookEntryrecords move unchanged to any destination that reads Price Books. Vendor pricing objects (Conga Price Lists, DealHub or Nue catalogs) are converted. Salesforce says SBQQ objects do not map directly to RCA at all (source). - How much pricing logic is code. Quote Calculator Plugins, Apex on quote lines and TurboPricing configurations all have to be re-expressed. Declarative rules take days; scripts take weeks.
- How many integrations touch quotes. Each ERP, e-signature, billing or document system that reads quote objects is re-pointed and re-tested. Count them in discovery; each adds roughly a week.
Finding your own number
Answer the twelve readiness questions — they cover the three drivers above and give a range. For a Revenue Cloud Advanced move, Prodly and IdeaHelix offer free assessments of the CPQ setup. For a Kugamon move, a scoping call returns a fixed-price plan.
To Revenue Cloud Advanced, 12–18 months in practice for a full rebuild, longer with extensive custom logic, large catalogs or multiple integrations. To Kugamon, typically 4–8 weeks because standard Products and Price Books move as-is.
Usually catalog and pricing when list prices live in vendor objects or code, and quotes and install base when subscription data is large or dirty. Integrations are the most often underestimated.
Yes. Segments can move one at a time while the old CPQ stays live; see phased migration. The install base should still move in one pass so renewals are never split across systems.
No. Salesforce CPQ is end of sale, not end of life; existing customers can renew and no end-of-life date has been announced (Salesforce). The timeline is yours to set.
See your migration plan
Published timelines by source platform, a fixed implementation fee, and a calculator that labels every estimate.