Microsoft Dynamics Legacy Product End-of-Life Timeline [2026]

Dynamics GP ends support April 9, 2026; NAV ended January 2026; AX 2012 ended January 2024. End-of-support means no security patches, compliance risk, and accelerating costs. Organizations running unsupported systems face regulatory exposure, security vulnerabilities, and operational risk that compounds annually.

Last updated: June 19, 202611 min read10 sections

Quick Reference

Dynamics GP EOS (18.x)December 31, 2029 (product support); April 30, 2031 (security patches)

Dynamics GP 2016/2016 R2 EOSJuly 14, 2026 (extended support ends)

Dynamics NAV 2017 EOSJanuary 11, 2027 (extended support ends)

Dynamics NAV 2018 EOSJanuary 11, 2028 (extended support ends)

Dynamics SL 2018 EOSJuly 11, 2028 (extended support); January 15, 2030 (service plan)

AX 2012 R3 EOSJanuary 10, 2023 (fully unsupported — 3+ years ago)

Security Patch FrequencyStops at EOS; no further patches released

Typical Migration Timeline12–18 months from decision to go-live

Microsoft has systematically announced end-of-life timelines for its legacy Dynamics products, creating a wave of migrations across the global install base. Understanding the timeline of end-of-support dates, what they mean practically, and the resulting migration urgency is critical for organizations running Dynamics GP, NAV, SL, or AX 2012.

As of June 2026, Dynamics GP (version 18.x, Modern Lifecycle) continues to receive full product support, with Microsoft having extended its support end date to December 31, 2029 (security patches through April 30, 2031). Dynamics AX 2012 R3 reached full end-of-support in January 2023. Dynamics NAV 2017 mainstream support ended in January 2022 (extended support runs through January 2027). Dynamics SL 2018 has extended support through July 2028. Organizations on these systems face varying levels of urgency depending on version and lifecycle status.

Microsoft Dynamics Product End-of-Support Timeline

Product	End-of-Support Date	Status (as of June 2026)	Years in Market (approx.)	Typical Install Base
Dynamics AX 2012 R3	January 10, 2023 (extended)	3+ years fully unsupported	14 years	~3,000 organizations
Dynamics NAV 2017 & earlier	January 11, 2022 (mainstream); January 11, 2027 (extended)	Mainstream ended; extended support active through Jan 2027	15+ years	~8,000–12,000 organizations
Dynamics NAV 2018	January 10, 2023 (mainstream); January 11, 2028 (extended)	Mainstream ended; extended support active through Jan 2028	15+ years	Included in NAV install base above
Dynamics SL 2018	January 9, 2024 (mainstream); July 11, 2028 (extended)	Mainstream ended; extended support active through Jul 2028; service plan through Jan 2030	20+ years	~2,000 organizations (shrinking)
Dynamics GP 2016 / 2016 R2	July 14, 2026 (extended support)	Approaching end of extended support	25+ years	Subset of GP install base
Dynamics GP 18.x (Modern Lifecycle)	December 31, 2029 (product support); April 30, 2031 (security patches)	Fully supported; receiving regular updates	25+ years	~15,000–20,000 organizations
Dynamics 365 Finance & Operations	Modern Lifecycle (no fixed retirement date)	In support; evergreen with regular updates	8+ years	~5,000 organizations
Dynamics 365 Business Central	N/A (continuous update)	Evergreen; always current	8+ years	~50,000+ organizations

Key Insight: The migration landscape has shifted significantly since 2024. Dynamics GP (version 18.x) has support through December 2029—giving organizations a planning runway, not a crisis. However, older GP versions (2016 and earlier), AX 2012 R3, and organizations with outdated NAV versions face immediate or near-term action points. AX 2012 R3 reached full end-of-support in January 2023 and is now 3+ years unsupported. Microsoft has encouraged all GP and SL customers to transition to Dynamics 365 Business Central, while the December 2029 deadline provides structured migration time. One exception: GP 2018 and GP 2018 R2 installs that never applied a tax update or hotfix (i.e., remained below version 18.5) stay on the Fixed Lifecycle Policy, whose extended support ends January 11, 2028—earlier than the Modern Lifecycle dates above. Applying any compatible tax release or hotfix moves them to 18.5+ and onto the Modern Lifecycle (December 2029 / April 2031).

What End-of-Support Actually Means

End-of-support (EOS) is not a hard cutoff; the system doesn't stop working. Rather, it means Microsoft stops providing:

Security Patches & Vulnerability Fixes

When a security vulnerability is discovered in an EOS system (SQL injection, authentication bypass, privilege escalation), Microsoft will not release a patch. The vulnerability remains in the system forever. This creates a growing surface area of security risk that compounds annually.

