By iCepts Technology Group, Microsoft Dynamics 365 Business Central Partner | Updated October 2026

The clock is running. If your distribution or manufacturing business still runs Dynamics NAV 2017, you have about 90 days before Microsoft support ends. This guide answers the questions you need to settle now and gives you a clear plan to move to Microsoft Dynamics 365 Business Central.

When Does Dynamics NAV 2017 Support End?

Microsoft ends all support for Dynamics NAV 2017 on January 11, 2027. After that date Microsoft provides no security updates, no non-security fixes and no free or paid assisted support.

NAV 2017 left mainstream support years ago. January 11, 2027 is the end of extended support, the last stage of the Microsoft lifecycle. There is no further extension.

What Happens If You Keep Running NAV 2017 After End of Support?

Your system keeps working, but you carry every risk alone. You get no security patches, no bug fixes and no help from Microsoft. For distributors and manufacturers, that means growing exposure in security, compatibility, add-on support and staffing.

• Security exposure. Your ERP holds customer, vendor, pricing and banking data. Your cyber insurance carrier may ask about unsupported software at renewal.
• Compatibility gaps. Windows Server, SQL Server and Microsoft 365 keep moving forward. NAV 2017 does not.
• Add-on risk. Your EDI, warehouse, shipping and sales tax add-ons may lose vendor support too.
• A shrinking talent pool. Fewer consultants and developers work in C/AL every year. Fixes take longer and cost more.

Can You Migrate NAV 2017 Directly to Business Central Online?

No. Microsoft does not offer a direct path from NAV 2017 to Business Central online. You must upgrade through Business Central 14 on-premises first or reimplement Business Central with a clean start.

Microsoft’s documented upgrade path for NAV 2015 through 2018 has four steps:

1. Upgrade to Business Central 14 on-premises.
2. Convert every C/AL customization to an AL extension.
3. Upgrade to Business Central on-premises version 25 or later.
4. Run the cloud migration tool to replicate your data to Business Central online.

Should You Upgrade or Reimplement When You Leave NAV 2017?

Upgrade if your NAV system is clean and your customizations still matter. Reimplement if you run on years of workarounds or your processes have changed. Many distributors and manufacturers choose a fresh start because it lets them adopt standard Business Central features and leave old problems behind.

For help deciding what to bring forward, read what to keep, replace or leave behind in your NAV to Business Central migration.

What Should Your 90-Day NAV 2017 Migration Plan Include?

A strong 90-day plan has three phases. Spend days 1 to 30 assessing your system. Spend days 31 to 60 choosing your route, partner and scope. Spend days 61 to 90 cleaning data, building a sandbox and running your first trial migration.

Days 1 to 30: Assess Your Current State

• Inventory your customizations. List every modified object, report and integration. Mark each one keep, replace or retire.
• List your add-ons. Confirm each vendor offers a Business Central version on Microsoft AppSource.
• Map your critical processes. Order to cash, procure to pay, warehouse, production and month-end close.
• Size your data. Find oversized tables, years of old history and duplicate records.
• Review your risk. Talk with IT and your insurance carrier about running NAV 2017 after January 11.

Outcome: a fit-gap summary.

Days 31 to 60: Decide and Design

• Choose your route. Upgrade or reimplement, based on your fit-gap results.
• Select your partner. Look for proven Business Central experience in your industry.
• Right-size your licensing. Choose Essentials or Premium. Manufacturers that use production orders need Premium.
• Set scope and phases. Go live first with financials, sales, purchasing and inventory. Add advanced features later.
• Name your team. Assign an executive sponsor, a project lead and an owner for each core process.

Outcome: an approved project plan with a budget and a target go-live date.

Days 61 to 90: Prepare and Launch

• Clean your data. Close old purchase orders. Block inactive items, customers and vendors. Fix units of measure.
• Stand up a sandbox. Configure Business Central and test your core processes.
• Run your first trial migration. Load master data and open balances. Find problems while they are cheap to fix.
• Protect NAV during the bridge. Limit network exposure, tighten user access and test your backups.
• Tell your people. Share the why, the timeline and what changes for each team.

Outcome: a live project with your first trial migration complete.

What If You Can’t Go Live on Business Central by January 11, 2027?

Set a firm go-live date and manage the gap. Isolate the NAV server, restrict user access, keep backups tested and patch the operating system and database where you can. Keep the bridge period short so a temporary fix does not become years on unsupported software.

Why Should Distributors and Manufacturers Move to Business Central?

Business Central online removes future end-of-support deadlines, adds built-in AI and connects your ERP to Microsoft 365 and Power BI. You trade server hardware and upgrade projects for a predictable per-user subscription.

• Continuous updates. Microsoft keeps your system current.
• Built-in AI. Copilot and AI agents help your team process sales orders and find insights faster.
• Microsoft 365 integration. Work with ERP data inside Outlook, Excel and Teams.
• Real-time reporting. Connect Power BI for live dashboards on inventory, margins and production.

Frequently Asked Questions About NAV 2017 End of Support

How long does a NAV 2017 to Business Central migration take?

Timing depends on your customizations, data volume and chosen route. A focused reimplementation often moves faster than a full technical upgrade with heavy C/AL code. A fit-gap assessment gives you a realistic timeline for your business.

Can you keep your NAV customizations in Business Central?

Yes, if you upgrade. You must rebuild every C/AL customization as an AL extension before it runs in Business Central online. Many companies find that standard Business Central features now replace a large share of their old customizations.

Can you keep historical data if you reimplement Business Central?

You bring master data, open balances and open documents into Business Central. Older transaction history usually stays in a read-only archive or reporting database, so your team can still look it up.

Do manufacturers need Business Central Premium?

Yes, if you use production orders or service management. Business Central Essentials covers financials, sales, purchasing, inventory and warehouse management. Premium adds manufacturing and service management.

Will your NAV add-ons work in Business Central?

Many NAV add-ons for EDI, warehouse, shipping and sales tax now offer Business Central versions on Microsoft AppSource. Confirm each one with the vendor during your assessment and plan a replacement for any that do not.

Start Your NAV 2017 Plan Today

January 11 will arrive whether you act or not. Companies that start now choose their route, their partner and their go-live date. Companies that wait let the deadline choose for them.

iCepts Technology Group helps distributors and manufacturers across the U.S. move from Dynamics NAV to Business Central.

Sources: Microsoft Lifecycle: Ending Support in 2027 and Microsoft Learn: Migrate Dynamics NAV to Business Central online.