Microsoft Dynamics NAV to Business Central Upgrade

Moving from Microsoft Dynamics NAV touches finance, operations, IT, and leadership. Because it affects how core business processes run every day, the upgrade requires careful planning from the start. A Dynamics NAV migration involves assessing the current environment, cleaning and protecting ERP data, managing a controlled move, and transitioning to Dynamics 365 Business Central in a way that keeps disruption minimal. Whether the starting point is NAV 2009, 2013, 2015, 2016, 2017, or 2018, the right upgrade path depends on what is actually in the environment and how the business operates today.

Is Your Microsoft Dynamics NAV Version Still Right for Your Business?

Microsoft ended mainstream support for Dynamics NAV 2018 in January 2023, and older NAV versions have been out of support for longer. If your business still runs on Dynamics NAV, the system may continue to work day to day. But maintaining it, securing it, and connecting it with newer business tools will become increasingly difficult over time.

That creates practical risks:

NAV no longer receives new feature development, while Dynamics 365 Business Central continues to receive regular product updates

Security patches become limited or unavailable once support windows close

Regulatory and compliance updates may need manual handling or custom fixes

NAV-skilled developers and consultants become harder to find

ISV add-ons and third-party integrations built for Dynamics NAV may lose vendor support

An upgrade may not be urgent today. But each year on an unsupported NAV version quietly adds cost, risk, and complexity that becomes harder to manage the longer it is left unaddressed.

What a Microsoft Dynamics NAV to Business Central Upgrade Includes

A Dynamics NAV to Business Central upgrade is more than a version change. It affects code, data, reports, add-ons, integrations, and users. Without a clear scope at the start, teams are left making rushed decisions during testing or at go-live, when the cost of getting it wrong is higher.

The upgrade covers:

Code and customizations

Dynamics NAV used C/AL, while Business Central uses AL extensions. Custom logic built into your NAV environment, including modified base objects, custom reports, approval flows, and business rules, needs to be reviewed before the move. Some customizations can be rebuilt. Some can be replaced by standard Business Central functionality. Some may no longer be needed at all.

Data migration

Customer, vendor, item, chart of accounts, dimensions, and posting group data must be extracted, cleaned, validated, and loaded into Business Central. Open transactions including purchase orders, sales orders, open invoices, and inventory balances need careful handling so teams can trust what they see after go-live.

Reports and role centers

NAV reports built with RDLC or Word layouts may need to be rebuilt or adjusted for Business Central. Role centers, dashboards, and user views should reflect how finance, sales, purchasing, and operations teams actually work day to day.

Add-ons and ISV solutions

Third-party NAV add-ons require a separate review. Some have Business Central versions available through Microsoft AppSource. Others may need to be replaced, rebuilt, or removed if Business Central already covers the same function natively.

Integrations

Every system connected to Dynamics NAV, including payment tools, warehouse systems, e-commerce platforms, EDI, payroll, and CRM, needs to be assessed before the move. Connections are then rebuilt or re-established using Business Central APIs, approved apps, or workflow tools where appropriate.

How to Know If the Upgrade Is Right for Your Business Right Now

Upgrade timing depends on your current Dynamics NAV version, support status, system pressure, and business plans. Some organizations need to move quickly because support, security, or compliance risk is already present. Others have room to plan a phased migration to Dynamics 365 Business Central with more time to review data, customizations, integrations, and budgets.

Running NAV 2018 — extended support ends January 2028

High: start planning now

Running NAV 2009 to NAV 2016 with no security updates

High: risk is already present

Growing users, transactions, or reporting needs are slowing NAV

Medium to high

Compliance or regulatory needs are hard to manage in NAV

High

A key ISV add-on is ending NAV support

A key ISV add-on is ending NAV support Medium to high

Planning a new ERP integration or connected system

Medium: review the upgrade path first

Stable operations, limited customizations, and budget constraints

Plan a phased approach

What Business Central Adds for Your Teams After the Upgrade

After moving from Dynamics NAV, teams work in a modern ERP environment that brings finance, operations, reporting, and daily access together in one Microsoft system. Dynamics 365 Business Central connects with Microsoft 365, Power BI, Power Automate, and Teams, so work moves with fewer manual steps and less reliance on older NAV processes.

Business Central provides clearer financial visibility, bank reconciliation tools, multi-currency and multi-entity support, and audit trails that ease period-end close and external reporting.

Inventory forecasting, purchase planning, warehouse management, and manufacturing tools help teams manage stock, demand, and production with far less manual effort than many older NAV setups require.

The SaaS model removes much of the burden of on-premise server maintenance, manual patching, and infrastructure management. Microsoft handles platform updates and security patches, which frees the IT team to focus on users, configuration, and system support.

Power BI dashboards inside Business Central let managers review live business data without waiting for manual report runs or separate spreadsheet exports.

Users reach Business Central through a browser or supported device, so teams can work without depending on VPNs or remote desktop setups for everyday ERP tasks.

Our Dynamics NAV to Business Central Upgrade Process

