In September 2024, “AI agents in your CRM” was the biggest story in enterprise software. Two years later, Microsoft’s own documentation says you can no longer create new instances of the Dynamics 365 Sales Close Agent as of September 30, 2026, and that existing instances will be removed on October 30, 2026. An AI agent that shipped, got adopted, and got retired inside a single budget cycle. That is not an isolated case — it is the clearest signal yet of a structural shift every CRM and ERP buyer now has to plan around: the platform you bought is being remodeled while you live in it, and nobody is putting the cost of that remodel in your budget.

Key Takeaways

• Salesforce ended support for Workflow Rules and Process Builder on December 31, 2025, and has moved Salesforce CPQ to end-of-sale — supported and renewable, but no longer receiving new feature development.
• Microsoft’s Dynamics 365 Sales deprecation list now retires AI features on the same schedule as legacy ones: Sales Close Agent (removed October 30, 2026), the preview Sales Hub Dialer (removed July 2026), and SharePoint MCP tools (deprecated August 2026).
• HubSpot replaced v1/v2/v3 API versioning with date-based versions like /2026-03/ and /2026-09/, each carrying a minimum 18-month support window — which means every integration you own now has a published expiry date.
• Zoho forced every CRM org off the classic UI in July 2026; records and automations migrated automatically, but tab groups, layouts, themes, and view preferences did not.
• “End of sale” is not “end of life.” The expensive mistake in 2026 is not ignoring deprecations — it is panic-migrating off a product that still has years of support left.
• Deprecation management is no longer a project phase. It is a permanent operating cost that needs an owner, a quarterly review, and a budget line.

Four Vendors, One Pattern

Pull the official deprecation notices from the major platforms side by side and the pattern stops looking like normal software churn.

Salesforce. Workflow Rules and Process Builder — the automation primitives that thousands of mid-market orgs were built on — reached end of support on December 31, 2025. The automations still run, but bugs found after that date do not get fixed, and you can no longer create new ones. Salesforce ships a Migrate to Flow tool that converts some logic automatically and flags the rest as partially migrated, which in practice means a real project, not a button. Separately, Salesforce CPQ is now end-of-sale: Salesforce states plainly that it is “end of sale, not end of life,” that existing customers keep licenses, add users, and renew, and that no end-of-life date has been announced — but also that the product is “in a maintenance phase — supported, but no longer receiving new feature development,” with Revenue Cloud Advanced positioned as the successor. Salesforce maintains a live Active Product & Feature Retirements list, and it is not short.

Microsoft. The Dynamics 365 Sales deprecation page is the most instructive document in enterprise CRM right now, because of how recent the retired features are. Sales Close Agent: no new instances after September 30, 2026, existing instances removed October 30, 2026, with customers redirected to the Sales Development agent. The chat-based AI setup assistant for that same agent disappears after June 2026. The Sales Hub Dialer — an embedded softphone in preview — was deprecated and removed from all environments in July 2026. Even the plumbing is churning: the SharePoint MCP tools msdyn_GetDocumentSearchResults and msdyn_SalesAnswerFromDocuments were deprecated in August 2026, and linking Dynamics 365 records to Teams channels was deprecated in May 2026.

HubSpot. HubSpot did something more consequential than retiring a feature — it rewrote the contract. As of its Spring 2026 developer release, HubSpot moved from v1/v2/v3 numbering to date-based API versioning: versions named for their ship window (/2026-03/, /2026-09/), immutable once released, with a minimum 18-month support window — roughly six months of active maintenance followed by twelve months of critical fixes only. Around that, the sunsets are stacking up: Contact Lists v1 was sunset April 30, 2026; the Pipelines API v1 is scheduled to sunset December 4, 2026; creating new legacy public apps was disabled May 26, 2026; and legacy private app creation is being removed from the account UI in late September 2026 (September 28 for newly created accounts, October 26 for older ones), with Service Keys as the replacement. The /2026-09/ version shipping September 8, 2026 also began enforcing admin-configured validation rules on every CRM API write path — a change we have written about elsewhere in the context of what breaks.

Zoho and NetSuite. Zoho retired the classic CRM interface in July 2026 on a staged schedule — July 15–17 for Free, Standard, and Professional, July 21–24 for Enterprise, Ultimate, and Bundle plans — with no opt-out. Zoho’s own guidance confirmed the good news and the bad news together: records, custom fields, workflows, blueprints, approval processes, and permissions migrated automatically, but tab groups had to be manually rebuilt as Teamspaces, and layout, theme, and view preferences reset. NetSuite, meanwhile, applies two scheduled version upgrades to every account per year — 2026.1 and 2026.2 — automatically, on Oracle’s calendar, not yours.

Why This Is Different From Normal Software Churn

Software has always deprecated things. Three things are genuinely new, and they change the math for a mid-market buyer.

