Last updated:
What changed on 13 January 2026?
Dynamics CRM 2016 reached the end of extended support. Microsoft no longer releases security updates or bug fixes for it and no longer provides technical support. The servers keep running, but vulnerabilities found from now on stay open.
Dynamics CRM 2015 had reached this point on 14 January 2025, and Dynamics CRM 2013 on 9 January 2024. The only on-premises version still supported is Dynamics 365 Customer Engagement (on-premises) 9.1.
Microsoft support dates for on-premises Dynamics versions
Dates from Microsoft's lifecycle pages. Versions whose support has ended no longer receive security updates.
| Version | Mainstream support | Extended support |
|---|---|---|
| Dynamics CRM 2011 | Ended 12 July 2016 | Ended 13 July 2021 |
| Dynamics CRM 2013 | Ended 8 January 2019 | Ended 9 January 2024 |
| Dynamics CRM 2015 | Ended 14 January 2020 | Ended 14 January 2025 |
| Dynamics CRM 2016 | Ended 12 January 2021 | Ended 13 January 2026 |
| Dynamics 365 Customer Engagement (on-premises) 9.0 | Ended 12 July 2023 | Not extended; move to 9.1 |
| Dynamics 365 Customer Engagement (on-premises) 9.1 | Until 13 January 2029 | Until 10 January 2031 |
Who does this affect?
- Organizations running Dynamics CRM 2016 or an earlier version on their own servers.
- Organizations on Dynamics 365 Customer Engagement (on-premises) 9.0.
What are the ways forward?
- Stay on-premises and upgrade to 9.1. Your data stays on your own servers, and extended support runs until 10 January 2031. Version 9.0 can only be reached from Dynamics CRM 2016 version 8.2, and 9.1 is an update installed on top of 9.0. Earlier versions are first brought to 8.2 step by step.
- Move to Dynamics 365 in the cloud. There are no servers left for you to run, and Microsoft keeps the service up to date. Microsoft's path for moving the database to the cloud needs version 9.0 or later as the source. Plug-ins that run outside the sandbox and reports that read SQL views are rebuilt.
- Stay for now and reduce the risk. If the move can't start right away, limit who and what can reach the CRM servers, test your backups and set a date for the move. This buys you time; it does not replace security updates.
Dynamics 365 in the cloud or 9.1 on-premises?
Both are supported ways forward from Dynamics CRM 2016. The right one depends on where your data must stay and how much server-side customization you have.
| Topic | Dynamics 365 (cloud) | Dynamics 365 Customer Engagement (on-premises) 9.1 |
|---|---|---|
| Where it runs | In Microsoft's cloud, on Microsoft Dataverse | On your own servers or your own cloud infrastructure |
| Updates | Microsoft updates it continuously | You install the updates Microsoft releases |
| Customization | Plug-ins and custom workflow activities run only in the sandbox; reports are FetchXML-based | Plug-ins outside the sandbox and reports that read SQL views also work |
| Licensing | Dynamics 365 online licenses are bought before the move | A server license plus client access licenses (CALs) |
| Infrastructure | Nothing for you to run | Windows Server 2016 or later, SQL Server 2016 SP2 or later, and running the servers are on you |
| Good fit when | You don't want to run servers and want new features | Data must stay on-premises, or you depend on server-side customizations |
How do you move from Dynamics CRM to Dynamics 365?
A move carries not just the data but also customizations, reports and integrations. So we start by mapping the current version and what has to change. The choice between cloud and on-premises is settled at this stage too.
- Assessment. We review the version, customizations, reports and connected systems.
- Preparation. Where needed, we upgrade to 9.x on-premises and fix unsupported customizations.
- Trial move. We move the data to a test environment and validate it with your users.
- Go-live and support. We complete the move in a planned window and support the environment afterwards.