Revenue Cloud
Delivering Salesforce Revenue Cloud: A Practical Guide for Partners
How Revenue Cloud works under the hood, what changes coming from Salesforce CPQ, and how partners can deliver faster, lower-risk projects.

Written by
Prodly Marketing
Published on
Updated on
Revenue Cloud is quickly becoming the center of quote-to-cash work in the Salesforce ecosystem. For partners, that means a growing pipeline of implementations, CPQ migrations, and ongoing optimization work, along with a new architecture that rewards teams who understand it deeply.
This guide covers how Revenue Cloud is built, what changes for teams coming from Salesforce CPQ, and the delivery practices that keep projects on schedule.
Where Revenue Cloud came from
Until 2024, Salesforce pricing capabilities had grown up separately across Sales Cloud, Salesforce CPQ, B2B Commerce, and Salesforce Industries. In early 2024, Salesforce launched Revenue Lifecycle Management as a single native platform for quote-to-cash that also extends product catalogs and quoting to partners and customers. It was renamed Revenue Cloud Advanced later that year, and Agentforce Revenue Management in 2025. As of September 2026, it's simply Revenue Cloud again, though you'll still see the Agentforce Revenue Management name across Salesforce documentation and Trailhead.
At the same time, Salesforce moved CPQ to end of sale in March 2025. Existing customers can still renew, add users, and get support, but no new CPQ licenses are sold. Clients on CPQ are now planning their move, and new implementations are starting on Revenue Cloud from day one. Both create work for partners who know the platform.
How Revenue Cloud works
Standard objects at the foundation
Revenue Cloud is built on the familiar Sales Cloud standard objects: Product, Price Book, Price Book Entry, Opportunity, Quote, and Quote Line Item. Quotes still depend on Price Book selection, so price book design is a fundamental decision in any pricing solution. Get the price book strategy wrong early and it will follow you through every phase of the project.
Product Selling Models
The Product Selling Model object defines how a product is sold: as a one-time sale, a term-defined subscription, or an evergreen subscription, with monthly or annual pricing terms for subscriptions. A product can carry multiple selling models, with a Price Book Entry for each one. For clients with mixed one-time and subscription offerings, this removes a lot of the product duplication that older setups relied on.
Catalogs and Categories
Products are assigned to Categories, which belong to Product Catalogs. These drive product discovery during quoting, and a product can sit in multiple categories and catalogs. Catalog design is a business conversation as much as a technical one, so bring sales leadership in early.
Pricing Procedures
The pricing engine is where Revenue Cloud departs most from what CPQ teams know. Pricing Procedures are built on Expression Sets from Salesforce's Business Rules Engine, originally developed for Salesforce Industries. They chain together pricing elements that read from Decision Tables, and those Decision Tables pull data from Salesforce objects and must be refreshed when that data changes.
The standard elements include List Price, Volume Discount, Tier Discount, Attribute-Based Price, Bundle-Based Price, Formula-Based Pricing, Manual Discount, Subscription and Proration elements, Price Adjustment Matrix, Derived Price, Aggregate Price, and Rounding Values. Account-specific contract pricing is handled within the List Price and Volume Discount elements through a "Use contract-based pricing" setting.
Context Definitions
Context Definitions are the data sets that feed processes like pricing. They're made up of nodes and attributes, attributes map to specific objects and fields, and context tags make those attributes available inside Pricing Procedures. Context is the bridge between your data model and your pricing logic. Most client-specific pricing requirements eventually touch it.
What changes for teams coming from Salesforce CPQ
Salesforce CPQ is a managed package. Revenue Cloud runs natively on the platform using standard objects, with an API-first design that Salesforce positions as faster and more reliable at scale. That shift reaches every layer of a client's setup.
A few practical consequences for migration projects:
Pricing logic gets rebuilt
Price rules and discount schedules have no one-to-one equivalent. Expect to redesign pricing in Pricing Procedures rather than translate it line by line.
The install base moves to managed assets
CPQ subscriptions and assets consolidate into Revenue Cloud's managed assets, which are designed to track the full lifecycle of what a customer owns, from amendments and renewals to cancellations.
Transactions are scoped to what's open
Migration focuses on current quotes and orders, since the two pricing engines differ too much for historical transactions to carry over practically.
Catalog and pricing design deserve a fresh look
Successful migrations pair a data migration platform with advisory work to redesign product catalogs and pricing around what Revenue Cloud can do.
Scoping is where partners win or lose margin on these projects. Our free Revenue Cloud implementation guide walks through the planning decisions in detail, from catalog redesign to install base strategy.
The hard part of delivery: configuration data
Every Revenue Cloud implementation lives or dies on configuration data. Products, selling models, price book entries, catalogs, categories, price adjustment tiers, attribute adjustments, and bundle adjustments are all records, and they're all connected.
That creates three delivery problems.
Moving configuration between environments
A realistic project runs through development, QA, UAT, and production. Each move means carrying hundreds or thousands of related records while preserving every relationship between them. Spreadsheet exports and record IDs break the moment two orgs drift apart.
Keeping environments in sync after the move
Revenue Cloud adds its own maintenance steps. After product and pricing changes land in an org, you need to refresh Decision Tables, sync pricing data, and rebuild the product index for product discovery. Skip any of them and testers report pricing bugs that don't exist.
Migrating from CPQ
Moving a client's CPQ catalog, pricing, and install base means transforming data from one object model into another, often across multiple test cycles before cutover. Prodly Migrate automates that transformation, so your team can rerun migrations as the design evolves instead of rebuilding scripts each cycle. Once you're live, Prodly DevOps uses the same data sets to carry ongoing deployments forward.
For ongoing deployments, the fastest teams treat configuration data as a release artifact: versioned, repeatable, and deployed the same way every time. Prodly offers pre-built templates for Revenue Cloud, which deploy the full configuration data model without mapping every object relationship by hand.
Best practices for partners delivering Revenue Cloud
Design price books and catalogs before you build
Price book selection drives quoting, and catalog structure drives product discovery. Settle both with the client before configuring a single product.
Extend the standard contexts
The recommended approach is to extend the standard Sales Transaction and Product Discovery context definitions into custom ones, activate them, and point your Pricing Procedures at the extended versions. This gives you room to customize without touching what Salesforce ships.
Start Pricing Procedures from the templates
Create custom Pricing Procedures by saving a copy of the Revenue Management Default Pricing Procedure from Expression Set Templates. Then assign it in both Salesforce Pricing Setup and Revenue Settings, plus Product Discovery Settings if it should drive catalog prices. Pricing Setup covers API calls, while Revenue Settings controls pricing on quotes and orders, so missing either one is a common setup mistake. Version your procedures and document which version is active in each environment.
Put the post-deployment steps in every runbook
Make Decision Table refreshes, pricing data sync, and product index rebuilds a standard post-deployment step. It eliminates a whole category of false defects during UAT.
Use scratch orgs for enablement
Scratch orgs last up to 30 days, can be created on the preview release to test upcoming features, and can be snapshotted to duplicate a configured org with its data. That makes them useful for demos, team training, and testing new features before they reach a client.
Plan your data movement strategy at kickoff
Decide how configuration will move between environments before the first sprint. Changing approach mid-project is expensive, and clients notice when environments fall out of sync.
Building a Revenue Cloud practice
Revenue Cloud rewards partners who invest in understanding its architecture, from pricing procedures and context definitions to the configuration data underneath. The teams that build repeatable delivery processes now will carry that advantage into every implementation and migration that follows.
If you're scoping a Revenue Cloud project or planning a CPQ migration for a client, talk to the team at Prodly.
© 2026 Prodly. All rights reserved.



