Why Salesforce CPQ Customers Need to Decide What Comes Next
Salesforce CPQ is still available to existing customers, but its future direction is clear. The Salesforce CPQ deprecation process is not an immediate End of Life event. Salesforce’s current documentation explains that existing customers can continue using CPQ, add users, and renew their CPQ subscriptions.
However, for organizations considering a longer-term replacement, Salesforce’s current migration guidance recommends assessing the complexity of the existing CPQ implementation and selecting a migration strategy based on the organization’s current state, risk tolerance, and future-state design.
The key question is therefore not simply how to replace Salesforce CPQ. It is whether the business needs to move to a broader revenue-management architecture or only replace the CPQ capabilities it currently relies on.
Agentforce Revenue Management, formerly Revenue Cloud, is designed to support a broader revenue lifecycle, including product catalog management, quoting, contracting, orders, assets, subscriptions, invoicing, and usage-based pricing. Salesforce describes the transition from CPQ as an architectural shift that can require changes to the data model, business processes, integrations, and migration strategy.
A focused CPQ replacement addresses a different requirement. When the business primarily needs product configuration, pricing, discounts, quoting, approvals, and quote documents, it can replace that layer without redesigning the wider revenue architecture.
For Salesforce CPQ customers, the decision can therefore be framed around three questions:
- Keep Salesforce CPQ for now when the current implementation still meets business requirements and there is no immediate need to change the architecture.
- Move to Revenue Management when the organization needs the broader revenue lifecycle capabilities and is prepared for the associated architectural and data changes.
- Replace the CPQ layer when the main requirement is to retain core quoting and pricing capabilities without moving the entire revenue architecture to Revenue Management.
Salesforce also reports that approximately 15% of Revenue Cloud Advanced customers have migrated from Salesforce CPQ.
This article focuses on that decision: how to assess an existing Salesforce CPQ implementation, identify the capabilities the business still needs, and determine whether a broader revenue-management platform or a dedicated CPQ tool for Salesforce is the better fit.
Audit Your CPQ Setup Before Choosing a Replacement
Before selecting a replacement, document what Salesforce CPQ actually does in the current Salesforce org. The implementation may include product configuration, pricing rules, discounts, quoting, approvals, document generation, and downstream automations, as well as Apex, Flow, integrations, reports, and permissions that depend on CPQ objects.
Salesforce identifies CPQ-org complexity as the most important factor in migration-strategy selection. Its assessment framework looks at product catalog complexity, pricing logic, asset and subscription base, custom code, integrations, and geographic scope.
Group the current implementation into a few functional areas:
- Configuration: bundles, product options, dependencies, and product attributes.
- Pricing: price books, price rules, discount schedules, tiered or block pricing, contracted prices, and surcharges.
- Quoting: quotes, quote lines, revisions, and Opportunity-related processes.
- Approvals and documents: discount approvals, quote templates, and document generation.
- Supporting components: Apex, Flow, integrations, reports, dashboards, and permissions that depend on CPQ.
Then classify each capability as keep, simplify, rebuild, or remove. This assessment is also an opportunity to remove CPQ bloat. Do not automatically migrate inactive products, obsolete pricing rules, unused configurations, or customizations that are no longer required. Salesforce specifically recommends auditing pricing rules and removing inactive or redundant rules during assessment. It also recommends catalog rationalization before technical configuration begins.
Choose Between Revenue Management and a Focused CPQ Replacement
The CPQ audit also can help answer a more important question than which product to buy: does the organization need a broader revenue-management platform, or does it primarily need a replacement for its existing CPQ layer?
When Revenue Management Is the Better Fit
Revenue Management is primarily a fit for mid-to-large enterprises with complex quote-to-cash processes and revenue models that extend beyond traditional CPQ. This is especially relevant for:
- High-tech and SaaS companies with subscriptions, usage-based pricing, and recurring revenue.
- Manufacturers with complex product configurations, tiered pricing, and different pricing models across sales channels.
- Business services and IT companies managing complex contracts, account structures, and recurring services.
- Large enterprises that need quoting, contracts, orders, assets, subscription management, and billing connected across the revenue lifecycle.
Salesforce customer examples include companies such as Siemens and Cisco, which use Revenue Cloud for broader subscription, pricing, and revenue processes.
Find Salesforce CPQ Alternative
A focused replacement makes sense when the business still needs core CPQ capabilities, but does not need to redesign its wider revenue architecture. The goal is to retain the configuration, pricing, discounting, and quoting functions that remain relevant without carrying over unnecessary complexity from the existing implementation.
There are several Salesforce CPQ alternatives on AgentExchange (now AgentExchange), ranging from focused quoting and document-generation tools to broader CPQ applications. The right option depends on which parts of the existing CPQ implementation the organization needs to retain.
When evaluating the best CPQ vendor to replace Salesforce CPQ, appero quote CPQ Light is one example worth considering because it combines product configuration, pricing, and quote generation in a Salesforce-native application. It also works with Salesforce data and supports quoting processes in Sales Cloud. This makes it relevant when the CPQ audit shows that the organization mainly needs to preserve configuration, pricing, and quoting capabilities rather than move to a broader revenue platform.
The practical distinction is scope. Revenue Management addresses a wider revenue lifecycle, while a focused CPQ application can replace the specific quoting and pricing capabilities identified during the CPQ audit.
That is why the CPQ audit comes first: the replacement should fill the gaps that actually exist, rather than recreate the entire Salesforce CPQ footprint.
What About Custom Development?
Custom Apex, Flow, and Lightning Web Components can reproduce specific CPQ functions, but the development effort is only one part of the TCO. The organization also assumes ownership of testing, deployment, documentation, security, troubleshooting, and future changes to the pricing and quoting logic.
For a narrowly defined requirement, custom development may look simpler initially. However, rebuilding a substantial CPQ architecture means creating and maintaining that architecture after the original migration project is complete, which can add significant long-term technical debt and maintenance costs.
If a Salesforce-native CPQ solution already covers the required capabilities, it can be a lower-TCO alternative to rebuilding and maintaining those capabilities with custom code.
| Salesforce CPQ Replacement Options Compared | |||
|---|---|---|---|
| Factor | Revenue Management migration | Custom Salesforce development | Focused native CPQ app (appero quote) |
| Primary scope | Broader revenue lifecycle | Specific business requirements | Core CPQ and quoting |
| License cost | Revenue Cloud Growth: $150/user/month; Advanced: $200/user/month, billed annually | No license, but development and maintenance costs apply | From €37.50/user/month, with lower per-user pricing for larger license volumes and longer terms |
| Architecture impact | Significant | Depends on the solution design | Typically narrower |
| Data model changes | Significant changes to the data model | Depends on the implementation | Depends on the app and existing Salesforce model |
| Pricing migration | Requires mapping existing CPQ pricing into the new pricing model | Rebuilt in custom logic | Configured using the application’s pricing model |
| Custom-code ownership | CPQ-dependent custom code may require review or redesign | Organization owns the custom CPQ code | No custom CPQ code required for core functionality |
| Implementation effort | Broader migration and potential redesign | Development, testing, deployment, and maintenance | Focused implementation around required CPQ capabilities |
| Ongoing maintenance | Includes the new revenue architecture and related integrations | Organization owns the custom code and future changes | Depends on the application’s configuration and any required customizations |
| Time-to-value | Longer due to broader migration and architectural changes | Varies, but typically longer due to development, testing, and iteration | Faster for focused CPQ requirements, with implementation typically measured in weeks |
| Best fit | Mid-to-large enterprises that need a broader revenue lifecycle | Highly specific requirements not covered by available solutions | Businesses that need CPQ capabilities without a broader revenue-platform migration |
The choice depends on the scope and cost the business is prepared to take on. Revenue Management fits organizations that need a broader revenue architecture and can support its higher implementation and ongoing costs. For those that need core CPQ functionality without that enterprise complexity, appero quote (CPQ Light) offers a pragmatic 80/20 alternative, with implementation measured in weeks rather than months.
Cancel and Replace Salesforce CPQ with a Native Salesforce App
After identifying the required capabilities and selecting the replacement solution, the next step is to translate the existing CPQ logic into the new system. appero quote provides a practical example of how this can work: legacy Salesforce CPQ Price Rules, Summary Variables, and Product Options can be assessed based on the business logic they support and mapped to appero quote’s Product Groups, Product Properties, and pricing capabilities.
1. Map Product configuration to the new CPQ.
For example, Salesforce CPQ Product Options and bundle dependencies can be mapped to appero quote’s bundle and add-on products, Product Properties, and Product Groups.
Pricing logic can be handled in a similar way. Salesforce CPQ Price Rules and Discount Schedules can be mapped to appero quote’s scale prices, price dependencies, surcharges, discounts, and discount matrices. Requirements that use Summary Variables for grouping and aggregation can be addressed through Product Groups and their calculation capabilities.
appero quote also extends Salesforce Product2 with additional fields for quoting, while Product Properties can capture product-specific information and participate in calculations. Product Groups can organize quote items and support positioning, discounts, taxes, and grouped calculations.
2. Recreate pricing and discount logic.
Pricing is often the most complex part of a CPQ replacement. appero quote supports quantity-based pricing through Bulkprice rules, price dependencies, surcharges, and discounts at both quote-line-item and total level. Discounts can be entered manually or applied automatically through the Discount Matrix. appero quote also supports percentage or absolute markups and markdowns and lets multiple price calculations be applied in a defined sequence.
The existing Salesforce CPQ pricing logic should be translated based on the pricing results the business still needs. Quantity-based pricing, conditional discounts, and price adjustments can then be configured using the corresponding appero quote pricing and discount capabilities.
3. Recreate quote documents.
The next part of the replacement is the customer-facing quotation. appero quote includes a Template Wizard for creating quote templates with basic formatting and stationery options. Templates and their associated styles can then be further customized, including through CSS.
Templates can use Salesforce data through mergefields, which read Salesforce field values dynamically when the quote is generated. appero quote supports merge fields for Opportunity, Account, Contact, Quote, User, and Product records, and additional Salesforce fields can be configured as custom merge fields.
The quote editor also supports reusable Bricks for recurring content such as text, products, and other quote elements. Calculation elements include subtotals, net totals, gross totals, and group totals.
The document should be rebuilt around the quote requirements that remain after the Salesforce CPQ audit rather than automatically reproducing the previous template.
4. Validate the replacement before cancelling Salesforce CPQ.
The replacement should be validated against the CPQ audit before Salesforce CPQ is removed. Test the product configurations, pricing rules, discounts, approvals, and generated documents that are business-critical, including the edge cases that previously depended on Salesforce CPQ.
Only after the required functionality has been reproduced and the new quoting process has been validated should the organization proceed with cancelling Salesforce CPQ.
The goal is not to recreate Salesforce CPQ feature for feature. It is to preserve the CPQ capabilities the business still depends on while removing functionality that is no longer required.
Conclusion: Salesforce CPQ Cancel and Replace Without Moving to Revenue Cloud
Moving away from Salesforce CPQ does not automatically mean moving to Revenue Management. With Salesforce CPQ End of Sale, existing Salesforce CPQ customers can continue using the product, but questions around Salesforce CPQ End of Life also make long-term replacement planning relevant. CPQ remains widely used: 47% of companies surveyed in Copperberg’s research, with another 17% actively exploring adoption.
Revenue Management is designed for a broader revenue lifecycle and its migration from CPQ involves architectural, data-model, pricing, integration, and business-process changes. For mid-to-large enterprises that need this broader architecture and can support the associated investment, it can be the target platform.
For organizations focused on core CPQ capabilities, looking for the best CPQ software to replace Salesforce CPQ, for example like appero quote CPQ Light, offers a more focused alternative. It is a native Salesforce solution covering product configuration, pricing, discounts, and quote creation without requiring a move to the broader Revenue Management architecture.
The practical approach is to clean up the existing CPQ implementation, retain the logic the business still uses, and rebuild those requirements in the selected solution rather than reproducing the entire legacy implementation.