Real-world impact: An organization running AX 2012 R3 (fully past EOS since January 2023) discovers a SQL injection vulnerability in 2026. The organization can't upgrade to a patched version because there isn't one. The organization must either accept the vulnerability (and risk) or migrate to a supported system.

Bug Fixes & Stability Updates

Customers on EOS systems that encounter bugs must either (1) find workarounds, (2) accept the bug, or (3) pay for custom fixes. This is expensive & unsustainable long-term.

Performance & Compatibility Updates

As underlying infrastructure evolves (Windows Server versions, SQL Server versions, cloud platforms), EOS Dynamics systems may have compatibility issues. Supporting these becomes a perpetual maintenance burden.

Compliance & Regulatory Risk

Financial institutions, healthcare organizations, and government agencies often have compliance requirements that mandate running supported, patched software. Running an EOS system can violate:

SOX (Sarbanes-Oxley): Public companies must maintain "effective internal controls over financial reporting." Running unsupported ERP software on which you can't patch vulnerabilities contradicts this mandate.
HIPAA: Healthcare organizations must implement "appropriate safeguards" for patient data. Unpatched software is not a safeguard.
PCI-DSS: Any organization handling payment card data must run patched, supported systems. Unpatched systems are non-compliant.
GDPR & Data Protection: EU organizations must implement appropriate technical measures to protect data. Running unpatched software fails this requirement.

Practical impact: Auditors increasingly flag the use of EOS software as a control deficiency. Some organizations are required by audit findings to migrate within 12 months as a remediation item.

The Cost of Staying Unsupported

Organizations sometimes ask: "What if we just stay on Dynamics SL / NAV / GP after support ends?" The answer is: it's possible, but costs compound.

Year 1 (EOS Year) Costs of Staying Unsupported

Security monitoring: $20K–$50K annually (hire security consultants to audit & monitor for vulnerabilities)
Workarounds & custom fixes: $10K–$30K (bugs that would be fixed by vendor must be fixed internally)
Regulatory & compliance overhead: $15K–$40K (audit responses, compliance documentation)
Integration & compatibility issues: $10K–$20K (compatibility with third-party systems, newer OS versions)

Year 1 cost of staying unsupported: $55K–$140K (estimates based on typical mid-market consulting rates; actual costs vary by organization size and security posture)

Years 2–3+ Costs (Compounding)

As time passes post-EOS, costs multiply:

