Salesforce CPQ still runs. Support is still active, renewals still process, and nothing breaks on Monday morning. That is exactly why so many teams have spent the last eighteen months doing nothing about it. The problem is that the cost of this decision was never support risk — it is that Salesforce’s own path forward is a rebuild, and every quarter you wait makes that rebuild bigger. Here is where things actually stand in September 2026, and the three options on the table, including the one most evaluations skip.
Where things actually stand
Salesforce moved CPQ to end of sale in March 2025. No new customers, no new licenses, no forward roadmap. Existing customers kept support and renewals, and still have them. What Salesforce has never published is an end-of-life date — partner commentary generally points somewhere around 2029 or 2030, based on how Salesforce has retired products before, but there is no authoritative timeline to plan against.
Meanwhile the investment moved. Revenue Cloud Advanced became the product Salesforce sells and builds on, and the Spring ’26 release rebranded that bundle as Agentforce Revenue Management. Legacy CPQ is a managed package sitting outside the core object model those agents run on.
Why “still supported” is the trap
Support is not the thing that will hurt you. Two other things will.
Your customizations are now migration scope. Every price rule, approval chain, quote template variant and integration you add to legacy CPQ this quarter is one more item on a future project plan. The list only grows. Teams that start evaluating while the list is short choose on their own terms; teams that wait choose under renewal pressure with fewer options and less leverage.
You are architecturally outside the new stack. Agentforce Revenue Management runs on core Salesforce objects. Legacy CPQ is a managed package that sits outside them. Staying indefinitely is not a neutral hold — it is a decision to sit out whatever Salesforce ships next.
Three paths, honestly compared
Most teams frame this as a binary: stay, or do the Salesforce-sanctioned migration. There are three.
A migration is not an upgrade
The most expensive misconception in this whole decision is that moving from CPQ to Revenue Cloud Advanced works like a version bump. It does not. RCA is built on the core platform with a different catalog model, a different pricing engine and a different way of building the quoting UI. That is a genuine improvement in architecture — and it is also the reason the work is a rebuild rather than a migration.
Here is what that actually means when you scope it.
None of that is an argument for standing still. It is an argument for being precise about which rebuild you are signing up for, and for asking whether the org underneath the quoting layer has to move at all.
The option most evaluations skip
Legacy CPQ is a managed package on top of your Salesforce org. So the practical question is narrower than “which revenue platform do we standardize on?” It is: does replacing the quoting layer require replacing everything under it?
Mobileforce CPQ runs natively inside your existing Salesforce instance, priced per seat. Your CRM stays your CRM. Your users keep their logins and their roles. What changes is the layer that configures, prices and documents the quote.
Feature by feature
What you get out of the box against what still needs another product, a builder, or a project.
| Features | Mobileforce | Salesforce CPQ |
|---|---|---|
| Simple quoting capabilities | ||
| Ability to create a product library | ||
| Easy-to-use tools for implementation | ||
| SSO-supported CRM login and role-based access control | ||
| Multi-tiered pricing, multiple price books & methodologies | ||
| CPQ anything — products, software, subscriptions, services | ||
| All routes to market with partner & customer self-service CPQ | ||
| No-code change management for products, bundles, price books, rules, promotions, approvals & doc templates | Not easy to use | |
| Broad API support | ||
| Ability to set up bespoke use-case demos fast | ||
| No-code builder for bundling, pricing rules, product configuration | Only with Lightning and Flow Builder | |
| Built-in 3rd party integration connectors (ERP, finance, e-sign, productivity) | ||
| AI-powered CPQ agents (sales agent and sales ops admin agent) | Not for admins | |
| Beyond-CPQ modules (customer portal, joint engagement plan, onboarding, field service) | Only with separate FSM and Communities | |
| Mobile CPQ and offline accessibility | ||
| Omnichannel CPQ (direct, partner, eCommerce) | Only with Experience Builder |
Comparison reflects publicly available information as of September 2026.
When each approach makes sense
Choose Revenue Cloud Advanced if…
- Salesforce is your system of record through 2030 and beyond
- You have budget and appetite for a multi-phase rebuild
- Billing and revenue lifecycle need to live on the same platform
- Agentforce is central to your revenue roadmap
- You have dedicated internal Salesforce development capacity
Choose Mobileforce if…
- You want to keep Salesforce CRM and change only the quoting layer
- The rebuild timeline is the blocker, not the licensing cost
- Sales ops needs to change bundles and rules without a developer
- Reps quote on site, partners quote in a portal, or both
- Quoting has to reach field service, not stop at signature
Questions to ask before you sign an SOW
Whoever you end up with, these are the questions that separate a scoped project from a discovery exercise billed by the hour.
- How many quote templates do we actually have, counting conditional sections and localized variants?
- How many price books, currencies and channel-specific lists carry their own rules?
- Which systems touch CPQ today — ERP, billing, CLM, e-sign, tax — and who re-tests each one?
- What happens to historical quotes, and what does reporting continuity look like the week after cutover?
- After go-live, when sales ops changes a bundle or an approval threshold, is that our change or a ticket?
- What does a rep do on a customer site with no connectivity?
- What is the second phase, and is it in this SOW or the next one?
Frequently asked questions
Is Salesforce CPQ end of life?
No. It reached end of sale in March 2025, which stopped new licenses and new development. Existing customers still renew and still receive support. Salesforce has not published an end-of-life date.
How long do we realistically have?
Nobody outside Salesforce knows. Partner commentary tends to point at 2029 or 2030 based on how Salesforce has wound products down historically, but that is inference, not a commitment. Plan against your own roadmap rather than a date that has not been announced.
Is Revenue Cloud Advanced the same product as Salesforce CPQ?
No. RCA is a broader revenue platform built on the core Salesforce object model, with a different catalog structure, pricing engine and UI toolkit. The Spring ’26 release rebranded the bundle as Agentforce Revenue Management.
Can we keep Salesforce CRM and replace only CPQ?
Yes. That is the third path in this article. Mobileforce CPQ runs inside your existing Salesforce org and is priced per seat, so the CRM, the users and the SSO configuration stay as they are.
What if we also use HubSpot, Dynamics or Sugar?
Mobileforce is CRM-agnostic, so a future CRM change does not force a second quoting migration.
Keep your Salesforce data. Lose the rebuild bill.
Book a 30-minute call. We’ll show you how Mobileforce CPQ runs inside your existing Salesforce org, and scope what moving actually involves for your configuration.
