Microsoft Dynamics NAV, long known as Navision, remains deployed in a large number of SMEs around the world. This ERP, originally developed in Denmark in the 1980s, has supported generations of businesses in managing their financial, logistical, and production flows.
The current situation of Dynamics NAV warrants careful examination: with the end of scheduled support, upcoming licensing constraints, and migration to Business Central, the decisions to be made go far beyond a simple software choice.
End of NAV Support: A Game-Changing Timeline for SMEs
Most of the content available online focuses on the end of support for NAV 2018, scheduled for January 2028. This point is valid, but it masks a more pressing reality for companies still on earlier versions.
NAV 2017, a version still very common in French SMEs, will see its extended support end on January 11, 2027. No official Extended Security Updates program has been announced for this version. In practical terms, affected companies will no longer have access to security patches from that date.
For more recent versions like NAV 2018, the situation post-2028 is also restrictive. As detailed in the Dynamics NAV presentation by ASCI, this software covers a wide functional scope, but after the end of support, organizations will no longer be able to renew their service plans or acquire additional licenses. NAV then becomes a frozen system, which raises concrete issues of regulatory compliance and cybersecurity.
Dynamics NAV and Financial Management: What the ERP Really Covers
The core functionality of NAV is based on financial management. General accounting, asset management, bank reconciliations, multidimensional budgets: the financial module is designed for mid-sized structures that need accounting rigor without the heaviness of ERPs intended for large groups.
On the other hand, NAV’s native analytical capabilities remain limited compared to current standards. The integrated dashboards and reports work, but they do not offer the flexibility of modern business intelligence tools. Companies still using NAV frequently complement the financial module with exports to Excel or third-party connectors to Power BI.
Supply Chain and Production in NAV
Beyond finance, NAV includes modules for inventory management, procurement, and production planning. These functions allow for tracking inventory movements, managing bills of materials, and controlling manufacturing orders.
- Inventory management supports location tracking, automatic replenishments, and valuation according to various accounting methods
- The production module manages routing, machine capacities, and manufacturing orders with net requirements calculation (MRP)
- Project management allows for tracking budgets, allocated resources, and progress billing
These modules have proven themselves in industrial and trading contexts. Their main limitation lies in the architecture: NAV operates on a client-server on-premise model, which implies a local infrastructure to maintain and manual updates.
Migration to Business Central: Technical Constraints and Strategic Choices
Microsoft positions Dynamics 365 Business Central as the direct successor to NAV. The technical lineage is real: Business Central takes over the application engine of NAV and extends its capabilities in a cloud environment.
The migration is not a simple upgrade. Transitioning from NAV to Business Central involves several structural transformations:
- The development language shifts from C/AL to AL, requiring the rewriting of existing customizations
- Extensions replace direct modifications to the source code, imposing a redesign of the development approach
- Cloud hosting (Azure) replaces the local server, with implications for data management and connectivity
- Updates become automatic and monthly, removing fine control over the upgrade schedule
The rewriting of customizations represents the heaviest aspect of a migration project. A company that has heavily customized its NAV over the years may face a project lasting several months, with a budget that directly depends on the volume of specific code accumulated.
Microsoft’s Bridge to Cloud Program
To accelerate migrations, Microsoft offers a promotional program called Bridge to Cloud, which provides preferential pricing conditions to NAV customers wishing to switch to Business Central. This program explicitly targets companies under NAV, GP, and SL, with discounted cloud licenses during a transition period.
Field feedback on this point varies: some companies view these conditions as an opportunity, while others believe that the total cost of migration far exceeds the pricing advantage on licenses, once development, training, and change management are taken into account.
Staying on NAV After 2028: Concrete Risks and Maneuvering Room
Some companies are considering keeping NAV beyond the end of support, relying on their existing perpetual licenses. This option is technically possible but carries identified risks.
Without security patches, any discovered vulnerability remains open. For companies subject to regulatory obligations (GDPR, industry standards), the lack of security updates can pose a compliance issue. External audits increasingly incorporate the support status of software into their evaluation criteria.
The inability to extend the license pool after the end of service plans also limits growth. A company that hires or opens a new site will not be able to add users to its NAV instance. NAV becomes a system that can no longer support the organization’s evolution.
The market for NAV skills is also contracting. C/AL developers are gradually shifting to AL and Business Central, making corrective maintenance and upgrades increasingly costly to outsource to specialized providers.
For companies still on NAV 2017 or earlier versions, the decision window is closing rapidly. Those using NAV 2018 have a slightly longer timeframe, but the migration project is better anticipated than dealt with in the urgency of an end of support.