Salesforce CPQ End-of-Sale Impact on Custom Logic

Salesforce CPQ End-of-Sale: Technical Implications for Existing Deployments

The Salesforce CPQ product has reached End-of-Sale status for new acquisitions as of March 2025. Existing customers retain support and renewal options, but feature development for the legacy CPQ product line has ceased. Salesforce is directing new and migrating customers toward Revenue Cloud Advanced.

This transition mandates a strategic review for technical teams maintaining custom CPQ logic, including Apex triggers, configuration rules, and custom UI elements built atop the legacy architecture. Revenue Cloud Advanced generally requires a comprehensive reimplementation, not a simple upgrade path.

Impact on Custom Logic and Extensions

For developers maintaining existing Salesforce CPQ configurations, the primary concern is how custom code interfaces with the deprecated architecture. Any Apex classes, Visualforce controllers, or LWC components relying on specific CPQ object structures (like SBQQ__Quote__c, SBQQ__ProductOption__c, etc.) or internal calculation sequence hooks need thorough auditing.

1. Apex Triggers and Handlers: Custom Apex code executing within the CPQ calculation sequence or modifying quote line fields based on standard CPQ logic may not map directly to the Revenue Cloud Advanced framework.
2. Custom Pricing/Discounting Logic: Logic embedded in custom pricing rules or complex product bundles needs validation against the new Revenue Cloud configuration objects.
3. Data Model Changes: Revenue Cloud likely utilizes a different underlying data model for subscription management, consumption tracking, and contract generation. Direct SOQL queries referencing legacy CPQ fields might require refactoring.

// Example of existing CPQ-dependent Apex logic
public class QuoteLineProcessor {
    public static void validateLine(SBQQ__QuoteLine__c ql) {
        if (ql.SBQQ__ProductCode__c == 'LEGACY_SERVICE') {
            // Logic tied directly to old pricing structure
            if (ql.SBQQ__ListPrice__c > 10000) {
                // Throw error or adjust field
            }
        }
    }
}

Migration Pathway: Reimplementation vs. Upgrade

It is critical to understand that moving to Revenue Cloud Advanced is characterized as a reimplementation. This suggests that the underlying metadata structure and configuration paradigm are significantly altered from the legacy CPQ product. Admins and architects should budget for a full project lifecycle, not just a patch cycle.

• Existing Configurations: Existing Price Rules, Product Rules, Discount Schedules, and Contracted Pricing records built in the legacy CPQ environment will not automatically port over.
• Data Migration: Historical quote and order data may require ETL processes to map to the new Revenue Cloud data structure, particularly concerning assetization and subscription records.

Considerations for New Implementations

For organizations newly evaluating CPQ functionality, Salesforce CPQ is no longer an option. Technical assessments must focus on alternative platforms, including those integrated via external services or the native capabilities provided by other CRM suites. Technical diligence should focus on:

• API Accessibility: Evaluating the robustness and limitations of the target platform's APIs for integrating custom validation or complex post-processing logic.
• Extensibility Framework: Understanding the platform’s equivalent of Apex hooks or extension points for custom execution during the quoting lifecycle.
• Governance Risk: The high documented failure rate (67%) for CPQ implementations often relates to prerequisite maturity (undocumented rules, low transaction volume). Ensure comprehensive documentation of all required pricing logic before selecting a replacement solution.

Key Takeaways

• End-of-Sale Status: Salesforce CPQ is frozen for new customer acquisition; feature parity ends for existing customers.
• Revenue Cloud Advanced: This is the successor product, requiring a full reimplementation, not an upgrade from legacy CPQ.
• Custom Code Freeze: Existing Apex and configuration logic tied to legacy CPQ objects must be audited for compatibility and refactored for the new data model.
• Architectural Review: Treat any transition as a greenfield implementation project to account for significant configuration and data model shifts.