A Microsoft Dynamics NAV upgrade requires a clear plan before any technical work begins. The migration is managed in defined steps, so data, code, reports, users, and connected systems are reviewed carefully before the move to Dynamics 365 Business Central.

Discovery and system assessment

Review the current NAV version, database size, custom code, users, and add-ons
Map existing pain points across finance, operations, reporting, and IT teams
Define the upgrade scope, timeline, risks, and required business inputs

Business Central planning

Set up the Business Central tenant, roles, security model, and user structure
Plan the chart of accounts, dimensions, workflows, and approval paths early
Confirm the data migration order, test cycles, and validation checkpoints

Custom code review and rebuild

Review each C/AL object and decide what to rebuild, replace, or retire
Rewrite approved NAV customizations as AL extensions for Business Central
Test the new extensions against real process needs before migration begins

Data migration and setup

Prepare master data, open transactions, balances, and key history for the move
Run test migrations in a sandbox before touching the live NAV environment
Validate records, balances, permissions, and workflows with business users

Integrations and reporting

Reconnect CRM, e-commerce, warehouse, payroll, EDI, and payment systems
Rebuild key reports, dashboards, role centers, and Power BI connections
Test each connection with real transactions before go-live approval

Cutover and post-go-live support

Plan the data freeze, final migration, user access, and go-live checks
Support users during launch and resolve issues found in live operations
Review system performance, reports, and workflows over the first few weeks

Data Migration: What Moves, What Gets Cleaned, and What Stays Archived

Data migration is one of the most sensitive parts of a Dynamics NAV upgrade. Older NAV systems often carry years of records, custom fields, duplicate entries, inactive accounts, and data gaps. Before anything moves into Dynamics 365 Business Central, the scope is reviewed in detail: what should be migrated, what needs cleanup first, and what should stay archived for reference.

Master data

Chart of accounts, customers, vendors, items, units of measure, locations, fixed assets, and employee records

Duplicate records, missing fields, inactive records, naming issues, and setup gaps

Financial data

Open general ledger entries, bank account data, balances, and posted transaction history

Trial balance accuracy, posting setup, account mapping, and reporting needs

Open transactions

Sales orders, purchase orders, open invoices, partial shipments, and pending receipts

Transaction status, open quantities, tax details, and cutover readiness

Dimensions and posting groups

Dimensions, posting groups, cost centers, departments, and related mappings

Business Central setup rules, mapping conflicts, and reporting structure

Historical data

Selected financial, sales, purchase, and inventory history based on business needs

Retention needs, audit requirements, file size, and archive options

Data cleanup

Incomplete records, duplicate entries, unused accounts, and outdated master data

Items that need correction, approval, or removal before the final load

Security, Compliance, and Access Control in Business Central

Dynamics 365 Business Central runs on Microsoft Azure, which provides stronger security controls than most older Dynamics NAV environments. That includes multi-factor authentication, role-based access, encryption for data in transit and at rest, and Microsoft cloud compliance coverage across SOC 2, ISO 27001, and GDPR-related controls.

Before permissions are set up in Business Central, the existing security model is reviewed in detail. This gives your team a clear opportunity to assess who actually needs access, where approval limits should sit, and which NAV users may have inherited wider permissions than their current role requires.

Configuration covers:

User roles and permission sets built around Business Central access rules

Department-level access for finance, operations, purchasing, and warehousing

Approval workflow permissions based on your business hierarchy

Audit logging for sensitive financial activity and system changes

If your business operates under specific compliance requirements, such as SOX, HIPAA, or industry-specific regulations, those needs are factored into the permission design before users move into the new environment.

Common Upgrade Risks and How We Manage Them

A Dynamics NAV to Business Central upgrade can affect data, custom code, integrations, users, and daily operations. The risk becomes easier to manage when each issue is identified early, tested properly, and assigned to the right owner before cutover.

Customization complexity is underestimated

We complete a C/AL code review during discovery before migration planning starts

Data quality issues appear during migration

We run data checks, test loads, and business sign-off before final migration

Daily operations are disrupted at go-live

We plan the cutover window, final data load, user access, and rollback steps

Users struggle with the new system

We provide role-based training before go-live using real business scenarios

Integrations fail after go-live

We test connected systems in a sandbox before the final cutover

Scope changes extend the timeline

We define scope early and use a clear review process for new requests

Microsoft 365 and Power Platform: What Opens Up After the Upgrade

Moving from Dynamics NAV to Dynamics 365 Business Central also gives your teams cleaner access to the Microsoft tools they likely already use every day. Tasks that often require custom development in NAV can be handled through built-in connections across Microsoft 365 and Power Platform.

Power BI:

Live dashboards connected to Business Central data for finance, sales, inventory, and operations reporting.

Power Automate:

Workflow automation across Business Central, Outlook, Teams, SharePoint, and approved external systems.

Microsoft Teams:

Business Central records such as invoices, purchase orders, and customer details can be shared directly inside Teams conversations.

