{"title":"Upgrading the Data to Business Central: Single-Tenant Deployment","url":"https://jonas-paprotka.de/docs/dev-itpro/upgrade/upgrading-the-data/","by":"JOP-AL","license":"Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrading-the-data, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact.","credit":"Microsoft Corporation, CC BY 4.0","origin":"https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrading-the-data","source":{"name":"Business Central developer and IT pro docs","repo":"https://github.com/MicrosoftDocs/dynamics365smb-devitpro-pb","commit":"828b6ee72fcd75755627cd6011f3d20899217ab2","date":"2026-11-19"},"checked":"2026-11-19","description":"This article describes the tasks required for upgrade the data to version 14 when you have a single-tenant deployment.","date":"2024-04-18","meta":{"topic":"how-to"},"outline":[{"level":1,"title":"Upgrading the Data to Business Central: Single-Tenant Deployment","slug":"upgrading-the-data-to-business-central-single-tenant-deployment","at":0,"chars":32208},{"level":2,"title":"About Data Upgrade","slug":"about-data-upgrade","at":1087,"chars":670},{"level":2,"title":" Prerequisites","slug":"prerequisites","at":1757,"chars":4313},{"level":2,"title":" Task 1: Create full SQL backup of old database","slug":"task-1-create-full-sql-backup-of-old-database","at":6070,"chars":364},{"level":2,"title":"Task 2 Uninstall all extensions in old database","slug":"task-2-uninstall-all-extensions-in-old-database","at":6434,"chars":1081},{"level":2,"title":" Task 3: Upload Business Central partner license to old database","slug":"task-3-upload-business-central-partner-license-to-old-database","at":7515,"chars":309},{"level":2,"title":" Task 4: Delete all objects except tables in old database","slug":"task-4-delete-all-objects-except-tables-in-old-database","at":7824,"chars":324},{"level":2,"title":"Task 5: Clear server instance and debugger breakpoint records in old database","slug":"task-5-clear-server-instance-and-debugger-breakpoint-records-in-old-database","at":8148,"chars":692},{"level":2,"title":" Task 6: Convert old database to Business Central","slug":"task-6-convert-old-database-to-business-central","at":8840,"chars":833},{"level":2,"title":" Task 7: Import upgraded application objects to converted database","slug":"task-7-import-upgraded-application-objects-to-converted-database","at":9673,"chars":774},{"level":2,"title":" Task 8: Connect a Business Central Server instance to converted database","slug":"task-8-connect-a-business-central-server-instance-to-converted-database","at":10447,"chars":1007},{"level":2,"title":" Task 9: Compile all objects in converted database","slug":"task-9-compile-all-objects-in-converted-database","at":11454,"chars":2046},{"level":2,"title":"Task 10: (Upgrade from Dynamics NAV 2018 or Business Central Fall 2018 only ) Increase the application version of converted database","slug":"task-10-upgrade-from-dynamics-nav-2018-or-business-central-fall-2018-only-increase-the-application-version-of-converted-database","at":13500,"chars":1030},{"level":2,"title":" Task 11: Run the schema synchronization on converted database","slug":"task-11-run-the-schema-synchronization-on-converted-database","at":14530,"chars":711},{"level":2,"title":"Task 12: Run data upgrade on converted database","slug":"task-12-run-data-upgrade-on-converted-database","at":15241,"chars":1862},{"level":2,"title":"Task 13: Upgrade Javascript-based control add-ins to new versions","slug":"task-13-upgrade-javascript-based-control-add-ins-to-new-versions","at":17103,"chars":1200},{"level":2,"title":" Task 14: Publish and generate symbols for extensions","slug":"task-14-publish-and-generate-symbols-for-extensions","at":18303,"chars":4596},{"level":2,"title":" Task 15: Upgrade or repair V2 extensions","slug":"task-15-upgrade-or-repair-v2-extensions","at":22899,"chars":3387},{"level":2,"title":"Task 16: Publish and install local functionality extensions","slug":"task-16-publish-and-install-local-functionality-extensions","at":26286,"chars":2653},{"level":2,"title":" Task 17: Import permission sets and permissions","slug":"task-17-import-permission-sets-and-permissions","at":28939,"chars":1035},{"level":2,"title":"Task 18: \\(Optional\\) Import data encryption key","slug":"task-18-optional-import-data-encryption-key","at":29974,"chars":219},{"level":2,"title":"Task 19: Set the language of customer database","slug":"task-19-set-the-language-of-customer-database","at":30193,"chars":190},{"level":2,"title":"Task 20: (Optional) Update Web Server instance configuration file","slug":"task-20-optional-update-web-server-instance-configuration-file","at":30383,"chars":1395},{"level":2,"title":"(Optional) Task 21: Delete upgrade objects","slug":"optional-task-21-delete-upgrade-objects","at":31778,"chars":347},{"level":2,"title":"Related information","slug":"related-information","at":32125,"chars":83}],"text":"# Upgrading the Data to Business Central: Single-Tenant Deployment\n> NOTE\n > If you're coming from version 13 or earlier, Business Central Spring 2019 (v14) is a required step to upgrade to the latest version of Business Central. However, mainstream support for version 14 ends in October 2023, and minor updates to the version are no longer available. New customers can't use version 14 in production, but only as a path for upgrading to latest version. Existing customers on version 14 remain supported by Microsoft as defined in the Fixed Lifecycle Policy<https://learn.microsoft.com/lifecycle/products/dynamics-365-business-central-onpremises-fixed-policy>.\nSee print-friendly quick reference<singletenant-upgrade-checklist>\nThis article describes the tasks required for upgrading the data of a Dynamics NAV or Business Central database to a Business Central major version or cumulative update.\nThis article pertains to a single-tenant deployment. For upgrade instructions for a multitenant deployment, see Upgrading the Data: Multitenant Deployment<upgrading-the-data-multitenant>.\n## About Data Upgrade\nYou use data conversion tools provided with Business Central to convert the old data with the old version's table and field structure, so that it functions together with the new version's table and field structure. Mainly, only table objects and table data are modified during the data upgrade process. Other objects, such as pages, reports, codeunits, and XMLports are upgraded as part of the application code upgrade process.\nThe data upgrade process described in this article leads you through the database conversion (technical upgrade) and then the upgrade of the actual data, which is achieved by using the upgrade toolkit/upgrade codeunits.\n##  Prerequisites\nBefore you start the upgrade tasks, make sure you meet the following prerequisites:\n1. Your computer uses the same codepage as the data that will be upgraded.\n If you use conflicting codepages, some characters will not display in captions, and you might not be able to access the upgraded database. This is because Dynamics NAV must remove incorrect metadata characters to complete the data upgrade. In this case, after upgrade, you must open the database in the development environment on a computer with the relevant codepage and compile all objects. This adds the missing characters again.\n Optionally, you can export the captions before the upgrade. See https://learn.microsoft.com/dynamics-nav/How-to--Add-Translated-Strings-for-Conflicting-Text-Encoding-Formats.\n2. (Upgrading from Dynamics NAV only) Custom V1 extensions used in the old deployment have been converted to V2 extensions.\n See Converting Extensions V1 to Extensions V2<../developer/devenv-upgrade-v1-to-v2-overview>.\n3. You have upgraded the application code, and have the FOB files that contain the upgraded application code.\n For more information about upgrading the application code, see upgrading-the-application-code.\n4. You have the upgrade toolkit FOB files that are available on the Business Central installation media (DVD).\n The upgrade toolkit includes upgrade codeunits for handling the data upgrade. The upgrade toolkit can be in the same FOB file as the application code or in a separate FOB file.\n For W1 versions, you can find the default upgrade toolkit objects in the UpgradeToolKit\\Data Conversion Tools folder on the Business Central installation media (DVD). Choose the FOB that matches the Dynamics NAV version from which you are upgrading:\n From|To Business Central April 2019|To Business Central October 2018\n Microsoft Dynamics NAV 2015|Upgrade80014x.FOB|Upgrade800130.FOB\n Microsoft Dynamics NAV 2016|Upgrade90014x.FOB|Upgrade900130.FOB\n Microsoft Dynamics NAV 2017|Upgrade100014x.FOB|Upgrade1000130.FOB\n Microsoft Dynamics NAV 2018|Upgrade110014x.FOB|Upgrade1100130.FOB\n Business Central Fall 2018|Upgrade13x14x.FOB|Not applicable\n For local versions, you will find the upgrade toolkit objects in the UpgradeToolKit\\Local Objects folder. The files follow the same naming convention except they include the 2-letter local version, such as Upgrade110014x.DK.fob for Denmark, Upgrade110014x.DE.fob for Germany, or Upgrade90014x.IN.fob for India.\n5. You have exported the customized permission sets (except SUPER) and permissions from the old database that you want to reuse in the upgraded database.\n  When upgrading from Dynamics NAV\n   To export permission sets and permissions, you run running XMLPort 9171 and 9172.\n   It is important that you exclude the SUPER permission set when running XMLPort 9171. You can do this by adding the filter `Role ID is <>SUPER`.\n   See how-to--import-export-permission-sets-permissions#ExportPerms.\n  When upgrading from an earlier version of Business Central\n   In the client, search for and open the Permission Sets page, select the user-defined permission sets that you want to keep, and then choose Export Permission Sets. This action runs XMLPort 9173 Export Permission Sets.\n6. If the old deployment uses data encryption, you have exported the encryption key file that it used for the data encryption.\n See how-to-export-and-import-encryption-keys.\n7. \\(Optional\\) Make a copy of the configuration file (web.config or navsettings.json) for all Business Central Web Server instances in the old deployment.\n8. Business Central has been installed.\n As a minimum, you must install the following components:\n  Server\n  SQL Server Components\n  Business Central Web Server components\n  Dynamics NAV Development Environment(DISCONTINUED AFTER: Business Central Spring 2019).\n  AL Development Environment\n  (optionally) Business Central Server Administration tool\n See Installing Business Central Using Setup<../deployment/install-using-setup>.\n> NOTE\n> If the old Dynamics NAV application uses Payment Services for Microsoft Dynamics ERP, be aware that this was discontinued in Microsoft Dynamics NAV 2017. This means that most of the objects that are associated with this feature will be deleted during the upgrade. Some objects you will have to manually delete.\n##  Task 1: Create full SQL backup of old database\nCreate a full backup of the old database in the SQL Server. Alternatively, you can make a copy of the old database and perform the upgrade tasks on the copy.\nSee https://learn.microsoft.com/sql/relational-databases/backup-restore/create-a-full-database-backup-sql-server?view=sql-server-ver15&preserve-view=true.\n## Task 2 Uninstall all extensions in old database\nOpen the Dynamics NAV Administration Shell or Business Central Administration Shell that matches to old database, and run these commands:\n1. To get a list of the extensions that are installed, run this command:\n ```\n Get-NAVAppInfo -ServerInstance <ServerInstanceName> -Tenant default\n ```\n Replace `<ServerInstanceName>` with the name of the Dynamics NAV Server instance that the database connects to.\n2. For each extension, run this command to uninstall it:\n ```\n Uninstall-NAVApp -ServerInstance <ServerInstanceName> -Name <Name> -Version <N.N.N.N>\n ```\n Replace `<ServerInstanceName>` with the name of the Dynamics NAV Server instance that the database connects to.\n Replace `<Name>` and `<N.N.N.N>` with the name and version of the Extension V1 as it appeared in the previous step.\n Alternately, to remove them all at once, you can run this command:\n ```\n Get-NAVAppInfo -ServerInstance <ServerInstanceName> -Tenant default | % { Uninstall-NAVApp -ServerInstance <ServerInstanceName> -Name $_.Name -Version $_.Version }\n ```\n##  Task 3: Upload Business Central partner license to old database\nBy using the Dynamics NAV Development Environment that matches the old database, upload the Business Central license to the database.\nSee Uploading a License File for a Specific Database<../cside/cside-upload-license-file#UploadtoDatabase>.\n##  Task 4: Delete all objects except tables in old database\nIn the development environment version that matches the database, open the old database, open Object Designer, select all objects except tables, and then choose Delete.\nYou can also use the [DeleteObjects](/dynamics-nav/deleteobjects\n) command of the finsql.exe.\n## Task 5: Clear server instance and debugger breakpoint records in old database\nClear all records from the dbo.Server Instance and dbo.Debugger Breakpoint tables in the database in SQL Server.\n1. Make sure that you stop the old server instance, and close any tools that connect to the database, such as the Dynamics NAV Administration Tool and development environment.\n2. Using SQL Server Management Studio, open and clear the dbo.Server Instance and dbo.Debugger Breakpoint tables of the old database. For example, you can run the following SQL query:\n ```\n DELETE FROM [<My NAV Database Name>].[dbo].[Server Instance]\n DELETE FROM [<My NAV Database Name>].[dbo].[Debugger Breakpoint]\n ```\n##  Task 6: Convert old database to Business Central\n1. If the database is on Azure SQL Database, you may get add your user account to the dbmanager database role on the master database.\n This membership is only required for converting the database, and can be removed afterwards. This step isn't required for Azure SQL Managed Instance.\n2. To convert the old database to the Business Central format, run the new Dynamics NAV Development Environment for Business Central, open the old database, and follow the conversion instructions.\n If you do not run the development environment as an administrator, you will get an error and the conversion will be stopped.\n For more information about how to open a database, see ../cside/cside-open-database.\n> IMPORTANT\n> Do not run schema synchronization at this time. Choose to run it later.\n##  Task 7: Import upgraded application objects to converted database\nUsing Dynamics NAV Development Environment for Business Central, import the application objects that you want in the database. This includes the application objects FOB file (from the application code upgrade) and the upgrade toolkit objects FOB file.\n1. Import the application objects FOB file first, and then import the upgrade toolkit FOB file.\n See ../cside/cside-import-objects.\n2. IMPORTANT When prompted about table synchronization, set the Synchronize Schema option to Later.\n3. When you import the FOB file, if you experience metadata conflicts, the Import Worksheet windows appears.\n Review the Worksheet page. See ../cside/cside-import-worksheet.\n Choose Replace All, and then OK to continue.\n##  Task 8: Connect a Business Central Server instance to converted database\nYou use the Business Central Server Administration tool or Set-NAVServerConfiguration cmdlet<https://learn.microsoft.com/powershell/module/microsoft.dynamics.nav.management/set-navserverconfiguration> in the Business Central Administration Shell to connect a Business Central Server instance to the converted database.\nThe service account that is used by the Business Central Server instance must be a member of the db_owner role in the Business Central database on SQL Server or Azure SQL Database.\nSee Connecting a Server Instance to a Database<../administration/connect-server-to-database> and Giving the account necessary database privileges in SQL Server<../deployment/provision-server-account#dbo>.\n> IMPORTANT\n> When upgrading a large database, you should increase the SQL Command Timeout setting for the Business Central Server instance, to avoid timeouts during schema synchronization. The default setting is 30 minutes.\n##  Task 9: Compile all objects in converted database\n1. In the Dynamics NAV Development Environment, set it to use the server instance that connects to the database.\n See Changing the Server Instance<../cside/cside-change-server-instance>.\n2. Use the Dynamics NAV Development Environment or finsql.exe to compile all objects. This includes the imported application objects, data tables, and system tables.\n> IMPORTANT\n> Choose to run schema synchronization later. For example, in Object Designer, choose Tools, choose Compile, set the Synchronize Schema option to Later, and then choose OK. See ../cside/cside-compiling-objects.\n3. (Upgrade from Microsoft Dynamics NAV 2016 and earlier only) If you get errors on the following table objects, use the Object Designer to delete the objects because they are no longer used.\n  Table 470 Job Queue (replaced by the ../developer/devenv-task-scheduler)\n  Table 824 DO Payment Connection Details\n  Table 825 DO Payment Connection Setup\n  Table 827 DO Payment Credit Card\n  Table 828 DO Payment Credit Card Number\n  Table 829 DO Payment Trans. Log Entry\n  Table 1510 Notification Template\n> IMPORTANT\n> When you delete a table object, in the Delete confirmation dialog box that appears, set the Synchronize Schema option to Force.\n> In this step, it's very important that you do not use the Sync. Schema For All Tables option from the Tools menu.\n4. (Upgrade from Microsoft Dynamics NAV 2016 and earlier only) If the old database includes test runner codeunits, you will get errors on these codeunits that the OnBeforeTestRun and OnAfterTestRun trigger signatures are not valid. To fix these issues, you change the signature of the OnBeforeTestRun and OnAfterTestRun triggers to include the TestPermission parameter.\n See Resolving OnBeforeTestRun and OnAfterTestRun Trigger Errors When Converting a Database<resolve-onbeforetestrun-onaftertestrun-compile-errors>.\n The triggers for codeunit 130400 CAL Test Runner and 130402 CAL Command Line Test Runner will be updated for you during the data upgrade.\n## Task 10: (Upgrade from Dynamics NAV 2018 or Business Central Fall 2018 only ) Increase the application version of converted database\nYou must increase the application version that is assigned to the database.\nUse the https://learn.microsoft.com/powershell/module/microsoft.dynamics.nav.management/set-navapplication cmdlet of the Business Central Administration Shell to increase the application version number of the database from its current version.\nTo see the current version, use the following command:\n```powershell\nGet-NAVApplication -ServerInstance <ServerInstanceName>\n```\nTo increase the version by 1, run the following command:\n```powershell\nSet-NAVApplication -ServerInstance <ServerInstanceName> -IncrementApplicationVersion\n```\nOr, to specify change to another version, run the following command:\n```powershell\nSet-NAVApplication -ServerInstance <ServerInstanceName> -ApplicationVersion <N.N.N.N> -Force\n```\nFor example, if the old version was `11.0.24279.0`, then you could change the version to `14.0.24279.0`.\n##  Task 11: Run the schema synchronization on converted database\nSynchronize the database schema with validation.\nFor example, run the https://learn.microsoft.com/powershell/module/microsoft.dynamics.nav.management/sync-navtenant cmdlet from the Business Central Administration Shell.\n```powershell\nSync-NAVTenant -ServerInstance <ServerInstanceName>\n```\nWhen completed, the tenant (database) should have the status OperationalDataUpgradePending. To verify this, run the following cmdlet:\n```powershell\nGet-NAVTenant -ServerInstance <ServerInstanceName> -tenant default\n```\nSee Synchronizing the Tenant Database and Application Database<../administration/synchronize-tenant-database-and-application-database>.\n## Task 12: Run data upgrade on converted database\nA data upgrade runs the upgrade toolkit objects, such as upgrade codeunits and upgrade tables, to migrate business data from the old table structure to the new table structure. You can start the data upgrade from the Dynamics NAV Development Environment or Business Central Administration Shell.\n1. Open the Business Central Administration Shell as an administrator, and then run https://learn.microsoft.com/powershell/module/microsoft.dynamics.nav.management/start-navdataupgrade cmdlet as follows:\n ```\n Start-NavDataUpgrade -ServerInstance <ServerInstanceName> -FunctionExecutionMode Serial -ContinueOnError\n ```\n Replace `<ServerInstanceName>` with the name of the Business Central Server instance that is connected to the database.\n> NOTE\n> In the last phase of data upgrade, all companies will be initialized by running codeunit 2 Company Initialization. This is done automatically. If you want to skip company initialization, then use the `Start-NavDataUpgrade` with the `-SkipCompanyIntitialization` parameter.\nTo view the progress of the data upgrade, you can run Get-NavDataUpgrade cmdlet with the `–Progress` switch.\nThe data upgrade process runs CheckPreconditions and Upgrade functions in the upgrade codeunits. If any of the preconditions are not met or an upgrade function fails, you must correct the error and resume the data upgrade process. If CheckPreconditions and Upgrade functions are executed successfully, codeunit 2 is automatically run to initialize all companies in the database unless you set the `-SkipCompanyIntitialization` parameter.\n2. Check for and resolve upgrade errors.\n Run the following command to get a list of any errors that have occurred:\n ```\n Get-NAVDataUpgrade -ServerInstance <ServerInstanceName> -ErrorOnly\n ```\n Resolve the errors before going to the next task.\n## Task 13: Upgrade Javascript-based control add-ins to new versions\nThe Business Central Server installation includes new versions of Microsoft-provided Javascript-based control add-ins, such as the Business Chart control add-in. If you application is using any of these add-ins, you must upgrade them to the new versions as follow:\n1. Open the Business Central client.\n If the application uses the Business Chart control add-in, you will get an error about High Charts. Upgrading the Business Chart control add-in will clear this error.\n2. Search for and open the Control Add-ins page.\n The page lists all the registered control add-ins.\n3. Choose Actions > Control Add-in Resource > Import.\n4. Locate and select the .zip file for the control add-in and choose Open.\n The .zip files are located in the Add-ins folder of the Business Central Server installation. There is a sub-folder for each add-in. For example, the path to the Business Chart control add-in is `C:\\Program Files\\Microsoft Dynamics 365 Business Central\\140\\Service\\Add-ins\\BusinessChart\\Microsoft.Dynamics.Nav.Client.BusinessChart.zip`.\n5. After you have imported all the new control add-in versions, restart Web Server instance.\n##  Task 14: Publish and generate symbols for extensions\nComplete this task if you are upgrading one of the following:\n Microsoft Dynamics NAV 2018 deployment that uses V2 extensions.\n Denmark (DK) version of Microsoft Dynamics NAV 2017 or earlier\n German (DE) version of Dynamics NAV or Business Central October 2018 (Cumulative Update 2 or earlier)\nIn this task, you will publish and generate symbols that are required for using V2 extensions. Symbols are the application programming interface between AL code and C/AL code. Symbols enable the ability to reference C/AL objects from AL objects. Symbols are provided as an extension package, and are published to the server instance, but not installed on tenants. There are three types of symbols: system, application, and test. System symbols contained references to the platform system objects. The application symbols contained references to the business application objects. The test symbols contained references to the test libraries used by Microsoft extensions.\n1. To get list of the extensions currently published symbols, run the following command from the Business Central Administration Shell:\n ```\n Get-NAVAppinfo -ServerInstance <ServerInstanceName> -SymbolsOnly\n ```\n2. Unpublish the existing system, test, and application symbols by using the Unpublish-NAVAPP cmdlet<https://learn.microsoft.com/powershell/module/microsoft.dynamics.nav.apps.management/unpublish-navapp>:\n ```\n Unpublish-NAVApp -ServerInstance <ServerInstanceName> -Name <name> -Version <n.n.n.n>\n ```\n3. Publish the system.app and test.app symbol files.\n If you installed the AL Development Environment, you can find the symbol files where your installed the environment, which by default is C:\\\\Program Files \\(x86\\)\\\\Microsoft Dynamics 365 Business Central\\\\140. Otherwise, you can find the files in the ModernDev folder on the installation media.\n To publish the symbols, open the Business Central Administration Shell as an administrator, and run the following command for each of the symbol files:\n ```\n Publish-NAVApp -ServerInstance <ServerInstanceName> -Path <SymbolFilePath> -PackageType SymbolsOnly\n ```\n4. Generate the application symbol references by using the finsql.exe file as follows:\n 1. Make sure that Enable loading application symbol references at server startup (EnableSymbolLoadingAtServerStartup) is set on the Business Central Server instance.\n  See Configuring Business Central Server<../administration/configure-server-instance>.\n 2. Open a command prompt as an administrator, change to the directory where the finsql.exe file has been installed as part of Dynamics NAV Development Environment, and then run the following command:\n  ```\n  finsql.exe Command=generatesymbolreference, Database=\"<MyDatabaseName>\", ServerName=<DatabaseServerName>\\<DatabaseInstance>\n  ```\n  Replace values for the Database and ServerName settings to suit.\n  If the application database contains test objects (ID 130000-139999), then make sure to exclude these objects when generating symbols. You can do this by using the `-Filter` parameter and running the command twice:\n  ```\n  finsql.exe command=generatesymbolreference, ServerName=<DatabaseServerName>\\<DatabaseInstance>, Database=\"<MyDatabaseName>\", filter=\"Object ID=1..129999\"\n  ```\n  ```\n  finsql.exe command=generatesymbolreference, ServerName=<DatabaseServerName>\\<DatabaseInstance>, Database=\"<MyDatabaseName>\", filter=\"Object ID=140000..1999999999\"\n  ```\n> NOTE\n> This command does not generate a file. It populates the Object Metadata table in the database.\n3. When you run the command, the console returns to an empty command prompt, and does not display or provide any indication about the status of the run. However, the finsql.exe may still be running in the background. It can take several minutes for the run to complete, and the symbols will not be generated until such time. You can see whether the finsql.exe is still running by using Task Manager and looking on the Details tab for finsql.exe.\n When the process ends, a file named navcommandresult.txt is saved to the Dynamics NAV Client connected to Business Central installation folder. If the command succeeded, the file will contain text like `[0] [06/12/17 14:36:17] The command completed successfully in '177' seconds.` If the command failed, another file named naverrorlog.txt will be generated. This file contains details about the error(s) that occurred.\nFor more information about generation symbols, see Running C/SIDE and AL Side-by-Side<../developer/devenv-get-started>.\n4. Restart the Business Central Server instance.\n##  Task 15: Upgrade or repair V2 extensions\nComplete this task if you are upgrading from a Microsoft Dynamics NAV 2018 deployment that uses V2 extensions. In this step, you will upgrade the V2 extensions that you previously uninstalled. The upgrade process will reinstall these extensions.\nThe Business Central installation media (DVD) includes several new versions of Microsoft extensions (that is, extensions that have Microsoft as the publisher). If your old deployment uses these extensions, you have to upgrade the current versions to the new versions.\n1. To get list of the extensions currently published on the application, run the following command from the Business Central Administration Shell:\n ```\n Get-NAVAppinfo -ServerInstance <ServerInstanceName>\n ```\n2. Upgrade the Microsoft extensions that were published in the old deployment to new versions.\n The new extension versions are found in the `\\Extensions` folder of the installation media (DVD). Follow these steps for each extension by using the Business Central Administration Shell:\n 1. Publish the new extension version by running the https://learn.microsoft.com/powershell/module/microsoft.dynamics.nav.apps.management/publish-navapp cmdlet:\n  ```\n  Publish-NAVApp -ServerInstance <ServerInstanceName> -Path <ExtensionFileName>\n  ```\n 2. Synchronize the schema with the database by running the https://learn.microsoft.com/powershell/module/microsoft.dynamics.nav.apps.management/sync-navapp cmdlet:\n  ```\n  Sync-NAVApp -ServerInstance <ServerInstanceName> -Name <Name> -Version <N.N.N.N>\n  ```\n 3. Upgrade the data of the extensions.\n  To run the data upgrade, run the https://learn.microsoft.com/powershell/module/microsoft.dynamics.nav.apps.management/start-navappdataupgrade cmdlet:\n  ```\n  Start-NAVAppDataUpgrade -ServerInstance <ServerInstanceName> -Name <Name> -Version <N.N.N.N>\n  ```\n  Apart from upgrading the data, this command will install the new extension version.\n For more information about publishing extensions, see ../developer/devenv-how-publish-and-install-an-extension-v2.\n3. Repair, synchronize, and install other currently published extension versions that you still want to use, but have not been upgraded to new versions.\n For each extension, complete the following steps from the Business Central Administration Shell:\n 1. Compile the extension to make it work with the new platform by running the https://learn.microsoft.com/powershell/module/microsoft.dynamics.nav.apps.management/repair-navapp cmdlet.\n  ```\n  Repair-NAVApp -ServerInstance <ServerInstanceName> -Name <Extension Name> -Version <N.N.N.N>\n  ```\n 2. Synchronize the schema with the database by running the https://learn.microsoft.com/powershell/module/microsoft.dynamics.nav.apps.management/sync-navapp cmdlet:\n  ```\n  Sync-NAVApp -ServerInstance <ServerInstanceName> -Name <Name> -Version <N.N.N.N>\n  ```\n  3. Install the extension by running the https://learn.microsoft.com/powershell/module/microsoft.dynamics.nav.apps.management/install-navapp cmdlet:\n   ```\n   Install-NAVApp -ServerInstance <ServerInstanceName> -Name <Name> -Version <N.N.N.N>\n   ```\n7. (Optional) Unpublish unused extension versions by running the https://learn.microsoft.com/powershell/module/microsoft.dynamics.nav.apps.management/unpublish-navapp:\n ```\n Unpublish-NAVApp -ServerInstance <ServerInstanceName> -Name <Name> -Version <N.N.N.N>\n ```\n## Task 16: Publish and install local functionality extensions\nComplete this task if you are upgrading one of the following:\n Denmark (DK) version of Microsoft Dynamics NAV 2017 or earlier\n German (DE) version of Dynamics NAV or Business Central October 2018 (Cumulative Update 2 or earlier)\n India (IN) version of Dynamics NAV 2016\nWith these language versions, some of the local functionality has been moved from the base application to extensions. These extensions will have to be published and installed to maintain the functionality. The extensions are available on the installation media (DVD).\nIf you are upgrading from a Denmark (DK) version, you must publish and install the following extensions to get the local functionality:\nName|Extension package\nOIOUBL|OIOUBL.app\nPayroll Data Import Definitions (DK)|ImportDKPayroll.app\nPayment and Reconciliation Formats (DK)|FIK.app\nTax File Formats (DK)|VATReportsDK.app\nIf you are upgrading from a German (DE) version you must publish and install the following extensions to get the local functionality:\nName|Extension package\nELSTER VAT Localization for Germany|Elster.app\nIf you are upgrading from an India (IN) version of Dynamics NAV 2016, you must publish and install the following extensions to get the local functionality:\nName|Extension package\n--|--\nIndia Tax Base|IndiaTaxBase.app\nIndia Tax Engine|IndiaTaxEngine.app\nIndia Tax GST|IndiaTaxGST.app\nIndia Upgrade Tables|IndiaUpgradeTables.app\nIndia TCS|IndiaUPGTCS.app\nIndia TDS|IndiaUPGTDS.app\nFixed Asset Depreciation for India|INFADepreciation.app\nIndia Gate Entry|INGateEntry.app\nIndia Voucher Interface|INVoucherInterface.app\nIndia Data Migration|UPGIndia.app\nFollow these steps for each extension by using the Business Central Administration Shell:\n1. Publish the new extension version by running the https://learn.microsoft.com/powershell/module/microsoft.dynamics.nav.apps.management/publish-navapp cmdlet:\n ```\n Publish-NAVApp -ServerInstance <ServerInstanceName> -Path <ExtensionFileName>\n ```\n The new extension versions are found in the `\\Extensions` folder of the installation media (DVD).\n 2. Synchronize the schema with the database by running the https://learn.microsoft.com/powershell/module/microsoft.dynamics.nav.apps.management/sync-navapp cmdlet:\n  ```\n  Sync-NAVApp -ServerInstance <ServerInstanceName> -Name <Name> -Version <N.N.N.N>\n  ```\n3. Install the newly published local functionality extensions by running the https://learn.microsoft.com/powershell/module/microsoft.dynamics.nav.apps.management/install-navapp cmdlet:\n ```\n Install-NAVApp -ServerInstance <ServerInstanceName> -Name <Name> -Version <N.N.N.N>\n ```\n##  Task 17: Import permission sets and permissions\nImport the permission sets and permissions XML files that you exported from the old database as follows:\n Upgrade from Dynamics NAV:\n  1. Open table 2000000004 Permission Sets in the client, and delete all permission sets except SUPER.\n> NOTE\n> You are only required to delete those permission sets that are also included in the permission sets XML file that you will import. Because if you try to import a permission set with the same name as one already in the database, you will get an error.\n2. Run XMLport 9171 and XMLport 9172 to import the permission sets and permission XML files.\n See how-to--import-export-permission-sets-permissions#ImportPerms.\n Upgrade from an earlier Business Central version:\n  1. In the client, search for and open the Permission Sets page.\n  2. Delete all user-defined permissions.\n  3. Choose Import Permission Sets, then select the permissions set file that you exported previously.\n   This action runs the XMLPort 9174 Import Tenant Permissions.\n## Task 18: \\(Optional\\) Import data encryption key\nIf you want to use data encryption as before, you must import the data encryption key file that was exported previously.\nSee how-to-export-and-import-encryption-keys.\n## Task 19: Set the language of customer database\nIn the Dynamics NAV Development Environment, choose Tools, choose Language, and then select the language of the original customer database.\n## Task 20: (Optional) Update Web Server instance configuration file\nIf you have installed the Business Central Web Server, populate the navsettings.json file for the Business Central Web Server instance with the settings of the old web.config file or navsettings.json.\n If the old deployment used a web.config file, then you have to manually change the settings in the navsetting.json file that is used on the new Business Central Web Server instance.\n If you upgraded from Business Central October 2018, you can replace the navsettings.json file on the new Business Central Web Server instance with the old file. However, as of Business Central April 2019, the following settings are now configured under a root element called ApplicationIdSettings instead of the root element NAVWebSettings.\n   AndroidPrivacy\n   AndroidSoftwareLicenseTerms\n   AndroidThirdPartyNotice\n   BaseHelpUrl\n   BaseSettingsSectionName\n   CommunityLink\n   FeedbackLink\n   IosPrivacy\n   IosSoftwareLicenseTerms\n   IosThirdPartyNotice\n   KeyboardShortcutsLink\n   PrivacyLink\n   LegalLink\n   SignInHelpLink\n  If the old navsettings.json file uses any of these settings, then you will have to move them from the NAVWebSettings element to the ApplicationIdSettings element.\nFor more information about the navsettings.json file, see Configuring Business Central Web Server Instances<../administration/configure-web-server>.\n## (Optional) Task 21: Delete upgrade objects\nAt this point, you have upgraded the database to Business Central. Now, you can delete the upgrade codeunits and upgrade table objects that you imported in task 9. This task is recommended but not required.\nWhen you delete tables, on the Delete dialog box, set the Synchronize Schema option to Force.\n## Related information\nupgrading-the-application-code\nupgrading-to-business-central"}