Microsoft is moving customers from Dynamics NAV to Dynamics 365 Business Central. For businesses still using NAV, 2026 is a good time to review their ERP system and plan the next step. Microsoft has announced April 30, 2031, as the end-of-sale date for Dynamics NAV. After this date, certain NAV licenses and renewal options will no longer be available. Dynamics NAV 2018 extended support ends earlier, on January 11, 2028.
These dates do not mean that NAV will stop working immediately. However, businesses should start planning how to support and modernise their ERP systems going forward.
Why are NAV customers facing a decision point?
Dynamics NAV has supported businesses for many years, but it is now a legacy ERP platform. Continuing with an older NAV environment can make it harder to adopt new technology, maintain integrations, support changing business requirements, and keep the ERP environment aligned with Microsoft’s product roadmap.
The upcoming milestones make it important to assess:
- Current NAV version and support status
- Existing licenses and Service Plan
- Customisations and extensions
- Third-party solutions and integrations
- Historical and operational data
- Reporting and business intelligence requirements
- Future compliance and digital transformation needs
What does the 2031 end-of-sale date mean?
April 30, 2031, is an end-of-sale milestone. It does not mean NAV installations will automatically stop functioning. After this date, customers will face restrictions on several commercial options, including:
- Service Plan renewals: Existing NAV service plans will no longer be renewable.
- Additional perpetual licenses: New perpetual user licenses for existing NAV deployments will no longer be available.
- NAV subscriptions: Certain NAV subscription licenses will no longer be renewable.
- Migration benefits: Some benefits associated with active NAV service plans will no longer be available.
Businesses should therefore distinguish between end of sale and end of support.
Why move to dynamics 365 business central?
Microsoft positions Dynamics 365 Business Central as the modern ERP platform for NAV customers. Business Central provides capabilities that address many of the limitations associated with legacy NAV environments:
- Cloud-based ERP with Microsoft-managed infrastructure
- Continuous updates rather than traditional major upgrade cycles
- Integration with Microsoft 365, including Outlook, Excel, and Teams
- Power BI for reporting and analytics
- Power Automate and Power Platform for workflow automation
- AI and Copilot capabilities
- Access across devices and locations
- Scalability for growing organisations
The objective should not be to simply reproduce the existing NAV system in Business Central. Migration provides an opportunity to review existing processes and determine what should be retained, simplified, or modernised.
Upgrade or Reimplementation?
The right approach depends on the existing NAV environment.
Upgrade and Migration
A migration approach can be suitable when existing business processes, data, and customisations remain relevant.
The project typically involves:
- Assessing existing NAV customisations
- Migrating relevant data
- Reviewing integrations
- Converting applicable customisations
- Testing business processes
- Preparing users for the new environment
NAV customisations written in C/AL require particular attention because Business Central uses the modern AL extension model.
Reimplementation
Reimplementation starts with a cleaner Business Central environment and focuses on current business requirements.
This can be appropriate when the NAV environment contains:
- Outdated customisations
- Unused functionality
- Complex workarounds
- Redundant data
- Legacy integrations
Instead of carrying every legacy component forward, organisations can redesign processes around standard Business Central functionality.
What changes with Business Central?
One of the biggest changes is the move from traditional NAV customisation to the AL extension model. Business Central also provides stronger integration with the wider Microsoft ecosystem. Finance and operational data can be connected with Power BI for reporting, while Power Automate can support workflow automation.
AI is another important area of development. Microsoft continues to expand Copilot and AI capabilities within Business Central, helping organisations automate selected tasks and work with business information more efficiently.
What should UAE businesses consider?
UAE organisations should consider local regulatory and operational requirements as part of their ERP migration strategy.
This includes reviewing:
- VAT processes and reporting
- UAE e-invoicing requirements
- Financial reporting
- Integration with external systems
- Data residency and security requirements
- Business Central localisation requirements
The UAE’s e-invoicing program also makes ERP readiness increasingly important. The pilot phase began on July 1, 2026, with mandatory implementation scheduled to begin on January 1, 2027, for businesses meeting the applicable criteria.
An ERP migration planned without considering these requirements can result in additional changes later. Including them during solution design can help create a more sustainable ERP environment.
Licensing and Migration Planning
Licensing should be reviewed at the beginning of the migration project. Eligible NAV and Business Central on-premises customers may have access to Microsoft’s Bridge to Cloud program, subject to the applicable eligibility and licensing conditions.
Businesses should review their current
- NAV licenses
- User requirements
- Service Plan status
- Microsoft subscriptions
- Business Central licensing needs
The licensing model should be considered alongside the technical migration plan rather than after the solution has been designed.
A practical 90-day migration checklist
Organisations considering a NAV-to-Business Central transition can start with these steps:
- Assess the current NAV environment
Document the NAV version, licences, customisations, integrations and third-party solutions. - Review business processes
Identify which processes should be retained, improved, or replaced. - Analyse data
Determine what historical and operational data need to be moved to Business Central. - Evaluate migration options
Compare migration and reimplementation based on cost, complexity, and business requirements. - Review licensing
Assess Business Central licensing and applicable Microsoft migration programs. - Define the target environment
Document reporting, integrations, security, compliance, and user requirements. - Build a migration roadmap
Plan data migration, testing, training, deployment, and post-go-live support.
Prepare for the next stage of your ERP Journey
The change from Dynamics NAV to Business Central is an ideal opportunity for businesses to revamp their ERP landscape without sacrificing the processes or information that are still relevant to their operations.
BEMEA assists businesses operating in the UAE region to conduct assessments of their NAV landscapes and plan for Business Central implementation to meet their requirements. With over 300 implementations successfully carried out by our teams, we are well-positioned to assist you in migrating to Business Central.
FAQs
Does Dynamics NAV stop working after April 30, 2031?
No, April 30, 2031, is the announced end-of-sale date. Existing NAV installations do not automatically stop working on that date. However, certain licensing and renewal options will no longer be available.
When does NAV 2018 support end?
Dynamics NAV 2018 extended support ends on January 11, 2028.
Is Business Central the replacement for Dynamics NAV?
Yes. Microsoft positions Dynamics 365 Business Central as the modern ERP platform and migration path for NAV customers.
Do all NAV customisations need to be rebuilt?
Not necessarily. Each customisation should be assessed. Some may be replaced with standard Business Central functionality, while others may need to be rebuilt using AL extensions.
When should businesses start planning?
Businesses should start assessing their NAV environment well before the support and end-of-sale milestones. Starting in 2026 provides sufficient time to evaluate options, prepare data, address customisations and plan the transition properly.
