Revenue Cloud Advanced data model: the objects, by module, from the developer guide
Revenue Cloud Advanced is built on core Salesforce objects, organised in the developer guide into Product Catalog Management, Salesforce Pricing, Rate Management, Product Configurator, Transaction Management, Advanced Approvals, Dynamic Revenue Orchestrator, Usage Management and Billing. Quotes are standard Quote and QuoteLineItem records with Transaction Management fields; the install base is Asset with AssetStatePeriod. None of it maps directly from SBQQ.
The modules
Salesforce documents Revenue Management in nine developer-guide sections (Revenue Management Developer Guide). Here are all nine, with the objects you meet first in each. The first four hold the quote-to-cash records most CPQ teams care about:
| Module | What it holds | Representative objects | Source |
|---|---|---|---|
| Product Catalog Management | Products, classifications, attributes, catalogs, bundles, qualification rules. | Product2, ProductClassification, AttributeDefinition, ProductAttributeDefinition, ProductSellingModel | developer.salesforce.com |
| Salesforce Pricing | Pricing procedures, price adjustment methods, price books, cost books, decision tables. | PricebookEntry, PriceAdjustmentSchedule, AttributeBasedAdjustment | developer.salesforce.com |
| Transaction Management | Quotes, orders, contracts, assets and their lifecycle. | Quote, QuoteLineItem, QuoteLineDetail, QuoteLineGroup, QuoteAction, Order, OrderItemDetail, ContractItemPrice, Asset, AssetStatePeriod, AssetContractRelationship, SalesTransactionType | developer.salesforce.com |
| Product Configurator | Constraint-based configuration of bundles and attributes. | ProductConfigurationRule, ProductConfigurationFlow; constraint models written in CML. | developer.salesforce.com |
| Advanced Approvals | Approval chains for quotes and orders. | See the developer guide section. | developer.salesforce.com |
| Usage Management | Usage resources, grants, entitlements and consumption for usage-based products. | UsageResource, ProductUsageGrant, UsageEntitlementBucket, TransactionJournal, UsageSummary | developer.salesforce.com |
| Rate Management | Rates and rate adjustments for consuming a resource beyond the allowance. | RateCard, RateCardEntry, RateAdjustmentByTier, RateAdjustmentByAttribute, PriceBookRateCard | developer.salesforce.com |
| Dynamic Revenue Orchestrator | Breaking an order into fulfilment steps for downstream systems. | FulfillmentPlan, FulfillmentStep, ProductFulfillmentDecompRule, FulfillmentAsset | developer.salesforce.com |
| Billing | Billing schedules, invoices, credit and debit memos, payments, tax and the general ledger. | BillingSchedule, BillingTreatment, Invoice, InvoiceLine, CreditMemo, PaymentTerm, LegalEntity, GeneralLedgerAccount | developer.salesforce.com |
The model in one picture
The concepts that have no SBQQ equivalent
- Product selling model.
ProductSellingModeldefines how a product is sold — one-time, evergreen subscription, or termed subscription — and a product can have several (developer.salesforce.com). In SBQQ this was a mix of product fields and subscription settings. - Asset state period.
AssetStatePeriodis a span during which an asset has the same quantity, amount and MRR; an asset has as many periods as changes (developer.salesforce.com). SBQQ tracked this through Subscription and Contract records. - Quote line detail.
QuoteLineDetailrecords the breakdown of a line — negative quantities, early renewals, repricing during an amendment (developer.salesforce.com). SBQQ expressed amendments as new quote lines. - Pricing procedures. Declarative pricing logic replaces price rules and Quote Calculator Plugin scripts. Salesforce’s own comparison table lists this as the pricing-engine difference (salesforce.com).
From SBQQ to Revenue Cloud: the concept map
The same map the object mapper uses, with what the partner migration tools do with each object (per Prodly’s public webinar and Salesforce Help’s list of what the tools cannot migrate, Salesforce Help):
| Salesforce CPQ (SBQQ) | Revenue Cloud Advanced | With the migration tools |
|---|---|---|
Product2, PricebookEntry (standard) | Product2 + ProductClassification; PricebookEntry reused, priced through pricing procedures | Automatic |
SBQQ__Quote__c | Quote with Transaction Management fields | Not migrated by the tools; open quotes by hand |
SBQQ__QuoteLine__c | QuoteLineItem + QuoteLineDetail | Not migrated by the tools |
SBQQ__QuoteLineGroup__c | QuoteLineGroup | Not migrated by the tools |
SBQQ__ProductFeature__c, SBQQ__ProductOption__c | Attribute-based catalog (ProductRelatedComponent) | Automatic (bundle structure) |
SBQQ__ProductRule__c | Constraint-based configurator rules | Assisted |
SBQQ__PriceRule__c | Pricing procedures | By hand for complex rules |
SBQQ__DiscountSchedule__c | PriceAdjustmentSchedule | Assisted; advanced schedules by hand |
SBQQ__ContractedPrice__c | ContractItemPrice | Assisted |
SBQQ__Subscription__c + Contract | Asset + AssetStatePeriod + AssetContractRelationship | Assisted (consolidated into assets) |
SBQQ__QuoteTemplate__c | Rebuilt as document templates | By hand |
| Quote Calculator Plugin | Pricing procedures, with Apex pre- and post-hooks where needed | By hand |
Salesforce Help confirms the two that teams ask about most: contracted prices move from a custom object to ContractItemPrice on standard objects, and pricing moves from rules executed in the browser to procedures executed on the server (Salesforce Help).
The configuration layer: context definitions, procedures and CML
Three parts of Revenue Cloud are configuration rather than data, and they shape how a project runs:
- Context definitions. Revenue Cloud’s pricing and configuration read data through context definitions, which map the fields a procedure or rule can see. The developer guide points to the Context Service reference for them (developer guide).
- Pricing procedures and decision tables. Pricing is a sequence of steps, with lookups held in decision tables, and Salesforce Pricing exposes them through standard objects, business APIs, invocable actions and the Metadata API (developer guide).
- Constraint Modeling Language. Configuration rules are written in CML, a declarative language for constraints (developer guide).
The definitions are metadata and move between sandbox and production with deployment tools; the decision-table rows and catalog records they read are data. Either way, somebody on the team needs to own them after go-live. In SBQQ, most of the same logic sat in records: price rules, product rules and discount schedules.
What it means for a migration
Salesforce’s FAQ: CPQ-specific objects, custom fields, pricing rules and scripts “don’t map directly — a structured migration and data transformation process is required” (Salesforce). The object table above is why. Products carry over; nearly everything else is re-expressed in a different shape. The CPQ to Revenue Cloud guide sequences that work; the partner tools automate parts of it.
One model, three names in the documentation
Salesforce’s developer guide is now titled the Revenue Management Developer Guide and says “Revenue Cloud is now Revenue Management” (developer guide); its Help pages say Revenue Management (formerly Revenue Cloud) (Salesforce Help); its price list says Revenue Cloud (Salesforce). They are the same objects. When you search the documentation, try all three names, and expect older pages to say Revenue Lifecycle Management.
No. Salesforce describes it as native to Salesforce core (Salesforce). Its objects are standard objects — Quote, QuoteLineItem, Order, Asset — with Transaction Management fields, plus core objects such as ProductClassification, ProductSellingModel and PriceAdjustmentSchedule (developer guide).
Asset, with AssetStatePeriod tracking each span of consistent quantity, amount and MRR, and AssetContractRelationship linking assets to contracts (developer guide). Amendments, renewals and cancellations are asset-based (Salesforce).
Not directly. Both are quote headers, but RCA’s Quote carries Transaction Management fields and its lines use QuoteLineItem plus QuoteLineDetail with a different pricing model. Salesforce says a structured migration and data transformation is required (source). Mapping: data migration guide.
Pricing procedures. They run on the server as a sequence of steps that builds a price waterfall, with decision tables for lookups and Apex pre- and post-hooks where needed (Salesforce Help). Discount schedules become PriceAdjustmentSchedule records. Complex price rules and Quote Calculator Plugin logic are rebuilt by hand; the migration tools do not convert them (Salesforce Help).
In ContractItemPrice, a standard object, instead of the SBQQ__ContractedPrice__c custom object. Salesforce Help also lists account, partner and channel-specific pricing as native (Salesforce Help).
Yes. The developer guide’s Billing section documents standard objects for billing schedules, invoices and invoice lines, credit and debit memos, payment terms and schedules, tax and the general ledger (developer guide). They come with Revenue Cloud Billing, which Salesforce sells separately (Salesforce); Invoice Management is an add-on for invoicing on Advanced (Salesforce).
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. 135 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.