| title | description | author | ms.reviewer | ms.topic | ms.search.keywords | ms.date | ms.author |
|---|---|---|---|---|---|---|---|
FAQ about Migrating to Business Central Online |
Get answers to your questions about migrating to the cloud from an on-premises solution. |
jswymer |
jswymer |
conceptual |
cloud, edge |
11/30/2022 |
jswymer |
[!INCLUDEazure-ad-to-microsoft-entra-id]
This section contains answers to frequently asked questions about migrating from on-premises solutions to [!INCLUDEprod_short] online.
Tip
Check the tips in this article if your organization is not yet ready to migrate to [!INCLUDE prod_short] online but are thinking hard about it. For more information about migration, see Migrate On-Premises Data to Business Central Online.
[!INCLUDE bc-cloud-products]
For more information, see Upgrading from Dynamics NAV to Business Central online.
To migrate to [!INCLUDEprod_short] online, the on-premises solution must use SQL Server 2016 or a later version, and the database must have compatibility level 130 or higher. The on-premises solution must also be one of the supported versions.
For comparison, see the [System Requirements for [!INCLUDEprod_long] (on-premises) 2021 Release Wave 1](../deployment/system-requirements-business-central-v18.md) and subsequent versions.
How is my on-premises data migrated to my [!INCLUDEprod_short] online tenant?
Data is migrated using an Azure service called Azure Data Factory (ADF). ADF is a service that is always running within the [!INCLUDEprod_short] online service manager. When you start the cloud migration, a data pipeline is created in the ADF service so that data can flow from your on-premises solution to your Business Central online tenant. If your data source is a local SQL Server instance, you're also asked to configure a self-hosted integration runtime (SHIR). The runtime is installed locally and manages the communication between the cloud services and your on-premises data without opening any ports or firewalls.
There are no restrictions on the type of data that can be migrated. [!INCLUDE db-storage-limit]
We recommend that you reduce the number of companies that you're migrating data for in each migration run. You can specify which companies to include in the migration in the assisted setup wizard.
If you want to add more companies after the first selection of companies, you can add more companies in the Cloud Migration Management page in Business Central online. For more information, see Run the tool multiple times.
Yes. The SQL connection string is passed to Azure Data Factory, where it's encrypted and delivered to your Self-Hosted Integration Runtime. The connection string is used to communicate with your SQL Server instance during the data replication process. For more information, see How do I find my SQL connection string?.
You can find the connection string in SQL Management Studio for an on-premise SQL Server database or in Azure portal for an Azure SQL database. The user name and password defined in the connection requires a SQL Authenticated user name/password
A connection string to an on-premise SQL Server database looks like this:
Server={SQLServerName}{SQLServerInstance};Database={DatabaseName};User ID={UserName};Password={Password};
A connection string to an Azure SQL database looks like this:
Server=tcp:{ServerName},1433;Initial Catalog={DatabaseName};Persist Security Info=False; User ID={UserName};Password={Password};MultipleActiveResultSets=False;Encrypt=True;TrustServerCertificate=True;Connection Timeout=30;
To learn more, go to Define SQL database connection and integration runtime.
Find the Integration Runtime name in the Microsoft Integration Runtime Manager, which you can find in your Windows system tray or by searching for the program. You must type the name. You can't copy and paste the name. You can get the key from the Cloud Migration Management by selecting the Get runtime service key action.
No, there's no limit on the number of tenants that can be added to your Self-Hosted Integration Runtime. Each added tenant has a dedicated pipeline created. However, if there are multiple tenants migrating using the same Integration Runtime, it's important to plan their migrations in a way that avoids overlapping in time. This will help prevent your Integration Runtime service from experiencing an excessive load.
No, only tables that are available in both your on-premises solution and your [!INCLUDEprod_short] online tenant will migrate. Any customization must be made into an extension and installed on both your on-premises solution and your [!INCLUDEprod_short] online tenant to replicate.
Yes, but it requires that someone defines tables mappings to move the customized fields. For more information, go to Define Migration Table Mappings.
When you connect your on-premises solution to [!INCLUDE prod_short] online as part of the migration, all existing users are automatically added to the Intelligent Cloud user group, unless they have the SUPER permission set. In this configuration, your on-premises solution is the primary source where all business transactions take place. The [!INCLUDEprod_short] online environment is read-only, and the data is used to generate intelligent business insights based on your on-premises data for you. We restrict permissions to prevent users from accidentally entering transactions or updating primary records only to have that information overwritten and lost when data replication takes place. Once the migration is complete, you can assign the relevant permissions to all users and stop using your on-premises solution.
No. Since you aren't required to configure your on-premises solution with Microsoft Entra ID, we can't guarantee a mapping between on-premises users and users in your [!INCLUDEprod_short] online tenant. [!INCLUDEprod_short] online requires Microsoft Entra accounts, and users must be manually added. All permissions must be granted in the [!INCLUDEprod_short] tenant, independent from your on-premises permissions.
For more information, see Managing Users and Permissions.
Yes, data is only replicated from the on-premises solution to your Business Central online tenant for the purposes of migration. Once you start using [!INCLUDE prod_short] online, you must stop using your on-premises solution.
No. But if your cloud migration includes data upgrade of a large amount of data, we recommend that you uninstall the extensions that that include any data to move. It speeds up the upgrade and overall cloud migration process. You can reinstall the extensions after the migration.
Troubleshooting Cloud Migration
Migrating On-Premises Data to Business Central Online