Legacy CPQ replacement: what counts as legacy, and how to replace it
A CPQ is legacy when its vendor has stopped developing it, when nobody in-house can change it, or when its data model blocks what the business now needs. In 2026 that describes Salesforce CPQ (end of sale, frozen), many Apttus-era Conga implementations (partner-maintained, pricing moving off-platform), and most home-grown Apex CPQ. Replacement means choosing one of three paths and migrating six data sets.
What counts as legacy in 2026
| CPQ | Why it is legacy | Source |
|---|---|---|
| Salesforce CPQ (SBQQ) | End of sale since March 2025; no new features; online documentation retired July 2026. Supported and renewable, but frozen. | Salesforce · KB 005388761 |
| Apttus-era Conga CPQ | Product renamed in 2020; investment now in Conga’s Advantage Platform, TurboEngines, and PROS pricing rather than the in-org packages; usually SI-maintained. | Thoma Bravo · Conga docs |
| Home-grown Apex CPQ | No vendor, no roadmap, and the developer who wrote it has usually moved on. Every pricing change is a code change. | custom CPQ playbook |
| Spreadsheet quoting | Not a CPQ, but the most common legacy state: no approval trail, no install base, no renewals. | — |
The warning signs
- Pricing changes wait for a partner, a developer, or a release that is not coming.
- Reps keep a “real” price list in a spreadsheet because the system’s is wrong or slow.
- Renewals are found in a report rather than generated by the system.
- Reporting on quotes needs an export because the data is in package objects or outside the org.
- Agentforce or any AI tool cannot see quote data without an integration.
- The last three admin tickets were about workarounds, not improvements.
Three replacement paths
| Vendor’s successor | Salesforce-native alternative | External platform | |
|---|---|---|---|
| Example | Salesforce Revenue Cloud Advanced; Conga Advantage Platform. | Kugamon. | DealHub, Nue. |
| Data location | In the org (RCA) or on the vendor’s platform (Conga Advantage). | In the org, as standard Products, Price Books, and package objects. | Vendor’s cloud, synced to the org. |
| Who owns change | Usually an SI. | Your admin. | Vendor admin console. |
| Published price | RCA: $150 / $200 per user per month (Salesforce). Conga: no. | $65–$125 (AppExchange). | No. |
| Implementation | RCA: partner-quoted; a full rebuild runs 12–18 months in practice (source). | Fixed $25K–$30K; 3–12 weeks. | Vendor-scoped. |
| Guide | CPQ to RCA | Native CPQ, defined | DealHub · Nue |
What replacing a legacy CPQ involves
The same six data sets every time: catalog, pricing, open quotes, install base, templates and approvals, integrations. The twelve-step checklist sequences them; the SBQQ object map and the Apttus object map show what each holds. For home-grown Apex, the inventory is the migration: document every pricing branch before touching data (custom CPQ playbook).
Cost the three paths over three years in the calculator before you choose. Published license prices are used where they exist; everything else is labeled an estimate.
Salesforce calls it end of sale, not end of life (Salesforce). It is supported and renewable but receives no new features, and its online documentation was retired in July 2026 (KB 005388761). By the usual definition — no further development — it is legacy. See end of sale vs end of life.
It depends on whether you want quote data to stay in the org as standard objects (Kugamon or Revenue Cloud Advanced) or can accept a synced copy (DealHub, Nue), and on whether an admin or an SI will own it. Compare published prices and implementation terms; only Kugamon and Salesforce publish license prices, and only Kugamon publishes a fixed implementation fee (pricing).
To a Salesforce-native alternative such as Kugamon: 4–8 weeks from Salesforce CPQ, 6–10 from Conga, 6–12 from a home-grown build (timeline table). To Revenue Cloud Advanced: a full rebuild runs 12–18 months in practice (source).
Yes, and it is the most common custom-CPQ migration. The work is documenting every pricing branch in the Apex, deciding which are still needed, and configuring them in the package instead of coding them. Typical time to Kugamon is 6–12 weeks (playbook).
Ready to run the numbers?
Published licence prices, a fixed implementation fee, and typical timelines by source platform.