Salesforce CPQ End-of-Sale: What RevOps Teams Need to Do Now

If you’re running revenue operations on Salesforce CPQ, you’ve probably seen the announcement. In March 2025, Salesforce officially declared CPQ “End of Sale.” No new customers. No new features. No product investment. The product is frozen.

What most organizations haven’t done yet is act on it. Fourteen months in, the majority of CPQ customers are still in wait-and-see mode. That window is closing, and the cost of waiting is no longer theoretical.

Where Most Teams Are Right Now (And Why That’s a Problem)

The majority of organizations still on Salesforce CPQ filed the EOS announcement under “deal with later.” That made sense in Q2 2025. It doesn’t make sense anymore.

Here’s the timeline playing out in real time:

• 2025 to 2026: Support slows. Bug resolution takes longer. Salesforce begins redirecting partner and internal resources away from CPQ
• 2026 to 2027: Aggressive Salesforce campaigns begin pushing Agentforce Revenue Management migrations. Expect upsell pressure, reduced legacy discounts, and expiring incentive offers
• 2027 to 2028: Formal End of Life announcement expected, with migration deadlines attached
• 2029 to 2030: Full support sunset, based on typical enterprise software patterns. Salesforce has not confirmed an official EOL date

The companies that start now get to make a deliberate decision. The ones that wait until 2027 will be making a reactive one, under contract pressure, with fewer implementation partners available and less negotiating leverage.

That window is closing faster than most executives realize.

The Honest Truth About Migrating to Agentforce Revenue Management

Salesforce rebranded Revenue Cloud Advanced to Agentforce Revenue Management at Dreamforce 2025. It’s a meaningful evolution, with AI agents embedded directly into quoting, contracting, billing, and renewal workflows. The platform is genuinely compelling for organizations that are ready for it. For a full breakdown of how it compares to legacy CPQ, read our guide here.

But Salesforce’s sales motion can obscure some realities worth knowing before you commit.

It’s a reimplementation, not an upgrade. Agentforce Revenue Management is built natively on Salesforce core using standard objects. Legacy CPQ runs as a managed package. These are fundamentally different architectures. Your pricing rules, product bundles, CPQ scripts, and Quote Line Editor customizations don’t carry over. Everything gets rebuilt.

The timeline is longer than the pitch deck suggests. Most enterprise migrations run 12 to 18 months. Organizations with complex product catalogs, multi-territory pricing, or deep ERP integrations should plan for the longer end of that range, and budget for it accordingly.

Licensing costs will go up. Agentforce Revenue Management is priced at a premium over legacy CPQ. Factor that into your business case before you start building one.

The platform is still maturing. The Winter ’26 and Spring ’26 releases have added meaningful improvements: multi-order creation from a single quote, new pricing formulas, and deeper Agentforce AI integration for forecasting. But some capabilities that CPQ customers take for granted are still being developed on the new platform. Evaluating ARM today is different from evaluating it in 2023.

None of this means Agentforce Revenue Management is the wrong answer. For many organizations, it’s exactly the right one. But going in with clear eyes about the scope is what separates a successful migration from a troubled one.

5 Things RevOps Teams Need to Do This Year

1. Audit Your CPQ Environment Before Anyone Touches Anything

This is the step most teams skip, or do too quickly, and it’s the one that causes the most pain downstream.

Before any vendor conversation, document:

• Every active product bundle, pricing rule, and quote template currently in use
• All custom scripts, flows, Apex triggers, and third-party integrations connected to CPQ
• Where quotes break down and require manual workarounds: spreadsheets, offline approvals, side tools
• Your Salesforce renewal date and current contract terms

Two things come out of this audit. First, you get a realistic read on how complex your migration actually is. Second, and more importantly, you get clarity on what your business actually needs today versus what it needed when CPQ was first configured.

Most teams discover their CPQ environment was built for a version of the business that no longer exists. That’s useful information before you spend 18 months rebuilding it.

2. Get the Right People Aligned Before You Schedule a Single Demo

The technical work is rarely what derails a CPQ migration. It’s the organizational work.

Sales leadership, the CFO, and RevOps need to be aligned on three things before any vendor is brought into the conversation:

• Why now. Not “because EOS happened.” That’s not compelling to a CFO. The real reason is that legacy CPQ is already limiting revenue velocity, forecasting accuracy, and AI readiness in ways that have a measurable cost
• What winning looks like. “Quotes still generate” is not a success metric. Faster cycle times, cleaner revenue data, fewer approval bottlenecks, and a quote-to-cash process that scales with the business are
• How this connects to the broader strategy. Boards in 2026 want to see AI-ready infrastructure, tighter alignment between sales and finance, and unified revenue forecasting. A CPQ migration done right addresses all three. Done poorly, it’s just a disruptive IT project