First, the fastest-churning layer is now the layer vendors want your workflows in. Every vendor is pushing customers to move sales process, service routing, and document handling into agent instructions, prompts, and copilot surfaces. Those are also the features with the shortest observed lifespans. A workflow rule from 2018 lasted seven years before end of support. Sales Close Agent did not last two.

Second, deprecation moved from the UI into the integration contract. A UI retirement costs you retraining. An API version with a published 18-month floor costs you an engineering cycle on a recurring calendar, forever. If you run six integrations against HubSpot, you have just acquired six standing renewal obligations that did not exist under permanent v3 endpoints.

Third, “maintenance phase” is a real product state with real consequences. Salesforce CPQ still works, is still supported, and can still be renewed — but it will not get new capabilities. If your quoting roadmap for the next three years assumes the product improves, that assumption is now false, even though nothing was technically taken away.

What This Should Change About How You Buy

Most CRM and ERP evaluations still score vendors on features and price. Neither tells you what a platform will cost you when it changes. Add these to your evaluation and your contract:

1. Ask for the retirement history, not the roadmap. Every vendor will show you what is coming. Ask instead what they retired in the last 24 months and how much notice customers got. The published deprecation pages make this checkable before you sign.
2. Get a written notice window for end-of-sale on modules you depend on. If your business case rests on CPQ, field service, or a specific agent product, a contractual notice period is worth more than a discount.
3. Negotiate migration assistance up front. The cheapest time to secure vendor-funded migration help is before signature, not after the retirement notice lands.
4. Price-protect your renewal. Successor products — Revenue Cloud Advanced versus CPQ, one agent SKU versus another — are rarely priced like the thing they replace.
5. Confirm export rights in machine-readable form. Portability is the only real hedge against a platform direction you did not choose.

What This Should Change About How You Build

Architecture decisions determine how much any given deprecation actually hurts. Four rules we apply on every implementation:

1. Build on the primitive with the longest runway. When a vendor has two ways to do the same thing, build on the one they are investing in — Flow, not Process Builder; Projects-based apps and Service Keys, not legacy private apps.
2. Never put load-bearing process on a preview feature. The Sales Hub Dialer was in preview and was removed outright. Preview means “we may delete this,” and vendors mean it.
3. Pin your API version and calendar the upgrade. Under date-based versioning, pinning is correct — but pinning without a scheduled review is how you discover a sunset in production. Put the version number and its support horizon in your integration documentation.
4. Keep the system of record out of the AI layer. Agent instructions, prompts, and copilot configurations are the most volatile surface on any platform. Business rules that must survive a vendor’s product reshuffle belong in objects, fields, validation, and flows — not in a prompt attached to an agent SKU that may be renamed next release.

The Operating Rhythm That Actually Works

The organizations that handle this well are not smarter about technology. They just made deprecation somebody’s job. A workable quarterly cadence:

1. Name an owner. One person — usually the CRM admin or RevOps lead — owns platform change monitoring. Unowned means unnoticed.
2. Subscribe to the primary sources. Salesforce’s Active Product & Feature Retirements list, the HubSpot Developer Changelog, the Dynamics 365 deprecations index and Power Platform important changes, Zoho release announcements, and NetSuite release notes. Vendor emails are not a monitoring strategy.
3. Maintain a dependency inventory. Every integration, managed package, custom object, automation, and API version, with the business process it supports. Without it, every deprecation notice becomes a discovery project.
4. Triage into now, next, and never. Hard removal dates go on the roadmap. End-of-sale items go on a watchlist. Features you do not use get ignored on purpose.
5. Fund it. Put a platform maintenance line in the annual budget separate from new projects. In our experience with mid-market orgs, teams that budget nothing for this end up paying for it anyway — out of the project budget, at the worst possible moment.

The Counter-Move: Don’t Over-React Either

There is an equal and opposite failure mode, and we see it more often than negligence: panic migration. A CRM manager reads “Salesforce CPQ is end of sale,” concludes the product is dying, and launches a Revenue Cloud Advanced project a year before there is any business reason for one. But Salesforce has explicitly not announced an end-of-life date, and existing customers keep licenses, add users, and renew. The same is true of most deprecation notices — Microsoft’s own guidance states that deprecated features continue to work and are fully supported until officially removed, and that notice periods “might span a few years.”

The discipline is to separate three states: removal with a date (act on the calendar), deprecated, no removal date (stop building new work on it, plan the exit deliberately), and end-of-sale but supported (keep running it, and time your migration to a business trigger like a quoting redesign, not to a press release).

CRM Experts Online’s Perspective

We spend a lot of our time on the receiving end of these notices, and the pattern in what it costs clients is consistent. The damage almost never comes from the deprecation itself. It comes from three things around it: nobody knew which processes depended on the retired feature, the migration tool converted 70% of the logic and quietly left the rest, and the work landed in a quarter that already had a full roadmap.

