Is Dynamics GP or NAV being discontinued?
Both, on very different clocks, and the panic is aimed at the wrong one.
Dynamics GP end of support dates
| BUSINESS PROFILE | TYPICAL USERS |
|---|---|
| April 1, 2025 | No new customers on GP perpetual licenses |
| April 1, 2026 | No new customers on GP subscription licenses |
| December 31, 2029 | End of enhancements, tax and regulatory updates, service packs, and support |
| April 30, 2031 | End of security updates |
That date has a sharper edge than it looks. The final year-end tax update ships in December 2029, so you can file 2029 W-2s in January 2030 and then you are done. Microsoft moved the date from September to December so filers could close a full tax year. Read that as a concession, not a signal more extensions are coming. (Source: Microsoft’s GP lifecycle page.)
The version trap most GP shops miss
That 2029 date applies only to versions under the Modern Lifecycle Policy, meaning 18.2 and later. GP 2018 R2 and earlier sit under the Fixed Lifecycle Policy, and GP 2016 and GP 2016 R2 reached end of life on July 14, 2026. Check your build number before assuming you have three years.
Dynamics NAV end of support dates
| VERSION | SUPPORT ENDS | STATUS |
|---|---|---|
| NAV 2015 | Expired | No new customers on GP perpetual licenses |
| NAV 2016 | April 14, 2026 | Expired |
| NAV 2017 | January 11, 2027 | 5 months out |
| NAV 2018 | January 11, 2028 | Final release |
Microsoft stopped selling NAV years ago and mainstream support ended for every version. What remains is a security-patch window closing in January 2028. GP customers have a three-year runway. A NAV 2017 customer has a fiscal quarter.
Dynamics SL and AX are further along
SL 2018 left mainstream support in January 2024 and its extended window closes July 11, 2028. AX 2012 R3 went fully unsupported on January 10, 2023.
Check your license type, not just your version
If you hold GP under subscription or SPLA rather than perpetual, confirm your use rights after April 30, 2031. Perpetual holders can run unsupported software indefinitely. Subscription holders may not.
When do you need to be off legacy Dynamics ERP?
Work backward from your fiscal year-end
Nobody cuts over on August 14. Finance teams cut on a fiscal boundary, because reconciling a partial year across two ledgers costs more in controller hours than the migration does.
A GP payroll customer needs to be live on January 1, 2030. Entity count, data condition, and custom code volume drive the schedule of a Business Central implementation, so get yours scoped rather than working from someone else’s average. Count the assessment, customization inventory, budget cycle, and data cleanup, and elapsed time from first conversation to go-live runs about a year. That puts budget conversations in 2028.
Why we tell clients to move earlier than the math requires
Every GP customer in North America is working from the same calendar, and channel capacity will not expand to meet a 2029 spike. Start in early 2028 and you pick your consultants and your date. Start in mid-2029 and you take whoever is left.
If you are on NAV 2017, the math is already broken
You will run unsupported software for part of this transition. Make that a decision rather than an accident: document the risk, isolate the server, and fix a go-live date. Our NAV to Business Central upgrade guide covers the sequencing.
What happens if you stay
“It keeps running” is true and beside the point. The failures arrive in this order.
Payroll and tax compliance
Federal and state tax tables, 1099 forms, W-2 formats, and T4 and RL-1 for Canadian entities all stop updating. Your team patches tax calculations by hand or buys a service, a permanent cost nobody budgeted.
Infrastructure and ISV attrition
GP and NAV are certified against specific SQL Server and Windows Server versions, and no hotfix is coming when your host retires an OS image. Meanwhile your EDI, document management, and barcode add-ons quietly deprioritize their GP and NAV editions. That hurts more than the Microsoft date, because the ISV never sends a formal notice.
Insurance and audit exposure
Cyber insurance renewals increasingly ask whether business-critical systems still receive vendor security patches. Answering no on the system holding your GL and AP is a bad renewal conversation.
Your replacement options, ranked
Option 1: Cloud migration to Business Central online
The right answer for most GP and NAV customers. The Cloud Migration tool replicates data table by table, reports success and failure per table, and runs against a sandbox first. For GP it maps your main account segment to the Business Central account number and remaining segments to dimensions, the most consequential decision in the project.
Option 2: Technical upgrade path for NAV
Business Central online only accepts NAV solutions brought to version 14 or later, and data in code-customized tables cannot carry forward. That is a hard constraint from Microsoft Learn, not a partner opinion. If your instance carries heavy C/AL customization in base tables, the “upgrade” is a re-implementation wearing a costume. Price it as one. We have watched more budget vanish into preserving twelve-year-old code than into any other decision here.
Option 3: Business Central on-premises
Legitimate with a real data-residency or connectivity constraint. It follows a fixed lifecycle and forfeits the Copilot and agent layer, which Microsoft restricts to online customers. Choose it for a reason you can write down.
Option 4: Leaving Microsoft entirely
Worth evaluating only if you have genuinely outgrown Business Central: process manufacturing with deep formula and batch genealogy, or 20+ entities with heavy intercompany consolidation. Business Central supports up to 300 companies per environment, so multi-entity alone is not the trigger, and a support deadline never justifies rebuilding your integrations, identity model, and reporting stack at once.
What Business Central covers, and where the ceiling is
Sophisticated buyers can smell it when a partner invents a gap to sell IP. Here is the honest split.
The AI and agent layer
- Payables Agent, GA November 7, 2025. Monitors a shared vendor mailbox, reads invoice attachments, matches vendors and GL accounts, stages invoices for approval.
- Sales Order Agent, GA November 2025, with multiple instances per company as of update 28.3.
- Expense Agent, public preview, English and US-only at launch, UK, Australia, and New Zealand from July 2026.
- Agent Designer, GA May 2026. Builds custom agents from natural-language instructions instead of AL code.
- Business Central MCP Server, GA January 27, 2026, expanded in version 28.
The AI is the easy part. The data underneath is the prerequisite. A GP database with four spellings of the same vendor produces as bad an agent as it does a report.
Three capabilities miscast as gaps
- Multi-location inventory is strong natively: Locations, SKUs, Transfer Orders, availability by location. If you run a GP bin-tracking add-on, you may not need it anymore.
- Shopify has a native, free connector. Marketplaces, EDI through SPS or TrueCommerce, and 3PL still need extension.
- Item variants and attributes are native, but variants are single-dimension, so a size x color x fit x style matrix needs more than the base product.
What the Cloud Migration tool will not move
Historical GL detail
Summary amounts land in the live ledger; transaction detail lands in separate GP Historical Snapshot tables, queryable from Power BI but not part of your ledger. Set depth with Oldest GL Year and Oldest Snapshot Year, three to five years in our experience, with the full database copied to Azure Data Lake. For reporting, use the native connector with Fabric Dataflow Gen2 or Azure Data Factory OData. If a partner proposes bc2adls, push back: it is unsupported sample code.
Module coverage
Financials, sales, purchasing, and inventory migrate cleanly. Project accounting, service, and manufacturing need work outside the tool, and GP Manufacturing does not map at all. Premium includes manufacturing, but the model differs, and treating that as data mapping instead of process redesign is how projects slip two quarters. Our manufacturing practice scopes it separately.
NAV customizations
Extensions are the only supported customization model online. Every piece of custom logic gets rebuilt, replaced, or retired. About a third of what we inventory exists because NAV could not do something Business Central now does natively.
How to start
- Pull your exact version and build. A GP 2016 shop is already unsupported; a GP 18.7 shop has three years.
- Run Microsoft’s free readiness check and get the structural issues in writing.
- Inventory integrations and ISV add-ons with each vendor’s Business Central roadmap beside them. A distributor we assessed found four of eleven had native replacements and two had no cloud path.
- Classify every customization: rebuild as an extension, replace with native functionality, or retire.
- Set your history policy with your controller and auditor in the room.
- Fix the go-live date on a fiscal boundary, then add a quarter of buffer.
Why Volt for a GP or NAV migration
This is a decade-plus operating decision. Business Central ships two major release waves a year plus monthly updates, and the firm you pick is the firm walking those release notes with you in 2036.
Vertical and industry expertise
We started as an apparel consulting firm, with more than 30 years in Microsoft ERP behind it. In apparel that means size and color matrices that survive a real assortment. In footwear, seasonal carryover that does not need a spreadsheet. In furniture, lead-time accuracy across a made-to-order book. In manufacturing, lot traceability that holds up in a recall drill. Volt 365® Apparel extends Business Central where the base product stops: Soft Allocation, Apparel Attributes with 30 configurable slots, Item Statuses, Seasonality, and Accruals & Landed Costs. See how it fits an apparel operation.
A hands-on engagement model
The principals and architects who scope your migration stay through delivery. No sell-and-disappear handoff, which matters most on decisions that are expensive to reverse, like dimension mapping.
Enterprise pedigree, applied to the mid-market
440+ ERP implementations and a 265% average ROI, with brands including Allure Bridals, 5.11 Tactical, Rag & Bone, and Groove Life. Volt is a 10x Microsoft Inner Circle member, the top 1% of Microsoft Business Applications partners worldwide.
24/7 Global Support
ERP operations do not stop at 5pm, and neither should your support. Volt provides 24/7 global support backed by teams across the U.S., Canada, Europe, and Asia, giving customers access to Dynamics expertise across time zones.
Whether you need help with Business Central, legacy Dynamics environments, integrations, or an issue that cannot wait until the next business day, our global team helps keep your operations moving.
Ready to Plan Your Migration?
Frequently Asked Questions
Yes. Enhancements, tax and regulatory updates, service packs, and technical support end December 31, 2029, with security updates through April 30, 2031. That date covers Modern Lifecycle versions; GP 2018 R2 and earlier have earlier dates, and GP 2016 already expired on July 14, 2026.
NAV is already discontinued as a product. Microsoft no longer sells licenses and mainstream support has ended for every version. NAV 2016 expired April 14, 2026, NAV 2017 ends January 11, 2027, and NAV 2018, the final release, ends January 11, 2028.
With a perpetual license, the software keeps working, but you lose tax updates, security patches, and Microsoft support, and ISV add-ons drop off on their own schedules. Under subscription or SPLA, confirm your use rights after April 30, 2031 before assuming you can stay.
Work backward from a fiscal year-end. The schedule depends on entity count, data condition, and custom code volume, so get yours scoped. Counting assessment, budget approval, and data cleanup, elapsed time from decision to go-live runs about a year. GP payroll customers need to be live January 1, 2030, so budget in 2028.
No. It moves summary amounts for historical years into the live ledger and puts transaction detail into separate GP Historical Snapshot tables, queryable from Power BI but not part of your ledger. Depth is set by Oldest GL Year and Oldest Snapshot Year; older data is archived to Azure Data Lake.
