Plain answers to the questions NAV customers are actually asking — before scope is set and timelines are locked.
Most NAV migration conversations start in the wrong place. Someone in IT pulls together a project scope, finance wants assurance the numbers will carry over cleanly, and leadership asks whether this counts as a full reimplementation. By the time the real questions surface, months have passed and the team is already negotiating timelines without a clear picture of what the project actually involves.
The questions that matter most are not about features. They are about risk, timing, data, and the gap between what people assume a migration involves and what it actually requires. Below are the questions Western Computer hears most often from NAV customers thinking through this decision, answered plainly.
Do I have to migrate from Dynamics NAV to Business Central right now?
NAV customizations written in C/AL code do not transfer directly to Business Central. Each customization is assessed during discovery and classified as: rebuild as a Business Central extension, replace with standard Business Central functionality, find an equivalent app on Microsoft AppSource, or retire it. Not every customization survives in its original form, and that is often the right outcome.
It is worth being direct about this: discovering customizations late, without documentation, is the most common source of go-live disruption. During a migration assessment, Western Computer reviews every custom object and produces a clear recommendation before the project scope is set. A plant manager who relies on a heavily modified costing report should not be surprised by that conversation at cutover. Surfacing those dependencies during discovery, not during go-live week, is what separates a clean migration from a chaotic one.
How much historical data needs to move from NAV to Business Central?
Most organizations migrate open balances, open transactions, and a defined window of recent historical data, then archive older records in a read-accessible format. You do not need to bring over every transaction from the past decade. The right window depends on your reporting requirements, audit obligations, and how often staff actually retrieve historical records for live work.
The risk is not bringing too little data. The risk is bringing data that has not been cleaned. Duplicate vendor records, inconsistent customer naming, and unreconciled balances create exactly the same problems in Business Central that they were creating quietly in NAV. Migration is the right moment to address that, and teams that invest in data cleanup before the project starts consistently have smoother go-lives than those that defer it to the migration phase.
How long does a NAV to Business Central migration take?
The realistic range is four to twelve months. A NAV 2018 environment with limited customization and clean data can complete assessment, preparation, testing, and go-live in four to six months. An older NAV version with hundreds of custom objects, deep integrations, and years of accumulated workarounds will take six to twelve months, with extension development as the longest single workstream.
There is no shortcut through the extension development phase; it either gets done properly before go-live or it surfaces as production issues afterward. Western Computer's five-step migration approach walks through exactly how that sequencing plays out in practice, including what weekend cutovers actually look like for teams that cannot afford extended downtime.
The preparation required to compress cutover to a tight window is substantial, which is another reason the assessment phase matters so much. You cannot plan a two-day cutover if you have not validated what needs to happen during those two days.
How does Business Central licensing differ from Dynamics NAV licensing?
Dynamics NAV used perpetual licenses purchased upfront. Business Central uses a subscription model billed per user per month. Licensing breaks into two tiers: Essentials handles finance, supply chain, and project management, which covers the core of what most NAV customers are running today. Premium adds manufacturing and service management on top of that. What both tiers share is that updates come automatically with no need for complex upgrade projects or unnecessary downtime to install a new version.
Organizations that compare list price per user without accounting for what they were spending to maintain NAV tend to underestimate the value of the switch. Server infrastructure, SQL Server licensing, BREP maintenance, and the cost of internal or external resources to keep the environment stable add up. Research from Forrester has found that organizations migrating off legacy ERP systems can recover significant costs through reduced infrastructure and maintenance overhead. The advisory conversation worth having is about total cost of ownership across three years, not monthly license fee per user.
Will employees be able to use Business Central after migrating from NAV?
Yes. Business Central shares NAV's underlying data model and core logic, so the concepts are familiar to anyone with NAV experience. The interface is different, but the learning curve is far shorter than switching to a different ERP vendor. Role-specific training, delivered close to go-live rather than months before it, is the most effective approach.
That said, change management is not something to underfund. Users who learned NAV through years of daily use have built habits around specific screens, menus, and workflows. Those workflows exist in Business Central, sometimes in a cleaner form, but finding them requires hands-on training that goes beyond a one-day overview session. The organizations that see the smoothest adoption build internal champions who can answer day-to-day questions once the partner's active engagement winds down, typically three to six months post-go-live.
What can Business Central do that Dynamics NAV cannot?
Business Central SaaS includes native integration with Microsoft 365, Power BI, Power Automate, Teams, and Copilot. It receives two major update waves per year, automatically, with no separate upgrade project required. AI-assisted features including reconciliation support and document intelligence are built in and updated continuously. None of these capabilities are available in Dynamics NAV.
According to Microsoft's Business Central migration documentation, the platform is designed so every update builds directly on the previous one, compounding over time. Power BI reporting that would have required separate investment and custom development in a NAV environment is available out of the box. The platform you are running six months after go-live is more capable than the one you went live on, and that improvement continues without action on your part.
What is the first step to migrate from Dynamics NAV to Business Central?
The right first step is a structured assessment of your current NAV environment before committing to a project scope. That assessment should cover your NAV version, your customization inventory, your data quality, your third-party integrations, and where your team's actual operational dependencies live. The output is a migration blueprint with realistic timelines and costs, not a rough estimate.
The hidden costs of staying on NAV on-premises are easy to underestimate until you map them against a three-year horizon. Going into a NAV to Business Central migration without a completed assessment is where cost overruns and difficult go-lives tend to originate. The assessment is not overhead; it is the foundation everything else depends on.
Western Computer has guided hundreds of NAV customers through this process across manufacturing, distribution, and professional services. If your team is beginning to evaluate the move, a migration readiness conversation is the right first step before any scope decisions are
