Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
You cannot move a Dynamics NAV installation directly to Business Central online using Microsoft’s documented migration route. First upgrade NAV to Business Central on-premises, then migrate that Business Central environment to the cloud. The upgrade steps depend on your NAV version; a full migration also requires addressing C/AL customizations, while a separate Business Central v14 reimplementation route moves essential data rather than the entire NAV history.
Which upgrade path applies to your NAV version?
Microsoft’s documented standard routes use different intermediate versions. Treat these as planning paths, not a substitute for checking your exact source build, localization, customizations, and target release in Microsoft’s current Supported upgrade paths to Business Central on-premises guidance.
| Installed NAV version | Documented route to Business Central online |
|---|---|
| NAV 2015–2018 | Business Central on-premises v14 → Business Central on-premises v25 or later → Business Central online |
| NAV 2013 or NAV 2013 R2 | NAV 2018 → Business Central on-premises v14 → Business Central on-premises v25 or later → Business Central online |
| NAV 2009 SP1 or NAV 2009 R2 | NAV 2013 or NAV 2015 → NAV 2018 → Business Central on-premises v14 → Business Central on-premises v25 or later → Business Central online |
The route table comes from Microsoft Learn’s Migrate Dynamics NAV to Business Central online guidance. Microsoft’s upgrade matrix also warns that minor updates across releases are not all compatible. Confirm the precise sequence for your starting build and intended target release before scheduling upgrade work.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Can you migrate Dynamics NAV directly to Business Central online?
No—not through Microsoft’s documented path. NAV versions earlier than Business Central v14 must first be upgraded to Business Central on-premises. After the application and data have been brought to a suitable on-premises Business Central version, the cloud migration workflow handles replication, data upgrade, validation, and cutover.
#1 Best Overall
This distinction matters when estimating work: the NAV application upgrade and the move from Business Central on-premises to online are separate stages, with different compatibility checks and prerequisites.
Choose between full migration and reimplementation
Full migration: retain a broader data history and existing functionality
A full migration upgrades the application and data through the required on-premises versions, addresses custom functionality, and then uses the cloud migration workflow. It is the route to assess when retaining a broad history and the existing solution’s functionality is important. It does not mean every customization or every table’s data will transfer unchanged.
Business Central v14 reimplementation: move essential data
Microsoft describes a separate v14 reimplementation option as an essential-data-only route. It can move items such as master data, opening balances, and setup, rather than preserving the entire NAV database and all customizations. Consider it only if a reduced data scope and a deliberate fresh start fit the business’s needs. Verify the option’s current release status and supported details before selecting it.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Plan for C/AL customizations and customized-table data
For the full route, NAV C/AL customizations must be converted to AL extensions. Microsoft warns that data from tables with code customizations cannot be carried forward unless those customizations are converted to extensions. Inventory the custom objects and affected tables early, then decide how each customization will be converted, replaced, or retired. Do not assume that copying the database alone preserves customized behavior or its data.
Check the online migration prerequisites
Microsoft’s FAQ about Migrating to Business Central Online lists these requirements for the on-premises solution used in the online data migration stage:
- SQL Server 2016 or later.
- Database compatibility level 130 or higher.
- Azure Data Factory for the data pipeline.
- A self-hosted integration runtime when the source is a local SQL Server instance.
These are cloud-migration requirements after the NAV application has been upgraded to a supported Business Central on-premises version; they do not replace the version-specific upgrade steps.
How the migration proceeds
Microsoft’s roadmap separates the project into six broad phases. The work and calendar depend on the source environment, data volume, extensions, and validation requirements; the documentation does not establish a general migration duration or outage window.
- Prepare. Assess the current environment, project scope, prerequisites, data quality, and which companies will migrate in each batch.
- Upgrade NAV to Business Central on-premises. Follow the version-specific route and address C/AL customizations through AL extensions for a full migration.
- Set up cloud migration. Connect the on-premises database to the Business Central online tenant, install the required integration runtime where applicable, select companies, and configure the replication schedule.
- Replicate and validate. Run initial and incremental data replication, check results, and resolve issues before proceeding.
- Run the data upgrade and complete migration. Complete the cloud migration steps, then make the online environment primary.
- Complete post-migration work. Enable users, reconnect integrations, monitor the environment, and address performance needs.
Account for Business Central v14 and NAV lifecycle dates
Business Central v14 remains an intermediate upgrade step in Microsoft’s documented routes for some older NAV versions. Microsoft says v14 mainstream support ended in October 2023, minor updates are no longer available, and new customers cannot use it in production. Treat v14 as an upgrade bridge where the route requires it, not as the production destination for a new deployment.
Best Value
Microsoft identifies 2017 as the year the final Dynamics NAV version was released and January 2028 as the end of NAV extended support. Check Microsoft’s lifecycle information and the current upgrade matrix when planning, since lifecycle and target-release details can change.
Quick Recap
What to confirm before committing to a route
- Your exact NAV version, build, localization, and database state.
- The current supported upgrade sequence for that starting point and your intended Business Central release.
- Whether the goal is Business Central online or an on-premises deployment.
- Whether the project needs broad historical data or can use an essential-data-only reimplementation.
- How C/AL customizations and data in customized tables will be handled.
- SQL Server version, database compatibility level, Azure Data Factory setup, and integration runtime needs for the online migration.
- Company batching, validation responsibilities, integrations, and cutover readiness.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
