CPQ migration FAQ: 38 questions, grouped by platform, each with a source

No. It’s end of sale. Salesforce stopped selling CPQ to new customers in March 2025; existing customers can renew, add users, and receive support, and Salesforce has announced no end-of-life date. It is in maintenance mode — no new features — and in July 2026 Salesforce retired the online documentation in favor of a single PDF. Sources: Salesforce’s end-of-sale page and Salesforce KB 005388761. Our explainer: Salesforce CPQ is end of sale.

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.

Kugamon CPQ is $65/user/month, published on the AppExchange listing — vs. Revenue Cloud Advanced at $200 (Growth edition $150). Quote to Cash and Subscription Management are $95; Subscription Billing is $125. Implementation is a fixed fee ($15K–$30K depending on edition) versus a Revenue Cloud Advanced rebuild that runs 12–18 months in practice. Run your team size and term in the ROI calculator.

Full quote-to-cash — not just quoting. Kugamon covers CPQ, order management, invoicing, subscription billing, subscription management, and inventory — all natively on Salesforce. The broken handoff between quoting and billing is one of the most cited frustrations in the CPQ market. With Kugamon, it's one system, one data model, no reconciliation nightmares.

Yes. Kugamon is purpose-built for complex B2B revenue models — subscription + one-time + usage (with minimal customization), multi-element bundles, tiered pricing, multi-year contracts with ramp schedules, and hybrid billing. If you're currently handling this in Salesforce CPQ or with a combination of CPQ and spreadsheets, Kugamon can handle it in a single system without custom code.

100% native — built on Salesforce Lightning from day one. No external database. No middleware. No API sync to worry about breaking. Kugamon lives inside your Salesforce org, uses your existing Salesforce data model, and respects your existing profiles, permissions, and workflows. This is a fundamental architectural difference from tools like DealHub, which bolts onto Salesforce from the outside via API, and Nue, which uses a hybrid model — meaning data that lives outside your Salesforce org and a sync layer that can break.

Yes. Because Kugamon is 100% native on Salesforce, it is fully compatible with Agentforce out of the box — no integration layer, no API sync, no custom connectors required. Agentforce agents can read and act on Kugamon quote, order, and billing data just like any other Salesforce object. As Salesforce continues to expand Agentforce's revenue management capabilities, Kugamon customers benefit automatically. DealHub syncs a copy of each quote to standard Salesforce Quote or Opportunity Product records, so Agentforce works on that copy, not on DealHub’s master record; Nue’s billing and usage data reach Salesforce through an asynchronous sync. With Kugamon, you're already there.

No. This is one of the most common complaints about Salesforce CPQ and Conga — they create a single point of failure where one admin holds all the institutional knowledge. Kugamon is built for Salesforce administrators and RevOps teams to manage themselves, with point-and-click configuration and no proprietary scripting language to learn. When your admin leaves, your system doesn't break.

Reps revert to Excel when the CPQ adds friction. Kugamon runs entirely inside Salesforce Lightning — reps never leave the CRM, never context-switch to a separate application, and never wait for slow page loads. The quoting workflow is designed for rep velocity first, compliance second. If it's faster than their current process, they'll use it. That's the bar we build to.

Revenue Cloud Advanced (RCA) is Salesforce’s successor to Salesforce CPQ, sold since 2024 (launched as Revenue Lifecycle Management in June 2024, renamed Revenue Cloud that September). It is a separate product with a new data model, priced at $200 per user per month (Advanced) or $150 (Growth) on Salesforce’s pricing page. It is built into the core platform but sold in pieces: Revenue Cloud Billing is a separate, quote-only product, and Dynamic Revenue Orchestration, Invoice Management and External User Support are add-ons. Salesforce marketed Revenue Cloud as Agentforce Revenue Management from October 2025 until it restored the Revenue Cloud name on September 14, 2026. A full rebuild runs 12–18 months in practice. Kugamon is the Salesforce-native alternative at $65 per user per month. Full explainer: What is Salesforce Revenue Cloud? → · Side-by-side: Salesforce CPQ vs Revenue Cloud Advanced →

Salesforce CPQ (SBQQ) is the legacy product, now end of sale — no longer sold to new customers. Revenue Cloud Advanced is its replacement — a brand-new architecture and data model, sold at $200/user/month, with no first-party Salesforce migration tool yet (Salesforce has announced one for December 2026 and points customers to partner accelerators such as Forsys RevRamp, IdeaHelix, and Prodly). Kugamon is the #1 rated native CPQ on AppExchange (4.9 stars across 130+ public reviews) — same Salesforce-native architecture, same data model your admins already know, with quote, order, billing, and subscriptions in one package starting at $65/user/month.

