Microsoft Dynamics NAV Features: A Practical Guide

Microsoft Dynamics NAV is a legacy ERP whose mainstream support ended January 2023; extended support runs to January 2028. Its direct successor is Dynamics 365 Business Central, a cloud-SaaS rebuild that carries forward NAV’s full functional scope — financials, supply chain, manufacturing, and projects — with continuous updates replacing annual version releases. If you’re still running NAV, this article covers what it did well, what migrated into Business Central, and what a realistic upgrade path looks like.

What Is Microsoft Dynamics NAV?

Dynamics NAV was Microsoft’s mid-market ERP, aimed at small and medium businesses that needed more than accounting software but weren’t ready for enterprise-tier systems like Dynamics AX. It covered financials, supply chain, manufacturing, and project management in a single on-premises package.

NAV 2018 was the last standalone release. Microsoft replaced it with Dynamics 365 Business Central in 2018, which is cloud-first and receives continuous updates rather than annual version releases.

What Financial Management Features Did NAV Include?

NAV’s financial module was its strongest area. The general ledger handled multi-company and multi-currency setups. Accounts payable and receivable were tightly integrated, and bank reconciliation could be partially automated through bank feeds (in later versions).

Budgeting in NAV allowed for multiple budget scenarios — useful for comparing actuals to different forecast models. Dimension-based analysis let finance teams slice data by department, project, or cost center without restructuring the chart of accounts.

All of these capabilities exist in Business Central today, with improvements. The dimension structure is the same; the chart of accounts maps directly in a migration.

Supply Chain and Inventory

NAV’s supply chain tools were built for product-based businesses with moderate complexity. Core capabilities included:

• Purchase orders and vendor management — requisition-to-invoice workflows with approval routing
• Sales order processing — integrated with inventory and invoicing, with availability promises
• Inventory management — real-time stock levels across multiple locations, with item tracking (lot and serial numbers)
• Warehouse management — pick, put-away, and bin management for businesses with warehouse operations

Demand forecasting used historical sales data to suggest reorder quantities. For businesses running standard replenishment, this reduced stockouts without requiring a separate planning tool.

In my experience implementing these setups, the NAV warehouse module was adequate for single-warehouse operations. Multi-site businesses with complex fulfillment flows often found they needed customizations or third-party add-ons.

Manufacturing Capabilities

NAV included a production module suited to make-to-order and make-to-stock environments. Key features:

• Bills of materials (BOMs) — multi-level structures with component substitutions
• Capacity planning — work center and machine center scheduling with load visibility
• Production orders — planned, firm planned, and released statuses with routing
• Quality control checkpoints — definable at production stages
• Lot and serial tracking — end-to-end traceability from raw material to finished goods

Batch production and process manufacturing scenarios were workable in NAV, though the module was not designed for highly complex discrete manufacturing. Businesses needing advanced scheduling (finite capacity, constraint-based) typically added third-party tools.

Project Management

NAV’s Jobs module supported time-and-materials and fixed-price project billing. You could track labour, materials, and expenses against a project budget, and invoice based on progress or completion.

Job costing gave granular cost visibility at the task level. When I’ve set up Jobs for professional services clients, the biggest practical limitation was reporting — NAV’s native project reports were functional but required customization to produce useful management dashboards. Power BI integration (available in later NAV versions and standard in Business Central) addressed much of that.

Integration with Microsoft Products

NAV integrated with Office products in useful but limited ways. The Outlook integration let users manage customer contacts and log interactions from email. Excel was used for data export and import, and for financial reporting via report layouts.

Power BI connectivity was introduced in NAV 2017 and 2018, enabling live dashboards. This was a meaningful step forward — prior versions required data exports to build BI reports.

For a more detailed look at how these integration patterns evolved, see Does Microsoft Dynamics 365 Integrate with Office 365?.

What Carried Forward into Business Central

Dynamics 365 Business Central is not a new product — it is a rearchitected continuation of NAV. Microsoft ported the functional logic of every major NAV module:

• General ledger, dimensions, and chart of accounts structure
• Purchase and sales order workflows
• Inventory and warehouse management
• Manufacturing (BOMs, routings, production orders)
• Jobs (project management)
• Service management

	Dynamics NAV	Business Central
Delivery model	On-premises only	Cloud SaaS (online) or on-premises
Update cadence	Annual version releases	Two major waves per year, automatic in online
Customization approach	C/AL code modifications (C/SIDE)	AL extensions via Visual Studio Code
Support status	Extended support to Jan 2028 (NAV 2018); older versions end-of-life	Active, mainstream support

The core data model is recognizable to anyone who worked in NAV. The primary differences are the delivery model (cloud SaaS with automatic updates), the extensibility model (AL extensions instead of C/SIDE modifications), and the integration surface (native Dataverse connectivity, Power Platform, Microsoft Teams).

Customizations are where migration gets complicated. NAV customizations built directly in C/AL code cannot move to Business Central without being rewritten as AL extensions. This is the main source of migration cost and timeline for businesses with heavily modified NAV installs. The Microsoft migration guide for NAV to Business Central covers the technical steps in detail.

For a comparison of the two products side by side, see Dynamics NAV vs Dynamics 365.

What Does the Upgrade Path from NAV to Business Central Look Like?

If you’re on NAV 2018 (or earlier), the supported route to Business Central online is:

1. Upgrade data to Business Central Spring 2019 (v14) or a later on-premises version
2. Convert C/AL customizations to AL extensions
3. Run the cloud migration tool to move data to Business Central online

Businesses on heavily customized NAV installs often find step 2 is the longest part — inventorying all modifications, deciding what to rebuild vs. replace with standard BC functionality or AppSource apps, and testing.

Extended support for NAV 2018 runs until January 2028, per Microsoft’s lifecycle page. That is not a comfortable amount of runway — organisations planning a migration should be starting discovery now, not in 2027.

For more detail on how the upgrade process works in practice, see Dynamics 365 Upgrade Process.

Should You Stay on NAV or Move to Business Central?

The case for staying on NAV temporarily: extended support until January 2028 means security patches continue. Migration duration varies with C/AL customization, integrations, data volume, and testing scope; a heavily modified environment needs materially more runway than a lightly customized one. If a migration is underway and needs that runway, NAV is not an unsupported liability today.

The case against staying: NAV receives no functional updates. Business Central releases two major waves per year and has accumulated a substantial catalogue of additions since 2018 — Copilot capabilities, improved Power Platform integration, enhanced e-commerce connectors, and continuous compliance updates for VAT and regulatory requirements. Every month on NAV is a month of widening functional gap.

I’d also flag the partner ecosystem: NAV-specific ISV add-ons are losing support from their vendors. If a third-party NAV module is central to your operations, check whether that vendor has a Business Central equivalent and what their NAV support timeline looks like.

The right time to migrate was probably 2021. The second-best time is now. Start with a time-boxed discovery engagement that inventories customizations, integrations, data, and critical processes; only then can a Business Central partner give you a defensible scope and cost estimate.

To understand what Business Central costs on an ongoing basis, see Dynamics 365 Business Central Pricing: 2026 Cost Guide.