Dynamics NAV has served a large number of UK logistics and distribution businesses well. It is a capable system for businesses of a certain size and complexity, and for many it remained adequate for years. The difficulty now is timing rather than capability: Microsoft's support clock on Dynamics NAV has run out, and the remaining versions are following it on a fixed schedule that does not move.
Every version of Dynamics NAV is already out of mainstream support. Extended support, which covers security updates only, is ending version by version, and two of the four most recent releases have now passed that point: NAV 2015 ended 14 January 2025 and NAV 2016 ended 14 April 2026. NAV 2017 follows on 11 January 2027, and NAV 2018, the final release, ends on 11 January 2028. Once a version passes its end of support date, Microsoft issues no further patches, including security patches, for that version. Any logistics business still running NAV 2016 or earlier is operating ERP software with no further security updates coming, which is not a distant planning issue. It is a deadline that has already arrived.
Migration to Dynamics 365 Business Central is the path Microsoft has built for NAV customers, and it is the most common route for logistics businesses in the UK moving off the platform. This guide covers what that migration involves, the timescales to plan around, and how to manage the transition without disrupting day-to-day operations.
The Dynamics NAV Support Timeline
Dynamics NAV follows Microsoft's Fixed Lifecycle Policy: five years of mainstream support followed by five years of extended support, with a hard end date for each version. The table below sets out where each version currently stands.
Versions older than NAV 2015 are already unsupported. Dates based on Microsoft's published lifecycle policy as of June 2026.
Versions older than NAV 2015 are already unsupported in any form. Once extended support ends for a given version, the business is running ERP software that will receive no further security updates, no bug fixes, and no technical support from Microsoft, while still holding financial, stock, and customer data that the business depends on daily. For logistics operators specifically, that risk is compounded by the carrier integrations, EDI connections, and warehouse systems that typically sit around NAV, all of which depend on a stable, supported core.
The practical implication is straightforward. Businesses still running NAV 2016 or earlier are already past the support deadline and should treat migration as immediate, not a project to be scoped at leisure. NAV 2017 customers have until January 2027, which sounds like time but is not, once a typical three to eight month project timeline and a realistic planning and procurement period are factored in. NAV 2018 customers have the longest runway, to January 2028, but the same logic applies: that date is the latest point to be live on Business Central, not the point to start planning.
Why Logistics Businesses Move from Dynamics NAV to Business Central
Beyond the support deadline, the operational limitations of Dynamics NAV that most commonly drive migration decisions in logistics fall into four categories.
Real-time reporting
Dynamics NAV is an on-premise system, and most installations in logistics businesses are running on infrastructure and reporting tools that predate the real-time reporting expectations of a modern operation. For a logistics business that needs live stock positions, live order status, and live financial data to manage operations hour by hour, end-of-day or manually refreshed reports are a fundamental constraint. Business Central provides live data natively, accessible directly in the system and through Power BI dashboards that update continuously.
Integration capability
Connecting Dynamics NAV to modern e-commerce platforms, carrier management systems, or third-party logistics portals typically requires bespoke middleware that is expensive to build and increasingly difficult to maintain as NAV itself ages out of support. Business Central is built with an open API as a core architectural feature, which means integrations are faster, cheaper, and more reliable to implement and maintain.
Cloud infrastructure and scalability
Dynamics NAV runs on-premise or in a hosted environment, with the associated infrastructure management overhead, and that overhead only grows as the underlying version ages. Adding a new warehouse location, a new user base, or a remote working requirement involves IT infrastructure work, often on hardware and software that Microsoft no longer supports. Business Central is cloud-native, scaling without infrastructure changes and accessible from any device anywhere.
Microsoft ecosystem and AI capability
Business Central is part of the Microsoft 365 ecosystem, which means native integration with Teams, Outlook, SharePoint and, increasingly, Microsoft Copilot. The AI-assisted features in Business Central, including demand forecasting, payment prediction, and Copilot-assisted data entry, are not available in Dynamics NAV and represent a meaningful capability differential as they mature.
What the Migration Involves
Discovery and scoping
A properly structured migration begins with Discovery: a thorough assessment of the current Dynamics NAV configuration, the customisations and modifications built up over the system's lifetime, the integrations it connects to, and the data it holds. NAV implementations in logistics businesses are frequently customised more heavily than equivalent Sage or other mid-market systems, so this phase carries particular weight: it identifies the migration scope, surfaces data quality issues and customisations that need to be addressed before migration, and produces the go-live plan and project timeline.
Compressing or skipping Discovery to reduce upfront cost is the most common cause of migration projects that exceed budget and timeline. The issues that Discovery surfaces do not disappear if Discovery is skipped; they surface later in the project when they are more expensive to address, and with a fixed support end date already on the calendar, that delay carries more risk than it would for a like-for-like system swap.
Data cleansing and preparation
Most Dynamics NAV databases in logistics businesses contain data that has accumulated over many years, often a decade or more, and includes inactive records, duplicate customers or suppliers, inconsistent item categorisation, and historical transactions that are no longer relevant to the operation. Migrating that data as-is transfers the problem to Business Central. Cleansing before migration produces a clean starting point in the new system.
The data sets that require the most careful attention in a logistics migration are typically the stock master, customer and supplier records, and the chart of accounts. Stock data in particular often contains significant historical residue that creates noise in Business Central's planning and reporting if it is migrated uncleaned.
Business Central configuration
Business Central needs to be configured to match the operational structure of the business: warehouse locations, stock categories, carrier relationships, pricing structures, approval workflows, and reporting dimensions. For a logistics business, this configuration work draws on the process redesign decisions made during Discovery, and it is the phase where the business takes the opportunity to improve processes rather than simply replicating Dynamics NAV's approach, including any legacy customisations, in a new system.
Data migration and testing
Data is extracted from Dynamics NAV, mapped to the Business Central data model, and migrated in test runs before the final go-live migration. Testing validates that the migrated data is accurate, that processes work as designed, and that integrations with carrier and e-commerce systems function correctly before the business is live on Business Central.
Go-live and stabilisation
Go-live is the point at which the business begins operating from Business Central. For most logistics operations, a weekend cutover, where the final data migration runs on the Friday and Business Central is live for Monday morning orders, is the most practical approach. A period of hypercare support immediately after go-live ensures that issues arising from live operational use are addressed quickly.
The Role of QuickStart Solutions
For logistics businesses working against a Dynamics NAV support deadline who want a defined scope, fixed cost, and accelerated timeline for their Business Central migration, Advantage's QuickStart Solutions provide a structured path to go-live. QuickStart is designed for businesses where the scope is well-defined and the requirement is for a fast, low-risk migration rather than an open-ended project, which makes it particularly well suited to NAV customers migrating against a fixed end of support date.
Talk to Our Migration Team
Advantage has supported logistics and distribution businesses through migrations from Dynamics NAV, Sage 200, Sage 50, Dynamics GP, and bespoke systems to Business Central. If your business is running Dynamics NAV 2016 or earlier, support has already ended and migration should be an immediate priority. If you are on NAV 2017 or 2018, the right starting point now is a structured conversation about where your version sits on the support timeline and what migration would involve for your specific operation.
Contact Advantage today or call 020 3004 4600.
Related Resources
- Modernising Your Logistics ERP: The Complete Guide 2026
- Data Migration and Legacy Modernisation
- QuickStart Solutions
- Dynamics 365 Business Central
- Advantage Transformation Sprint
Frequently Asked Questions
When does support for Dynamics NAV end?
It depends on the version. NAV 2015 lost extended support in January 2025, and NAV 2016 lost extended support on 14 April 2026, so both are now unsupported. NAV 2017 follows on 11 January 2027, and NAV 2018, the final release, ends on 11 January 2028. All versions of Dynamics NAV are already out of mainstream support, meaning none receive new features; the dates above mark the end of security updates as well. Businesses still on NAV 2016 or earlier are running unpatched ERP software today.
Why do logistics businesses migrate from Dynamics NAV to Business Central?
The most immediate driver is the fixed end of support date attached to every NAV version. Beyond that, the common operational drivers are the need for real-time reporting that NAV's on-premise architecture cannot provide, the requirement to connect to e-commerce or carrier platforms cost-effectively, the limitation of on-premise infrastructure as businesses add locations or remote users, and the desire to access Microsoft Copilot and AI capability that is built into Business Central but not available in Dynamics NAV.
What data can be migrated from Dynamics NAV to Business Central?
The core data migrated from Dynamics NAV to Business Central typically includes the chart of accounts, customer and supplier master records, stock items and categories, open transactions including outstanding orders and invoices, and a defined period of historical transaction data. NAV implementations often carry custom fields, tables, or modifications built up over the system's lifetime, and these are assessed during Discovery to determine what should be replicated, replaced with standard Business Central functionality, or retired. The migration scope is agreed during Discovery based on what the business needs to operate from day one in Business Central.
How long does a Dynamics NAV to Business Central migration take?
The timeline depends on the complexity of the Dynamics NAV configuration, the extent of any custom development built up over the years, the number of integrations to be reproduced or replaced, and the extent of process redesign required. A straightforward migration for a distribution business with clean data, limited customisation, and limited integrations can be completed in three to four months. More complex migrations with significant data cleansing, heavy customisation, multi-site setup or extensive integration work typically take five to eight months. Given the fixed support deadlines on each NAV version, businesses are advised to start planning well ahead of their version's end of support date rather than treating it as the start date for the project.
Will we lose our Dynamics NAV historical data after migrating?
A defined period of historical transaction data is migrated to Business Central as part of the project. For data that pre-dates the migration window, Dynamics NAV can typically be retained in a read-only archive mode for a period after go-live, allowing users to reference historical records while the operation runs on Business Central. Once a NAV version passes its end of support date, however, retaining it even in read-only mode carries security risk, since it will no longer receive patches, so the practical archive window narrows as the deadline approaches. The specific arrangement depends on the Dynamics NAV licensing terms in place at the time of migration.
