If you run Salesforce CPQ today, you face a timing question, not an emergency. Your options are to stay put, reimplement on Revenue Cloud Advanced, or keep Salesforce CRM and replace only the quoting layer. Salesforce stopped selling Salesforce CPQ to new customers in March 2025. Existing customers can still use it, renew it, add users and get support, and Salesforce has not announced an end-of-life date. This guide gives you a decision framework for a Salesforce CPQ migration. It covers what should push you to act now, what justifies waiting, and how to judge migration risk either way.
TL;DR
- Salesforce CPQ is end of sale, not end of life. You can renew, add users and receive support. Nothing forces you to migrate, and there is no published end-of-life date.
- Salesforce now invests in Revenue Cloud Advanced (RCA), which is part of Agentforce Revenue Management. Moving to RCA means a reimplementation with a different data model and configuration approach. It is not an upgrade.
- Waiting is a legitimate choice if quoting is stable, complexity is moderate and your renewal economics are acceptable. In the short term, waiting costs you little and buys planning time.
- Migrating sooner makes sense when the business pain is already real. Signs include quoting performance problems, rule maintenance that needs specialists, a growing amount of Quote Calculator Plugin (QCP) and custom code, middleware sprawl, or a product and pricing roadmap that Salesforce CPQ cannot support.
- Base the decision on your own roadmap, not the vendor's. Score pain, pressure and planned change over the next 18 to 24 months. If two or more are pressing, a Salesforce CPQ migration usually earns its place in the plan.
What End of Sale Actually Changes for You
End of sale changes who can buy Salesforce CPQ. It does not change whether you can keep running it. Salesforce no longer sells Salesforce CPQ to new accounts. Existing customers keep access and support, and they can renew and add users. Salesforce has not announced an end-of-life date.
What has changed is the pace of innovation. Salesforce CPQ (configure, price, quote) no longer gets meaningful new feature development, and Salesforce's strategic investment has moved to Revenue Cloud Advanced. In our assessment, this creates a widening capability gap between Salesforce CPQ and dedicated CPQ platforms. That gap grows slowly rather than arriving on a cutover date.
This distinction matters for your CPQ renewal. You are not negotiating against a shutdown deadline. You are negotiating for a product that is stable but no longer gaining features, which is a much more manageable position.
The Three Paths, Stated Plainly
There are three credible paths, and each fits a different profile. Here they are briefly, in terms of timing. For full fit criteria, see the three paths compared.
Path 1: Stay on Salesforce CPQ for now
Salesforce CPQ remains a reasonable fit in three situations: your configuration needs are low to moderate, your quoting happens entirely inside the Salesforce ecosystem, and your workflow needs are not complex. If that describes you, staying is not avoidance. It is a sensible use of your budget and your team's capacity for change.
Staying makes the most sense when:
- Quote volume is manageable.
- Your rule set is stable.
- Admins can make routine changes themselves.
- Your product roadmap for the next two years adds no new configuration or revenue-model complexity.
Path 2: Reimplement on Revenue Cloud Advanced
Revenue Cloud Advanced is Salesforce's strategic successor. It keeps CRM, quoting and billing with a single vendor. It covers more of the revenue lifecycle than Salesforce CPQ. In our assessment, though, it offers less depth on configure-price-quote specifically than dedicated CPQ platforms do.
Be realistic about scope. Plan for this move as a redesign. RCA uses a different data model and a different approach to the catalog and configuration, and your existing SBQQ configuration does not carry over directly. Treat it as a new implementation plus a data migration, and budget for testing accordingly.
Path 3: Keep Salesforce CRM and replace only the quoting layer
The third path is often overlooked. You keep Salesforce CRM as your system of record and replace only the CPQ layer with a dedicated configure-price-quote platform. This has the narrowest scope of the three. It fits when your CRM, reporting and sales process are working and only quoting has reached its limits.
A Decision Framework: Migrate or Wait
Base the decision on three inputs: current pain, commercial pressure and planned change. Don't react to headlines.
Signals that favor waiting
- Quotes generate quickly and reliably at your current volume and catalog size.
- Your admins can add products and adjust pricing rules without bringing in a consultant.
- You have few or no QCP customizations and little custom Apex around quoting.
- Your CPQ renewal terms are acceptable, and your contract gives you time to plan.
- No major product launch, pricing model change or acquisition is scheduled in the next 18 months.
Signals that favor acting now
- Quoting performance problems appear as catalogs, nested bundles or rule volume grow, and reps fall back to spreadsheets.
- Product complexity has outgrown the rules engine, which leads to misquotes and manual workarounds.
- Changes to pricing rules, product rules or quote templates need specialist or partner help, so every change brings an invoice or a delay.
- Your stack relies on middleware or custom code to sync pricing, inventory or bill of materials (BOM) data between CPQ and your enterprise resource planning (ERP) system.
- Renewal costs have risen while new features have stopped arriving.
- Your roadmap needs capabilities Salesforce CPQ was not designed for. Examples include engineer-to-order (ETO) and configure-to-order (CTO) products, multi-level BOMs, and quotes that combine hardware, labor, projects, services, subscriptions and recurring revenue.
How to weigh them
Score each category honestly. If quoting is only imperfect, wait and plan. If two or more categories are pressing, waiting is no longer a neutral choice, because you keep investing in a platform you plan to leave. An example would be performance problems combined with a roadmap that Salesforce CPQ cannot support.
Understanding Migration Risk on Either Path
Every path except doing nothing carries migration risk. The biggest risks are rarely about licensing. They are missed scope and regressions, meaning things that worked before stop working.
Before you choose, take an inventory of everything you actually run:
- Products and nested bundles
- Product rules and price rules
- QCP scripts
- Approval workflows and quote templates
- Intégrations
- Open quotes, contracts, subscriptions and assets
- Every report that depends on SBQQ objects
The size of that inventory determines your effort and your migration timeline. A vendor's schedule does not.
Next, look at architecture. Some replacements copy CRM data into a separate platform and sync it back. That creates downstream risks: stale or mismatched records, sync failures and delays, duplicate records that need reconciling, reports built on a copy instead of the source, more middleware to maintain, and governance questions about where customer and pricing data now lives. Treat where the quote data lives as a top selection criterion, not a technical detail.
Finally, plan for both systems to run at once. Running your current system alongside the replacement for a set period, with a tested rollback plan, protects revenue better than switching over all at once.
Where Experlogix CPQ Fits in the Decision
Experlogix CPQ is mainly relevant to the third path, where you keep Salesforce CRM and replace only the quoting layer. It integrates with Salesforce CRM and runs inside the Salesforce workflow. Reps configure, price and quote without ever feeling like they've left Salesforce. There is no separate login, and reps don't have to switch away from the opportunity and account records they already use.
Experlogix does more than read data from Salesforce. It writes enriched configuration details, pricing calculations and approval status back to Salesforce in real time, and it can write to standard or custom Salesforce objects without developers. Its Cloud Connect integration syncs quotes, orders and approvals across CRM and ERP without custom code. This removes the middleware and point-to-point integrations that break with every platform update.
For complex quoting, Experlogix brings industrial-grade capabilities to Salesforce. These include hundreds of configuration options, multi-tier pricing, guided selling, BOM and routing automation for the handoff to ERP in manufacturing, and data that flows both ways between CPQ and CRM. A low-code rule builder lets business users manage configuration and pricing logic, so routine changes depend less on developers or consultants.
Experlogix is not the right fit for everyone. Another path may serve you better if your catalog is simple or your quoting is subscription-only and self-service. The same applies if your organization has already committed to a Revenue Cloud Advanced reimplementation for billing and revenue lifecycle reasons. Replacing only the quoting layer makes the most sense when quoting is complex: deep configuration, manufacturing output, and mixed revenue streams on a single quote.
The Bottom Line on Timing Your Salesforce CPQ Migration
Salesforce CPQ end of sale is a reason to plan, not a deadline. You can renew, add users and receive support, and no end-of-life date has been announced. That lets you decide on your own schedule, based on evidence.
Reimplementing on Revenue Cloud Advanced is a redesign. Compare it fairly with replacing only the quoting layer while you keep Salesforce CRM. Both are real projects, and the question is which one serves your roadmap. Waiting is a sound choice when quoting is stable and complexity is moderate. Acting is the better choice when performance, administration costs, reliance on middleware, or planned product and pricing changes are already straining the platform.
Teams that make this call deliberately tend to face fewer surprises in their next budget cycle. They know their rule inventory, they know which customizations won't survive a move, and they negotiate renewals with options in hand instead of under pressure.
A practical next step is to build your migration-readiness inventory. Document every product bundle, product rule, price rule, QCP script, approval path, quote template and downstream integration. Then take your hardest real quote, not a demo catalog, and use it to test every path you are considering.
FAQ
Can I stay on Salesforce CPQ?
Yes. Existing customers can keep using Salesforce CPQ, renew it, add users and receive support, and Salesforce has not announced an end-of-life date. Staying makes sense when quoting is stable, complexity is moderate and your renewal terms are acceptable. The trade-off is that Salesforce CPQ no longer gets meaningful new feature development.
When should a company migrate off Salesforce CPQ?
Consider migrating when two or more of these three are pressing over the next 18 to 24 months:
- Current pain, such as performance or maintenance problems
- Commercial pressure, such as worsening renewal costs
- Planned change, such as new products, pricing models or acquisitions
If quoting is only imperfect, use the time to plan instead.
What are the signs Salesforce CPQ no longer fits?
Common signs include:
- Quote generation slows and reps fall back to spreadsheets.
- Product complexity outgrows the rules engine and causes misquotes.
- Routine rule or template changes need specialist help.
- Pricing, inventory or BOM data depends on middleware or custom code to sync with ERP.
- Renewal costs rise while new features stall.
- Your roadmap includes ETO or CTO products, multi-level BOMs, or quotes that mix products, services, labor, projects and recurring revenue.
What coexistence or parallel-run strategy protects revenue continuity during a CPQ transition?
Because Salesforce CPQ remains supported, you can run it alongside the replacement for a set period instead of switching over all at once. Test the new system with your hardest real quotes and keep a tested rollback plan. Retire the old system only after the new one produces matching quotes, approvals and downstream data.
What should be included in a Salesforce CPQ migration inventory?
At a minimum, include:
- Products and nested bundles
- Product rules and price rules
- QCP scripts
- Approval workflows and quote templates
- Intégrations
- Open quotes, contracts, subscriptions and assets
- Every report that depends on SBQQ objects
The size of this inventory, more than any vendor schedule, determines the effort involved in your migration.
Test your hardest quote, not a demo catalog
