Moving from Microsoft Dynamics NAV to Dynamics 365 Business Central is more than a software upgrade. The right approach depends on your current NAV version, customizations, data, integrations, and whether you plan to use Business Central online or on-premises.
This guide explains the upgrade paths, key migration steps, cost considerations, risks, and how to choose the right implementation partner.
Table of Contents
- NAV to Business Central Upgrade: At a Glance
- Why Upgrade Dynamics NAV to Business Central?
- What Does a NAV to Business Central Upgrade Involve?
- Upgrade or Reimplementation: Which Approach Is Right?
- 8 Steps to Migrate from NAV to Business Central
- How Much Does a Dynamics NAV Upgrade to Business Central Cost?
- How to Make a NAV Upgrade Less Risky
- NAV to Business Central Upgrade: A Real Client Example
- Why Choose Dynamics Square USA for Your NAV Upgrade?
- Frequently Asked Questions
NAV to Business Central Upgrade: At a Glance
Upgrade path: Older NAV versions may require intermediate upgrade steps before moving to a current Business Central release.
Customizations: Existing C/AL customizations may need to be converted to AL extensions, replaced with standard functionality, or redesigned.
Cost: There is no fixed upgrade cost. Pricing depends on users, data, customizations, integrations, third-party solutions, and implementation scope.
Potential savings: Eligible customers may qualify for a 30% discount on qualifying three-year Dynamics 365 subscriptions through Microsoft's Bridge to Cloud 3 program.
Upgrade or reimplementation: Businesses with significant legacy customizations should evaluate both options.
Planning: Data assessment, testing, integration validation, and user preparation are essential for a smooth transition.
Partner expertise: An experienced Business Central partner can assess your NAV environment and recommend a suitable migration strategy.
Why Upgrade Dynamics NAV to Business Central?
For many US businesses, Microsoft Dynamics NAV has been a dependable ERP system for years. But as technology, customer expectations, and business operations evolve, legacy ERP systems can become harder to maintain and adapt.
A NAV to Business Central upgrade offers a path to modernize the ERP environment while preserving the data and processes the business still needs. Business Central provides capabilities for financial management, supply chain, sales, inventory, projects, reporting, and business process automation.
For US companies, the move can also create a stronger foundation for Microsoft 365, Power Platform, analytics, and other connected business applications.
Modernization does not mean transferring every old customization into the new system. A good upgrade assesses what the business needs today and whether each customization should be retained, replaced by standard Business Central functionality, or redesigned. This can reduce technical debt and make the new ERP easier to maintain.
Microsoft supports migration from Dynamics NAV to Business Central online, but NAV customers must first upgrade to a supported Business Central on-premises version before moving to the cloud.
What Does a NAV to Business Central Upgrade Involve?
The first step is to assess the existing NAV environment. The project team should examine the NAV version, database, customizations, extensions, third-party applications, integrations, reports, historical data, user requirements, and current business processes.
The upgrade route depends on the starting version. Microsoft's documented upgrade paths for NAV 2015, NAV 2016, NAV 2017, and NAV 2018 include an intermediate move to Business Central 14 before progressing to a later supported Business Central version and, where applicable, Business Central online. Older NAV versions can require additional intermediate steps. Review Microsoft's upgrade paths and NAV migration guidance for the route that applies to your environment.
For example, a business planning to upgrade Dynamics NAV 2017 to Business Central should not assume it can move directly from NAV 2017 to the latest cloud release.
What Happens to NAV Customizations and Data?
Business Central online uses an extension-based architecture. Microsoft explains that C/AL code customizations need to be converted to AL extensions for a full NAV-to-cloud migration. Data in tables affected by code customizations cannot simply be carried forward unless those customizations are handled appropriately through extensions.
That does not mean every historical customization must be recreated. A practical Dynamics NAV to Business Central assessment should classify existing functionality into three groups:
Retain: Functionality the business still needs.
Replace: Custom functionality now available as standard Business Central capability.
Redesign: Processes that would benefit from a better or more modern approach.
Data also needs careful planning. Customer, vendor, item, financial, inventory, and transactional information should be validated before migration, with test migrations performed before production cutover.
Upgrade or Reimplementation: Which Approach Is Right?
A full upgrade from NAV to Business Central is not the only option.
Microsoft documents a Business Central 14 reimplementation option for organizations that want a cleaner start rather than carrying forward all legacy customizations and historical data. The tool focuses on essential business information such as master data, opening balances, setup, and selected transactional data. Microsoft currently documents this as a preview feature, so its suitability should be assessed carefully with an experienced partner. See Microsoft's Business Central 14 reimplementation guidance.
Reimplementation may be attractive when years of accumulated customizations have created unnecessary complexity. For organizations that need to preserve their full data set and functionality, the standard full migration route may be more appropriate.
The choice should be based on the NAV environment, business continuity needs, data-retention requirements, customizations, integrations, and future operating model.
8 Steps to Migrate from NAV to Business Central
Once you understand your NAV version, deployment options, customizations, and data requirements, the next question is practical: how do you migrate from NAV to Business Central?
While every implementation is different, most successful NAV to Business Central migrations follow eight core steps.
1. Assess Your Existing NAV Environment
Document your NAV version, database, customizations, extensions, third-party applications, integrations, reports, users, companies, and business-critical processes.
This assessment determines whether intermediate upgrade steps are required and helps establish whether a full upgrade or reimplementation is the better approach.
2. Define Your Business Central Migration Strategy
Decide where you are going and how you will get there. Depending on your NAV version and requirements, the destination may be Business Central online or on-premises. Older NAV versions may require intermediate upgrade stages before reaching a supported Business Central version and migrating to the cloud.
At this stage, define the project scope, timeline, responsibilities, licensing requirements, and go-live strategy.
3. Review and Rationalize Customizations
Do not automatically carry every NAV customization into Business Central.
Classify existing customizations as functionality to retain, replace, or redesign. Functionality already available in standard Business Central may eliminate the need for custom development, while genuinely necessary customizations may need to be rebuilt as AL extensions.
4. Prepare and Clean Your Data
Identify the data that needs to move and remove unnecessary or obsolete information.
Review customers, vendors, items, financial data, inventory, open transactions, master records, historical data, and other critical information. Data cleansing can prevent problems later in testing and production.
5. Migrate and Validate the Data
Perform a test migration before the final cutover.
After migrating the data, validate financial balances, inventory, customer and vendor records, open transactions, dimensions, and other business-critical information. Multiple test runs can help identify and resolve migration issues before go-live.
6. Rebuild and Test Integrations
Your NAV environment may connect with banking systems, CRM platforms, payroll, EDI, e-commerce, warehouse management, payment services, or other applications.
Assess each integration for Business Central compatibility and test it in the new environment. An ERP migration can affect processes beyond the ERP itself, so integration testing should be part of the overall plan.
7. Conduct User Acceptance Testing and Training
Technical validation is only part of the process. Finance, sales, purchasing, warehouse, operations, and management teams should test the workflows they use every day.
Use this stage to identify process gaps, train users, document new procedures, and make sure employees are comfortable with Business Central before the final transition.
8. Go Live and Monitor the New Environment
Once data, customizations, integrations, and users have been validated, execute the agreed cutover plan.
After go-live, monitor transactions, integrations, reports, user issues, and system performance closely. A structured post-go-live support period can help resolve issues quickly while users adjust to the new Business Central environment.
From Eight Steps to a Successful Migration
From our experience with NAV to Business Central implementations, we know that no two migrations are the same. Older NAV versions, complex C/AL customizations, third-party solutions, and integrations can significantly change the upgrade journey.
Early assessment is key. Identifying what to retain, replace, or redesign helps reduce migration risks, control costs, and create a smoother transition to Business Central.
How Much Does a Dynamics NAV Upgrade to Business Central Cost?
The cost of a Dynamics NAV upgrade to Business Central depends on several factors, including the NAV version, number of users and companies, customizations, data volume, integrations, third-party applications, and deployment model. Microsoft does not publish a single fixed price for a NAV-to-Business-Central upgrade because implementation requirements vary significantly between businesses.
For US businesses, the total cost typically consists of two main components: Business Central licensing and implementation services. Licensing depends on the users and licenses required, while implementation costs depend on the complexity of the existing NAV environment and the scope of the migration.
Factors That Affect NAV to Business Central Upgrade Cost
NAV version: Older NAV versions may require additional upgrade steps before reaching a current Business Central release.
Customizations: Existing C/AL customizations may need to be converted to AL extensions, replaced with standard Business Central functionality, or redesigned.
Data volume and quality: Large databases and extensive data cleansing or transformation can increase migration effort.
Integrations: Connections with CRM, payroll, EDI, banking, e-commerce, warehouse, or other systems may require redevelopment and testing.
Number of users and companies: Larger deployments generally require more configuration, testing, training, and licensing.
Third-party solutions: Existing NAV add-ons must be assessed for Business Central compatibility or replacement.
Deployment model: Business Central online and on-premises have different licensing, infrastructure, and support considerations.
Can You Reduce the Cost of Moving from NAV to Business Central?
Eligible NAV and Business Central on-premises customers may qualify for a 30% discount on qualifying three-year Dynamics 365 subscriptions through Microsoft's Bridge to Cloud 3 (BTC3) promotion. The promotion is available for eligible customers enrolling between January 1, 2026, and December 31, 2027, subject to Microsoft's licensing and eligibility requirements.
Importantly, the 30% discount does not mean the entire NAV-to-Business-Central project will cost 30% less. BTC3 applies to qualifying Dynamics 365 subscriptions under specific conditions. Businesses should confirm their eligibility with Microsoft or an authorized licensing partner before including the discount in their budget.
For an accurate estimate, first assess your NAV version, customizations, integrations, data, users, third-party applications, and preferred deployment model. This provides a clearer picture of the implementation scope, licensing requirements, migration effort, and potential Bridge to Cloud savings.
How to Make a NAV Upgrade Less Risky
A successful NAV to Business Central upgrade should begin with preparation rather than technology alone.
The project team should document the current environment, identify obsolete customizations, clean unnecessary data, assess integrations, and establish a realistic migration and testing plan.
Microsoft's cloud migration preparation guidance recommends preparing the environment, validating prerequisites, performing migration tests, and running a dry run before production cutover. The cloud migration process also involves replication, data upgrade, validation, and post-migration activities.
For US businesses, review localization, tax, reporting, banking, payroll, payment, EDI, e-commerce, and other integrations before selecting the final migration approach. These dependencies can significantly affect project scope.
The objective is simple: the new Business Central environment should support the business on day one, not merely prove that the data was technically transferred.
NAV to Business Central Upgrade: A Real Client Example
The best way to understand the realities of a NAV upgrade is to look at what happens when a business actually goes through one. At Dynamics Square, we have seen that every NAV environment comes with its own combination of legacy processes, customizations, integrations, and operational challenges.
One example is our work with Adams Recycling, a recycling and materials recovery organization in South Carolina. The company was running mission-critical finance, purchasing, inventory, warehouse, and sales operations on NAV 2018. Its environment had become difficult to support after its consultant became unavailable, leaving the business with an ERP system that was increasingly difficult to maintain.
We approached the project as more than a technical migration. First, we assessed the existing NAV environment and its business-critical processes. Then, we upgraded the organization to Business Central SaaS, helping move its core operations to a cloud-based platform.
The change had a practical impact. The company moved away from server-dependent operations, gained access to Microsoft 365 integration, reduced repetitive manual data entry, and established a foundation for future Power BI reporting and a customer portal.
The project reinforced an important point: a successful NAV to Business Central upgrade is not about moving everything exactly as it exists. It is about understanding what the business needs to preserve, what can be improved, and what Business Central can do differently.
That is why the assessment, customization review, data migration, testing, and go-live planning discussed in this guide matter so much. The technology provides the destination, but the quality of the upgrade depends on how carefully the journey is planned.
Why Choose Dynamics Square USA for Your NAV Upgrade?
Moving from NAV to Business Central is not simply a matter of transferring data from one system to another. The upgrade path, customizations, integrations, data requirements, licensing considerations, and testing strategy all need to work together. Choosing the right implementation partner is especially important for businesses with a heavily customized or long-running NAV environment.
A successful Dynamics NAV to Business Central project requires more than migration tools. It requires expertise across legacy NAV environments, Business Central architecture, data migration, AL extensions, integrations, testing, licensing, and the operational needs of the business.
Dynamics Square is a Microsoft Solutions Partner, founded in 2011, with 14+ years of experience, 500+ clients and implementations, and 150+ Microsoft Certified Consultants. With a presence in the USA, UK, and Canada, Dynamics Square supports businesses with Business Central implementation, migration, customization, and ongoing support.
For a US organization planning an upgrade from NAV to Business Central, this experience can help turn a complex migration into a structured, manageable project. Dynamics Square USA can assess your existing NAV environment, identify the appropriate upgrade or migration route, review customizations and data requirements, and develop a practical roadmap for Business Central.
Ready to evaluate your NAV environment? Book a demo with Dynamics Square USA to discuss your upgrade requirements and Business Central roadmap.
