All posts
Legacy Modernization

Dynamics CRM On-Premises Is Ending: Dynamics 365 Online, Salesforce, HubSpot or Something Custom

By

October 25, 2026

6 min read

Dynamics CRM 2016 reached end of support on January 13, 2026, and on-premises Dynamics 365 Customer Engagement 9.x leaves mainstream support on January 12, 2027. How to choose the next CRM, and why the plugins, integrations and reports built around the old one decide the timeline.

Dynamics CRM
CRM
Salesforce
HubSpot
End of Support

Many mid-sized companies still run CRM on their own servers: Dynamics CRM 2016 or the on-premises edition of Dynamics 365 Customer Engagement. CRM 2016 lost support on January 13, 2026. Customer Engagement 9.x on-premises moves from mainstream to extended support on January 12, 2027, which means security fixes only.

Want a second opinion on this for your system?

Book a free 30-minute call. You'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.

Where people go

Destination

Fits when

Watch for

Dynamics 365 Sales online

You want the closest match to what you have, and you are on Microsoft 365

Customizations and plugins need review; per-user licensing

Salesforce Sales Cloud

You want the largest ecosystem and are willing to rebuild processes

Higher per-user cost; Flow is now the only supported automation

HubSpot

Sales and marketing are tightly linked and the process is fairly standard

Less suited to complex, custom data models

A custom application

The "CRM" is really a specialised operational system that happens to have contacts in it

You own it forever; only worth it when no product fits

What decides the timeline

  • Plugins and custom workflows written against the old SDK.

  • Integrations: the ERP sync, the website forms, the email marketing tool, the phone system.

  • Reports, often built in SSRS directly against the CRM database, which no SaaS CRM allows.

  • Data quality. Duplicates and dead records migrate perfectly and cost money per seat and per record forever after.

  1. Inventory customizations and integrations, and mark each keep, replace with a product feature, or drop.

  2. Clean and deduplicate before migrating, not after.

  3. Move reporting to a separate data store fed from the CRM, so reports survive the change and any future one.

  4. Migrate in one cutover for the core sales team; keep the old system read-only for a defined period.

hoolco Monthly Review

Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.

As of October 25, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.