As of today, companies can move from almost any version of Microsoft Dynamics NAV to the current release of Microsoft Dynamics 365 Business Central. However, the path varies greatly and is longer the further back your version sits. Microsoft's supported upgrade paths require older NAV environments to pass through one or more intermediate releases before they reach the cloud. One that is still running NAV 2009 will be looking at three or four, each with its own code conversion, data validation, and testing cycle.
This entirely transforms the shape of the project, and it is why two companies who think they're asking for the same migration can end up with timelines and budgets that look nothing alike. The gap is caused by what accumulates while you wait: customizations, workarounds that lack documentation, and significant functionality gaps that do not have a direct upgrade path.
Usually, no. Microsoft's documented upgrade paths treat this as a relay of multiple smaller migrations. NAV 2018 and Business Central On-premises from October 2018 can move directly to Business Central version 14, then on to current releases. NAV 2013 must upgrade to NAV 2018 then v14. NAV 2015 can go straight to NAV 2018.
NAV 2009 environments generally need to pass through a mid-2010s NAV release before they even reach version 14. Each hop is its own project: convert the code from C/AL to AL, rebuild customizations as extensions, migrate the data, and test the result before moving on. Skipping a stage isn't an option Microsoft supports.
Aside from Microsoft's upgrade path, technical debt and customizations are the usual reason. Every year a system runs past its intended lifespan, it picks up a few more workarounds built to cover a feature Microsoft has since released natively.
We consistently see the same pattern: customers who waited longest must assess their processes thoroughly and consider whether their upgrade path offers an opportunity to improve upon them. Customizations are another significant decision point as organizations may find Business Central extensions or built-in features that serve the same purpose and are readily available.
While there are no Microsoft-recommended pathways to skip any upgrade steps, having a clear idea of your plan and a knowledgeable partner can help you avoid making mistakes that others have learned from already. Western Computer offers a variety of options for companies looking to move on from Dynamics NAV and considering all of them helps you avoid overcomplicating your project.
In addition to this, Microsoft has also introduced the Bridge to Cloud program, which is designed to smooth out your migration and lower your overall cost. It isn't a shortcut around critical upgrade steps, but it changes the chances of error.
Find out exactly where you stand before picking a target date. An upgrade assessment maps your current version, your customizations, your ISV solutions, and the realistic path from where you are to where you want to be, hop by hop. That's a straightforward technical upgrade for some companies.
Others, especially those sitting on the oldest NAV releases with years of custom code, find a reimplementation makes more sense than chasing every intermediate hop. Either way, the assessment is what turns “we should probably move to the cloud eventually” into an actual number and an actual timeline. Western Computer treats that first conversation as exactly that, a conversation, not a sales pitch, because the honest answer to how complex a migration will be is different for every company still running NAV.
Knowing that your migration may take an indirect path is an important first step, but it doesn't cover all the concerns you may have as you make the jump. We put together a list of our clients' most frequently asked questions to help guide your decision process.
Ready to have a conversation about the next steps? Our team of experts will be more than happy to walk you through the different NAV to Business Central migration options we offer.