Executive sponsors who understand the strategic dimension will make decisions faster and defend the investment better when the project hits its inevitable rough patches.

3. Ask These Questions Before You Commit to Any Path

Most RevOps teams jump to platform evaluation before they’ve answered the questions that should drive the decision. These are the ones that matter:

• Is Salesforce our long-term system of record, or are we operating across multiple CRMs?
• Are we moving toward usage-based, subscription, or consumption pricing in the next two years?
• How M&A-active is the business? Acquisitions stress CPQ environments in ways that become visible only after they close
• What’s the current state of our product catalog data? Is it clean enough to migrate, or does it need a full rebuild first?
• Do we have the internal bandwidth to run an 18-month implementation alongside business as usual?

The answers don’t point to one universal path. They point to your path.

4. Treat Data Cleanup as a Standalone Project, Not a Migration Task

This is consistently the most underestimated piece of the entire process, and it applies regardless of where you end up migrating.

Most CPQ environments accumulate years of catalog debt: SKUs that were deprecated but never deleted, pricing rules that contradict each other, bundles that were built for one-off deals and never cleaned up, and product data that was accurate when someone entered it in 2019.

Migrating dirty data to a new platform doesn’t fix it. It just gives you the same problems in a new environment, with a more expensive support contract.

Start the cleanup now, separately from any migration planning, because:

• It reduces migration complexity and cost regardless of which platform you choose
• It speeds up your current quoting process in the meantime
• Agentforce Revenue Management’s AI capabilities, the ones Salesforce is selling you on, require clean, structured data to actually work

This work is unglamorous. It’s also the highest-ROI thing a RevOps team can do in the next six months.

5. Start Vendor Evaluation This Quarter, Even If You’re Not Ready to Buy

The gap between “we should look at this” and “we’re ready to start” is where most organizations lose a year.

You don’t have to be ready to migrate to begin a structured evaluation. What you need to do this quarter is:

• Map your current state requirements against what’s available on the market today
• Understand what Agentforce Revenue Management actually delivers in 2026, not what was on the roadmap in 2023
• Get a realistic implementation estimate for your specific environment, not an industry average
• Build a business case with numbers your CFO will recognize

Companies that complete this work now have real advantages. They negotiate from a position of knowledge. They have time to choose the right implementation partner rather than whoever is available. And they don’t get rushed into a decision by a contract renewal deadline.

What This Looks Like by Industry

The five steps above apply universally. How they play out depends heavily on your vertical.

High Tech and SaaS

This is where CPQ complexity tends to be highest. Usage-based pricing, professional services bundles, multi-tier channel pricing, and product catalogs that change faster than any other industry. The good news is that Agentforce Revenue Management was largely built with this segment in mind. The AI-driven quoting, consumption billing, and Agentforce integration are genuinely valuable here.

The challenge is that High Tech organizations also tend to have the most heavily customized CPQ environments. The audit in Step 1 is especially critical before assuming ARM is the right path.

Manufacturing

CPQ in manufacturing doesn’t sit in isolation. It’s connected to ERP, supply chain, inventory, and configure-to-order workflows in ways that a standard Salesforce migration plan rarely accounts for.

Any path forward needs to start with those integration dependencies, not with the Salesforce platform decision. Choosing ARM and then discovering your ERP integration requires a six-month rebuild is an avoidable problem.

Healthcare Life Sciences

Compliance adds a layer that pure technical migrations tend to underestimate. Pricing rules, approval workflows, and audit trails in HLS environments need to be validated against regulatory requirements, not just functional requirements.

The data cleanup step is also more sensitive here. Patient-adjacent and contract data governance requirements mean the catalog cleanup process needs legal and compliance sign-off, not just RevOps.

Semiconductors

Long sales cycles, complex product configurations, and significant channel complexity make semiconductor CPQ environments among the hardest to migrate cleanly. The evaluation question here is almost always whether ARM’s native capabilities are mature enough for the specific configuration requirements, or whether a composable, vendor-agnostic approach makes more sense.

The Bottom Line

The decision isn’t whether to move off Salesforce CPQ. That’s settled. The decision is when, where, and how. And those answers look different for every organization.

The teams that come out ahead won’t necessarily be the fastest. They’ll be the ones that audited honestly, aligned internally before the vendor conversations started, asked the hard questions before committing, and built a migration plan around where the business is going rather than where it’s been.

If your team is still running on Salesforce CPQ and hasn’t mapped out a path forward yet, that’s the work, and it starts now. Schedule a discovery call with N28 Technologies to walk through where your current environment stands, what your options actually are, and what a realistic transition plan looks like for your org.