How do you build a budget for a Dynamics NAV upgrade project?

How do you build a budget for a Dynamics NAV upgrade project?

A Dynamics NAV upgrade budget typically ranges from €50,000 for a straightforward on-premises update to well over €500,000 for a full migration to Microsoft Dynamics 365 Business Central at a larger organisation. The final number depends on the size of your organisation, the complexity of your current setup, and how much custom development work has accumulated over the years. The sections below break down the main cost drivers so you can build a realistic budget from the ground up.

What are the main cost drivers in a Dynamics NAV upgrade?

The main cost drivers in a Dynamics NAV upgrade are the scope of technical migration work, the volume of customisations and integrations, data migration complexity, licensing fees, and the time needed for testing and user adoption. Together, these factors determine whether your project lands at the lower or upper end of the budget range.

Most organisations underestimate how much of the budget gets consumed by work that happens before and after the actual system switch. A solid project management approach helps you map these costs early, so nothing comes as a surprise later.

Here is a breakdown of the typical cost categories to plan for:

  • Licensing and subscription fees — moving from NAV to Business Central usually means shifting from a perpetual licence to a monthly subscription model
  • Implementation and configuration — setting up the new environment, migrating settings, and configuring workflows
  • Customisation redevelopment — rebuilding or replacing custom code that does not carry over natively
  • Data migration — cleaning, mapping, and validating data before it moves to the new system
  • Testing — functional, integration, and user acceptance testing to confirm the system works as expected
  • Change management and training — preparing your teams to actually use the new system effectively
  • Cutover and go-live support — the final transition window and the hypercare period immediately after

How much does a Dynamics NAV to Business Central migration typically cost?

A Dynamics NAV to Business Central migration typically costs between €80,000 and €400,000 for a mid-sized organisation, though larger enterprises with complex landscapes regularly exceed this range. The wide spread reflects how differently each organisation has used and extended NAV over time.

For a smaller company running a relatively standard NAV setup with limited customisations, a migration project can be completed efficiently. For a multinational with years of custom development, third-party integrations, and large data volumes, the investment grows accordingly.

A few factors that push costs toward the higher end:

  • Multiple legal entities or company codes in a single NAV environment
  • Heavily modified standard processes (finance, warehousing, manufacturing)
  • Integrations with external systems such as CRM, EDI platforms, or production tools
  • Large historical datasets that require thorough cleansing before migration
  • Geographically distributed teams needing localised training and support

It is worth noting that licensing costs alone do not tell the full story. The implementation services around the migration often represent 60 to 70 percent of total project spend, which is why getting the scope right at the start matters so much.

What’s the difference between a greenfield and brownfield upgrade budget?

A greenfield upgrade means starting fresh with a new Business Central implementation, while a brownfield upgrade migrates your existing NAV data and configuration into the new environment. Greenfield projects often cost more upfront because everything is built from scratch, but brownfield projects carry hidden costs tied to legacy complexity that can be equally significant.

Greenfield budget considerations

In a greenfield approach, you redesign your business processes before implementing the system. This creates an opportunity to eliminate inefficiencies, but it also requires more time for workshops, process design, and stakeholder alignment. Budget for a longer design phase and more intensive change management, since users are adapting to both a new system and new ways of working simultaneously.

Brownfield budget considerations

A brownfield migration carries the existing setup into Business Central, which sounds faster but often surfaces technical debt. Custom objects, deprecated fields, and outdated integrations all need to be assessed and resolved. The upfront cost may appear lower, but remediation work during the migration can expand the budget quickly if the initial assessment was not thorough enough.

Whichever route you choose, a maturity assessment before committing to either path gives you a clear picture of where your organisation actually stands. This prevents budget surprises that only appear mid-project.

How do customisations and integrations affect the upgrade budget?

Customisations and integrations are consistently the largest variable in a Dynamics NAV upgrade budget. Every custom object, modified standard report, or bespoke workflow needs to be reviewed, redeveloped, or replaced, and that work is labour-intensive. Integrations with external systems add further complexity because Business Central connects differently than NAV did.

The first step is a full inventory of what you actually have. Many organisations discover during this process that a significant portion of their customisations are no longer used or have been superseded by standard Business Central functionality. Identifying and retiring unnecessary custom code before the migration reduces both cost and risk.

For integrations, the shift from NAV’s older web services to Business Central’s API-first architecture often requires rebuilding connections rather than simply migrating them. Budget for discovery, redevelopment, and thorough integration testing for each connected system. Skipping this step is one of the most common reasons go-live dates slip.

You can explore our full range of services to understand how data migration management and test management work together to handle exactly this kind of complexity.

What budget should you set aside for change management and training?

Change management and training typically represent 15 to 25 percent of the total Dynamics NAV upgrade budget, though this figure is frequently underestimated or cut when budgets come under pressure. That is a mistake. A system that works technically but is poorly adopted by the people using it fails to deliver its business case.

Training costs cover the obvious elements: workshops, documentation, e-learning content, and hands-on practice sessions. But effective change management goes further than training. It includes communicating the reasons for the change, addressing resistance at team and individual levels, and providing ongoing support after go-live so that adoption actually sticks.

Budget items to include in this category:

  • Role-based training for all user groups, not just power users
  • Communication planning and stakeholder engagement activities
  • Super-user or champion programmes to embed knowledge in the business
  • Post-go-live support and hypercare to catch adoption gaps early
  • Process documentation and quick-reference guides

Organisations that invest properly in this area see faster time-to-productivity after go-live and fewer costly support calls in the months that follow.

How we help you build and manage your Dynamics NAV upgrade budget

We work with organisations across the full lifecycle of a Dynamics NAV upgrade, from the initial scoping and budget-building phase through to post-go-live hypercare. Here is what that looks like in practice:

  • Maturity assessment — before any budget is committed, we assess your current ERP landscape, customisations, data quality, and organisational readiness to give you a realistic baseline
  • Scope definition and cost modelling — we map your greenfield or brownfield route, identify the real cost drivers, and help you build a budget that holds up under scrutiny
  • Data migration management — we use rigorous As-Is/To-Be analysis and testing procedures to prevent data loss and errors during the migration itself
  • Cutover management — we plan and monitor the go-live transition end-to-end, including hypercare and aftercare, so operational continuity is never at risk
  • Change management — we address both the technical and human side of the upgrade, driving genuine adoption rather than just delivering training sessions
  • We are active across Microsoft Dynamics 365 and other ERP platforms, available on-site and remotely, in the Netherlands, Belgium, and internationally

If you are preparing for a Dynamics NAV upgrade and want a clear picture of what it will actually cost, get in touch with our team or learn more about what we do.

Gerelateerde artikelen

our other
blogs