Dynamics CRM 2016 end of support: upgrade to 9.x or move the data
Dynamics CRM 2016 end of support: 8.2 ended January 13, 2026, 8.0 and 8.1 earlier. Microsoft's program needs 9.0 or later. Compare three ways off 8.x.
Dynamics CRM 2016’s last release, 8.2, has been out of support since January 13, 2026, the date on Microsoft’s 2026 end of support list. Releases 8.0 and 8.1 left years earlier. Microsoft’s on-premises to online (OP2OL) migration program, which moves on-premises Dynamics CRM to Dynamics 365 online, requires version 9.0 or later. Every CRM 2016 release is 8.x, so an install still on it sits below that floor until it is upgraded.
This page covers three outcomes:
- Upgrade to 9.x, then apply to the program
- Move the data instead of the database
- Upgrade to 9.1 and stay on your own servers
Compared side by side: CRM 2016 options compared. Where this page joins Microsoft pages into a step Microsoft does not state, it says “our reading”. Microsoft’s pages set the supported path and its conditions, not how long a route takes or how often one fails.
Checked against Microsoft’s pages in November 2026.
When did Dynamics CRM 2016 support end?
Dynamics CRM 2016’s last release, 8.2 (the December 2016 Service Pack), left support on January 13, 2026, per Microsoft’s 2026 end of support list. Earlier releases ended sooner, per the CRM 2016 product page: 8.0 in July 2018 and 8.1 in January 2019.
| Release | Microsoft’s name | Support ended |
|---|---|---|
| 8.0 | Original Release | July 2018 |
| 8.1 | Service Pack 1 | January 2019 |
| 8.2 | December 2016 Service Pack | January 13, 2026 |
The product page names the policy: “Dynamics CRM 2016 (Dynamics 365) follows the Fixed Lifecycle Policy.” The lifecycle overview gives the rule behind the staggered dates: “customers are required to move to the latest service pack to remain in support.” “When a new service pack is released, customers will be supported on the prior service pack for 12 or 24 months to allow time to move to the latest service pack.”
Our observation: Microsoft’s product page can show January 14, 2026 in a US browser, while its 2026 list says January 13. This page uses the list’s date.
Does CRM 2016 stop working after end of support?
Microsoft’s 2026 end of support list does not say CRM 2016 stops running. It says what stops arriving: “Upon retirement or end of support, there will be no new security updates, non-security updates, free or paid assisted support options or online technical content updates.” That sentence rules out paid assisted support too.
Our observation: neither the 2026 list nor the CRM 2016 product page lists an Extended Security Update offer for CRM 2016. Microsoft’s lifecycle overview offers ESU only for “certain legacy products as a last resort option” and does not name CRM 2016.
Why CRM 2016 sits below the online migration program’s 9.0 floor
Microsoft’s program page says: “To perform the migration, your source environment must be a version of Dynamics CRM V9.0 or Dynamics 365 (9.0/9.1).” Its table of supported versions reads “Version 9.0 or later.” for on-premises Dynamics CRM.
Reaching 9.0 or 9.1 meets the floor.
Even from 9.0 or later, the program has conditions:
- Licenses first: “Customers must procure licenses to Dynamics 365 online before they start the migration process.”
- SQL Server: “Also, SQL Server must be aligned with the supported/compatible versions.”
- Customizations: “This program requires the customer or engaged partner to fix or mitigate any unsupported customizations or SQL Server-level changes that might block the database migration.”
- Portal access: “All migrations require appropriate access and permission to the Lifecycle Services portal.” Microsoft’s OP2OL whitepaper (August 2026) adds: “Access to your regional LCS portal is activated after successful onboarding to the Program through the nomination process.”
- Validation: the whitepaper says “It is also the customer’s responsibility to validate the migrated instance.”
- Who can nominate: Microsoft’s pages differ. The program page names Microsoft partners nominating their customers; the FastTrack migration page says “Partners and customers can nominate for the migration services for on-premises to online (OP2OL) through the self-serve tool.” Confirm the current terms with Microsoft directly.
The whitepaper also warns: “Older Dynamics CRM versions and heavily customized deployments are more prone to failures during initial dry runs.” Our reading: the whitepaper’s floor is CRM 9.0, so this is said of versions the program accepts, and a heavily customized 9.x organization database should plan for dry runs that may fail.
Route 1: upgrade CRM 2016 to 9.x, then apply to the online migration program
The deployment’s servers and each organization database carry separate release numbers, and Microsoft’s steps upgrade the servers first.
In our reading of Microsoft’s upgrade pages, route 1 runs in this order:
- Prepare: backups, encryption keys, the 1023-field limit, custom database objects (Before you upgrade).
- On 8.0 or 8.1, apply the December 2016 update to reach 8.2 (From 8.0 or 8.1).
- Upgrade the servers to 9.0, on new servers or in place (From 8.2; Upgrading on new servers or in place).
- Apply the latest 9.1 update, then update or import each organization database (From 8.2; Why end at 9.1).
- Apply to Microsoft’s program, on the conditions above.
The program then imports and upgrades the organization database; validating the result stays with you. The whitepaper’s Phase 2 says: “Microsoft Dynamics CRM organization is imported and upgraded.”
Before you upgrade: backups, encryption keys and the field limit
Microsoft’s upgrade planning page lists these checks:
- “Always run a full backup of the Dynamics 365 databases before you upgrade to a new version of the product.”
- “Copy the organization encryption key for all organizations that will be upgraded.” “The encryption key is required to activate data encryption when you import an organization database into a new instance of SQL Server.”
- “If you have more than 1023 fields defined for an entity, you must delete the additional fields before you run the upgrade, or the upgrade will fail”.
- “We suggest that, if you have added custom database objects such as triggers, statistics, stored procedures, and certain indexes, you remove those objects from the configuration and organization databases.”
- “For each organization that you upgrade, we recommend that the volume have free space that is at least three times the size of the organization database file (organizationName_MSCRM.mdf) and four times the size of the log file (organizationName_MSCRM.ldf).”
From 8.0 or 8.1
Microsoft’s support article for the December 2016 update (the 8.2 service pack in the table above) says: “This must be installed on a server running Microsoft Dynamics CRM 2016 (version 8.0) or later.” Our reading, joining that article with the upgrade pages below: an 8.0 or 8.1 deployment applies the December 2016 update first, then follows the 8.2 steps.
That update is one way: “December 2016 Update for Dynamics 365 cannot be uninstalled from the Microsoft Dynamics 365 server to roll back the program to the previous version.” The package was on Microsoft’s Download Center in November 2026, with no promise it stays.
From 8.2 (December 2016 Service Pack)
Microsoft sets the floor for the first hop: “The only supported upgrade path to Dynamics 365 Server, version 9.0 is upgrade from December 2016 Service Pack for Dynamics 365 (on-premises), or later update, to Dynamics 365 Server, version 9.0.” Microsoft’s 9.1 update page then gives the 8.2 steps in order:
- “Upgrade all computers running Dynamics 365 Server and desktop applications in your deployment to Dynamics 365 Customer Engagement (on-premises), version 9.0.”
- “Apply the latest version 9.1 update to all computers running Dynamics 365 Server and desktop applications in your deployment.”
- “Next, update or import each organization.”
Upgrading on new servers or in place
Microsoft’s planning page recommends a new instance of SQL Server: “Migrate by using a new instance of SQL Server.” “We recommend this option for upgrading the deployment.” Its reason: “it provides the least amount of potential downtime for users since the existing deployment can remain functional until the upgrade is completed and verified.” The steps it lists:
- “Install (recommended) or upgrade all server roles to Dynamics 365 Server, version 9.0.”
- “Import organizations into the new or upgraded deployment.”
- “During the import, organizations will also be upgraded.”
The import has a floor too: “Only December 2016 update for Dynamics 365 Customer Engagement (on-premises) (8.2) or later organizations are supported for importing with this version of Dynamics 365 Customer Engagement (on-premises).”
In place, by contrast: “During an in-place upgrade, only the organization that you specify to upgrade is upgraded.” “If the deployment contains additional organizations, those organizations are disabled and are not upgraded.” No page we read gives an in-place path for an 8.2 server on a host older than Windows Server 2016.
Windows Server and SQL Server versions
Our reading: if your 8.2 servers run Windows Server 2012 or 2012 R2, the 9.0 hop needs different hosts.
- 8.2 hosts: the December 2016 update’s download listing names operating systems up to “Windows Server 2012 R2”.
- 9.0 hosts: the requirements list only Windows Server 2016 editions: “The following editions of the Windows Server 2016 operating system are supported for installing and running Dynamics 365 Server:”
- 2012 and 2012 R2 lifecycle: Microsoft’s ESU page says: “Extended support for Windows Server 2012 and Windows Server 2012 R2 ended on October 10, 2023.” Their last Extended Security Updates year ended on October 13, 2026, per the same page.
The requirements pages (9.0 view, 9.1 view) list:
| Release | Windows Server listed | SQL Server listed |
|---|---|---|
| 9.0 | 2016 Standard and Datacenter | 2016 with Service Pack 2 or 3; 2017 (needs 9.0 Update 0.3) |
| 9.1 | 2016, 2019 and 2022 Standard and Datacenter (2022 needs Service Update 1.25) | 2016 with Service Pack 2 or 3; 2017; 2019; 2022 (needs Service Update 1.25) |
Why end at 9.1, not 9.0
The program’s floor is 9.0, but 9.0 itself is out of support: “Support for version 9.0 ended on July 12, 2023, and it no longer receives security updates.” And: “Customers on 9.0 must upgrade to 9.1 and apply the latest cumulative update to remain supported.” Ending the upgrade on 9.1 is our reading of those lines, not a program rule.
Open questions: product keys and the 9.x source
- Product keys. Microsoft’s planning page says: “Before the upgrade, obtain the product key that you will enter during the upgrade.” Whether your CRM 2016 licenses cover that key is not stated on the pages we read. Get the licensing answer from Microsoft or your partner, in writing, before the first hop.
- The source. Whether the 9.x source must run in production before the program, or whether an organization database upgraded in a temporary deployment qualifies, is not stated on the pages we read. The program page says of its whitepaper: “This technical document outlines the prerequisites and provides a step-by-step guide to the migration process.” The whitepaper does not say either. Ask, in writing, during nomination whether an upgraded copy of the database qualifies as the source.
Route 2: migrate CRM 2016 data to Dataverse with ETL
Our reading: a data migration does not pass through the program, so the program’s version floor does not apply. The data moves; the old database does not.
Microsoft’s implementation guide for customer engagement apps sorts the tools:
- Flat files: “For more complex migrations, such as moving all the data from an old CRM system, manual import from flat files isn’t efficient and can cause errors.”
- ETL tools: “Instead, use ETL tools like SSIS or Azure Data Factory.”
- Power Automate and Azure Logic Apps: “Although we have these options, they aren’t meant to do large data migration jobs.”
Microsoft’s Power Platform architecture guidance puts a staging layer in the middle:
- “Data is first ingested into a temporary migration staging database, where it undergoes transformation and validation.”
- “Only after these steps are completed, the data is loaded into Dataverse.”
When the guidance says it fits:
- “Direct migration isn’t feasible due to data quality issues, schema mismatches, or the need for business rule enforcement.”
- “The migration process needs to be auditable, repeatable, and support rollback or reprocessing of specific data segments.”
That page names no Dynamics CRM source and assumes Dataverse is the right destination. Our reading, applied to CRM 2016: the 8.x organization database is the source and Dataverse in Dynamics 365 online is the target.
What a CRM 2016 data move has to decide
Our questions, not Microsoft steps:
- Schema, logic and access first. The schema (tables and columns), the logic (plug-ins and workflows) and the access model (security roles) are built or moved in the target before any data loads.
- Licenses. The data lands in Dataverse in Dynamics 365 online, so licensing still comes first.
- CRM mappings. Keep source record IDs or remap lookups? Users, teams and business units before records? Activities with parties and Regarding links, notes and attachments, statecode and statuscode pairs? Target plug-ins on or off during loads? Per-table record counts, and the final delta and freeze at cutover?
- Created and modified history. Microsoft’s page on developer data import jobs (not ETL tools) says: “To import data in the createdon column, map the source column that contains this data to the overriddencreatedon column.” And: “You cannot import data into the modifiedon, createdby, and modifiedby columns.” It points to custom columns for the rest.
- What stays behind. “However, just because you need to see data in Dynamics 365 doesn’t mean that the data must live in the Dynamics 365 Dataverse database.” “Often, you can replace data that you don’t migrate with embedded Power BI reports, virtual entities, embedded canvas apps with connectors to the source data, and so on.”
- Who can reach the staging copy. The staging guidance says: “Apply role-based access control (RBAC) to restrict access to the staging database and migration tools.” “Encrypt data at rest and in transit, especially when handling sensitive or personal data.” “Validate data completeness and integrity before loading data into Dataverse to avoid partial or corrupt migrations.”
Staying on-premises after CRM 2016
Moving online is not the only outcome. Route 1’s upgrade ends on 9.1, and Microsoft’s lifecycle page keeps 9.1 in support on its latest cumulative update: “For Dynamics 365 for Customer Engagement Apps, version 9.1 (Service Pack 1), the end of Mainstream Support is extended to January 13, 2029, and the end of Extended Support is extended to January 10, 2031.” Stopping on 9.1 is not a route to Dynamics 365 online. Reaching it still takes route 1’s upgrade steps, with the same open question on product keys.
The product date is not the host date. A 9.1 server left on Windows Server 2016 runs on a host that reaches its extended end date in January 2027, per its lifecycle page; if its SQL Server is 2016, that version’s end of support date on Microsoft’s 2026 list was July 14, 2026. Our reading: of the hosts the 9.1 requirements list, only Windows Server 2022 (October 14, 2031) and SQL Server 2022 (January 11, 2033), both needing Service Update 1.25, stay in support past January 10, 2031. Windows Server 2019 (January 9, 2029), SQL Server 2017 (October 2027) and SQL Server 2019 (January 8, 2030) end first.
CRM 2016 options compared: upgrade, move the data or stay on 9.1
| Question | Route 1: upgrade, then apply | Route 2: move the data | Stay on 9.1 |
|---|---|---|---|
| What moves | The organization database, upgraded by the program | The data you choose, loaded into Dataverse in Dynamics 365 online | Nothing; the deployment stays on your servers |
| Microsoft's program | Used; stated floor 9.0, other conditions apply | Not used | Not used |
| Fits when | The organization database should move as it stands, with customizations that can be fixed or mitigated | Data quality, schema mismatches or business rules rule out a direct move | Moving online is not required, and mail is not in Exchange Online |
| What can block it | Unsupported customizations or SQL Server-level changes; entities over 1023 fields; the 9.0 hop's Windows Server 2016 hosts | Not stated on the pages above | Windows Server or SQL Server versions that leave support before 9.1 (all but the 2022 versions) |
| Ends on | Dynamics 365 online | Dynamics 365 online | 9.1 on its latest cumulative update; extended support to January 10, 2031 |
What CRM 2016 end of support does not mean
- That CRM 2016 stops running, or that running it is safe. The list names what stops arriving, security updates included; no page above ties a breach or audit finding to it.
- That every 8.x release left support in January 2026.
- That Microsoft refuses 8.x requests. What happens to a request from an 8.x install is not stated on the pages above.
- That reaching 9.0 or 9.1 gets you into the program, or that the program does the rest. The conditions above still apply, and validating the migrated instance is yours.
- That 9.1 being in support covers the servers under it. Windows Server, SQL Server and Exchange Online keep their own dates.
- That every CRM 2016 owner must move online. Outside server-side synchronization with Exchange Online (see the callout above), no page above says so.
- That these are Microsoft’s routes, or the only options.
- That route 2 is a copy of the old system, or faster, cheaper or safer than route 1. No page above compares the two routes for a CRM 2016 install, upgrade hops included, on speed, cost or safety.
CRM 2016 migration checklist: what to settle first
Our recommended order, based on the pages above:
- Confirm the release of every organization: 8.0, 8.1 or 8.2. Microsoft’s organization upgrade page, written for 9.x deployments, shows where Deployment Manager lists it: “On the Deployment Manager home page, in the console tree, select Organizations.” “In the details pane for each organization, review the Version column.”
- List each server’s Windows Server and SQL Server version against the requirements list.
- Check where mail syncs: Exchange Online or Exchange Server.
- Inventory before any hop: customizations and custom database objects, Reporting Extensions (included in the 9.0 server download), and each organization’s encryption key, backed up and copied.
- Decide what data must move, and what can stay behind.
Microsoft’s whitepaper notes: “Very often customers complement this migration project with the archival or clearing of historical data, just before the migration process.” Migration work from crm.vet runs through Citizen Development Academy. For the data clean-up both routes can start with, see its guide to Dynamics CRM on-premises to online migration and data cleansing.
A free first look at your CRM 2016 route
If you still run Dynamics CRM 2016 on your own servers, a short conversation can give you a first view of your release, your data and which route to test first. It is free, and there is no obligation. It is not a nomination to Microsoft’s program; licensing and program terms still go to Microsoft.
Related articles
Microsoft Power Platform - Expanding Dynamics 365 CRM
The importance of data for organizations is increasing every day. However, you often find yourself lost in optimizing business processes while completely ignoring the importance...
Dynamics 365 workflow failure monitoring with Power Automate
Dynamics 365 workflow failure monitoring with Power Automate: list failed and waiting System Jobs on a schedule, attach a CSV and alert a shared mailbox.