The Guide to the Salesforce CPQ Sunset and Revenue Cloud Migration

For years, Salesforce CPQ (formerly known as SteelBrick) has been the backbone of quote-to-cash operations for thousands of enterprise organizations. It shaped how sales teams handled complex pricing, sophisticated product bundling, and automated contract generation. However, the enterprise software landscape is shifting, and what once represented the standard in sales automation is now being strategically retired to make way for a more unified, scalable, and native architecture.

The official announcement of the Salesforce CPQ sunset has forced Revenue Operations (RevOps), IT, and finance departments worldwide to reassess their technology stack. Specifically, the legacy Salesforce CPQ end of sale 2025 marks a critical turning point for businesses. As of March 2025, no new licenses for the legacy managed package are being sold to net-new customers. Salesforce is directing all future investment and customer onboarding toward its modern successor: Salesforce Revenue Cloud.

For businesses currently relying on legacy CPQ, this is not merely an impending software update; it is a prompt to evaluate and modernize your entire revenue architecture. Preparing for a comprehensive Revenue Cloud migration requires a strategic understanding of the timeline, the fundamental architectural differences between the two platforms, and the downstream impact on connected enterprise systems such as your ERP and billing engines.

This guide will break down the true urgency of the CPQ end of sale, explore the new platform's capabilities, and provide a CPQ replacement roadmap to help your organization migrate from Salesforce CPQ to Revenue Cloud without disrupting your daily revenue flow.

1. The Reality of the Legacy Salesforce CPQ End of Sale 2025

To navigate this transition effectively, organizations must first understand the difference between "End of Sale" (EOS) and "End of Life" (EOL).

The legacy Salesforce CPQ end of sale 2025 means the product is no longer commercially available to new buyers. Existing customers can still renew contracts, add seats, and continue utilizing their customized setups. Standard support and critical security patches will be maintained in the near term.

However, the Salesforce CPQ sunset effectively freezes the platform in time. Meaningful product innovation has ceased—modern demands such as native usage-based billing, AI-driven dynamic pricing, and seamless multi-channel composability will not be retrofitted into the legacy managed package. While a hard End of Life (EOL) cutoff has not been officially announced by Salesforce, the practical cost of staying on the legacy system compounds over time. Businesses that remain will accumulate technical debt, experience slower support resolution, and fall behind organizations leveraging modern quoting systems.

For the latest on Salesforce's official support timeline, refer to the Salesforce Product & Feature Retirement page.

2. Exploring the CPQ Replacement: Enter Salesforce Revenue Cloud

As the CPQ replacement, Salesforce Revenue Cloud is positioned not just as a quoting tool, but as an end-to-end Revenue Lifecycle Management (RLM) platform.

The most critical distinction is that Revenue Cloud is built directly on the core Salesforce platform (Core CRM). Unlike legacy SteelBrick, which operated as a managed package sitting on top of the CRM with its own custom objects and unique data models, Revenue Cloud utilizes an API-first, metadata-driven architecture.