Revenue Cloud Advanced requires a complete rebuild — new data model, new architecture, no first-party Salesforce migration tool yet (one is on Salesforce’s roadmap for December 2026; today Salesforce points to partner accelerators — Forsys RevRamp, IdeaHelix, Prodly). A full rebuild runs 12–18 months in practice. Kugamon migrations average 4–8 weeks because we extend the Salesforce data model your admins already manage. Your Products, Price Books, and Accounts transfer directly. Most customers don’t need an SI partner.

No. Salesforce CPQ is end of sale, not end of life: no end-of-life date has been announced, you can keep renewing, adding users and getting support, and there is no forced migration. What has changed is where Salesforce is investing. Winter ’27 (generally available October 12, 2026) puts new buyer, partner and renewal quoting in Revenue Cloud, not in Salesforce CPQ, and Salesforce has announced a CPQ migration assistant with a December 2026 target. So the useful step is to plan, not to rush: decide where you want to land before your next CPQ renewal, and run your own numbers in the ROI calculator. A move to Kugamon takes 4–8 weeks, so it fits inside a normal renewal cycle.

RCA introduces a new data model (Product Catalog separated from Pricing) that existing Salesforce CPQ skills don’t fully transfer to. Configuration needs specialist skills (Constraint Modeling Language, pricing procedures, context definitions), and reviewers cite documentation gaps. The result is rebuild-style projects: a full rebuild runs 12–18 months in practice. Kugamon uses the native SF Product + Price Book model your admins already know — 4–8 week go-live, admin-led.

Revenue Cloud Advanced lists at $200/user/month ($150 for Growth), and Salesforce publishes no implementation price. Our three-year model at 50 users puts Revenue Cloud Advanced at about $897,000, including about $375,000 of implementation for a 50-user rebuild, and Kugamon CPQ at about $143,500, 84% lower: $65/user/month and a fixed $10K implementation fee on a three-year term ($15K on one year). Competitor figures are estimates: the midpoint of the low and high cases in our October 2026 competitor research. Run your own numbers in the ROI calculator.

Yes. Many customers come to us partway through an RCA project that’s slipping. Because Kugamon uses native Salesforce Product + Price Book, your existing catalog, accounts, opportunities, and pricing all stay where they are. The RCA-specific rebuild stops; Kugamon picks up the standard data model and ships you live in 4–8 weeks.

Yes, with limits. Revenue Cloud added line and group cloning in Summer ’25 and full-quote Deep Clone in Summer ’26; a clone is capped at 6,000 records, and quotes over 1,000 lines need a request to your Salesforce account executive. Kugamon supports one-click quote cloning with editable cloned lines, the way reps actually work, and loads a 100,000-product catalog in 3 seconds; in Kugamon’s benchmark the same load takes Salesforce CPQ 20 seconds.

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 ROI calculator 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.

DealHub is a multi-CRM platform — it supports Salesforce, HubSpot, Microsoft Dynamics, and others, which means none of them is the design center. Quote and order data lives in DealHub’s own database, not your Salesforce org; Salesforce receives a copy of each quote when the sync runs at configured milestones (for example submit or won). Kugamon is built exclusively for Salesforce. Every quote, order, invoice, and subscription is a record in your Salesforce org — no external storage, no sync, no drift.

Yes. Reps go back to Excel when quoting is slower than their workaround. Kugamon runs entirely inside Salesforce Lightning, so reps quote from the Account or Opportunity record they’re working on. The quoting workflow is designed for rep velocity first, compliance second — if it’s faster than the rep’s current workaround, they’ll use it.

Kugamon works with Agentforce out of the box because it’s 100% native Salesforce. Agentforce agents read Kugamon quote, order, and billing data the same way they read any other Salesforce record — no custom connector, no API mapping, no integration project. DealHub syncs a copy of each quote to standard Salesforce Quote or Opportunity Product records, so Agentforce works on that copy, not on DealHub’s master record; Kugamon is already there.

DealHub guided-selling playbooks rebuild cleanly in Kugamon, often with fewer steps because Kugamon’s Setup Wizard handles guided selling natively in Salesforce. Most teams use the migration as an opportunity to retire stale or rarely-used paths. Typical timeline is 4–6 weeks end-to-end, including a parallel-run validation period.

