Upgrade from Navision to Business Central: A Step-by-Step Guide

If your business is still running Microsoft Dynamics NAV (formerly Navision), you are operating on a platform that Microsoft has officially retired from mainstream support. The upgrade from Navision to Business Central is no longer optional for companies that care about security, scalability, and access to modern ERP capabilities. This guide walks you through what the migration involves, what it delivers, and how to approach it without disruption.

What Are Navision and Business Central?

Navision, originally developed by a Danish software firm and acquired by Microsoft in 2002, became one of the most widely adopted ERP systems for small and mid-sized enterprises. Over two decades, it helped businesses manage finances, supply chains, and core operations. Over time, Microsoft rebranded it as Dynamics NAV and continued building on it, but its on-premises architecture eventually reached its ceiling.

Microsoft Dynamics 365 Business Central is its cloud-native successor. Built on the same core foundation, Business Central extends NAV with modern cloud infrastructure, native Microsoft 365 and Power Platform integration, AI-driven insights, and a continuous update model. For organisations still on NAV, it represents a logical and well-supported migration path, not a complete platform change.

Why Upgrade from Navision to Business Central?

The case for making the move from Navision to Business Central is practical, not aspirational. Here is what organisations consistently gain:

• Continuous updates: Business Central receives two major release waves per year from Microsoft, ensuring your ERP stays current without costly upgrade projects.
• Cloud flexibility: Access the system from any device, anywhere. For businesses with remote teams, multiple sites, or hybrid working models, this is a significant operational improvement over on-premises NAV.
• Microsoft 365 integration: Work directly with Business Central data inside Outlook, Excel, and Teams, reducing the need to switch between applications and manual re-entry of data.
• Power BI and Copilot: Built-in analytics dashboards and AI-assisted workflows replace the custom reporting workarounds many NAV users have relied on for years.
• Lower total cost of ownership: Cloud hosting eliminates on-premises server infrastructure, reduces IT maintenance overhead, and shifts costs to a predictable SaaS subscription model.

Key Capabilities You Gain in Business Central

Business Central is a full-featured ERP platform designed for businesses from 10 to several hundred users. Compared to Navision, it delivers:

• Financial management: Advanced general ledger, multi-currency, multi-entity consolidation, accounts payable and receivable, bank reconciliation, and built-in audit trails.
• Supply chain and inventory: Real-time inventory tracking, automated purchase orders, vendor management, and warehouse management tools that were largely absent or limited in older NAV versions.
• Project and service management: Time tracking, resource planning, job costing, and service contract management built into the same platform.
• Power BI dashboards: Native integration gives finance and operations teams real-time visibility into KPIs without needing separate BI infrastructure.
• Microsoft Copilot: AI features embedded in Business Central help with cash flow forecasting, late payment prediction, product descriptions, and bank reconciliation suggestions.

Preparing for the NAV to Business Central Migration

Most Dynamics NAV upgrade projects that run into problems do so not during the technical migration, but in the planning phase. Thorough preparation reduces risk significantly.

1. Assess Your Current NAV Environment

Start by cataloguing every customisation, third-party add-on, integration, and report that your business currently relies on in Navision. Older NAV implementations often contain years of layered customisations, some of which may not be in active use. Identifying what is genuinely needed versus what can be retired is a critical first step.

2. Build a Cross-Functional Project Team

A successful Business Central migration requires input from IT, finance, operations, and any department with specialised processes in NAV. Do not treat this as an IT-only project. Business process owners need to be involved from day one to ensure requirements are captured accurately.

3. Set a Realistic Timeline

Depending on the complexity of your NAV environment, a migration can take anywhere from two to nine months. Scope out milestones for data audit, data migration, configuration, user acceptance testing (UAT), and training. Rushed timelines are the most common cause of post-go-live disruption.

4. Engage a Certified Microsoft Partner

