This article describes how to perform a Dynamics NAV upgrade by converting the database from one of the following versions to Business Central:
- Microsoft Dynamics NAV 2013
- Microsoft Dynamics NAV 2013 R2
- Dynamics NAV 2015, 2016
- Dynamics NAV 2017, 2018
This article can also be used to update you current D365 Business Central database to the latest cumulative update.
About Database Conversion in Dynamics NAV Upgrade
Converting a database, which is often referred to as a technical Dynamics NAV upgrade, changes the database so that it works on the latest D365 Business Central platform. The conversion updates the system tables of the old database to the new schema (data structure), and performs Dynamics NAV upgrade of all the reports to support Report Viewer 2015. It furnishes you with the recent platform features and performance enhancements.
The process is slightly different when you have multi-tenant deployment compared to a single-tenant deployment. The steps that follow indicate the differences where applicable.
Task 1: Preparation
- Transition from the use of codeunit 1
- Convert V1 Extensions to V2 extensions
Task 2: Preparing the Old Database
To convert the old database to a D365 Business Central database, the first task is to back up the old database and then prepare to convert it.
- Make a copy of the old databases or create a full database backup.
- For single-tenant mode, uninstall all extensions. For multitenant mode, be sure to uninstall all V1 extensions.
- Unpublish extensions versions that you do not want to use in the Dynamics NAV upgrade database.
- Open the Microsoft Dynamics NAV Development Environment that matches the Dynamics NAV version of the old database, and then connect to the old application database.
- In Object Designer, confirm that all objects are compiled and no objects are locked.
- On the Tools menu, select Build Server Application Objects, and then choose the Yes button.
- If any errors occur, they are shown in the Error List window. Ensure that you address all compilation errors before you continue.
- Then run the schema synchronization with validation to synchronize the database schema changes.
- And upload the Business Central Partner license to the database.
- (Multi-tenant only) Dismount tenants.
- Then stop the Dynamics NAV Server instance, and close the development environment.
- Clear all the records from the dbo.Server Instance and dbo.Debugger Breakpoint tables in the old application database in SQL Server.
- Close all to connections to the database.
Task 3: Run the Technical Upgrade on the Old Database
Next, you will convert the old database so that it can be used with D365 Business Central.
- If the database is on Azure SQL, add user account to the dbmanager database role on the master database.
- Install Business Central.
- Run the newly installed Microsoft Dynamics NAV Development Environment as an administrator.
- In the dialog box that shows, read the instructions about converting the database carefully because this action cannot be reversed.
- When you are ready, select the OK button, and then choose the OK button to confirm that you want to convert the database.
- When you are notified that the transformation was successful, select the OK button.
- If the database references any assemblies that are not included on the Business Central installation media, then add the assemblies to the Add-ins folder on Business Central Server.
- Connect a Business Central Server to the converted database.
- Go to the development environment, and set it to utilize the Business Central Server instance that connects to the database.
- Import the codeunit 1 replacement text file you created.
- Compile all objects without table mapping synchronizing (Synchronize Schema set to Later); you will do this later.
- Fix compilation errors.
- Recompile V2 extensions that you uninstalled previously.
- (Multi-tenant only) Mount the tenant.
- Run the schema synchronization with approval to finish the database transformation.
Task 4: Post-upgrade
- (Single tenant only) Install the V2 extensions that you uninstalled previously.
- If the old database utilized first-party V1 extensions, install and publish the V2 extensions that replace them.
- Transfer the custom code in the old codeunit 1 to use the new system event implementation.
- If you are going to convert a Microsoft Dynamics NAV 2016, you will have to modify C/AL code to ensure that the My Settings page works properly in the Business Central Web client.
- If you are going to convert a Dynamics NAV database, configure pages and reports included in the MenuSuite to be searchable in the Web client.
- Upload the customer license to the converted database.
Database and Windows collations in Dynamics NAV Upgrade
Starting from earlier SQL Server 2008, SQL Server collations are fully aligned with the collations in Windows Server. If you upgrade to D365 Business Central from Microsoft Dynamics NAV 2009, the step to convert the database includes upgrading the database from using SQL collations to using Windows collation. This collation changes provides users with the most up-to-date and phonetically accurate cultural sorting conventions.
Locus IT has worked with businesses that utilize Microsoft Dynamics NAV for their day to day operations and has provided unique solutions for their challenges. We provide Business Central implementation, Business Central upgradation, Business Central support and Business Central training services. For more information about how Microsoft Dynamics NAV can help your business, please contact us.