Nue is built for SaaS and AI companies and isn’t fully Salesforce-native — Nue’s CPQ is a Salesforce managed package that writes quotes and orders to standard Salesforce records; its billing, invoicing, usage-rating and self-serve engines run on Nue’s AWS platform against a replicated copy that syncs back asynchronously. Kugamon is built for full-spectrum B2B revenue (subscription, one-time, bundles, and usage with minimal customization) and lives 100% inside Salesforce. Every quote, order, invoice, and subscription is a record in your Salesforce org — no external database, no sync, no drift, and native Salesforce reports work on every record from day one.

No. Kugamon handles pure-subscription pricing as cleanly as Nue does, but with one important difference: when your business eventually adds one-time pricing, usage-based pricing, or bundled offerings, you’re not migrating again. Most companies start with subscription-only pricing and grow into hybrid revenue within a few years. Kugamon doesn’t require a re-platform when that happens.

Most Nue migrations complete in 3–6 weeks — on the lower end of our migration ranges because Nue’s quotes, orders, Products and Price Books are already Salesforce records. The biggest step is exporting billing, usage and subscription history from Nue and reconciling it with the Accounts and Products in your Salesforce org. After that, configuration is fast.

Kugamon has been on AppExchange longer than most CPQ alternatives, has a stable customer base of enterprise B2B sellers, and is the #1 rated CPQ in its category. We don’t make claims about competitor stability, but our customers tell us they sleep better knowing their CPQ is on a Salesforce-native platform with US-based support and a long track record of enterprise deployments — not a venture-stage startup.

DealHub acquired Subskribe on November 19, 2025 and says there is ‘no immediate impact’: existing Subskribe environments continue to operate, and customers keep their customer success contact. DealHub also says Subskribe will be ‘fully integrated into the DealHub platform’ with ‘a single user experience and unified data model’, and has published no date for that move. If you’re a Subskribe customer evaluating where to land, Kugamon is the Salesforce-native alternative.

Subskribe’s proprietary “Zeppa” scripting language doesn’t transfer on migration. In the Kugamon migration, Zeppa logic gets rebuilt as Kugamon configuration, with Flow where needed — no proprietary scripting to maintain.

Active subscriptions, contracts, and open quotes migrate into Kugamon’s Quote, Order and Subscription records and the standard Contract in your org. Historical order data can be preserved as read-only reference. Order-lifecycle rigidity in Subskribe (after execution only the order name and open opportunities can be edited, and an admin can revert or delete only before anything is invoiced or recognized) is replaced by Kugamon’s editable orders with full audit trail.

DealHub is multi-CRM and stores quote data outside Salesforce, syncing it back via integration. Kugamon keeps quotes and orders as records in your Salesforce org (Kugamon’s own Quote and Order objects, synced to Opportunity Products) — same login your reps already use, no sync layer, AppExchange-listed managed package. If staying Salesforce-native is your priority, Kugamon is the cleaner path.

The patterns we hear in every conversation: (1) every new sales feature competes for the same engineering capacity as product, (2) institutional knowledge is concentrated in one or two engineers who hold the whole system, (3) the catalog or pricing structure has outgrown the original design and brittle workarounds are accumulating, (4) Salesforce platform changes routinely break custom integrations. If two or more apply, replatforming to Kugamon pays back within a year.

Most custom CPQ logic falls into one of three buckets: catalog/pricing rules (replace with Kugamon configuration), approval workflows (replace with standard Salesforce approvals), and integration glue (rewrite as Kugamon API extensions). Truly business-specific Apex that does something Kugamon doesn’t can stay as a Kugamon extension. The goal is to retire the maintenance burden of the core CPQ system, not every line of Apex.

4–12 weeks, depending on how much custom logic must be ported. The single highest-leverage move is a documentation week-zero before kickoff: catalog every custom object, every Apex class, every Flow, every integration. Most custom-CPQ replatforming fails because of undocumented logic. We pair with your admin/developer through this week, then go to standard 4-phase migration.

Most of our custom-CPQ customers redirect that engineering capacity to product. The CPQ stops being a feature factory for sales-ops and becomes a vendor relationship. The engineering time the CPQ took goes back to the roadmap, and CPQ enhancements ship monthly via Kugamon releases without internal dev cost.