The complexity of moving from Navision to Business Central, especially for organisations with significant customisations or integrations, makes a qualified implementation partner essential. Look for a partner with documented Business Central delivery experience and an understanding of your industry. Teams like Buy Business Central, powered by Cetas, specialise specifically in NAV-to-BC transitions and can help you scope the project, manage data migration, and configure the system to your requirements before go-live.

Step-by-Step: The Upgrade Process from Navision to Business Central

Step 1: Back Up Your Existing NAV Data

Before any migration activity begins, take a full backup of your Navision database. This is non-negotiable. Ensure the backup is stored securely and verified as restorable.

Step 2: Clean Up Your System

Remove obsolete data records, inactive customisations, and unused integrations from NAV before migrating. A clean source system leads to a cleaner Business Central environment. This is also an opportunity to align your chart of accounts, customer and vendor records, and inventory data with how Business Central structures information.

Step 3: Migrate Data to Business Central

For organisations on older NAV versions, the path to Business Central Online typically involves upgrading to Business Central on-premises first, then using Microsoft's Cloud Migration Tool to move to the cloud. Your implementation partner will map the right sequence of steps based on your current NAV version.

Step 4: Configure Business Central

Set up user roles and permission sets, configure workflows and approval chains, establish chart of accounts and dimensions, and connect any required integrations such as payment gateways, e-commerce platforms, or CRM systems. Business Central's extension model (AL-based, deployed via Microsoft AppSource) is the approved method for any custom functionality, replacing C/AL modifications from older NAV versions.

Step 5: User Acceptance Testing

Run UAT with representatives from every affected department. Test end-to-end business scenarios, not just individual screens. Confirm that all integrations, reports, and workflows are functioning as expected. Document and resolve issues before sign-off.

Step 6: Train Your Team

Business Central's interface differs meaningfully from older NAV versions. Provide role-specific training, not generic platform walkthroughs. Finance users, warehouse staff, and sales teams each need training tailored to their workflows. Complement instructor-led sessions with user guides, short video walkthroughs, and a clear process for raising post-go-live support queries.

Step 7: Go Live and Monitor Closely

Schedule go-live at a low-volume period in your business cycle if possible. Keep your implementation partner engaged during the first two to four weeks after launch. Most post-go-live issues surface in the first month and are resolvable quickly with the right support structure in place.

Data Migration: Best Practices for NAV to Business Central

Data quality is the most common cause of post-migration problems. Follow these practices to reduce risk:

• Conduct a full data audit before migration begins. Identify and resolve duplicates, incomplete records, and data format inconsistencies in NAV first.
• Use Microsoft's Business Central Migration Tool as your primary mechanism. Supplement with custom scripts only where the tool does not cover your data structures.
• Decide in advance what historical data to migrate versus archive. Migrating everything from a decade-old NAV system is rarely necessary and adds complexity.
• Run parallel validation: compare opening balances, customer records, and inventory levels between NAV and Business Central before go-live.
• Do not migrate data once and assume it is correct. Run multiple migration passes during the project and validate after each one.

Handling Customisations and Integrations in Business Central

One of the more complex aspects of a Dynamics NAV upgrade is handling accumulated customisations. NAV was heavily customisable using C/SIDE and C/AL, and many organisations have built significant bespoke functionality over the years.

Business Central uses a modern extension-based model. Custom functionality is built using AL code and deployed as extensions. This approach means customisations do not interfere with the core product, making future upgrades far simpler. During migration, each NAV customisation should be reviewed: can it be replaced by a standard Business Central feature? Is there an AppSource extension that covers the requirement? Only functionality with no equivalent should be rebuilt as a custom extension.

For integrations, Business Central supports REST APIs, Power Automate connectors, and a broad range of third-party connectors. Most common integrations, including CRM systems, e-commerce platforms, and payment processors, have well-documented integration patterns. Test all integrations thoroughly during UAT and do not assume they will work as expected without verification.

Common Challenges in the Navision to Business Central Upgrade

