Skip to main content

How to Upgrade Data from Microsoft Dynamics NAV to Microsoft Dynamics Business Central On Premise - Part 1


The launch of the Microsoft Dynamics Business Central gave way to upgrades from Microsoft Dynamics NAV to Microsoft Dynamics Business Central.

This blog is about sharing my experiences with Business Central Upgrade from NAV 2017.
However, for different versions of NAV, a set of steps are to be followed to get to NAV 2017 and then upgrade to Business Central On-Premise.


  • Microsoft Dynamics 365 Business Central
  • Microsoft Dynamics for NAV
  • Microsoft SQL Server Management Studio (SSMS)
  • Powershell ISE
  • Understand NAV to BC Upgrade Considerations - Click here
  • Understand Upgrade Path - Click here

Books & References:


Microsoft Dynamics NAV to Microsoft Dynamics 365 Business Central Upgradation includes two major steps
1. Code upgrade: This step is mandatory when you have customizations/modules installed on top of Base NAV. Basically, your NAV codebase is shifting from C/AL to AL and all the customizations that you have built for NAV will be moved to extensions in Business Central. To get more details on code upgrade you can refer C/AL to AL Conversion

Also, you can refer to my C/AL to AL Code conversion using Text2AL

2. Data upgrade: This step comes after your customization code has been upgraded from C/AL to AL.
We need to do this step to migrate all the existing steps from 

i. Uninstall any extensions installed in NAV 
 Use 'Get-NAVAppInfo -ServerInstance DynamicsNAV100' to get Apps Installed in NAV DB 

Use UninstallNAV-App -ServerInstance DynamicsNAV100 -Name <AppName>

ii. Delete All Objects except Table from NAV Development Environment

Filter ObjectType <> Table and Delete the Objects
List of Objects present for the filter ObjectType<>Table

Only Table Objects are present

iii. Delete any Debug Points if present: The debugger points are stored in Debugger Breakpoint Table in SQL DB.

iv. Delete any ServerInstances if present: The Server Instances are stored in Server Instance Table in SQL DB.

v. Provide DB Owner permission to the User:

vi. Import Business Central Partner (Development) License:
In NAV 2017 Dev goto  New > Alter Database > Goto Integration Tab > Uncheck - Save license in Database > Close the window.
Again goto Alter Database and Check - Save license in Database > Select the .flf file

The uploaded License looks like

At this point, the SQL DB is preprocessed and ready to be upgraded to Business Central On-Premise.
Now you can install Microsoft Dynamics 365 Business Central On-Premise and connect Busines Central On-Premise to SQL DB.

The next steps will be in the upcoming blog post.


This blog contains steps of how to make the NAV database ready to be upgraded to Business Central OnPremise.
The next step on connecting Business Central On-Premise to SQL DB will be in the next blog.


Popular posts from this blog

Something went wrong. An Error occurred - Error Resolution

Introduction: With the installation of NAV 2018 or BC On-premise, I have observed that when creating New Server Instance and New WebServer Instance, you will get the error 'Something went wrong. An Error occurred '. I referred to the community questions below but didn't find my resolution. Hence, I decided to write this blog. Pre-requisites: Microsoft Dynamics Business Central - On-Premise / NAV 2018 Understanding of Business Central Authentication  Books & References: Demonstration: 1. Creation of NAVServerInstance: In order to create NAVServerInstance, you can either add the Server Instance through Business Central Administration or Powershell command. Add Instance - Business Central Administration Add Insta

Universal Code Error and Resolution

Introduction: On Friday, May 12th, 2023, the Business Central On-Premise Production Environments started throwing universal code errors as follows. This occurred to every customer on a lower version of BC 19,20 and 21 irrespective of their localization, customization, and license. Pre-requisites:  Understanding of Technical Upgrade in Business Central On-Prem References: BC20 On prem. Universal Code requirement error after installing customer's license. - Dynamics 365 Business Central Forum Community Forum (40) Yammer : Dynamics 365 Business Central Development : View Conversation Root Cause: The certificate that signs Microsoft Base Application was expired. Errors started occurring if you Uninstalled, Installed Extensions, Restart Server Instances or for some even out of random started popping out. We first thought could be a license issue as we had fixed that before but this did not solve the issue. Resolution: Microsoft identified the issue and posted the following update The mi

How to update your Business Central to Latest CU

Introduction:  There are times when Microsoft releases the latest major version upgrade for Business Central Upgrade and you face many issues with it. As soon as the bugs are reported to Microsoft, they start to fix them and ask you to upgrade to a certain Cumulative Update. In this blog, I will be sharing my experience with Business Central v21 CU0 upgrade to Business Central v21 CU2. Pre-requisites:  Business Central DVD for Latest CU Basic Understanding of Business Central CU Updates Books & References:  List of Update Packages How to Update CU version Demonstration:  1. Check the current state of BC: As part of knowing the current state of your Business Central environment, I'm assuming that your Business Central Environment will have some data in the standard Base App also there will be customization with extended tables and newly created tables. Customization - TableExtension on Customer Table  Customization - Custom Table created Make a note of the data that is present i