Migrate from Conga Advantage CPQ (formerly Apttus CPQ) to Kugamon: the playbook
Conga Advantage CPQ — formerly Apttus CPQ — ships as ten managed packages, prices from its own Price List objects rather than standard Price Books, and increasingly runs pricing on Conga’s compute platform under a separate TurboEngines licence. Kugamon is one package on your standard objects, admin-owned, $65 per user per month, typically 6–10 weeks to migrate.
Should you leave Conga CPQ?
- Conga CLM, Composer or Sign is load-bearing and an SI is on retainerStaying on Conga is defensible — ask where pricing will run in two years
- Pricing changes wait for a developer or partnerKugamon fits — admin-owned, standard Price Books, published price
- You are unsure whether you run Apttus-era packagesCheck namespaces first: Apttus CPQ data model
Where you are
Conga is PE-owned and now sells two CPQs, and complex pricing logic lives in Apex callbacks that usually need a developer or partner to change — often one admin holds the institutional knowledge. Kugamon is the #1 rated native Salesforce CPQ — admin-owned, native Salesforce Products and Price Books, no proprietary data model.
Your Conga (formerly Apttus) deployment is one resignation away from a crisis. One admin holds the institutional knowledge for a sprawling configuration. Conga’s Salesforce package uses the standard Product object but prices from its own Price List objects instead of Price Books, and keeps quotes in its own Proposal objects. Conga publishes no implementation rate card; its own guidance is 3–6 months for a typical CPQ implementation (6–12 weeks for SMBs, 9+ months for complex enterprise). Conga is PE-owned (Thoma Bravo), completed its acquisition of PROS’s B2B business on February 2, 2026, and now sells two CPQs: Conga Advantage CPQ (formerly Apttus CPQ) and Smart CPQ (formerly PROS). Conga after the PROS acquisition →
Kugamon is the way out. The #1 rated CPQ on AppExchange, built on native Salesforce Products and Price Books — no proprietary data model, no SI partner required, no admin lock-in. Any Salesforce admin can manage Kugamon. Conga publishes no price list on conga.com; its one priced CPQ offer is on AWS Marketplace, $5,400 per user for 36 months (about $150 per user per month), on a listing marked ‘Deployed on AWS’. The calculator compares three-year cost with every Conga figure labeled as an estimate.
What you leave, what you gain
| What you leave behind | What you get with Kugamon |
|---|---|
| Admin burnout: Conga requires a dedicated admin who becomes a single point of failure — when that person leaves, the system becomes unmaintainable | Admin-owned configuration — any Salesforce admin can manage Kugamon without an SI or dedicated CPQ specialist |
| Shelfware risk: Conga's complexity leads to partial implementations — licenses keep renewing for reps who never adopt the tool | Uses native Salesforce Products and Price Books — zero duplicate maintenance, zero proprietary data model |
| Pricing from Conga’s own Price List objects instead of standard Price Books, and quotes in its own Proposal objects — creating double-maintenance | Adoption is built into the product: Lightning-native, rep-friendly workflows prevent the Excel-reversion pattern |
| Complex pricing and validation logic lives in Apex callbacks, so changes beyond Conga’s admin UI usually need a developer or partner | Built for Lightning from day one |
| Cost of ownership: Conga publishes no implementation rate card; its own guidance is 3–6 months for a typical CPQ implementation (6–12 weeks for SMBs, 9+ months for complex enterprise); upgrades are one-way, and June ’26’s mandatory security changes required custom-code updates | Fixed-fee implementation — $15K–$30K depending on edition, $5K less on a multi-year term (see the calculator for your TCO) |
Where your data lives, before and after
Conga’s packages live in your org, but its pricing objects are its own — and with TurboEngines, pricing computation can leave the org entirely.
What moves, and what gets rebuilt
Products are standard and move. Conga Price Lists become Price Books; proposals, bundles, rules and assets are rebuilt.
The migration, step by step
- Catalog & Rules Inventory
Export Conga product catalog, pricing matrices, and configuration rules. Document any custom objects, triggers, or Apex code used for CPQ logic.
- Native SF Price Book Alignment
Products are already standard Salesforce Products. Pricing moves from Conga's Price Lists into the native Salesforce Price Books that Kugamon directly extends. This is the core step.
- Rule Rebuild in Kugamon
Recreate configuration rules, discount schedules, and approval workflows using Kugamon's Setup Wizard. Prioritize highest-volume rules first.
- Extended Parallel Testing
Run Conga and Kugamon in parallel for 3–4 weeks. Complex Conga configurations warrant extra validation time before full cutover.
- Phased Cutover
Roll out by product line or team. Conga complexity often benefits from phased go-live rather than a single cutover date.
What it costs over three years
Conga’s Salesforce package uses the standard Product object but prices from its own Price List objects instead of Price Books, and keeps quotes in its own Proposal objects. Kugamon extends the native Salesforce data model directly: same Products, same Price Books, same security model. The result is a lower three-year cost in the calculator’s labeled comparison (Conga publishes no price list on conga.com and its one priced CPQ offer is on AWS Marketplace, so its figures are estimates), no SI partner required, and any Salesforce admin can manage it.
Most Conga-to-Kugamon migrations complete in 6–10 weeks. Conga deployments are typically the most complex starting state we see — lots of proprietary configuration, custom Apex extensions, and SI-built playbooks — but our migration team has done this many times. The Price Book alignment is the most time-consuming step; everything downstream of that is faster than building from scratch.
Conga is PE-owned (Thoma Bravo) and now sells two CPQs after the PROS deal. Before renewing, get in writing which CPQ your roadmap covers and how PROS pricing is licensed, and negotiate a cap on renewal increases. The calculator on this page shows what a switch to Kugamon would cost over three years.
Your Conga admin is more than ready. Kugamon is configured through the standard Salesforce admin interface — point-and-click, same security model, same deployment patterns. Most Conga admins describe the experience as “finally normal Salesforce work.” You don’t need a Kugamon specialist; you need a Salesforce admin, which you already have.
Most Kugamon migrations complete in 4–8 weeks — against the 12–18 months a Revenue Cloud Advanced rebuild takes in practice. We've been building Salesforce-native CPQ since 2009, across 150+ companies. We know where the traps are, and we've built a proven process to avoid them. You keep your Salesforce data, your product catalog, and your pricing rules. We handle the rest.
For Salesforce CPQ customers, your data stays in Salesforce — because Kugamon is in Salesforce. There's no database migration, no export-import, no data mapping to an external system. Your product catalog, price books, quotes, and order history remain exactly where they are. For teams migrating from other platforms — including DealHub, Nue, Conga, or a custom-built CPQ — Kugamon supports data imports to bring your product catalog, pricing, and historical quote data into Kugamon. Either way, we've done it before and we'll guide you through it.
How long would yours take?
Readiness check
Twelve questions about your catalog, pricing logic, approvals and integrations. Returns a timeline range.
Take the check →Object mapper
Where every Salesforce CPQ, Conga, Revenue Cloud Advanced, DealHub and Nue object lands — and what has no equivalent.
Look up an object →3-year cost
Published prices where they exist, labelled estimates where they do not, at your user count.
Open the calculator →Nothing is submitted and no email is asked for — all three run in your browser. 134 public AppExchange reviews are on the reviews page.
See your migration plan
Published timelines by source platform, a fixed implementation fee, and a calculator that labels every estimate.