Security vulnerabilities accumulate; more monitoring is required
Vendor lock-in increases (fewer partners willing to support EOS systems, so you're locked into current vendors)
Recruitment becomes harder (IT talent doesn't want to support 15+ year old systems)
Integration complexity increases (newer systems less likely to integrate with old systems)
Regulatory risk compounds (auditors increasingly flag EOS systems as control deficiencies)

Year 3–5 cost of staying unsupported: $150K–$400K annually (estimated range; varies significantly by organization)

By contrast, migrating proactively (cost: $100K–$250K for mid-market) eliminates these ongoing risks & costs. Migration is often the cheaper option when you factor in 3–5 year horizons.

Dynamics GP: A Defined Migration Window Through 2029

Dynamics GP (version 18.x, Modern Lifecycle), running at ~15,000–20,000 organizations globally, has support through December 31, 2029, with security patches continuing through April 30, 2031. Microsoft extended the previously announced September 30, 2029 end date to December 31, 2029 to allow organizations to meet payroll and tax obligations for the full 2029 year.

Important note for older GP versions: Organizations running GP 2016 or GP 2016 R2 under the Fixed Lifecycle Policy should be aware that extended support ends July 14, 2026. Organizations on GP 2015 or earlier have already passed their extended support dates. Upgrading to GP 18.x brings organizations under the Modern Lifecycle and the December 2029 support window.

The Migration Timeline Challenge

A typical Dynamics GP to Business Central migration takes 12–18 months from start to finish:

Months 1–3: Assessment & planning (current state analysis, data audit, business case development, partner selection)
Months 4–10: Design, build, and test (configuration, data migration, customization, UAT)
Months 11–12: Final testing, training, cutover, and hypercare

Organizations targeting a migration by end of 2028 (to avoid last-minute pressure before the December 2029 deadline) should begin planning in 2026–2027. Starting in mid-2028 or later will compress timelines and increase risk and cost.

GP Migration Paths

Organizations have three primary options for GP:

Option	Target System	Timeline	Cost Range (Mid-Market)	Best For
Recommended	Dynamics 365 Business Central (cloud)	12–18 months	$100K–$250K	Most GP organizations (mid-market, cloud-ready)
Enterprise	Dynamics 365 Finance & Operations (cloud)	15–24 months	$300K–$800K	Large enterprises, complex requirements
Alternative	Non-Microsoft ERP (SAP, Oracle, Infor)	18–30 months	$200K–$500K+	Organizations wanting non-Microsoft ecosystem

Business Central is the most common path: it's cloud-native, cost-effective, has a robust partner ecosystem, & has an 18-month average migration timeline. The downside: it requires organizations to commit to Microsoft's ecosystem (Microsoft 365, Power BI, etc.).

Dynamics NAV: Mainstream Support Ended; Extended Support Varies by Version

Dynamics NAV support status depends heavily on version. NAV 2017 mainstream support ended January 11, 2022, but extended support runs through January 11, 2027. NAV 2018 mainstream support ended January 10, 2023, with extended support through January 11, 2028. Any NAV version earlier than 2017 is fully unsupported.

NAV Migration Context

NAV is less common than GP, but still deployed at ~8,000–12,000 organizations. NAV was strongest in Europe & Commonwealth countries; North America NAV deployments are smaller. Organizations running NAV 2016 or earlier are operating fully unsupported. Those on NAV 2017 or 2018 have extended support through 2027–2028, but no new features or mainstream bug fixes—migration planning should begin now.

NAV Migration Paths

Business Central (recommended): Shortest, lowest-cost migration path. NAV & BC share underlying architecture; many NAV concepts map directly to BC. Timeline: 12–15 months.
Dynamics 365 Finance & Operations: For larger NAV deployments needing advanced supply chain / manufacturing. Timeline: 18–24 months.
Alternative ERPs: Less common but possible for organizations wanting non-Microsoft solution.

ERP Comparison Matrix: All Major Systems [2026]

Complete ERP comparison matrix. Score Dynamics 365, SAP S/4HANA, Oracle Fusion, NetSuite, Acumatica by feature.

Dynamics SL: Extended Support Through July 2028

Dynamics SL 2018 (the most current version) has extended support through July 11, 2028, with Microsoft's service plan coverage continuing through January 15, 2030. Mainstream support for SL 2018 ended January 9, 2024. Older SL versions have earlier end dates—any version prior to SL 2018 has already passed extended support.

Who Still Runs SL?

Roughly 2,000 organizations still run Dynamics SL, typically:

Small manufacturers or distributors (SL was strong in these verticals)
Organizations with minimal IT resources (can't afford migration)
Organizations with heavy custom SL code (migration complexity is high)

SL Migration Paths

Business Central (recommended): Requires significant data transformation; SL architecture doesn't map natively to BC. Timeline: 12–18 months. Cost: $100K–$200K for mid-market.
Dynamics 365 F&O: For larger SL deployments.
Alternative ERPs: Organizations with complex SL customizations sometimes choose non-Microsoft platforms to avoid re-engineering cost.

For SL organizations: those on SL 2018 have extended support through July 2028, but mainstream bug fixes and new features have ended. Begin migration planning in 2026 to allow sufficient runway before the July 2028 extended support deadline.

AX 2012: Fully Past End-of-Support Since January 2023

Microsoft Dynamics AX 2012 R3 reached end of mainstream support October 12, 2021, and full end-of-extended-support January 10, 2023—making it over 3 years fully unsupported as of June 2026. Roughly 3,000 organizations still run AX 2012, typically large manufacturers or distributors with significant customization.

AX 2012 Migration Urgency

AX 2012 organizations should treat migration as highly urgent. Operating 3+ years past all support has accumulated significant security vulnerability, compliance exposure, and vendor lock-in. Some organizations delay AX 2012 migration due to complexity (AX 2012 to D365 F&O is a significant re-implementation), but delaying amplifies risk & cost substantially.

AX 2012 Migration Paths

Dynamics 365 Finance & Operations (cloud): Recommended for large enterprises. Timeline: 18–24 months. Cost: $500K–$1.5M+
Business Central: For smaller AX 2012 deployments or organizations wanting lower-cost alternative. Timeline: 12–18 months. Cost: $100K–$300K.
Alternative ERPs: SAP, Oracle ERP Cloud, Infor.

Migration Decision Framework for EOS Systems

If you're running a legacy Dynamics system, here's how to approach migration decision-making:

Step 1: Assess Your Runway (What time do you have?)

GP 2016 / 2016 R2: Extended support ends July 14, 2026. Immediate action required.
GP 18.x (Modern Lifecycle): Support through December 31, 2029. Begin planning in 2026–2027 to avoid a compressed migration window.
NAV 2018: Extended support through January 11, 2028. Begin planning now.
NAV 2017: Extended support through January 11, 2027. Begin planning now.
NAV 2016 and earlier: Fully unsupported. Migrate urgently.
SL 2018: Extended support through July 11, 2028. Begin planning in 2026.
SL (older versions): Already past extended support. Migrate immediately.
AX 2012: 3+ years past all support. Highest urgency; migrate immediately.

Step 2: Assess Your Complexity (What effort will migration require?)

Low complexity: Minimal customizations, limited third-party integrations, clean data. Timeline: 10–12 months. Partner: generalist.
Medium complexity: Some customizations, 3–5 integrations, data quality issues. Timeline: 12–15 months. Partner: specialist.
High complexity: Heavy customizations, 10+ integrations, messy data, multi-site. Timeline: 15–20 months. Partner: migration specialist + senior consulting partner.

Step 3: Identify Your Constraints (What is your risk tolerance & budget?)

High risk tolerance / high budget: Choose Business Central or D365 F&O based on organization size & requirements.
Low risk tolerance / high budget: Choose D365 F&O (more stable, feature-rich, vendor-supported).
Low budget: Choose Business Central (lower cost, faster migration, cloud-based).
Want to leave Microsoft ecosystem: Evaluate SAP, Oracle, Infor, NetSuite.

Step 4: Develop Migration Plan

Once you've assessed runway, complexity, & constraints, build your migration plan with clear milestones & deadlines. Engage a partner early (month 1 of planning, not month 11).

Conclusion

The Dynamics product end-of-life landscape is more nuanced than it may appear. Dynamics GP (18.x) has a clear runway through December 2029, giving organizations structured migration time—but that runway requires active planning starting now to avoid a compressed, higher-risk migration in 2028–2029. AX 2012 R3 is 3+ years fully unsupported and organizations on it face compounding risk. NAV and SL organizations have varying timelines depending on version, with extended support windows running through 2027–2028. Migration is a significant investment (12–18 months, $100K–$250K+ for mid-market), but the cost of staying on fully unsupported systems—compounding security risk, compliance exposure, vendor lock-in, and regulatory violations—typically exceeds it over a 3–5 year horizon. Organizations should begin migration planning in 2026, before competitive demand for partners and rising implementation costs narrow their options.

Sources

Last validated June 19, 2026

Frequently Asked Questions

1What exactly does end-of-support mean?

End-of-support (EOS) means Microsoft stops releasing security patches, bug fixes, and performance updates. The system remains technically functional, but vulnerabilities discovered after EOS will never be patched. For compliance-sensitive industries (finance, healthcare, government), running unsupported systems creates regulatory risk. For all organizations, it increases security vulnerability and operational risk.

2Can we stay on Dynamics GP or NAV after end-of-support?

Technically, yes. Many organizations run EOS systems for years after support ends. However, this incurs growing risk: security vulnerabilities, compliance violations, vendor lock-in (because newer Microsoft systems won't connect easily to EOS systems), and difficulty hiring IT staff to support legacy technology. The question isn't "can we?' but "should we?"—and the answer for most is no.

3What is the practical deadline for migration?

For Dynamics GP 18.x (Modern Lifecycle): support runs through December 31, 2029. Organizations should begin planning in 2026–2027 to allow a 12–18-month migration window without year-end compression. For GP 2016/2016 R2: extended support ends July 14, 2026—immediate action required. For NAV 2017: extended support through January 11, 2027—begin planning now. For NAV 2018: extended support through January 11, 2028—begin planning now. For NAV 2016 and earlier: fully unsupported—migrate urgently. For SL 2018: extended support through July 11, 2028—begin planning in 2026. For AX 2012 R3: 3+ years past all support as of June 2026—highest urgency.

4Is Business Central the only option, or are there alternatives?

Business Central is Microsoft's modern cloud ERP and the recommended upgrade path for GP & NAV users. However, organizations can also migrate to Dynamics 365 Finance & Operations (larger enterprises), or non-Microsoft platforms (SAP, Oracle, Infor). Business Central is typically the most cost-effective & lowest-risk migration path for mid-market organizations.

5What if we are only partially through a migration?

If you're mid-migration when EOS hits, you can request extended support from Microsoft (often available for additional cost, typically $50K–$100K). This buys you 6–12 additional months. Plan your migration timeline conservatively to avoid needing extended support; it's expensive & Microsoft doesn't grant it indefinitely.

6Should we migrate all at once or in phases?

Migration strategy (big-bang vs. phased) depends on your organization’s risk tolerance & timeline. Big-bang migration (all modules, all sites, one cutover) is faster (3–6 months) but riskier. Phased migration (by module or geography over 6–12 months) is lower-risk but more operationally complex. For GP 18.x organizations, the December 2029 deadline provides planning runway—but starting in 2026–2027 allows time for a phased approach. For organizations already past EOS (AX 2012, NAV 2016 and earlier) or approaching near-term deadlines (GP 2016, NAV 2017), treat migration as the highest priority and plan for the most aggressive timeline your organization can sustain.