Deadline passed: January 13, 2026. Microsoft lists Dynamics CRM 2016 (Dynamics 365) among the products that reached end of support in 2026. That covers the last supported release, the December 2016 Service Pack (version 8.2). If you still run it, the servers work, but they no longer get security patches, and Microsoft no longer offers support.
This guide covers what changed, why Microsoft’s own route to the cloud doesn’t start from CRM 2016, and the three ways out.
What does Dynamics CRM 2016 end of support mean?
From Microsoft’s lifecycle pages:
| Release | Support ended |
|---|---|
| Original release (8.0) | July 2018 |
| Service Pack 1 (8.1) | January 2019 |
| Mainstream support, whole product | January 2021 |
| December 2016 Service Pack (8.2), extended support | January 13, 2026 |
Microsoft’s definition of end of support: no new security updates, non-security updates, free or paid assisted support options, or online technical content updates. CRM 2016 follows the Fixed Lifecycle Policy, so there is no rolling extension.
The practical risks are security (an internet-facing CRM with known, unpatched vulnerabilities), compatibility (newer Windows Server, SQL Server, browser and Outlook releases are not tested against 8.2) and compliance (auditors increasingly flag unsupported software holding customer data).
What should I do first if CRM 2016 is still running?
Before choosing a destination, reduce the risk of running unsupported software:
- Take full backups of the CRM organization databases and the configuration database, and test a restore.
- Limit exposure. If the CRM is reachable from the internet, review whether it needs to be, and who can sign in.
- Export the customisations as solutions, so the schema is documented even if the server fails.
- List the integrations that write to CRM, because they will need repointing whatever you choose.
- Set a decision date. An upgrade, an online move and a CRM switch each take planning; the longer the decision waits, the longer the system runs unpatched.
These steps don’t fix end of support, but they make every later option safer.
What are my options after Dynamics CRM 2016?
| Option | Supported until | Effort | Good fit when… |
|---|---|---|---|
| Upgrade on-premises to 9.1 | January 10, 2031 (extended) | Technical upgrade; customisations re-tested | You must stay on-premises |
| Move to Dynamics 365 Sales online | Ongoing (cloud service) | Data migration plus rebuild of plugins and integrations | You want to stay on Microsoft and stop running servers |
| Switch to another CRM | Ongoing | Data migration plus process redesign | Dynamics is more than your team needs, or you are consolidating |
Version 9.1 is the only on-premises release still supported. Microsoft extended it: mainstream support to January 13, 2029 and extended support to January 10, 2031. Version 9.0 ended on July 12, 2023.
How much time does an upgrade to 9.1 buy?
Version 9.1’s extended support runs to January 10, 2031, a little over four years from today. That is enough to stabilise, but it defers the same decision rather than removing it: 9.1 is the last on-premises release on Microsoft’s lifecycle list, and its mainstream support ends on January 13, 2029. If you upgrade, plan the eventual move to online or to another CRM at the same time, so the upgrade’s testing effort isn’t spent twice.
Can I use Microsoft’s on-premises to online migration from CRM 2016?
Not directly. Microsoft runs an on-premises to online (OP2OL) migration programme with tooling in Lifecycle Services and support from its migration factory team. Its eligibility rules:
- Source version 9.0 or later. CRM 2016 is version 8.x, so it must be upgraded to 9.x first.
- Supported SQL Server for that version.
- Dynamics 365 online licences bought before the migration starts.
- Unsupported customisations fixed first, by the customer or partner, including SQL Server-level changes.
- Partner nomination through Microsoft’s form.
So the Microsoft route from CRM 2016 is two projects: an on-premises upgrade to 9.x, then a database migration to online. A data migration skips the interim upgrade by moving records straight into a new Dynamics 365 online environment.
How do I move from Dynamics CRM 2016 to Dynamics 365 online?
- Inventory the organization: entities (standard and custom), record counts, attributes, option sets, relationships, business process flows, workflows, plugins, reports and integrations.
- Decide the route: upgrade-then-OP2OL, or a data migration into a fresh online environment.
- Build the target: solutions, custom entities and fields, option sets, business units, security roles, users.
- Migrate in dependency order: accounts, contacts, leads, opportunities and products, cases, custom entities, then activities (emails, phone calls, appointments, tasks, notes) and attachments.
- Keep history: original created dates, owners and the regarding record on every activity.
- Rebuild logic: classic workflows and plugins are re-validated or rebuilt, often as Power Automate flows; SSRS reports move to supported reporting.
- Repoint integrations and Outlook or email sync.
- Run a delta for records changed since the main run, then retire the on-premises servers.
Should I switch CRM instead?
Many CRM 2016 organizations were set up a decade ago for a different team. Before paying for an upgrade, ask:
- Do you use the Dynamics features that justify it (complex security, custom entities, Microsoft stack integration)?
- Would HubSpot or Salesforce fit the current sales process better?
- Is anyone left who knows why the customisations exist?
If you switch, the same inventory applies, plus a model translation: Dynamics accounts, contacts, leads and opportunities map to the new CRM’s objects, and custom entities need a home.
What breaks most often in Dynamics migrations?
- Activities losing their “regarding” link, so emails and calls float free of accounts.
- Owners mapped to the wrong users, especially for disabled users who still own records.
- Option set values that don’t match the target’s picklists.
- Business process flow stages with no direct equivalent in another CRM.
- Attachments stored outside the database, for example in SharePoint, which need their own move.
When to bring in FlitStack AI
FlitStack AI is a data-migration platform sold as software plus a done-for-you service. It moves Dynamics data into Dynamics 365 Sales online or another CRM: entities, custom entities, activities with original timestamps and owners, and attachments, with field-level mapping you review, validation on every record, one-click rollback and delta migration for cutover. The Dynamics 365 implementation service rebuilds workflows, business process flows and security in the new environment.
See the Dynamics 365 Sales migration hub, or switching platform: Dynamics 365 to HubSpot and Dynamics 365 to Salesforce. For a quote, book a free scoping call.