Data model

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.

9
Developer-guide modules
Core
Objects, not a package
Asset
Install base object
0
Direct maps from SBQQ

The modules

Salesforce documents Revenue Management in nine developer-guide sections (Revenue Management Developer Guide). The four that hold quote-to-cash data:

ModuleWhat it holdsRepresentative objectsSource
Product Catalog ManagementProducts, classifications, attributes, catalogs, bundles, qualification rules.Product2, ProductClassification, AttributeDefinition, ProductAttributeDefinition, ProductSellingModeldeveloper.salesforce.com
Salesforce PricingPricing procedures, price adjustment methods, price books, cost books, decision tables.PricebookEntry, PriceAdjustmentSchedule, AttributeBasedAdjustmentdeveloper.salesforce.com
Transaction ManagementQuotes, orders, contracts, assets and their lifecycle.Quote, QuoteLineItem, QuoteLineDetail, QuoteLineGroup, QuoteAction, Order, OrderItemDetail, ContractItemPrice, Asset, AssetStatePeriod, AssetContractRelationship, SalesTransactionTypedeveloper.salesforce.com
Product ConfiguratorConstraint-based configuration of bundles and attributes.Configuration rules and constraint models.developer.salesforce.com
Comparing RCA against a package that keeps your standard objects?Side by side →

The model in one picture

Catalog & pricing and Transactions & assets, both inside Your Salesforce org with Revenue Cloud Advanced Figure 1. Revenue Cloud Advanced on core objects. The selling model attaches to the product; the asset carries the subscription lifecycle; pricing runs as procedures rather than rules and scripts.Your Salesforce org with Revenue Cloud AdvancedCatalog & pricingProduct2 + ProductClassificationAttributeDefinitionProductSellingModel (one-time / evergreen / termed)PricebookEntry + pricing proceduresPriceAdjustmentScheduleTransactions & assetsQuote + QuoteLineItemQuoteLineDetail (amendments, repricing)Order + OrderItemDetailAsset + AssetStatePeriodContractItemPrice
Catalog & pricingTransactions & assets
Figure 1. Revenue Cloud Advanced on core objects. The selling model attaches to the product; the asset carries the subscription lifecycle; pricing runs as procedures rather than rules and scripts.

The concepts that have no SBQQ equivalent

  • Product selling model. ProductSellingModel defines 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. AssetStatePeriod is 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. QuoteLineDetail records 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).

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.

Common questions

Revenue Cloud data model — FAQ

All migration questions →

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.

Next step

Ready to run the numbers?

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