Salesforce CPQ End-of-Sale Impact on Custom Logic

Salesforce CPQ End-of-Sale: what it means for existing deployments

Salesforce CPQ has been End-of-Sale for new acquisitions since March 2025. Existing customers keep support and renewal options, but feature development on the legacy product line has stopped. New and migrating customers are being pointed at Revenue Cloud Advanced.

If your team maintains custom CPQ logic (Apex triggers, configuration rules, custom UI built on the legacy architecture), this is the moment to review all of it. Revenue Cloud Advanced generally means a full reimplementation rather than a simple upgrade path.

Impact on custom logic and extensions

The question for developers is how much of the code touches the deprecated architecture. Apex classes, Visualforce controllers and LWC components that rely on CPQ object structures (SBQQ__Quote__c, SBQQ__ProductOption__c and the rest), or on hooks into the internal calculation sequence, all need auditing.

1. Apex that runs inside the CPQ calculation sequence, or edits quote line fields off the back of standard CPQ logic, may not map directly onto the Revenue Cloud Advanced framework.
2. Pricing and discounting logic embedded in custom pricing rules or complex product bundles needs validating against the new Revenue Cloud configuration objects.
3. Revenue Cloud probably uses a different underlying data model for subscription management, consumption tracking and contract generation, so direct SOQL against legacy CPQ fields might need 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: why this counts as a reimplementation

Moving to Revenue Cloud Advanced is characterized as a reimplementation. That points to a metadata structure and a configuration model that have shifted a long way from legacy CPQ. Admins and architects should budget for a full project lifecycle rather than a patch cycle.

• Price Rules, Product Rules, Discount Schedules and Contracted Pricing records built in the legacy CPQ environment will not port over automatically.
• Historical quote and order data may need ETL work to map onto the new Revenue Cloud data structure, especially around assetization and subscription records.

Considerations for new implementations

If you are evaluating CPQ functionality now, Salesforce CPQ is off the table. That leaves alternative platforms, whether integrated through external services or native to another CRM suite. Technical diligence comes down to:

• How capable the target platform's APIs are, and where they stop, once you need custom validation or complex post-processing logic.
• What the platform offers in place of Apex hooks: the extension points you get for custom execution during the quoting lifecycle.
• The documented 67% failure rate for CPQ implementations often traces back to prerequisite maturity: undocumented rules, low transaction volume. Document every piece of pricing logic you need before you pick a replacement.