Migrate to Business Central Online from Business Central On-premises

Your Business Central on-premises solution can have an identical twin in a Business Central online tenant. Use this twin to migrate to the cloud, or use it to connect to intelligent cloud scenarios. The migration can be started quite easily from the assisted setup wizard in your on-premises solution.

Note

You can migrate to Business Central online from versions 14, 15, 16, and 17.

To verify that you are running on the version that supports this migration, in the Business Central administration center, open the environment that you intend to migrate your data to, and then choose the Apps action. Make sure that these apps have the latest updates installed:

  • Intelligent Cloud Base
  • Business Central Intelligent Cloud

If you are migrating from version 14, 15, or 16, you must also make sure that the following apps are updated:

  • Business Central Cloud Migration – Previous Release
  • Business Central Cloud Migration – Previous Release [code for your country-specific version]

For more information, see Managing Apps.

Migrating data from extensions

When your on-premises solution is connected to the cloud, it is highly recommended that you test the impact of any extension in a sandbox environment before you install the extensions in your Business Central production tenant to help avoid any data failures or unintended consequences.

In order to support data migration, tables and table extensions must specify if data from that table must be migrated or not. By default, the ReplicateData property is set to Yes so that, by default, any extension that is installed in the Business Central cloud tenant will have all its tables migrated.

In certain circumstances, you may want to not migrate all data. Here are a few examples:

  • The extension is installed in the Business Central online tenant but not in the Business Central on-premises solution

    In this case, Business Central will attempt to migrate the data but show a warning. Since the extension is not installed on-premises, any table related to that extension table will not migrate, and warning notifications will appear in the cloud migration status page.

    If you own the extension, we recommend that you set the ReplicateData property to No on the extension tables. If you do not, and if you want data to migrate, install the extension in both your Business Central cloud tenant and your on-premises solution. If you do not want data to migrate, uninstall the extension from your Business Central cloud tenant.

  • The extension references a base table

    This can cause your base table to appear empty when you view data in your Business Central cloud tenant. If that happens, uninstall the extension from your Business Central cloud tenant, and then run the cloud migration process again.

Data that is not migrated

During the data migration process, Business Central does not migrate most system tables, users, and permissions.

Upgrading to a new version of Business Central

If you upgrade to a new version of Business Central on-premises, including a cumulative update, then you must update the extensions as well. Depending on your on-premises solution, your Business Central tenant contains different extensions for the cloud migration. For more information, see Business Central Intelligent Cloud Extensions.

Important

You must always install, publish, or upgrade the Intelligent Cloud Base extension first, and then the product-specific extension or extensions. Also, you must update the extensions both on-premises and online.

Also, at the end of the upgrade, you must make sure to run the Set-NAVApplication PowerShell cmdlet to set the application version in the upgraded database. The cmdlet sets the applicationVersion field in the ndo$tenantdatabaseproperty table so that the migration code can verify that you're migrating from the right version. For more information, see Post-upgrade tasks. If the field is blank, the migration cannot run.

Tip

Before you set up migration, you can test that the applicationVersion field is set by using the Get-NAVApplication cmdlet.

See also

Migration On-premises Data to Business Central online
Connect to the Intelligent Cloud from On-Premises
Managing your Intelligent Cloud Environment
ReplicateData Property
Intelligent Insights with Business Central
Migrate Legacy Help to the Dynamics 365 Business Central Format
Upgrading from Dynamics NAV to Business Central Online
Important Information and Considerations for Before Upgrading to Dynamics 365 Business Central Spring 2019