Microsoft Dynamics NAV has been a reliable ERP solution for businesses for many years. It helps organisations manage finance, supply chain, inventory, sales, purchasing and other day-to-day operations from one system.

But business requirements have changed considerably since many NAV environments were first implemented. Companies now expect easier access to data, cloud connectivity, automation, modern integrations and systems that can adapt without going through a major upgrade every few years.

This is one of the reasons businesses are considering a NAV to Business Central migration.

Moving from NAV to Dynamics 365 Business Central gives organisations an opportunity not only to move to a newer ERP platform, but also to review old data, integrations and customisations that may have been part of the NAV system for years.

Before looking at the migration process, let us first understand where Dynamics NAV stands today.


Microsoft Dynamics NAV – An Older but Powerful ERP Solution

Microsoft Dynamics NAV, formerly known as Navision, was developed to help small and medium-sized organisations manage different areas of their business from one ERP system.

Depending on the implementation, NAV can support finance, accounts, supply chain, inventory, purchasing, sales, manufacturing and other operational processes.

For many organisations, NAV still performs the job it was implemented to do. The challenge is that older NAV environments often rely on on-premises infrastructure, legacy customisations and integrations that become more difficult to maintain as technology changes.

Microsoft later introduced Dynamics 365 Business Central as the next generation of its ERP offering for small and medium-sized businesses.

Introducing Microsoft Dynamics 365 Business Central: An All-in-One ERP Solution for Smooth Business Management

Dynamics 365 Business Central is a powerful ERP solution available for users to manage entire business operations in real-time. It provides a centralised platform to operate all processes while supervising the task in real-time to make data-driven decisions whenever needed.

Business Central allows users to communicate, collaborate, and share the data using a single, unified platform to make the data accessible to all, whether an executive or a higher authority.

With a cloud-based deployment, Business Central is flexible in nature, enabling users to customise the system based on changing business needs.

The flexibility to change business requirements makes this solution ideal for all industries, including service, manufacturing, and distribution.

When it comes to scalability, no one is better than Business Central for SMBs. As it allows the organisation to expand or shorten processes whenever requirements change.

Here comes cloud computing, capable of simplifying existing processes while offering global connectivity for optimal performance.

The cloud deployment of Business Central allows businesses to access and operate the data 24X7 to keep you informed about your business in real-time.

However, if you still want to host the data in-house and want to access global connectivity, you can avail yourself of the hybrid deployment option. While categorising your requirements.

The cloud options cost way less when compared with the on-premises deployment because users can access the cloud on a subscription basis. However, if you are going for on-premises deployment, you may have to invest a lot of money and effort in setting up the servers.

Why Should you Migrate from NAV to Business Central?

There is no point migrating an ERP system simply because a newer product exists.

The decision should be based on whether the current NAV environment can continue supporting the way the business operates and where it plans to go next.

Some common reasons businesses consider moving include:

  • Older NAV versions approaching or reaching the end of Microsoft support

  • Dependence on ageing on-premises infrastructure

  • Difficulty maintaining old customisations

  • Growing integration requirements

  • Need for cloud access

  • Increasing upgrade and maintenance effort

  • Requirement for closer integration with Microsoft's current ecosystem

Support lifecycle is particularly important.

Dynamics NAV 2016 reached the end of extended support on 14 April 2026. NAV 2017 reaches the end of extended support on 11 January 2027, while NAV 2018 reaches it on 11 January 2028.

So, it would be incorrect to say that every NAV version is already completely unsupported. The situation depends on the version your business is currently running.

For companies still relying on NAV, this makes now a sensible time to review the long-term ERP strategy rather than waiting until the existing environment becomes harder or more expensive to maintain.

Another question businesses should consider is whether everything in NAV really needs to be carried forward.

A relatively clean NAV environment may be suitable for an upgrade and migration approach.

A system that has been heavily customised over many years may need a different approach.

For example, if the existing NAV system contains old reports, unused customisations, duplicate data and processes that the business no longer follows, rebuilding all of them in Business Central could simply move old problems into a new ERP.

In such cases, a Business Central reimplementation may be worth considering.

The right choice depends on your NAV version, data, customisations, integrations and how much of the existing system still reflects the way your business works today.

Journey from Navision to Business Central Migration: A Simple yet Effective Process

The process to migrate NAV to Business Central isn’t complex. However, you will need the right NAV migration partner, like Dynamics Square, to simplify the process. A step-by-step procedure will give you an overview of the process and the resources a partner would need to migrate successfully to Business Central.

1. Understand Your Business Requirements

The first step is understanding what the business currently uses NAV for.

Your migration partner should speak with the relevant teams and identify the important processes, reporting requirements, integrations and custom functionality.

This is also the right time to identify what users would like to improve when moving to Business Central.

Simply copying every NAV process into the new ERP may mean missing the opportunity to simplify the system.

2. Analyse the Current NAV Environment

Once the requirements are understood, the existing NAV system needs to be reviewed.

The assessment should normally include:

  • Current NAV version

  • Database and data volume

  • Existing integrations

  • Customisations

  • C/AL development

  • Third-party add-ons

  • Reports

  • Number of companies

  • Historical data requirements

This gives the migration team a clearer idea of the work involved.

3. Review Existing Customisations

Customisations can have a major impact on a NAV migration.

