
Your Microsoft Dynamics NAV system may still handle daily operations. But as support ends for older versions and Microsoft invests in Business Central, maintaining the status quo can introduce new risks, costs, and missed opportunities.
Many ERP leaders delay the decision because NAV still works. However, continued functionality alone does not mean the system remains the best fit for the business.
Fortunately, organizations have more than one path for moving from Dynamics NAV to Business Central. This article compares two implementation options, explains the factors that influence scope and cost, and helps you identify the next best steps.
Which NAV Version Are You On?
An aging ERP environment is not automatically insecure, but staying current becomes harder as vendor support ends. NAV support status varies by version:
- NAV 2018: Extended support ends January 12, 2028
- NAV 2017: Extended support ends in January 2027
- NAV 2016: Extended support ended in 2026
- NAV 2015 and earlier: Out of support
To confirm your version, open the About page in Dynamics NAV and note the product version and build number. Then compare that information with Microsoft’s product lifecycle page. Earlier NAV versions have already moved beyond Microsoft’s support lifecycle.
Security Exposure Is an Actual Risk
Support status is only one consideration. Security exposure can also increase the urgency of maintaining and patching an aging ERP environment. In July 2026, Microsoft disclosed a critical vulnerability affecting NAV 2018 that could allow remote code execution without authentication or user interaction.
While Microsoft released a fix, the situation illustrates why organizations should maintain a clear patching and risk-management plan while using a legacy platform—a challenge many organizations face with aging ERP environments.
It’s also one reason why NAV migration is often part of a broader effort to simplify IT and position the business for future growth.
Why Move from Dynamics NAV to Business Central?
For finance and operations teams, Business Central can make reporting more accessible through Power BI while reducing repetitive work through workflows and Power Automate. Built-in approvals and automation can help teams manage routine tasks more consistently, turning an ERP migration into an opportunity to improve how work gets done.
As cloud-native ERPs evolve, Microsoft reports that Business Central has now surpassed 55,000 cloud customers, and that roughly half of those have used Copilot and at least one Business Central agent. These are capabilities teams can’t explore on legacy platforms like NAV.
Learn more about Microsoft Copilot and other AI-powered tools available in Business Central. Feature availability depends on the release, licensing, and deployment.
What Makes a NAV Migration More Complex?
Two organizations running the same NAV release can face very different projects. Scope and cost often depend on four factors:
- Your NAV version: Older releases may need intermediate upgrade steps and additional compatibility work.
- Legacy C/AL customizations: Teams must decide what to retire, replace with standard Business Central features, or rebuild as AL extensions.
- Data preparation: Customer, vendor, or inventory records may contain duplicates, obsolete information, or inconsistent master data.
- Integrations and specialized operational processes: These influence testing and implementation requirements.
How Customizations Influence Your Migration Path
Your migration path depends on what must be preserved, replaced, or redesigned.
Start by identifying which customizations are still business-critical, and which can be replaced by standard Business Central functionality. Review integrations to determine which still create value and which should be modernized or retired.
Just as important, consider how employees work today and what they will need to learn or do differently in the new environment. Have your business processes changed significantly since NAV was implemented? Would users benefit more from preserving existing workflows or modernizing them?
Before rebuilding a customization, review Microsoft AppSource for an ISV extension that already supports the requirement. A supported extension may replace legacy custom code while reducing development and long-term maintenance, but you’ll need to evaluate it with existing integrations.
What Data Should You Bring from NAV to Business Central?
One of the biggest misconceptions about moving from Dynamics NAV to Business Central is that everything has to come with you.
A migration gives you the opportunity to decide which information employees still need. Data should not move to the new ERP simply because it exists in NAV. Years of obsolete records, unused custom tables, outdated reports, and unnecessary historical transactions may be better retained outside the new production environment.
You can still maintain access to NAV for historical lookups, audits, and reporting needs. A good rule of thumb is to migrate the information needed to run the business today:
- Customers and vendors
- Open balances
- Active inventory records
- Open sales and purchase transactions
- Financial and reporting structures
What Are Your Options for Moving from Dynamics NAV to Business Central?
JourneyTeam’s Sherpa Program provides a guided option for qualifying Business Central implementations, while our ERP and CRM implementation services support more complex requirements. Both paths are designed to turn your business needs into a clearer scope, timeline, budget, and implementation estimate.
Option 1: Move to Business Central with Sherpa
Business Central Sherpa is a guided implementation path for organizations whose needs fit a predefined set of Business Central features. The program establishes the core environment, configuration, data migration, and adoption plan. It also helps determine which existing processes, integrations, and capabilities still need to move forward.
This approach often makes sense when requirements align closely with standard Business Central capabilities; customization and integration needs are limited, and the organization wants a structured path to scope, timeline, budget, and implementation.
Option 2: Choose a Custom Business Central Implementation
A custom implementation is designed for requirements that fall outside BC Sherpa’s scope. It is generally the stronger fit for organizations with extensive customizations, complex integrations, significant data needs, or specialized industry requirements. It also supports processes that should be redesigned rather than carried forward unchanged.
BC Sherpa vs. Custom Implementation
| Area | BC Sherpa | Custom implementation |
| Starting point | A guided deployment with predefined features, data, integrations, and project boundaries | A tailored project for requirements that fall outside those predefined boundaries |
| Data | Migrates the agreed core data needed for the defined scope | Supports broader, selective, or complex data migration based on business requirements |
| Customizations | Prioritizes standard Business Central capabilities with limited customization | Can use supported ISV extensions for specialized requirements, rebuild essential NAV customizations as AL extensions when an appropriate extension is unavailable, and develop new functionality |
| Processes | Uses standard Business Central processes where they meet the requirement | Can preserve, redesign, or create processes around complex operational needs |
| Integrations | Supports integrations included in the agreed BC Sherpa package | Can create, modernize, or extensively rework complex integrations |
| Business change | Provides a structured adoption path with a more standardized solution | May require broader process redesign, testing, training, and change management |
| Best fit | Requirements align closely with standard capabilities and complexity is limited | Requirements involve extensive customization, integrations, data, or specialized industry needs |
If you’re still exploring ERP options, download the Microsoft Dynamics ERP Buyer’s Guide for additional guidance.
How Much Does a NAV to Business Central Migration Cost?
Your total Business Central investment has two parts: Microsoft licensing (billed per user) and the implementation services needed to configure, migrate, test, and deploy the system.
The biggest variable is usually not the software. It’s the complexity of your business. For a deeper look, see Business Central Implementation Cost: 6 Factors That Set the Number.
A Real-World Journey from NAV to Business Central
Recognizing the need for a more scalable platform, Casper’s Ice Cream partnered with JourneyTeam on a NAV-to-Business Central migration that would modernize operations, streamline processes, and give employees better access to the information they need.
The company improved visibility across finance, inventory, manufacturing, warehousing, and logistics. The migration also eliminated a three- to four-day lag in inventory information and reduced manual order updates by more than 15 hours per week.
Casper’s experience highlights an important point: a successful NAV upgrade isn’t just about replacing an aging ERP system. It’s an opportunity to remove inefficiencies, improve access to information, and build a stronger foundation for future growth.
Read the full story: Casper’s Ice Cream’s NAV-to-Business Central migration.
Next Step: Find the Right Path Beyond NAV
Your NAV system may still be getting the job done. But maintaining it indefinitely may not be the best long-term strategy. The first step is to understand which processes, data, and customizations are worth preserving, and what your business needs next.
JourneyTeam can assess your current environment and help determine whether BC Sherpa or a custom project is the right delivery model.
That assessment will help you build a migration strategy that does more than replace an aging system; it can position your organization for future growth.