Apttus CPQ data model: packages, objects, namespaces, and migration mapping
Apttus CPQ — sold today as Conga CPQ — installs several managed packages into Salesforce. Configuration and pricing objects live in the Apttus_Config2 namespace; quotes live in Apttus_Proposal. The cart is a Product Configuration with Line Items; prices come from Conga Price Lists, not Salesforce Price Books. This reference lists the objects that matter and where each maps when you leave.
The packages
Conga’s install guide lists ten packages for a standalone CPQ implementation, installed in a fixed order, plus optional packages for Advanced Approvals, Deal Maximizer, Adobe Sign, and platform sync (CPQ Packages). The objects in each are listed on the CPQ Package Objects page. The ones that hold your data:
| Package (install order) | What it holds | Namespace |
|---|---|---|
| 1 · Conga Base Library | Shared UI component configuration used by the other packages. Required. | — |
| 2 · Conga Contract Lifecycle Management | Agreements, clauses, templates, wizards. Required even for standalone CPQ. | Apttus |
| 3 · Conga Quote Management | Quote/Proposal, Proposal Line Item, proposal documents and approval requests. | Apttus_Proposal |
| 4 · Conga Configuration & Pricing | Catalog structure, configuration, pricing, carts, orders, assets. The core of CPQ. | Apttus_Config2 |
| 5 · Conga Quote Configuration Integration | Links proposals to the cart: proposal adjustments, footnotes, summaries, tax breakups. | Apttus_QPConfig |
| 6 · Conga CPQ Api | REST/SOAP API layer for the cart. | Apttus_CPQApi |
| 7–8 · CLM Configuration / Quote CLM Integration | Link agreements to the cart and to quotes. Optional (Contract Management). | — |
| 9 · Conga Quote Asset Integration | Renewals: connects quotes to Asset Line Items. | — |
| 10 · Conga CPQ Setup | Setup and maintenance jobs. | — |
Namespaces shown are the ones Conga’s API documentation uses (CPQ Web Service, Apttus_Config2); you will see them all in Setup → Installed Packages.
Core objects and what they map to
Labels below are Conga’s; API names are given where Conga’s documentation uses them. The last column is the usual landing place when you move to a CPQ built on standard Salesforce objects.
| Conga object (label) | API name | Purpose | Maps to on exit |
|---|---|---|---|
| Product Configuration | Apttus_Config2__ProductConfiguration__c | The cart. One per configuration session, linked to a proposal or order. | Nothing — carts are transient. Migrate the resulting quote. |
| Line Item | Apttus_Config2__LineItem__c | A product or service in the cart, with quantity, term, pricing fields. | Quote line on the target quote. |
| Quote/Proposal | Apttus_Proposal__Proposal__c | The quote header: dates, account, opportunity, status. | Target quote header (open quotes only). |
| Proposal Line Item | Apttus_Proposal__Proposal_Line_Item__c | Synced copy of cart lines on the proposal. | Quote line. |
| Price List | Apttus_Config2__PriceList__c | A list of sellable products and their prices. | Standard Price Book (Pricebook2). |
| Price List Item | Apttus_Config2__PriceListItem__c | A product entry in a price list: list price, charge type, frequency. | Standard Price Book Entry. |
| Price Rule / Price Ruleset / Price Matrix | Apttus_Config2__PriceRule__c etc. | Conditional pricing, tiered and dimensional pricing. | Target CPQ’s tiered / account-specific pricing. |
| Product Option Group / Component | Apttus_Config2__ProductOptionGroup__c / …OptionComponent__c | Bundle structure: which options belong to which product. | Target bundle definition. |
| Constraint Rule (+ Condition, Action) | Apttus_Config2__ConstraintRule__c | Inclusion, exclusion, and validation rules for configuration. | Target CPQ validation / product rules. |
| Product Attribute Group / Value | Apttus_Config2__ProductAttributeGroup__c / …ProductAttributeValue__c | Configurable attributes on a product and their chosen values. | Product fields or target attribute model. |
| Asset Line Item | Apttus_Config2__AssetLineItem__c | The install base: what the customer owns, with dates and pricing. | Subscription / asset records (Kugamon: kuga_sub Subscription). |
| Order / Order Line Item | Apttus_Config2__Order__c / …OrderLineItem__c | Orders created from proposals or directly. | Target order objects. |
| Category / Category Hierarchy | Apttus_Config2__ClassificationName__c / …ClassificationHierarchy__c | Catalog browsing structure. | Product family / target catalog categories. |
Where the data really lives
Three things trip up migrations. First, Product2 is standard but pricing is not: your products are ordinary Salesforce products, but list prices sit in Conga Price List Items, so a standard Price Book export gives you nothing. Second, the cart is not the quote: Product Configuration records accumulate every configuration session, including abandoned ones; export proposals and their line items, not carts. Third, TurboEngines add an external copy: if TurboPricing or TurboConfig is enabled, master data is synced on a schedule to Conga’s compute platform (Conga docs); the org is still the source, but confirm the sync is current before you export.
A minimal export set
- Products
Standard
Product2with Conga classification fields. - Price lists and items
All active Price Lists and their Price List Items, including charge type and frequency.
- Bundle structure
Product Option Groups, Option Components, and Feature Sets.
- Rules
Constraint Rules with their conditions and actions; Price Rules with entries.
- Open quotes
Proposals not yet accepted or expired, with Proposal Line Items.
- Install base
Active Asset Line Items with start and end dates.
The Salesforce CPQ data migration guide covers the equivalent SBQQ set; the checklist sequences the whole move.
It is the managed-package namespace of the Conga Configuration & Pricing package (the core of Apttus / Conga CPQ). Objects such as Product Configuration, Line Item, Price List, and Asset Line Item carry the Apttus_Config2__ prefix, and the CPQ web service is invoked as Apttus_Config2.CPQWebService (Conga API reference).
No. List prices live in Conga Price List and Price List Item objects (Conga package objects). Products themselves are standard Product2 records. On exit, Price List Items map to standard Price Book Entries.
Asset Line Items (Apttus_Config2__AssetLineItem__c), with history in Asset Line Item History and Asset Transaction History (Conga docs). These are the records to migrate for renewals and amendments.
Both are managed packages with their own quote, line, bundle, and rule objects. The main difference: Salesforce CPQ prices from standard Price Books and adds SBQQ rules on top, while Apttus / Conga prices from its own Price Lists. See What is SBQQ? for the object-by-object view.
Ready to run the numbers?
Published licence prices, a fixed implementation fee, and typical timelines by source platform.