PLATFORM

CPQ (Configure Price Quote) FSM (Field Service Management) FRC (Field Revenue Cloud) Connected Portal

TOP INTEGRATIONS

HubSpot CRM Salesforce CRM Microsoft Dynamics CRM Creatio SugarCRM

Platform Demo

See how our platform works

REQUEST A QUOTE REQUEST A DEMO
#1 Choice for Enterprise CPQ
Dreamforce 2026 Recap

Dreamforce 2026: What Salesforce said about CPQ, and what it didn’t

The Revenue keynote was all Revenue Cloud. Legacy Salesforce CPQ got a migration tool and very little else. Here is the full picture for teams still running the managed package.

Dreamforce 2026 ran September 15–17 in San Francisco, and the main stage belonged to AI. AIforce put Salesforce inside Claude and Slack. Koa, a CRM-tuned reasoning model built with NVIDIA, got its own launch. If you only watched the main keynotes, you could have left without hearing the letters C, P and Q.

Quoting lived in one session: the September 16 Revenue keynote, titled Beyond CPQ: One Engine, Every Experience. The title tells you most of the story. Salesforce isn’t selling a better CPQ. It is selling Revenue Cloud, now branded Agentforce Revenue Management, as the platform underneath your whole revenue process. Legacy CPQ is the thing you move off of.

We went through the keynote and the partner recaps so you don’t have to. Here is what was said, what wasn’t, and what it means if you still run Salesforce CPQ.

Bottom line: Salesforce announced a CPQ Migration Assistant for December 2026 and a long list of Revenue Cloud features. It did not announce an end-of-life date, a single new feature for legacy CPQ, or what a migration will cost.

What changed: the decision in front of CPQ customers is the same one it was in August. You now have one more tool, and a much clearer view of where Salesforce is spending.

What Salesforce said  ·  What it didn’t say  ·  What it means  ·  Questions for your AE  ·  Your three options  ·  FAQ

Dec 2026Target date for the CPQ Migration Assistant
150+Customer-requested Revenue Cloud features highlighted
18Months since Salesforce CPQ went end of sale
0New features announced for legacy CPQ
Two-column chart: what Salesforce said about CPQ at Dreamforce 2026, and what it didn't say
The Revenue keynote, sorted. Everything on the left is a Revenue Cloud announcement.

What Salesforce said

1Revenue Cloud is “beyond CPQ”

Salesforce framed Revenue Cloud as one engine for the full commercial process: catalog and pricing, quotes and contracts, orders, assets, metering and rating, billing and collections. CPQ is now one piece of that engine rather than the product.

The line that stuck: you can’t have “probably right” revenue. AI can recommend an 18% discount. Revenue Cloud is the deterministic layer that checks whether the rep is allowed to give it.

2Quoting goes headless

Revenue Cloud’s pricing, quoting and approval logic is exposed through APIs and MCP, so sellers can work in Claude, Slack, ChatGPT or Gemini while the rules still run in Salesforce. The demos made it concrete. A seller built alternative proposals in Claude from call notes, then asked for a discount beyond their authority. The rules blocked it and offered a path forward. In Slack, the deal channel acted as a teammate that flagged weak deal structure and generated a branded proposal. An AI-built renewal factored in usage, support history and a negotiated cap on price increases.

3An October release, and more dates

The October release brings promotions (coupons and automated discounts), quotes up to 15,000 lines, ramp deal enhancements, and Constraint Studio for solver-guided configuration. Winter ’27 reaches general availability October 12. Revenue Cloud tools and skills through Salesforce MCP and accelerators through Salesforce Go are also targeted for October. A Revenue Cloud Skills Library is available now.

4A CPQ Migration Assistant, targeted for December

This is the one announcement aimed squarely at legacy CPQ customers. The assistant is meant to move you from the Salesforce CPQ managed package to Revenue Cloud, including configuration and not only data. That is a meaningful step up from data-migration scripts. It is also a roadmap date, not a shipped product.

5Consumption pricing, via m3ter

Salesforce announced its acquisition of m3ter in June. On stage, it laid out metering, mediation, aggregation, and richer usage pricing and billing, with first capabilities targeted for the first half of 2027.

6A customer story, and some big numbers

Workday CIO Rani Johnson described moving from a heavily customized environment to a Salesforce reimplementation on Revenue Cloud. Salesforce’s own session summary cited a 300% increase in Revenue Cloud customers and more than 80 million quotes created in the past year.

Timeline comparing Revenue Cloud roadmap dates with legacy Salesforce CPQ, which has no announced dates after its March 2025 end of sale
Every date announced at Dreamforce belongs to Revenue Cloud. The legacy CPQ track has one date, and it is in the past.

What Salesforce didn’t say

The gaps matter as much as the announcements, especially if you are building a 2027 budget around them.

1An end-of-life date

Salesforce CPQ has been end of sale since March 2025. It is still supported, still renewable, and still without a published shutoff date. Dreamforce didn’t change any of that. There is no forced migration, which means the timing of a move is still your call.

2Anything new for legacy CPQ

Every demo ran on Revenue Cloud. The Claude quoting, the Slack deal room and the AI renewal were shown on Revenue Cloud’s native objects, not on the managed package. Nothing on stage suggested the new surfaces would connect to legacy CPQ. If you stay on the package, the gap between what your reps have and what Salesforce demos will keep growing every release.

