Salesforce Revenue Cloud vs CPQ
What actually changed with Salesforce's move from CPQ to Revenue Cloud, what it means for your current implementation, and how to plan your migration.
The Short Version
Salesforce Revenue Cloud is the successor to Salesforce CPQ (originally SteelBrick, acquired in 2015). It's not just a rebrand — Revenue Cloud includes a new architecture, a new data model, and expanded capabilities including billing, subscription management, and revenue recognition.
Legacy Salesforce CPQ is a managed package installed on top of the Salesforce platform. Revenue Cloud is platform-native, which means better performance, easier customization, and tighter integration with the rest of Salesforce.
The catch: migrating from legacy CPQ to Revenue Cloud is not an upgrade — it's a re-implementation. Your existing CPQ configuration, custom Apex, and integrations don't carry over automatically.
Feature Comparison
What's included in legacy Salesforce CPQ vs Revenue Cloud.
| Feature | Legacy CPQ | Revenue Cloud | Notes |
|---|---|---|---|
| Product Configuration | Similar capabilities, new UI in Revenue Cloud | ||
| Pricing Rules & Discounting | Revenue Cloud adds AI-assisted pricing | ||
| Quote Document Generation | Revenue Cloud uses Dynamic Forms | ||
| Subscription Management | Native in Revenue Cloud | ||
| Revenue Recognition (ASC 606) | Built-in to Revenue Cloud Advanced | ||
| Billing & Invoicing | Unified with CPQ in Revenue Cloud | ||
| Revenue Lifecycle Management | Entirely new capability | ||
| Customization via Apex | Different APIs and extensibility model | ||
| Managed Package Architecture | Revenue Cloud is platform-native | ||
| Advanced Approvals | Redesigned in Revenue Cloud |
Migration Path: CPQ → Revenue Cloud
Typical migration takes 3-6 months. Here's the approach we use.
Assess Current State
Audit your existing CPQ setup — custom fields, Apex triggers, pricing rules, integrations, and document templates.
Gap Analysis
Compare your current functionality with Revenue Cloud capabilities. Identify what translates directly and what needs redesign.
Data Model Mapping
Map your existing CPQ objects and fields to the new Revenue Cloud data model. This is the most technical step.
Rebuild & Configure
Implement your product catalog, pricing rules, and workflows in Revenue Cloud. This is largely a re-implementation.
Data Migration
Migrate historical quotes, contracts, and subscription data. Plan for data transformation where models differ.
Test & Validate
Comprehensive testing of quote flows, pricing accuracy, integrations, and document generation.
Should You Migrate Now?
Migrate Now If...
- You need billing + subscription capabilities
- You're hitting performance limits
- You're starting a new CPQ project from scratch
- Your current implementation is minimal
Wait If...
- Your current CPQ works well and meets needs
- You have heavy custom Apex that would be costly to rebuild
- Budget is tight this fiscal year
- Revenue Cloud features haven't reached parity for your use case
Need Help Deciding?
We help companies assess their current Salesforce CPQ setup and plan migrations to Revenue Cloud. Free assessment — no commitment required.
Get a Migration Assessment