This natively integrated approach breaks down the traditional silos between sales, legal, and finance. It allows for high-performance pricing engines, seamless integration with Agentforce (Salesforce's AI agents), and a composable product catalog that can serve direct sales, partner portals, and self-service e-commerce channels simultaneously.

For technical details on Revenue Cloud's architecture, see the Salesforce Revenue Cloud documentation.

3. Revenue Cloud vs Salesforce CPQ Feature Comparison

To understand why a CPQ migration is necessary, it helps to see how the features fundamentally differ. Below is a Revenue Cloud vs Salesforce CPQ feature comparison highlighting the key differences between the two systems.

When analyzing Revenue Cloud Advanced vs legacy CPQ, it becomes clear that the new platform is designed for agility. Instead of creating hundreds of separate SKUs for a product that comes in different sizes and colors, Revenue Cloud utilizes dynamic attributes, drastically simplifying catalog maintenance.

4. Revenue Cloud Advanced vs Legacy CPQ: Why It's a Rebuild, Not an Upgrade

One of the most common misconceptions among RevOps teams is that the move to the new system will be a standard software upgrade. It isn't.

Because of the architectural differences outlined above, you cannot simply press a button to migrate from Salesforce CPQ to Revenue Cloud. It is a fundamental reimplementation of your quote-to-cash logic.

Your existing custom Apex triggers, complex JavaScript pricing calculators (QCP), and legacy Price Rules will not translate directly into Revenue Cloud's Business Rules Engine. Your data model must be meticulously remapped—for example, transitioning legacy Quote Lines into new Transaction Line Items. This reality makes the Revenue Cloud migration an opportunity to clean house. Before moving, organizations should audit their product catalogs, retire unused SKUs, and eliminate convoluted pricing workarounds that were built to bypass limitations of the old system.

Should You Migrate Now or Wait?

The right timing depends on your specific situation. Consider these factors:

• Contract renewal timing: If your Salesforce renewal is within 12 months, start planning now. Migration projects for mid-market to enterprise organizations typically take 6–12+ months depending on complexity.
• Catalog complexity: Organizations with fewer product SKUs and simpler pricing logic will have a shorter migration path. If you have hundreds of heavily customized SKUs, start the catalog audit immediately.
• Custom code footprint: Heavy QCP (JavaScript) customization and Apex triggers mean more rebuild work. Assess how much of your current logic is custom vs. declarative.
• Downstream dependencies: If your CPQ feeds into ERP, billing, or revenue recognition systems, factor in integration rebuild time.
• Business appetite for disruption: If a parallel-run approach (see Section 6) fits your operations, you can migrate incrementally. If your business requires a harder cutover, you'll need more planning runway.

Organizations with simple configurations and near-term renewals should prioritize migration planning. Those with complex setups and renewals further out have more time but should still begin assessment and catalog cleanup now.

Post 1: " The Technical Blueprint: Data Mapping and Architecture for Your Revenue Cloud Migration"

5. Ecosystem Impact: Rebuilding ERP Integrations and Microsoft Dynamics 365

Your CPQ system does not exist in a vacuum; it is the bridge between your CRM's front-office sales data and your ERP's back-office financial ledgers. Because the underlying data model is completely changing in Salesforce Revenue Cloud, your existing downstream integrations will break and must be re-architected.

For enterprise organizations utilizing Microsoft Dynamics 365 as their financial backend, this integration rebuild requires careful planning. You must ensure that the new Transaction Line Items generated by Revenue Cloud accurately map to your Dynamics 365 finance and operations modules to preserve accurate ledgers, revenue recognition, and supply chain fulfillment.

When planning your CPQ migration, IT leadership must consult official integration frameworks to ensure data consistency between Salesforce and Microsoft ecosystems. Microsoft provides extensive, officially documented patterns for these exact cross-system enterprise scenarios.

• For high-level architectural guidance on integrating external applications with Dynamics 365, review the Microsoft Dynamics 365 Integration Guidance.
• Organizations often leverage middleware or third-party logic engines to bridge pricing data between these systems. Standard connector documentation covers how modern APIs facilitate secure, real-time data handoffs.

Treating your ERP integration as an afterthought is how CPQ implementations go sideways. Engage your enterprise architects early to map the flow of master data between Salesforce and Microsoft Dynamics 365.

6. The Path Forward: Structuring Your Migration

Given the scope of a Revenue Cloud migration, executive leadership must prioritize business continuity. A "big bang" rollout—where you shut down legacy CPQ on Friday and turn on Revenue Cloud on Monday—is highly discouraged for complex enterprises.

The most successful transition strategies rely on a phased, parallel-run approach. Organizations should establish a timeline where net-new product lines, or entirely new geographic sales regions, are onboarded directly into Revenue Cloud. Meanwhile, existing inflight contracts remain housed within legacy CPQ until they reach their natural renewal cycle, at which point they are migrated to the new architecture.

What About Alternatives to Revenue Cloud?

Revenue Cloud is the natural successor within the Salesforce ecosystem, but it's not the only option. Organizations with significant concerns about Revenue Cloud maturity or fit should also evaluate third-party CPQ platforms—such as DealHub, Conga (formerly Apttus), or Zuora—particularly if their pricing models are heavily usage-based or if they're considering reducing their Salesforce footprint. Each alternative comes with its own integration trade-offs, and the right choice depends on your specific tech stack and business model.

Post 2: " Business Strategy: Timelines, TCO, and Alternatives to Revenue Cloud"