What is SBQQ? The Salesforce CPQ namespace, explained
SBQQ is the namespace prefix of the Salesforce CPQ managed package. Every object, field, and class the package adds to your org starts with SBQQ__ — SBQQ__Quote__c, SBQQ__QuoteLine__c, SBQQ__Subscription__c, and so on. The prefix comes from SteelBrick, the company Salesforce acquired in December 2015; managed-package namespaces cannot be renamed, so it stayed. If you see SBQQ in your org, you run Salesforce CPQ.
Where the name comes from
SteelBrick built its CPQ as a managed package on the Salesforce platform and registered the namespace SBQQ. Salesforce has never documented what the letters expand to; community sources read them as “SteelBrick Quick Quote,” after the product’s early name. Salesforce announced its agreement to acquire SteelBrick on December 23, 2015 (Forbes) and later renamed the product Salesforce CPQ. A managed package’s namespace is permanent, so the prefix outlived the brand. Timeline: Salesforce CPQ end-of-sale timeline.
The objects that carry the prefix
| Object | What it holds |
|---|---|
SBQQ__Quote__c | The quote header: account, opportunity, dates, status, totals. |
SBQQ__QuoteLine__c | Each product on a quote, with quantity, list, net, and discount fields. |
SBQQ__QuoteLineGroup__c | Optional grouping of quote lines. |
SBQQ__ProductOption__c / SBQQ__ProductFeature__c | Bundle structure: features on a parent product and the options inside each. |
SBQQ__ProductRule__c | Validation, alert, selection, and filter rules for configuration. |
SBQQ__PriceRule__c | Conditional price changes applied during calculation. |
SBQQ__DiscountSchedule__c | Volume and term discount tiers. |
SBQQ__ContractedPrice__c | Account-specific negotiated prices. |
SBQQ__Subscription__c | The install base: one record per subscribed product per contract, with dates and quantities. |
SBQQ__QuoteTemplate__c | Quote document layouts. |
| Standard objects used by the package | Product2, Pricebook2, PricebookEntry, Contract, Order. |
Sources: Salesforce CPQ object relationships · subscription fields · CPQ developer guide (PDF). Object-by-object migration mapping: Salesforce CPQ data migration.
How to tell if your org has SBQQ
- Setup → Installed Packages lists “Salesforce CPQ” (older orgs may still show “SteelBrick CPQ”) with namespace prefix SBQQ.
- Object Manager shows objects whose API names begin with
SBQQ__. - Opportunities have a “Quotes” related list pointing at
SBQQ__Quote__crather than the standard Quote object. - Reps use the Quote Line Editor to add products.
What end of sale means for SBQQ orgs
Salesforce stopped selling CPQ to new customers in March 2025. Existing SBQQ orgs can renew, add users, and receive support; there is no forced migration and no announced end-of-life date, but no new features arrive and the online documentation was retired in July 2026 (Salesforce · KB 005388761). Your SBQQ data is unaffected: it stays in your org under your control. When you migrate, the standard objects (Products, Price Books) move as-is and the SBQQ__ objects are mapped to the target — Revenue Cloud Advanced (a new data model; a full rebuild runs 12–18 months in practice) or a native alternative such as Kugamon (standard Products and Price Books; typically 4–8 weeks, playbook).
It is the managed-package namespace of Salesforce CPQ, registered by SteelBrick before Salesforce acquired it in December 2015 (Forbes). Salesforce has not documented an expansion; community sources read it as “SteelBrick Quick Quote.” Namespaces cannot be renamed, so the prefix stayed after the product became Salesforce CPQ.
Yes. SBQQ is the namespace; Salesforce CPQ is the product. An org with SBQQ__ objects is running Salesforce CPQ.
No. Revenue Cloud Advanced is built on core Salesforce objects with a different data model. SBQQ objects do not map directly to it; Salesforce says a structured migration and data transformation is required (source). Comparison: Salesforce CPQ vs Revenue Cloud Advanced.
Yes, once nothing references it: migrate open quotes and subscriptions, re-point integrations and automation, archive historical quotes, then uninstall from Setup. Uninstalling deletes the package objects and their data, so archive first. Sequence: CPQ migration checklist.
Ready to run the numbers?
Published licence prices, a fixed implementation fee, and typical timelines by source platform.