Older NAV environments may contain C/AL development that cannot simply be moved into modern Business Central in the same form.

The migration is therefore a good opportunity to review each customisation.

Some may already be covered by standard Business Central functionality. Others may need to be rebuilt as extensions, replaced with another application or removed completely if they are no longer required.

This avoids carrying unnecessary technical debt into Business Central.

4. Plan Data Migration from NAV to Business Central

Data migration from NAV to Business Central should start with deciding what information the organisation genuinely needs in the new system.

This may include:

  • Customers and vendors

  • Items

  • Chart of accounts

  • Opening balances

  • Financial information

  • Open sales and purchase transactions

  • Inventory

  • Fixed assets

  • Relevant historical records

Before moving the data, it is worth checking for duplicate customers, inactive suppliers, obsolete products and other records that no longer provide value.

Not every piece of historical information needs to be migrated simply because it exists in NAV.

Deciding what should move and what can remain archived can reduce migration complexity and give users a cleaner Business Central environment.

5. Configure and Migrate to Business Central

Once the existing NAV environment and data have been prepared, Business Central can be configured around the agreed requirements.

Depending on the business, this might include finance, purchasing, sales, inventory, warehousing, manufacturing, dimensions, permissions and reporting.

The required migration path will depend on the NAV version being used. Older NAV environments may require intermediate upgrade stages before the move to Business Central Online can be completed.

This is why the existing NAV version should be confirmed before agreeing on the final migration scope or timeline.

6. Test, Train and Go Live

Testing should be completed before switching users from NAV to Business Central.

This should include more than checking whether the data has appeared in the new system.

Finance teams should reconcile relevant balances, while business users should test their normal processes, such as creating sales orders, purchasing stock, processing invoices and running reports.

Integrations and custom extensions should also be tested.

Once these checks are complete, users can be trained on their relevant Business Central processes before the final migration and go-live.

How Much Does NAV to Business Central Migration Cost?

There is no fixed migration cost because NAV environments can be very different.

The cost generally depends on factors such as:

  • NAV version

  • Amount of data

  • Customisations

  • Integrations

  • Number of companies

  • Third-party applications

  • Historical data requirements

  • Testing

  • Training

  • Migration or reimplementation approach

A relatively standard NAV environment can require much less work than a system that has accumulated years of bespoke development.

This is why an assessment of the existing NAV environment is normally required before estimating the project properly.

How Can Dynamics Square Help with NAV to Business Central Migration?

Dynamics Square helps businesses assess, plan and manage their move from Microsoft Dynamics NAV to Dynamics 365 Business Central.

Rather than starting with the assumption that everything in NAV should be migrated, our team reviews the current environment to understand which data, processes, integrations and customisations need to move forward.

Our NAV to Business Central services can include:

  • NAV assessment

  • Migration planning

  • Business Central implementation

  • Data migration

  • Customisation assessment

  • Integration

  • Testing

  • User training

  • Go-live support

  • Ongoing Business Central support

If you are currently using Dynamics NAV and considering your next ERP step, contact Dynamics Square UK to discuss your NAV version, existing environment and Business Central migration requirements.

FAQs About NAV to Business Central Migration

1. Can I migrate from Dynamics NAV to Business Central?

Yes. Businesses using Dynamics NAV can move to Dynamics 365 Business Central. The migration route depends on the NAV version, customisations, data and target Business Central environment.

2. Can NAV 2018 migrate to Business Central?

Yes. NAV 2018 can be migrated to Business Central through the appropriate upgrade and migration path. Microsoft extended support for NAV 2018 ends on 11 January 2028.

3. Can NAV 2016 migrate to Business Central?

Yes. NAV 2016 can be migrated to Business Central through the required upgrade path. Microsoft extended support for NAV 2016 ended on 14 April 2026.

4. What data can be migrated from NAV to Business Central?

Depending on the project, businesses may migrate customers, vendors, items, financial information, balances, open transactions, inventory, fixed assets and relevant historical data.

5. What happens to NAV customisations during migration?

Existing NAV customisations should be reviewed individually. Some can be replaced with standard Business Central functionality, while others may need to be rebuilt as extensions, replaced with another application or removed.

6. Should we migrate NAV or reimplement Business Central?

It depends on the condition of the existing NAV environment. Migration may suit businesses that need to retain more of their existing processes and data, while reimplementation can be considered when the existing system contains significant legacy customisation or outdated processes.

See Also -

Kapil Jangid - Author
Kapil Jangid

Kapil Jangid is a Digital Marketing Expert with extensive experience in B2B technology marketing, ERP solutions, and Microsoft Dynamics 365. He specialises in SEO strategy, content marketing, lead generation, and organic growth, helping businesses improve online visibility, generate qualified leads, and drive digital transformation through data-driven marketing initiatives.

Does Microsoft Still Support Dynamics NAV?

Is Microsoft Dynamics NAV still supported? Check NAV 2016, 2017 and 2018 support end dates and learn when to consider moving to Business Central.

NAV to Business Central Data Migration – Your Major Concern Explained

Before your Microsoft Gold Partner starts the NAV to Business Central data migration process, you must know some part of it so that it can be carried out properly.

Let’s build the future of your business—together!

The right technology can change everything, and Dynamics Square ensures your business gets the tools it needs to succeed. Take the first step towards smarter solutions now!

Phone