Microsoft has issued definitive end-of-life timelines for three of its oldest on-premises enterprise resource planning systems—Dynamics NAV, Dynamics GP, and Dynamics SL—giving customers a hard date by which they must move to Dynamics 365 Business Central or risk operating without support and licensing options. The deadlines, published in a recent Microsoft Dynamics 365 Blog, set April 30, 2031 as the final day for NAV and GP commercial continuity, while SL users face a January 15, 2030 cutoff. For the thousands of businesses still reliant on these platforms, the clock is now ticking.
The Countdown: Key Dates at a Glance
| Product | Support Ends | Commercial Changes Date | Key Consequences |
|---|---|---|---|
| Dynamics NAV | Extended support: January 2028 | April 30, 2031 | Service plans end; no new perpetual user licenses; SPA subscriptions not renewable; SPLA use winds down |
| Dynamics GP | Enhancements/tax updates end December 31, 2029; Security updates until April 30, 2031 | April 30, 2031 | Service plans end; subscriptions not renewable; no new perpetual users; SPLA expected to end. New license sales stopped April 1, 2026 |
| Dynamics SL | Extended support: July 11, 2028 | January 15, 2030 | Service plans end; no new perpetual users; SPLA expected to end |
Dates confirmed by Microsoft’s July 28, 2026, migration announcement.
Dynamics NAV: Custom Code Is the Wildcard
The final version of NAV shipped in 2017, and Microsoft has now cemented the end of the line for its commercial viability. While extended support runs until early 2028, after April 2031, you can’t buy more user licenses or renew service plans. That means any growth or hardware refresh that demands extra seats becomes impossible without a migration. NAV users should also note that the older C/AL programming model must be converted to AL extensions for Business Central—a technically involved task that can take months if the system is heavily customized.
Dynamics GP: A Grace Period, Not an Indefinite Reprieve
GP’s timeline is more nuanced. Microsoft will stop delivering feature and regulatory updates by end of 2029, though it will offer security patches for a further 16 months. The April 2031 date mirrors NAV’s for the big commercial shifts. The company had earlier stopped selling new GP subscriptions as of April 2026. Organizations that need to add users or want ongoing tax table updates will feel pressure well before 2031.
Dynamics SL: The Shortest Fuse
SL customers are on the most urgent path. With extended support ending in July 2028 and commercial changes hitting just 18 months later, businesses running SL—particularly in project-driven sectors like professional services or government contracting—must prioritize migration now. The complexity of SL’s project accounting, billing, and custom tables means a rushed move in 2029 could be catastrophic.
What These Deadlines Mean for You
Beyond the dates, the operational impact varies by role. Here’s how it breaks down.
For Finance and Operations Leaders
Your current system won’t stop working on the deadline day, but it will become a frozen asset—no new licenses, no service plan safety net, and no compliance updates. As tax laws change, your team may have to manually adjust processes, introducing risk. Furthermore, without the option to add users, any merger, acquisition, or simple staff growth could force a chaotic migration under pressure.
For IT Managers and System Integrators
The migration to Business Central is not a simple lift-and-shift. It requires a thorough inventory of customizations, integrations, data mappings, and reporting requirements. You’ll need to decide between a full migration (bringing over historical data and recreating custom logic as extensions) or a reimplementation (starting fresh with master data and a few key opening balances). Each path demands careful testing in sandbox environments to avoid overwriting live data—Microsoft explicitly warns against running the cloud migration tool against a production Business Central tenant.
For Business Owners and Executives
The deadlines arrive in the context of broader technology trends: AI, automation, and real‑time analytics are becoming standard ERP features. Delaying migration means your competitors may gain capabilities you can’t access. But a poorly planned migration can disrupt operations for months. The strategic play is to treat this as a transformation program, not just an ERP upgrade. Budget for partner fees, internal project management, user training, and a period of parallel run. Start early—Microsoft’s partners will only get busier as 2030 approaches.
How We Got Here: A 20-Year ERP Journey
Dynamics NAV, GP, and SL have roots that go back decades. Microsoft acquired Navision (NAV) and Great Plains (GP) in 2002 with the aim of capturing the small and midsize business ERP market. SL, originally Solomon Software, followed later. These products thrived in the era of thick-client, Windows-server applications, serving manufacturing, distribution, and service industries.
By the 2010s, the industry pivot to cloud and software-as-a-service became undeniable. Microsoft launched Dynamics 365 in 2016, and in 2018, it released Business Central as the cloud successor to NAV. The company has since poured investment into Business Central, adding continuous updates, AI copilots, and deep integration with Microsoft 365 and Power Platform.
The announcements in 2025 and 2026 formalize what many saw coming: on‑prem Dynamics, though still running critical operations worldwide, are entering the final chapter of active commercial support. Microsoft’s message is consistent: the future is Business Central.
What to Do Now: A Practical Migration Roadmap
Whether you’re on NAV, GP, or SL, the actions are similar—but timing is everything. Here’s a five-step plan.
1. Audit Your Current Environment
Document everything: software version, database size, number of companies, user count, customized objects, third‑party add‑ons, integrations (EDI, payroll, e‑commerce, banking), reports, and security roles. Also identify “shadow processes”—the Excel sheets and manual workarounds that keep the business running—because they’ll need to be formalized in the new system.
2. Decide on Migration Strategy
- Full migration: Bring over historical transactions and convert customizations to AL extensions. Suitable when audit trails and deep history are critical.
- Reimplementation: Start with master data and opening balances, rebuilding only essential customizations. Faster and cleaner, but requires users to access historical data elsewhere.
You can mix approaches—for instance, migrate all sales history but reimplement purchasing.
3. Engage an Experienced Microsoft Partner
Business Central migrations are specialized. Look for partners with proven experience in your specific legacy product (NAV, GP, or SL) and your industry. They can help you navigate upgrade paths, tooling (like the GP migration wizard or NAV upgrade stages), and common pitfalls.
4. Run Multiple Test Migrations
Microsoft provides sandbox environments for exactly this purpose. Perform a dry run, validate data, fix mapping errors, test extensions, and measure migration duration. Repeat until it’s smooth. Never test on your production Business Central—replication can overwrite live data.
5. Invest in User Adoption
A new ERP that no one understands is a failure. Train users on their real-world tasks: month‑end close, billing, purchase approvals. Role‑based training, floor support during cutover, and a hypercare period with dedicated help are far more valuable than generic slide decks.
Outlook: No Extension, No Surprise
Microsoft has a history of sticking to these commercial deadlines. While the dates may feel distant, the complexity of ERP migration means planning must start now—2028 for an SL user is almost too late if you haven’t begun by 2025. Expect more guidance, tooling improvements, and AI‑powered migration assistants from Microsoft, but the ultimate responsibility rests with each customer. The next version of Business Central will only get more capable; your legacy system will only become more of a liability. The companies that begin their roadmap today will be the ones that turn this mandatory move into a genuine advantage.