Explainer

Apttus CPQ in 2026: what it is now, who owns it, and what to do if you still run it

Apttus CPQ is now Conga CPQ. Thoma Bravo became the majority owner of Apttus in October 2018; in May 2020 Apttus acquired Conga and the combined company took the Conga name. The Salesforce packages still carry the Apttus_Config2 namespace. If you run it, you have three realistic paths: stay, move deeper into Conga’s platform, or move to a Salesforce-native CPQ.

2018
Thoma Bravo takes majority of Apttus
$715M
Apttus buys Conga, 2020
Apttus_Config2
Namespace still in your org
10
Managed packages to install

What happened to Apttus

Apttus was a Salesforce-native quote-to-cash vendor. Two transactions changed it. On October 10, 2018, Thoma Bravo completed a majority investment in Apttus (Thoma Bravo press release). On May 7, 2020, Apttus and Conga announced they were combining; Apttus paid about $715 million for a majority of Conga, and the go-forward company operates under the Conga brand (Thoma Bravo · Bloomberg).

The product you bought as Apttus CPQ is listed on the AppExchange today as “Conga CPQ (formerly Apttus CPQ)”. In February 2026 Conga completed the acquisition of PROS’s B2B business, which adds a second pricing product line to the same company (what that means for Conga CPQ customers).

What Apttus CPQ is today

Conga CPQ for Salesforce installs as a set of managed packages — ten for a standalone implementation, in a fixed order: Base Library, Contract Lifecycle Management, Quote Management, Configuration & Pricing, Quote Configuration Integration, CPQ Api, the CLM integrations, Quote Asset Integration, and CPQ Setup (Conga install guide). The Configuration & Pricing package still uses the Apttus_Config2 namespace — the cart is a ProductConfiguration record, and its web service is invoked as Apttus_Config2.CPQWebService (Conga API reference). Quotes live in the Apttus_Proposal namespace.

Two things are new since the Apttus days. Conga now documents a separate “CPQ for Advantage Platform” product on its own platform, and it sells TurboPricing and TurboConfig, which move pricing and configuration computation off the Salesforce platform onto Conga’s compute service under a separate license (About TurboPricing). In practice, the direction of travel is away from “everything inside your Salesforce org.”

How to tell you are on an Apttus-era build

  • Object API names in your org start with Apttus_Config2__, Apttus_Proposal__, or Apttus__.
  • Pricing lives in Conga Price Lists and Price List Items, not in standard Salesforce Price Books.
  • A partner wrote and still maintains callback classes, custom pricing plug-ins, or TurboEngines settings.
  • Your quote template is a Conga Composer or X-Author document, and nobody in-house can change it.
  • Users open a separate cart page to add products rather than working on the quote record.

Your three options

There is no forced move. But the last major release you were promised as an Apttus customer has long since shipped, and each renewal is a chance to decide on purpose rather than by default.

Stay on Conga CPQ (Salesforce)Move within CongaMove to a Salesforce-native CPQ
What changesNothing today. Keep the packages, keep the partner.Adopt Advantage Platform and/or TurboEngines.Replace the packages with one that uses standard Salesforce objects.
Where pricing runsInside your org (unless Turbo is licensed).Conga’s compute platform, synced to your org.Inside your org.
Published priceNot published — contact Conga.Not published.Kugamon: $65 per user per month on the AppExchange listing.
Who maintains itUsually an SI.Usually an SI.Your admin.
Typical move timeDepends on scope.6–10 weeks from Conga CPQ (playbook).

If you are weighing the third path, start with the Conga CPQ alternatives guide and the Apttus data model reference, which shows what each object maps to.

Common questions

Apttus CPQ, explained — FAQ

All migration questions →

Yes, under the name Conga CPQ. The AppExchange listing is titled “Conga CPQ (formerly Apttus CPQ)”. New customers buy it from Conga; the Salesforce packages keep the Apttus_Config2 namespace.

Since May 2020, yes. Thoma Bravo-backed Apttus acquired a majority of Conga for about $715 million and the combined company took the Conga name (press release). Thoma Bravo had become the majority owner of Apttus in October 2018 (press release).

Conga does not publish a list price for Conga CPQ; pricing is by custom quote (conga.com). Third-party listings publish starting figures, but those are not vendor-confirmed, so we do not repeat them. For comparison, Kugamon publishes $65 per user per month on its AppExchange listing.

Configuration and pricing objects use Apttus_Config2 (for example Apttus_Config2__ProductConfiguration__c). Quotes use Apttus_Proposal (Apttus_Proposal__Proposal__c). Contract management uses the Apttus namespace. See the data model reference.

Export the catalog, price lists, active quotes, and asset line items; map them to standard Salesforce Products and Price Books; load them into the target CPQ; run both in parallel for one quote cycle; then uninstall. From Conga CPQ to Kugamon this typically takes 6–10 weeks — see the Conga migration playbook and the checklist.

Next step

Ready to run the numbers?

Published licence prices, a fixed implementation fee, and typical timelines by source platform.