Dynamics 365 Business Central SaaS: How to Export database and restore it on local SQL Server and configure a Business Central On-Prem Instance without Docker

27-03-2026

Pre-requisites: Business Central Admin Center & AzureStandard Storage Accounts  

Steps to follow:

1. Create a Storage account in Azure portal and get the BlobService SAS URL.

2. From Business Central Admin Center, create databaseexport request by providing SAS URL.

3. You need to wait for some time depending on database sizeto compete the backup process.

4. Once backup completes, the bacpac backup file will beavailable for download in Storage Account Containers.  Download the bacpac file to your local SQLServer.

5. Open SSMS, and right-click Databases and then selectImport Data-tier Application…

6. Follow the instructions and provide the bacpac file pathwhich you have downloaded in step 4.

7. Wait for some time till database restored.

8. Once database restored, it will be available in Databaselist.

9. It is worth to note that only 10 database export allowedper environment per month.

10. Install & configure Business Central On-Prem withMultitenant=True.

11. Create Application database using New-NAVApplicationDatabase-DatabaseServer <Server Name> -DatabaseName <Database Name>

12. Set database name to the instance using Set-NAVServerConfiguration-ServerInstance <Instance> -KeyName DatabaseName -KeyValue <Database Name>

13. Restart the service using Restart-NAVServerInstance-ServerInstance <Instance>

14. You need to get the Tenant ID and the same can beobtained from the table $ndo$tenantproperty of the restored database. Browsethe table and get the Tenant ID.

15. It is mandatory to have the same version of BusinessCentral in Saas & On-Prem or Saas may have higher version.

16. Publish the System Application, Business Foundation, BaseApplication & Application app using Publish-NAVApp -ServerInstance <Instance>-Path <App path>

17. Publish all Microsoft & Third-Party apps which areinstalled in SaaS environment using Publish-NAVApp -ServerInstance <Instance>-Path <App path>

18. Mount the tenant using Mount-NAVTenant-ServerInstance <Instance> -DatabaseName <Tenant Database Name>-DatabaseServer <Server Name> -Tenant <Tenant ID>-AllowAppDatabaseWrite

20. Sync the tenant using Sync-NAVTenant -ServerInstance <Instance>-Tenant <Tenant ID> -Mode Sync

21. Sync all apps which you published in step 17 using Sync-NAVApp-ServerInstance <Instance> -Name <App name> -Version <Version>

22. Proceed with data upgrade with Start-NavDataUpgrade-ServerInstance <Instance> -Tenant <Tenant ID>-FunctionExecutionMode Serial -ContinueOnError

23. You need to wait till State becomes Operational inupgrade process. The same can be checked with Get-NAVDataUpgrade <Instance>-detailed -tenant <Tenant ID>

24. You may also run Get-NAVAppTenant -serverinstance <Instance>to check if any app sync is pending or not.

25. Restart the service using Restart-NAVServerInstance-ServerInstance <Instance>

26. You can now access the webclient using http://localhost:<Port>/<Instance>/?tenant=<TenantID>

27. If you get the message that “You do not haveaccess in Business Central”, proceed to truncate user details by removing recordsfrom user related tables.