• Underestimating customisation complexity: Teams often discover during assessment that NAV has far more custom code than anyone realised. Budget time for a thorough code review before scoping the project.
• Data quality issues: Migrating poor-quality data from NAV into Business Central does not fix the underlying problems, it carries them forward. Invest in a data audit.
• User resistance: Change management is as important as technical delivery. Involve end users early, communicate the benefits clearly, and provide adequate training before go-live.
• Scope creep: Once a migration is underway, requests for additional functionality often emerge. Manage scope formally and defer non-essential enhancements to a post-go-live phase.

Choosing the Right Partner for Your Business Central Migration

Your choice of Business Central implementation partner will have a significant impact on the outcome of your Dynamics NAV upgrade. The right partner brings more than technical skills. They bring NAV-to-BC migration methodology, sector-specific knowledge, and the ability to manage the inevitable complexity that surfaces during a live project.

When evaluating partners, look for documented experience with NAV-to-Business Central migrations specifically, not just general Business Central implementations. Ask for reference customers at a similar scale and complexity to your own. Buy Business Central is a specialist Microsoft Dynamics 365 Business Central practice, backed by the implementation expertise of Cetas, and focused exclusively on helping organisations plan, migrate, and optimise Business Central. If you want a straightforward starting point, their team can review your NAV environment and outline a migration path without obligation.

Frequently Asked Questions: Upgrading from Navision to Business Central

1. How long does a NAV to Business Central migration typically take?

The timeline depends on the size and complexity of your NAV environment. A straightforward migration with limited customisations can complete in two to three months. Complex implementations, with significant custom code, multiple integrations, and large data volumes, typically run six to nine months. Your implementation partner should provide a project estimate after a scoping assessment.

2. Will my historical NAV data be available in Business Central after the migration?

Yes, historical data can be migrated to Business Central, though most organisations choose to migrate a defined period of transaction history and archive older records rather than move everything. Decisions about what to migrate and what to archive should be made during the planning phase based on your reporting and compliance requirements.

3. Can Business Central support the custom workflows we built in NAV?

In most cases, yes, though the implementation approach changes. Business Central uses an AL extension model rather than NAV's C/AL customisation approach. Some NAV customisations can be replaced entirely by standard Business Central functionality or AppSource extensions. Others will need to be rebuilt as AL extensions. Your partner will review existing custom code and advise on the most efficient path for each requirement.

4. Is Business Central available as an on-premises solution, or only in the cloud?

Business Central is available both as a cloud (SaaS) solution via Microsoft's data centres and as an on-premises installation. Most organisations moving from NAV choose the cloud (SaaS) version to take advantage of automatic updates, reduced infrastructure costs, and anywhere-access. On-premises Business Central is an option for organisations with specific compliance or data residency requirements.

5. What is the difference between migrating from NAV 2018 versus NAV 2009?

The gap between your current NAV version and Business Central determines how much technical work is involved. NAV 2018 is architecturally closer to Business Central and supports a more direct upgrade path. NAV 2009 and earlier versions require more significant data transformation, and any customisations built on the older C/SIDE environment will need to be fully rebuilt as AL extensions. Older versions also tend to have more accumulated data and custom code that requires careful review during the assessment phase.

Next Steps: Making the Move from Navision to Business Central

Upgrading from Navision to Business Central is a structured process. It requires planning, the right team, and disciplined execution, but it is well-trodden ground. Microsoft has invested significantly in making the migration path accessible, and thousands of organisations have completed it successfully.

If your business is still running Dynamics NAV, the most practical next step is an assessment of your current environment. Understand what you have, what you need, and what a realistic migration timeline looks like for your specific setup. From there, the path to Business Central is manageable, and the operational benefits on the other side, in terms of productivity, visibility, and reduced infrastructure overhead, are meaningful.

The longer you defer the move, the further outside mainstream support Dynamics NAV falls. Starting the planning process now puts you in control of the timeline rather than reacting to it.

Ready to start your NAV to Business Central migration? The Buy Business Central team works with organisations at every stage of the upgrade journey, from initial scoping to go-live. Get in touch to discuss your environment and get a clear picture of what your NAV to BC migration would involve.