Architecture diagram: Claude, Slack, ChatGPT and Gemini connect through the Revenue Cloud rules layer to core Salesforce objects, while legacy CPQ sits outside
Legacy CPQ lives in its own managed-package objects, outside the core model the new agent experiences were built on.

3What the Migration Assistant leaves behind

“Including configuration” is a real claim. The keynote didn’t say how the assistant handles custom Apex and quote calculator plugin scripts, quote document templates, integrations to ERP, billing, CLM, e-sign and tax, or historical quotes and reporting. Those are usually where migration effort lives.

4What a migration costs, or how long it takes

Workday’s story is Workday’s. The keynote offered no timeline or effort benchmark. Salesforce’s own end-of-sale guidance puts a typical migration at three to six months, with complex orgs taking longer.

5Who runs the assistant, and whether it’s included

Nobody said whether the assistant is part of your license or something a partner scopes into a statement of work. That one detail can change a budget by six figures.

What the December Migration Assistant was announced to move, next to six areas the keynote didn't address
What was announced for the Migration Assistant, next to the work the keynote didn’t address.

The Migration Assistant makes the move to Revenue Cloud easier. It doesn’t make it smaller.

What it means if you run Salesforce CPQ today

The deadline hasn’t moved. The distance has.

Nothing announced forces your hand. But each Revenue Cloud release widens the feature gap, and each customization you add to legacy CPQ adds to the list of things you’ll rebuild later. Standing still costs more every quarter, even with no deadline.

December is a scoping date, not a go-live date

If you plan to move to Revenue Cloud, waiting for the assistant is reasonable. Plan to run it against a sandbox in early 2027 and read its output as a scope document. Whatever it can’t convert is your real project.

Decide which layer you’re replacing

The keynote presented one direction: move your revenue stack onto Revenue Cloud. That is the right answer for some teams. For others, Salesforce is the CRM they want to keep, and quoting is the only part that’s broken. Those are different projects with different price tags.

Decision flow with two questions that sort Salesforce CPQ customers into moving to Revenue Cloud, replacing only the CPQ layer, or staying on purpose
Two questions that sort most CPQ customers into the right project.

Questions to ask your Salesforce AE this quarter

Take these to your account team or implementation partner before you commit budget.

  1. What exactly does the Migration Assistant convert, and what does it flag for manual rebuild?
  2. How does it handle our quote calculator plugin, custom Apex and lookup-table price rules?
  3. What happens to our quote document templates and historical quotes?
  4. Is the assistant included in our license, or delivered through a partner SOW?
  5. Which October features need Revenue Cloud Advanced licensing, and what does that cost for our seat count?
  6. If we stay on CPQ through 2027, what support terms apply at our next renewal?

Your three options, after Dreamforce

Stay, migrate to Revenue Cloud, or replace only the CPQ layer. Dreamforce made the second option better defined. It didn’t make the other two go away.

Choose Revenue Cloud if…

  • Salesforce is your system of record for revenue and billing through 2030 and beyond
  • You want the headless, agent-driven quoting shown on stage
  • Usage-based pricing is on your roadmap
  • You have budget and internal capacity for a multi-phase rebuild

Choose Mobileforce if…

  • You want to keep Salesforce CRM and change only the quoting layer
  • The rebuild timeline is the blocker, not licensing cost
  • Sales ops needs to change bundles and rules without a developer
  • Quoting has to reach field service, partners, or both

Mobileforce CPQ runs natively inside your existing Salesforce org, priced per seat. Your CRM stays, your users keep their logins and roles, and the layer that configures, prices and documents the quote is the only thing that changes. If Dreamforce convinced you that Revenue Cloud is where your whole revenue stack belongs, the Migration Assistant is good news. If it confirmed you’d rather keep Salesforce without a platform rebuild, that’s the option we built for.

Frequently asked questions

Did Salesforce announce a CPQ end-of-life date at Dreamforce 2026?

No. Salesforce CPQ remains end of sale, as it has been since March 2025. It is still supported and renewable, with no published shutoff date and no forced migration.

When is the Salesforce CPQ Migration Assistant available?

Salesforce targeted December 2026. Treat that as a roadmap date until it ships, and confirm packaging and eligibility with your account team.

Is Revenue Cloud the same as Agentforce Revenue Management?

Yes. The Spring ’26 release rebranded Revenue Cloud as Agentforce Revenue Management, and you will see both names used. Neither is the same product as legacy Salesforce CPQ.

Will the Claude and Slack quoting demos work with legacy CPQ?

Salesforce didn’t show that. Every demo ran on Revenue Cloud’s native objects, and nothing on stage connected the new experiences to the CPQ managed package.

Can we keep Salesforce CRM and replace only CPQ?

Yes. Mobileforce CPQ runs natively inside your existing Salesforce org. Your accounts, contacts, opportunities, users and reporting stay where they are.

Keep your Salesforce org. Skip the rebuild.

Book a 30-minute call. We’ll show you how Mobileforce CPQ runs inside your existing Salesforce org, and scope what moving would actually involve for your configuration.

Book a 30-minute call

Mobileforce is an enterprise CPQ and field service platform that runs natively inside Salesforce, HubSpot, Dynamics 365, Sugar and Creatio. Dreamforce details in this post reflect Salesforce’s September 16, 2026 Revenue keynote and published roadmap statements, which may change.

Book Your Personalized Demo Today