So the first thing we build on a new engagement now is not an automation — it is an inventory. What runs on what, and what breaks if the vendor removes it. That artifact does more to protect a CRM investment than any single configuration decision.

The second thing we do is push back on where AI logic lives. We are enthusiastic about agents in CRM, and we implement them. But we implement them as a layer over a durable data and process model, not as a replacement for one. When a vendor retires an agent product — and 2026 has now demonstrated they will — the client who put their qualification rules in objects and flows swaps the agent out in a sprint. The client who put those rules in prompts rebuilds their sales process.

The third thing: we tell clients honestly when a deprecation notice does not require action this year. Consulting firms have an obvious incentive to convert every vendor announcement into a project. Most of them should convert into a calendar entry instead.

FAQ

What is the difference between deprecated, end of sale, and end of life? Deprecated means the vendor intends to remove it eventually; it still works and is supported until removal. End of sale means new customers cannot buy it but existing customers keep, renew, and get support — typically with no new feature development. End of life means it stops working and stops being supported. Salesforce CPQ is end of sale and explicitly not end of life.

Do my Workflow Rules and Process Builders still run after December 31, 2025? Yes. Existing automations continue to execute, but Salesforce no longer supports them, bugs found after that date will not be fixed, and you cannot create new ones. That is a slow-burning risk, not an outage — but it means every unmigrated automation is now unsupported production logic.

How urgent is HubSpot’s date-based API versioning for a company with a few integrations? Urgent enough to document. Each version carries a minimum 18-month support window with roughly six months of active maintenance and twelve months of critical fixes only. Note which version each integration targets, and set a calendar reminder about twelve months out to plan the move to the next version.

We are on Dynamics 365 and using Sales Close Agent. What now? Microsoft’s documentation directs customers to create an instance of the Sales Development agent instead, with no new Close Agent instances after September 30, 2026 and existing instances removed October 30, 2026. Treat it as a migration with a hard date, and re-verify any process, reporting, or training built around the old agent.

Can we avoid this by choosing a smaller or more stable vendor? Not really — smaller vendors churn too, and often with less notice and no published deprecation list. What you can choose is a vendor that publishes retirements transparently and honors long notice windows. Ask to see the list during evaluation.

How much should we budget annually for platform change? There is no published industry figure we would stand behind. Our practical guidance is to fund a standing maintenance allocation separate from your project roadmap, sized to your customization footprint: a lightly configured org needs very little, while an org with heavy custom objects, managed packages, and multiple integrations needs a meaningful recurring line.

Does heavy customization make deprecation worse? Yes, materially. Every custom automation, package, and integration is a dependency on a vendor decision you do not control. That is not an argument against customization — it is an argument for customizing deliberately, on supported primitives, and knowing exactly what you have built.

What is the single highest-value thing we can do this quarter? Build the dependency inventory and assign an owner for monitoring vendor release and retirement feeds. Everything else in this article gets easier once those two exist.

Conclusion

The vendors are not going to slow down. Release cadences are accelerating, AI features are shipping and being replaced within a year, and integration contracts now come with published expiry dates. That is the environment, and it is not going back. What changes is whether your organization absorbs it as a series of surprises or handles it as a routine, budgeted, owned operating process.

If you are looking at a deprecation notice right now — an unmigrated set of Process Builders, a CPQ roadmap decision, integrations pinned to an API version you have not thought about since go-live, or an agent product with a removal date on it — we can help you scope what actually needs to happen and, just as usefully, what does not. Schedule a consultation with CRM Experts Online for a platform dependency review across Salesforce, HubSpot, Zoho, NetSuite, Dynamics 365, or SugarCRM, and get a prioritized plan instead of a pile of vendor emails.

Further Reading

• Salesforce: Salesforce CPQ Is End of Sale, Not End of Life
• Salesforce Help: Active Product & Feature Retirements
• Salesforce Ben: End of Support for Workflow Rules & Process Builder
• Microsoft Learn: Removed or Deprecated Features in Dynamics 365 Sales
• Microsoft Learn: Important Changes (Deprecations) Coming in Power Platform
• HubSpot Developer Changelog: Introducing Date-Based API Versioning
• HubSpot Docs: Sunsetted and Deprecated APIs
• HubSpot Docs: Developer Platform and API Versioning
• Zoho Help: Zoho CRM’s Old User Interface Is Set to Retire
• Oracle Docs: NetSuite Version 2026.2

John M Perez

CRM & ERP Enterprise Technology Expert and Entrepreneurial Executive with 20+ years of leading CRM, ERP, Customer Experience, and Block-chain initiatives and projects across internal and customer facing technologies.  Proven success in closing large deals in Pre Sales customer facing engagements and deploying enterprise wide CRM & Customer Experience solutions internationally and domestically.