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: March 19, 202611 min read9 sections

Quick Reference

Dynamics GP EOSApril 9, 2026 (33 months away)

Dynamics NAV EOSJanuary 13, 2026 (already ended)

Dynamics SL EOSJuly 10, 2019 (6+ years unsupported)

AX 2012 EOSJanuary 13, 2024 (already ended)

Users Still on EOS Systems~35% of Dynamics shops still on EOS or approaching EOS

Average Remaining RunwayGP: 9–12 months; NAV: already expired

Security Patch FrequencyStops at EOS; no further patches released

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

Microsoft has systematically retired 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 March 2026, Dynamics GP—the most widely deployed Dynamics product—has just 12 months of support remaining (ending April 9, 2026). Dynamics NAV already reached end-of-support in January 2026. Organizations still operating these systems face a critical decision: plan and execute a migration, or accept growing security & compliance risk.

Microsoft Dynamics Product End-of-Support Timeline

Product	End-of-Support Date	Status (as of March 2026)	Years in Market (approx.)	Typical Install Base
Dynamics SL (Solomon IV)	July 10, 2019	6+ years unsupported	20+ years	~2,000 organizations (shrinking)
AX 2012 R3	January 13, 2024	2 years past EOS	14 years	~3,000 organizations
Dynamics NAV (2017 & earlier)	January 13, 2026	Just reached EOS	15+ years	~8,000–12,000 organizations
Dynamics GP (2015 & earlier)	April 9, 2026	12 months remaining	25+ years	~15,000–20,000 organizations
Dynamics 365 Finance & Operations	October 13, 2025	End of mainstream support (extended through Oct 2030)	8 years	~5,000 organizations
Dynamics 365 Business Central	N/A (continuous update)	Evergreen; always current	5 years	~50,000+ organizations

Key Insight: Dynamics GP, the largest and most mature Dynamics product, ends support in 9 months. This creates a migration imperative for 15,000–20,000 organizations globally. Dynamics NAV already ended support and any remaining NAV deployments are operating unsupported. AX 2012 ended support 2 years ago; organizations still on AX 2012 are making a deliberate choice to operate unsupported (usually due to cost constraints or migration complexity).

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: A financial services organization running Dynamics SL (EOS since 2019) discovers a SQL injection vulnerability in 2025. 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)
Extended support insurance: $30K–$100K (if Microsoft offers extended support, which they do, at premium rates)
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: $85K–$240K

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

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

Dynamics GP: The Immediate Crisis (12 Months Remaining)

Dynamics GP, running at ~15,000–20,000 organizations globally, ends support April 9, 2026. This is roughly 12 months away (as of March 2026). For GP organizations, migration urgency is critical:

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 that haven't begun planning should start immediately. Organizations starting planning in Q3 2025 will be in crisis migration mode and face higher risk & costs. Organizations starting in Q4 2025 or later will likely miss the April 2026 deadline and will need to request extended support (costly) or accept operating unsupported (risky).

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 (Office 365, Power BI, etc.).

Dynamics NAV: Already at End-of-Support

Dynamics NAV reached end-of-support January 13, 2026—meaning any NAV systems currently in operation are now officially 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 still running NAV should migrate urgently (no remaining runway).

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.

Post-Migration Optimization & Stabilization [2026]

Manage post-migration hypercare, stabilization, user adoption, performance tuning, legacy decommissioning, and ROI measurement after go-live.

Dynamics SL: Oldest EOS Product (6+ Years Unsupported)

Dynamics SL (Solomon IV, acquired by Microsoft in 1998) reached end-of-support July 2019—over 6 years ago. Organizations still running SL are making a deliberate choice to operate unsupported & unpatched.

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: migration is urgent from a security & compliance perspective, even if it's not urgent from a system stability perspective. Start planning immediately.

AX 2012: Already 2 Years Past EOS

Microsoft Dynamics AX 2012 R3 reached end-of-support January 13, 2024—2 years ago. 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 urgent. Operating 2 years past EOS incurs all the risks mentioned above: security vulnerabilities, compliance exposure, 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.

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 an EOS system, here's how to approach migration decision-making:

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

GP: 12 months until EOS (April 2026). If not planning yet: immediate action required.
NAV: Already EOS (January 2026). Operating unsupported; migrate urgently.
SL: 6+ years EOS. Security & compliance risk is acute; migrate in 2026.
AX 2012: 2 years EOS. Migrate in 2026.

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 wave is creating a migration imperative for ~35,000–40,000 organizations worldwide. Dynamics GP, the largest wave, reaches EOS in April 2026 (12 months away). NAV already reached EOS. Organizations still running SL or AX 2012 are operating on borrowed time. The cost of migration is significant (12–18 months, $100K–$250K+), but the cost of staying unsupported is higher: compounding security risk, compliance exposure, vendor lock-in, and regulatory violations. Organizations should begin migration planning immediately if they haven't already. Those that wait until late 2025 will face crisis migration mode, higher costs, & elevated risk. Those that start now will deliver a smooth, controlled migration by the EOS deadline.

Frequently Asked Questions

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.

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.

For Dynamics GP ending April 2026: organizations should target cutover by Q1 2026 (12–15 months away from now). This assumes you start planning immediately. If you wait until Q4 2025 to begin migration planning, you'll be in crisis mode. For NAV (already EOS): migrate urgently if still in use. For systems already EOS (SL, AX 2012): urgency is compliance-driven (what are your risk tolerance & regulatory requirements?).

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.

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.

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. Given the GP EOS deadline, organizations without a migration plan should start immediately & plan for big-bang (or aggressive phased) cutover by Q1 2026.