News & Insights / Dynamics NAV 2016 migration options
Microsoft Dynamics NAV 2016 reached the end of extended support on 14 April 2026. Mainstream support had already ended on 13 April 2021. An existing NAV system may continue to run, but Microsoft no longer provides the normal security updates, non-security updates or assisted support that were available during the product lifecycle.
For an Australian organisation still using NAV 2016, the immediate task is not to rush into a technical conversion. It is to understand the current risk, stabilise critical operations and choose between an upgrade-led migration and a process-led reimplementation.
End of support does not mean NAV 2016 stops opening on the lifecycle date. It means the safety net around the product has changed.
After extended support ends, an organisation should expect:
This is a lifecycle risk, not proof that every NAV 2016 environment is already unsafe or unusable. The actual exposure depends on architecture, network access, custom code, authentication, integrations, infrastructure, backup quality and operational controls.
Before deciding on a future platform, document what must be protected today.
Record the NAV build, cumulative update, SQL Server version, Windows Server version, authentication method and important third-party components. One unsupported dependency can affect the plan even if another component remains supported.
Confirm that database and application backups complete successfully and can be restored.
Identify web services, remote access, ecommerce, banking, payroll, warehouse, EDI, reporting and customer or supplier portals connected to NAV. Include integrations that depend on exported files or scheduled jobs, not only APIs.
Avoid adding more legacy code unless it addresses an urgent operational or security need. Every new modification can increase discovery, conversion and testing effort later.
Treat the replacement decision as a business programme with an executive owner, not an open-ended IT maintenance issue.
A short stabilisation period can be appropriate when the organisation cannot move immediately. Work may include reducing exposure, confirming recovery, documenting integrations, resolving critical data issues and defining a funded roadmap.
This is a bridge, not a long-term product strategy. Its value is measured by how safely and quickly it enables the next step.
An upgrade-led route aims to retain more historical data, established processes and proven functionality. Microsoft's migration guidance explains that older Dynamics NAV environments first need to be upgraded to a supported Business Central on-premises path before data is moved to Business Central online. For NAV customisations written in C/AL, conversion to the Business Central extension model also needs to be assessed.
This route may suit an organisation when:
Continuity is not the same as simplicity. A technically complex legacy estate can make a full upgrade more expensive and harder to test than a selective reimplementation.
A reimplementation starts with present-day processes and moves selected master data, opening balances and required history rather than reproducing every legacy object. Historical NAV data can be retained in a read-only archive or reporting store where appropriate.
This route may suit an organisation when:
A reimplementation should not be confused with simply starting from an empty database. Data retention, audit access, reconciliation and cutover still require a governed plan.
The final choice can also be hybrid. For example, an organisation may preserve selected financial history while redesigning inventory, warehousing or approval workflows.
A useful assessment produces evidence for a decision rather than a generic recommendation. It should cover:
Confirm the current estate, business priorities and non-negotiable controls. Compare the upgrade, reimplementation and hybrid paths using the same criteria.
Define the target companies, dimensions, posting setup, permissions, extensions, integrations, reporting and data-retention approach. Decide what will be migrated, transformed, archived or retired.
Configure the target environment, develop only the required extensions and run a representative data migration. Reconcile balances and transaction counts before user acceptance testing begins.
Test complete business scenarios with migrated data, integrations, permissions and reports. Include month-end or year-end activities where they are in scope, plus failure and recovery scenarios.
Set a data freeze, migration runbook, reconciliation owners, go/no-go criteria and rollback or contingency plan. Make support contacts and escalation paths clear to every affected team.
Monitor errors, adoption, processing time and outstanding workarounds. Decommission the old environment only after data access, audit retention and recovery responsibilities are formally accepted.
A legacy modification should earn its place in the target system. Ask which regulatory, customer or operational requirement it satisfies and whether standard capability or a supported extension now covers the need.
Technical teams can extract records, but business owners need to decide which records are correct, active and legally required. Data cleansing cannot be delegated entirely to the migration script.
A posted sales invoice may work while the complete order, warehouse, shipment, invoice, payment and reporting process fails. Test end-to-end scenarios across teams and systems.
Define who can access historical NAV information, how it is protected, how long it is retained and how an audit request will be answered after go-live.
Role-based training should use realistic data and processes. Super users need time to practise exceptions and support colleagues before the cutover.
Microsoft lists the end of mainstream support as 13 April 2021 and the end of extended support as 14 April 2026.
Not automatically. An installed system may continue to operate, but Microsoft no longer provides the normal security and non-security updates or assisted support for that product version. Compatibility and operational risk can increase over time.
Microsoft's documented route requires older NAV data to be upgraded through a supported Business Central on-premises path before cloud migration. The exact route depends on the source version, customisations, extensions and the chosen data strategy.
No. Depending on legal, audit and operational needs, an organisation may migrate full history, selected history or essential master data and balances while retaining older information in a controlled archive.
No. The cost depends on custom code, data quality, integrations, process change, history requirements and testing. A discovery assessment is needed before either path can be compared fairly.
There is no universal safe period. Risk depends on the environment and controls. The organisation should document the exposure, apply compensating measures where possible and approve a time-bound transition plan.
Create an evidence-based inventory of the NAV environment before requesting a fixed migration proposal. Dynamic Aspect can help assess the current estate and map it to Dynamics 365 Business Central. Contact the team to discuss the next step.