Outlook integration:

Business Central records can be created, viewed, and updated from within Outlook, with fewer screen changes.

Microsoft 365 Copilot:

AI-assisted support for Business Central users, where licensing and setup allow.

Business Central

These connections can be planned as part of the upgrade itself, so your team starts with the integrations that fit how the business actually works day to day.

Why Work With Calance on Your NAV to Business Central Upgrade

A Microsoft Dynamics NAV upgrade requires more than technical execution. It needs a clear scope, careful planning, and a team that understands how NAV data, custom code, reports, users, and integrations actually move into Dynamics 365 Business Central. Calance approaches each upgrade with a practical plan, an honest assessment, and steady support through every stage of the move.

A clear assessment before the project begins

The current NAV version, customizations, data quality, integrations, users, and business processes are reviewed in detail upfront. If the upgrade needs extra cleanup, code review, or additional planning time, that is identified early so your team can make decisions with the full picture in view.

Deep familiarity with NAV and Business Central

Calance consultants have worked with Dynamics NAV across older and newer versions, including NAV 2009, 2013, 2015, 2016, 2017, and 2018. That experience helps in managing the transition from C/AL customizations, NAV reports, and legacy setups into a cleaner Business Central environment.

A plan shaped around your business

Every Dynamics NAV migration has different pressure points. Some businesses need careful data cleanup. Others require complex integrations, custom workflows, or ISV add-on review. The upgrade plan is built around your current setup, not applied as a template that fits no one in particular.

Support that continues after go-live

Questions tend to surface once users start working in the new system. Post-go-live support covers early issue resolution, report adjustments, workflow reviews, and user support as teams settle into Business Central.

Can we upgrade directly from NAV 2009 to Business Central?

It depends on your NAV setup, customizations, database size, and add-ons. Older versions often need extra technical review before the move. A proper assessment shows whether you need a staged upgrade path or a cleaner migration plan.

How long does a NAV to Business Central upgrade usually take?

Most projects take several weeks to a few months, depending on data volume, custom code, integrations, users, and testing needs. A smaller setup may move faster, while older or heavily customized NAV systems usually need more planning.

Will our team need to stop using NAV during the upgrade?

Your team can usually keep using Microsoft Dynamics NAV while planning, development, testing, and trial migration happen in separate environments. The main downtime usually happens during the final cutover, which is planned in advance.

Can we keep our existing NAV customizations?

Some customizations can be rebuilt in Business Central. Others may be replaced by standard features or removed if they are no longer needed. Each customization should be reviewed before deciding what stays, changes, or gets retired.

What happens to our current NAV reports?

Existing NAV reports need to be reviewed before migration. Some can be rebuilt in Business Central, some can move into Power BI, and some may be replaced with standard reporting options based on how your team uses them.

Do we need new licenses for Business Central?

Yes, Business Central uses a subscription-based licensing model. Your user count, roles, access needs, and feature requirements will shape the license plan. This should be reviewed before the upgrade budget is finalized.

Can Business Central work for multiple locations or business units?

Yes, Business Central can support businesses with multiple locations, departments, and entities. The setup needs careful planning around dimensions, permissions, reporting, inventory locations, approvals, and financial structure.

What if our NAV data has errors or duplicate records?

Data issues should be handled before migration. Duplicate customers, inactive vendors, missing fields, and old posting setups can create problems later. Cleaning the data early helps the new Business Central environment start on a stronger base.

Can we move to Business Central in phases?

Yes, some businesses choose a phased approach, especially when they have many users, locations, integrations, or custom processes. The right approach depends on risk, business timing, and how tightly your departments rely on NAV.

Will our existing integrations still work after the upgrade?

Most integrations need to be reviewed and reconnected for Business Central. Older NAV connections may not work as-is. Payment tools, CRM, warehouse systems, e-commerce platforms, and EDI links should be tested before go-live.

Is Business Central only available in the cloud?

Business Central is available as a cloud solution and an on-premises option. Many businesses choose the cloud version for easier updates and lower infrastructure work, but the right choice depends on your business, compliance, and IT needs.

How do we prepare users for the new system?

Users need role-based training before go-live. Finance, purchasing, sales, warehouse, and management teams should test real tasks in Business Central so they understand the new screens, workflows, reports, and approval steps.

Can we keep using Excel with Business Central?

Yes, Business Central works with Excel for tasks such as analysis, updates, and reporting. The goal is to reduce manual spreadsheet dependency where possible while still giving teams familiar tools for review and planning.

What should we check before choosing an upgrade partner?

Look for NAV experience, Business Central knowledge, code migration skills, data planning, integration support, testing discipline, and post-go-live availability. A good partner should explain the risks clearly before asking for a full project commitment.

When should we start planning the upgrade?

Start planning before support deadlines, compliance pressure, or system issues force a rushed decision. Early assessment gives you time to review cost, timeline, data quality, custom code, and the best path to Dynamics 365 Business Central.

Microsoft Dynamics NAV to Business Central Upgrade