A consolidated guide covering lifecycle deadlines, migration paths, and Bridge to Cloud 3 eligibility across Microsoft's legacy on-premises portfolio
Thousands of organizations worldwide have been running Microsoft Dynamics NAV, Dynamics GP, Dynamics AX, or Dynamics CRM on-premises for well over a decade. These systems still handle core operations across finance, supply chain, manufacturing, sales, and customer service. They work. The teams know them. Nobody is in a rush to change what runs.
But Microsoft has now sunset its entire legacy on-premises Dynamics portfolio. Every version of Dynamics AX is already out of support. Dynamics CRM 2016 exited support in January 2026. NAV and GP have firm commercial end-of-sale dates set for April 2031. The path forward for all four product lines leads to Dynamics 365, and the financial incentives to make the move are on a countdown of their own.
When Does Support End for Dynamics NAV, GP, AX, and CRM On-Premises?
The lifecycle situation is different for each product, but the direction is the same across all four. The table below consolidates the critical dates and migration destinations.
| Product | Mainstream Support Ends | Extended Support / Licensing Ends | Migrates To |
| Dynamics NAV | Already ended (all versions) | NAV 2018: January 2028; Licensing: April 30, 2031 | Dynamics 365 Business Central |
| Dynamics GP | December 31, 2029 | April 30, 2031 | Dynamics 365 Business Central |
| Dynamics AX | Already ended (all versions) | Already ended (AX 2012 R3: January 2023) | Dynamics 365 Finance & Supply Chain Management |
| Dynamics CRM / D365 CE v9 (on-prem) | January 12, 2029 | January 9, 2031 | Dynamics 365 Sales, Customer Service, Field Service (online) |
A few points worth noting. For NAV and GP, the April 2031 date is an end-of-sale, not a shutdown. The software doesn't stop working that day. What ends is the ability to renew Service Plans, renew subscription licenses, or purchase additional perpetual licenses. Growing organizations face a hard constraint on the existing system's useful life. AX customers face more immediate urgency: all support has already ended, and organizations are operating today without security patches or regulatory updates. On the CRM side, to January 2029 (mainstream) and January 2031 (extended), but no new on-premises release is planned. The platform's innovation is now cloud-only.
Why Should Legacy On-Premise Dynamics Users Migrate to Dynamics 365 Now?
The lifecycle dates set the outer boundary. But several other factors are compressing the practical timeline for all four product lines.
Bridge to Cloud 3 covers NAV, GP, AX, and CRM, and it expires December 2027. Microsoft's offers qualifying on-premises Dynamics customers a 30% discount on Dynamics 365 online licenses, locked in for a three-year non-cancellable term. The promotion covers all four legacy product lines: NAV, GP, AX, and CRM. It requires a perpetual license purchased before September 1, 2024, with an active Enhancement Plan at enrollment. The previous program, Bridge to Cloud 2, offered 40% and ended in December 2025. Each successive program offers less. Organizations that enroll before December 2027 lock in savings. Those that wait will migrate at list price.
Legacy Dynamics developer talent is drying up. Microsoft partners are no longer trained on C/AL (NAV), X++ for legacy AX versions, or older CRM customization frameworks. The ecosystem has moved to AL for Business Central, modern X++ on D365 Finance and Supply Chain Management, and cloud-native Power Platform development for D365 Customer Engagement. Organizations maintaining heavy customizations on any legacy platform are finding it progressively harder and more expensive to source developers who can maintain their systems.
Dynamics 365 AI capabilities widen the gap with every release. Business Central's 2026 Wave 1 introduced AI agents, including a Payables Agent that processes invoices and a Sales Order Agent that validates orders. Copilot is embedded across finance, supply chain, sales, and customer service workflows in Dynamics 365. Sales Copilot in D365 Sales summarizes customer interactions, drafts emails, and surfaces deal insights. These capabilities exist only in Dynamics 365 online. Legacy on-premises systems cannot access them, and with each semi-annual release wave, the functional distance grows.
What Does Dynamics 365 Change for Legacy ERP and CRM Customers?
Regardless of whether you're coming from NAV, GP, AX, or CRM on-premises, the move to Dynamics 365 brings a consistent set of operational shifts. A projects more than 200% ROI over three years and payback in under six months for organizations migrating to Business Central.
- Cloud-native access from any device — Teams access the full ERP or CRM from a browser, tablet, or mobile app with no VPN, no on-premises server dependency, and no version-specific desktop client to maintain.
- Continuous updates without upgrade projects — Microsoft delivers two major release waves per year. Updates apply automatically, eliminating the costly, disruptive upgrade cycles that legacy customers know well.
- AI and Copilot embedded in daily workflows — Natural-language financial analysis, AI-assisted bank reconciliation, demand planning, deal insights, and customer service summaries change how teams interact with their data across both ERP and CRM workloads.
- Unified Microsoft ecosystem — Dynamics 365 connects natively with Microsoft 365, Teams, Power BI, Power Platform, and Azure, creating a connected environment that legacy on-premises installations cannot match.
How to Plan Your Legacy Dynamics Migration to Dynamics 365
A well-planned ERP migration typically runs four to eight months from assessment to go-live for mid-market deployments. AX migrations to D365 Finance and Supply Chain Management can run longer depending on customization depth and multi-entity complexity. CRM migrations tend to move faster when customization is light, but organizations with extensive workflows, plugins, and integrations should budget for comparable timelines.
- Assess your customization footprint — Inventory every C/AL customization (for NAV), VBA/Dexterity modification (for GP), X++ customization (for AX), or plugin and workflow configuration (for CRM). Determine which carry forward in Dynamics 365, which are replaced by native functionality, and which need rebuilding. Alletec's Customization Detection Tool automates this analysis for NAV environments.
- Choose the right migration path — A technical upgrade migrates existing data and configurations with minimal process change. A reimplementation starts fresh on Dynamics 365, redesigning workflows around current business needs. A hybrid approach combines both. The right path depends on how heavily customized the current system is and whether those customizations still serve the business.
- Evaluate Bridge to Cloud 3 eligibility — BTC3 covers NAV, GP, AX, and CRM customers. It requires an active Enhancement Plan and a perpetual license purchased before September 1, 2024. Confirming eligibility and enrolling before the December 2027 deadline locks in the 30% discount for a full three-year term.
- Plan change management alongside the technical work — Teams that have used the same system for a decade or longer need structured training and clear communication about what changes before go-live. Migration success depends as much on user adoption as on data accuracy.
Alletec has guided NAV, GP, AX, and CRM migrations to Dynamics 365 across industries, using a designed to reduce deployment risk and accelerate adoption. Whether you're evaluating the move for the first time or ready to start, to assess where your current environment stands and map a practical path forward.