What is Microsoft Navision? Dynamics NAV Explained
If you have worked with ERP software for several years, you may have heard the names Microsoft Navision, Dynamics NAV, NAVISION, or Microsoft Dynamics 365 Business Central. These names are closely connected, but they do not all refer to exactly the same product version.
Microsoft Navision was a business management and ERP solution designed primarily for small and mid-sized organisations. It later became Microsoft Dynamics NAV, and its modern successor is Microsoft Dynamics 365 Business Central.
Navision and Dynamics NAV have been widely used to manage finance, purchasing, inventory, sales, manufacturing, warehousing, projects, and other business operations.
Microsoft acquired Navision in 2002 and continued developing the product within its business applications portfolio.
Today, businesses still running Microsoft Dynamics NAV may need to consider their long-term ERP strategy because support for older NAV versions has already ended, while even the final NAV releases are approaching the end of extended support.
This guide explains what Microsoft Navision is, how it became Dynamics NAV, what the software can do, how NAV differs from Business Central, and what existing NAV users should consider next.
What is Microsoft Navision?
Microsoft Navision is the former name of an enterprise resource planning system designed to bring core business processes into one platform.
Rather than maintaining separate systems for accounting, sales, purchasing, inventory, manufacturing, projects, and reporting, businesses could use Navision to manage multiple areas through a connected ERP environment.
Navision was particularly popular with small and mid-sized organisations that needed more functionality than basic accounting software but did not necessarily require an enterprise ERP platform designed for very large corporations.
Microsoft acquired Navision a/s in July 2002. At that time, Microsoft described Navision as a provider of integrated business software solutions for small and mid-market organisations.
Over time, Microsoft continued developing the software, eventually bringing it under the Microsoft Dynamics product family.
Is Navision the Same as Dynamics NAV?
Essentially, they belong to the same product family, but Navision and Dynamics NAV refer to different stages of the product's development.
The product evolved through several names before becoming the ERP platform businesses recognise today.
| Period | Product Name |
|---|---|
| Early product years | Navision |
| After Microsoft acquisition | Microsoft Business Solutions–Navision |
| Later Microsoft ERP releases | Microsoft Dynamics NAV |
| From 2018 onwards | Dynamics 365 Business Central |
Microsoft Dynamics NAV was therefore not an entirely unrelated ERP system. It was the evolution of the Navision product within Microsoft's business software portfolio.
Similarly, Dynamics 365 Business Central is the modern successor to Dynamics NAV, carrying forward many of the core ERP concepts while moving towards Microsoft's current cloud, integration, extension, automation, analytics, and AI architecture.
What Does NAV Stand for in Microsoft Dynamics NAV?
NAV originated from the Navision product name.
When Microsoft reorganised its business applications under the Dynamics brand, Navision became Microsoft Dynamics NAV.
You may therefore still hear businesses use terms such as:
- Microsoft NAV
- Dynamics NAV
- NAV ERP
- Microsoft Navision
- Navision ERP
- Dynamics Navision
In many organisations, employees continue to call the system “Navision” even when they are technically running a later Dynamics NAV release.
What Was Microsoft Dynamics NAV Used For?
Microsoft Dynamics NAV was designed to help organisations manage core business processes from a central ERP system.
Its exact functionality depended on the version, configuration, customisations, extensions, and industry solution deployed.
Common areas included:
Financial Management
Dynamics NAV could support important finance processes including:
- General ledger
- Accounts payable
- Accounts receivable
- Cash management
- Bank reconciliation
- Fixed assets
- Budgeting
- Financial reporting
- Multiple currencies
This allowed finance teams to work with financial information generated across different areas of the organisation.
Sales and Order Management
Businesses could use Dynamics NAV to manage:
- Sales quotes
- Sales orders
- Customer information
- Pricing
- Invoicing
- Returns
- Order fulfilment
Connecting sales transactions with finance and inventory helped reduce reliance on disconnected spreadsheets and systems.
Purchasing
Dynamics NAV could also support purchasing activities including:
- Purchase orders
- Supplier information
- Purchase invoices
- Receiving
- Procurement-related workflows
This helped businesses connect purchasing decisions with stock levels and financial information.
Inventory Management
Inventory-intensive businesses could use NAV to monitor:
- Stock levels
- Item availability
- Inventory movements
- Multiple locations
- Replenishment
- Item costing
For distributors, wholesalers, retailers, and manufacturers, inventory functionality was one of the important reasons for moving beyond basic accounting software.
Warehousing
Depending on the implementation, Dynamics NAV could support warehouse processes including receipts, put-away, picking, and movement of inventory.
Manufacturing
Manufacturing organisations could use Dynamics NAV for functions such as:
- Bills of materials
- Production orders
- Routings
- Capacity
- Production planning
- Material requirements
The ERP could therefore connect production operations with inventory and financial information.
Project and Job Management
Project-based organisations could use NAV to record costs, resources, time, and billing associated with jobs or projects.
Service Management
Businesses providing after-sales or equipment-related services could also use NAV functionality for service-related activities.
Why Did Businesses Choose Microsoft Navision and Dynamics NAV?
Dynamics NAV became a widely adopted ERP because it provided significant business management functionality while remaining adaptable to different industries.
Some of the main reasons organisations adopted NAV included:
One System for Multiple Departments
Instead of finance, inventory, purchasing, and operations maintaining separate data sets, NAV could provide a more connected operating environment.
Microsoft Ecosystem
Organisations already familiar with Microsoft technologies often found Dynamics NAV a natural fit within their wider IT strategy.
Customisation
Dynamics NAV became well known for its ability to be customised around specific business requirements.
That flexibility was useful, but it has also created challenges for some long-term NAV customers. Heavily customised environments can require significantly more assessment when planning an upgrade or cloud migration.
Industry Solutions
Microsoft partners and independent software vendors developed many industry-specific solutions around NAV, extending the platform for manufacturing, distribution, retail, professional services, and other sectors.
Is Microsoft Navision Still Available?
Microsoft Navision is not Microsoft's current ERP product name.
The product line evolved through Dynamics NAV and is now represented by Microsoft Dynamics 365 Business Central.
However, many businesses still operate older Dynamics NAV installations.
That distinction is important.
If someone says, “We use Navision,” they may actually be using NAV 2009, NAV 2013, NAV 2015, NAV 2016, NAV 2017, NAV 2018, or another legacy version.
The first step when planning an ERP upgrade should therefore be to identify the exact NAV version, customisations, database, integrations, add-ons, and infrastructure currently in use.
Is Microsoft Dynamics NAV Still Supported in 2026?
Support depends on the version.
Microsoft uses its Fixed Lifecycle Policy for the later Dynamics NAV releases.
As of 2026:
| Dynamics NAV Version | Current Position |
|---|---|
| NAV 2015 | Extended support has ended |
| NAV 2016 | Extended support ended in April 2026 |
| NAV 2017 | Extended support continues into January 2027 |
| NAV 2018 | Extended support continues into January 2028 |
Microsoft's lifecycle documentation confirms that NAV 2016 reached the end of extended support in April 2026. NAV 2017 and NAV 2018 remain within extended support for a limited period, with their respective lifecycle end dates falling in January 2027 and January 2028.
This matters because extended support is not the same as active product development.
Businesses operating legacy NAV systems should therefore consider whether continuing with an ageing ERP creates risks around security, compatibility, integrations, infrastructure, customisations, specialist skills, or future business requirements.
What Replaced Microsoft Dynamics NAV?
Microsoft Dynamics 365 Business Central is the successor to Dynamics NAV.
Business Central is Microsoft's business management solution for small and mid-sized organisations and supports areas including finance, sales, purchasing, inventory, warehousing, manufacturing, project management, service management, and reporting.
Microsoft's current Business Central platform also supports capabilities and integrations that reflect its newer technology ecosystem, including:
- Microsoft Teams
- Power BI
- Power Automate
- Microsoft 365
- Shopify
- Copilot
- APIs and web services
- Extensions developed using AL
Microsoft continues to release updates and new functionality for Business Central, including Copilot and agent capabilities.
Microsoft Dynamics NAV vs Business Central
Although Business Central developed from the NAV product family, businesses should not think of migration as simply installing a renamed version of NAV.
There are important differences.
| Area | Dynamics NAV | Dynamics 365 Business Central |
|---|---|---|
| Product generation | Legacy Microsoft ERP | Current Microsoft ERP platform |
| Typical deployment | Primarily on-premises | Cloud and on-premises options |
| Customisation approach | Often C/AL and direct customisation | AL extensions |
| Updates | Version-based lifecycle | Continuous cloud updates |
| Microsoft integration | Available, varies by version | Deeper modern Microsoft integration |
| Power Platform | Limited on older versions | Designed for Power Platform integration |
| AI capabilities | Limited | Copilot and agent capabilities |
| Infrastructure | Often customer-managed | Microsoft-managed with Business Central online |
| Future development | Legacy platform | Active Microsoft product |
Microsoft's current documentation shows that Business Central supports integrations, workflows, Power BI, Power Automate, Shopify, Copilot, APIs, and a broad set of finance and operational capabilities.
Should You Upgrade Dynamics NAV to Business Central?
Not every organisation needs to migrate for exactly the same reason.
However, there are several signs that a NAV environment should be reviewed.
Your NAV Version Is Out of Support
If Microsoft support for your version has ended, continuing indefinitely can increase technology and operational risk.
Customisations Have Become Difficult to Maintain
Some NAV environments have accumulated years of custom code.
Before migrating, businesses should identify which customisations are still genuinely required rather than automatically recreating everything.
Your Teams Depend on Manual Processes
If employees regularly export NAV data to spreadsheets, re-enter information into other applications, or build workarounds outside the ERP, the existing system may no longer meet current business requirements.
Remote Access Is Difficult
Cloud ERP can simplify access for organisations with multiple offices, remote employees, or distributed operations.
Integrations Are Becoming Harder to Maintain
Modern businesses increasingly need ERP integration with ecommerce, CRM, analytics, automation, banking, warehouse systems, and other applications.
Legacy integrations may become increasingly difficult or expensive to maintain.
Reporting Is Too Slow
Decision-makers may need more flexible access to operational and financial information than an ageing NAV configuration provides.
Business Central supports modern analytics and Power BI capabilities that can form part of a wider reporting strategy.
How Do You Migrate Dynamics NAV to Business Central?
A NAV-to-Business-Central migration should begin with an assessment rather than immediately attempting a technical upgrade.
Microsoft currently documents supported migration paths from Dynamics NAV to Business Central online.
For NAV 2015 through NAV 2018, Microsoft's standard migration route requires moving through Business Central version 14 on-premises before progressing to newer Business Central on-premises versions and ultimately Business Central online. Older NAV releases can require additional intermediate upgrades.
Microsoft also distinguishes between a full migration and a reimplementation approach.
A typical project should consider:
1. Assess the Existing NAV Environment
Document:
- NAV version
- Database
- Users
- Companies
- Modules
- Customisations
- Integrations
- ISV solutions
- Reports
- Data volumes
2. Review Customisations
Do not automatically move every NAV customisation.
Determine whether the requirement can now be handled using:
- Standard Business Central functionality
- Configuration
- AppSource extensions
- Power Platform
- New AL extensions
Microsoft states that C/AL customisations need to be converted to AL extensions for the standard Business Central online migration route.
3. Decide What Data to Move
Businesses need to determine whether they want:
- Full transaction history
- Selected historical data
- Master data
- Opening balances
- A fresh implementation with selected data
Microsoft's reimplementation path can be relevant where organisations want to move essential business data rather than carrying forward all legacy history and customisation.
4. Test Before Going Live
Migration should include sandbox testing, data validation, user acceptance testing, integration testing, and a controlled cutover plan.
Microsoft recommends performing migration dry runs before production cutover.
5. Train Users
Even when users are familiar with NAV, Business Central introduces changes to the interface, workflows, extensions, reporting, and integrations.
Training should therefore form part of the migration plan.
Upgrade or Reimplement: Which Approach Is Better?
This is one of the most important decisions for long-term NAV customers.
An upgrade may make sense if your existing environment is relatively clean and most configurations and business processes still provide value.
A reimplementation may be preferable when the existing NAV system contains:
- Excessive customisation
- Old integrations
- Poor-quality data
- Obsolete business processes
- Unused functionality
- Years of accumulated technical debt
Instead of recreating an old ERP environment in the cloud, reimplementation gives the organisation an opportunity to redesign processes around current Business Central functionality.
Microsoft now formally documents both migration and reimplementation approaches for NAV customers moving towards Business Central online.
Is Business Central Just Navision in the Cloud?
No.
Business Central has its roots in Navision and Dynamics NAV, but it has developed significantly beyond simply hosting NAV in the cloud.
Business Central now forms part of Microsoft's modern Dynamics 365 ecosystem and supports current capabilities for cloud administration, Power Platform integration, Teams, Power BI, Shopify, APIs, extensions, Copilot, and AI agents.
For existing NAV users, the familiarity of concepts and business processes can make Business Central a logical migration option, but the technology and operating model have changed substantially.
Is Microsoft Navision Still Right for Your Business?
If your organisation is currently running Dynamics NAV successfully, there may not be an immediate operational problem.
The more important question is whether the system remains suitable for the next five or ten years.
Consider:
- Is your NAV version still supported?
- How expensive is it to maintain?
- Can you find the required NAV skills?
- Are customisations holding back upgrades?
- Can NAV integrate easily with your current applications?
- Are employees relying heavily on spreadsheets?
- Can management access the reporting it needs?
- Does the ERP support future growth?
- Are infrastructure costs increasing?
- Would moving to Business Central simplify your architecture?
These questions provide a much stronger basis for an ERP decision than upgrading simply because a newer product exists.
Planning a Dynamics NAV to Business Central Migration?
Moving from Microsoft Dynamics NAV to Business Central is an opportunity to do more than replace ageing software.
It can also be used to review processes, eliminate unnecessary customisations, improve reporting, modernise integrations, and create a more scalable ERP environment.
However, the right migration approach depends on your NAV version, data, customisations, integrations, business requirements, and future plans.
Dynamics Square UK can help assess your existing Dynamics NAV environment and determine whether an upgrade, migration, or reimplementation of Dynamics 365 Business Central is the right approach for your organisation.
Our team can support requirements analysis, Business Central implementation, NAV migration, data migration, customisation, integration, testing, training, and post-go-live requirements.
Frequently Asked Questions
1. What is Microsoft Navision?
Microsoft Navision is the former name of a business management and ERP solution used by small and mid-sized organisations to manage processes such as finance, sales, purchasing, inventory, manufacturing, projects, and operations. It later evolved into Microsoft Dynamics NAV.
2. Is Microsoft Navision the same as Dynamics NAV?
Navision and Dynamics NAV belong to the same product lineage. After Microsoft acquired Navision in 2002, the product was developed within Microsoft Business Solutions and later became Microsoft Dynamics NAV.
3. What is Microsoft Navision called now?
The modern successor to Microsoft Navision and Dynamics NAV is Microsoft Dynamics 365 Business Central.
4. Is Dynamics NAV still supported?
It depends on the version. NAV 2015 and NAV 2016 have passed extended support. NAV 2017 remains in extended support into January 2027, while NAV 2018 remains in extended support into January 2028.
5. What is the difference between Dynamics NAV and Business Central?
Dynamics NAV is Microsoft's legacy ERP platform, whereas Business Central is its current business management solution. Business Central uses a modern extension model, offers cloud deployment, receives ongoing updates, and integrates more deeply with services such as Power Platform, Teams, Power BI, Shopify, and Copilot.
6. Can Dynamics NAV be migrated to Business Central?
Yes. Microsoft provides supported migration paths from Dynamics NAV to Business Central. The precise route depends on the NAV version, customisations, data, and target Business Central environment.
7. Should I upgrade NAV to Business Central?
Businesses should consider moving when their NAV version is approaching or has reached end of support, customisations are becoming difficult to maintain, integrations are ageing, reporting is limited, or the organisation wants a modern cloud ERP platform.
8. Can NAV customisations be moved to Business Central?
Some functionality can be carried forward, but legacy customisations should first be reviewed. For Microsoft's standard cloud migration path, C/AL customisations need to be converted to AL extensions. In many cases, existing customisations can also be replaced with standard Business Central functionality, extensions, or Power Platform solutions.