Run cloud migration setup for Dynamics GP migration

This article explains how to run the Cloud Migration Setup assisted setup guide to configure the components and connection for migrating data from a Dynamics GP on-premises database to a Business Central online environment. Learn more in Cloud migration setup overview.

Learn more in Dynamics GP migration to Business Central online: End-to-end overview.

About delegated administrators

Any user running the cloud migration setup flow as a delegated administrator must receive approval from a licensed user to run cloud migration. The licensed user must have an Essentials or Premium license and the SUPER permission set. The Cloud Migration Setup assisted setup guide displays an extra step where the delegated administrator can copy the autogenerated approval link and send it to the licensed user. After approval, the delegated administrator must restart the setup guide. The licensed user can revoke consent by opening the same link or the Delegated admin consent for cloud migration page and selecting Revoke Consent. Revoking consent stops cloud migration.

Prepare for migration setup

  • Review Cloud migration prerequisites for Dynamics GP and make sure the environments meet the requirements. You must have the SUPER permission set in Business Central.

    Important

    Don't set up cloud migration for a production environment that's already in use for business. You risk that the migration process overwrites data that's needed to run the business. Even if your migration targets a different company in that environment, you risk that the upgrade overwrites data that's shared across companies in the target environment.

  • Review existing users' access to the target companies. Dynamics GP migration retains existing Business Central permissions rather than automatically assigning a read-only permission set. Restrict data entry until migration is complete.

Tip

Run the assisted setup from a company that you aren't migrating. The guide prevents you from selecting your current company for migration. For example, sign in to the demonstration company, CRONUS, and start the process there.

Be aware of the storage capacity of your online tenant. If you need more storage than your included capacity, you can buy additional environments or additional storage capacity. Storage capacity is 80 GB plus allowances per licensed Essentials/Premium user and any storage capacity licenses. Learn more in Managing capacity.

Run the cloud migration setup

  1. Sign in to Business Central online and open the environment you want to migrate the data to.

  2. Use search to find and open the Cloud Migration Setup assisted setup.

  3. Read the information on the page and provided links. If you consent, switch on I accept warning & privacy notice, then select Next.

  4. Set Product to Dynamics GP, then select Next.

  5. On SQL Configuration, fill in the information about the SQL database connection and integration runtime.

    Learn more in Define your SQL database connection and integration runtime.

    Select Next when done. Once you choose Next, a new pipeline is created in the Azure service.

  6. After the pipeline is created, the Select companies to migrate page appears. Select one or more companies from the list, or turn on Migrate all companies when that option is available, then select Next.

  7. Select Finish to complete the setup guide and open the GP company migration configuration.

  8. Configure the companies and data to migrate. Learn more in Configure Dynamics GP company migration.

Tip

From GP Company Migration Configuration, select Migration settings to open GP Migration Settings. GP under Automatic Validation is on by default. This setting is separate from Run migration after replication, which starts data transformation automatically after replication. Review both options before your first run. Learn more in Validate Dynamics GP data migration.

Define SQL database connection and integration runtime

If the product you selected requires an SQL connection, the Define your SQL database connection page appears as part of the Cloud Migration Setup. Other source applications may require different connection information. The Define your SQL database connection page displays the connection information based on the product that you specified in the Choose your product page of the Cloud Migration Setup. The information is determined from the installed extensions for the product you've selected. The following list provides more details about the fields in this part of the assisted setup guide.

  • SQL Configuration:

    Specify SQL Server if the database is installed locally on an SQL Server instance. Specify Azure SQL if the database is an Azure SQL Database. The Azure SQL option doesn't apply to Dynamics GP, because it isn't supported.

  • SQL Connection String:

    You must specify the connection string to your SQL Server, including the name of the server that SQL Server is running on, and the name of the instance, the database, and the relevant user account.

    For example, Server=MyServer\BCDEMO;Database=BC210;User Id=MySQLAccount;Password=<SqlPassword>;, if you're migrating from Business Central on-premises.

    The following snippets illustrate a couple of connection strings with different formats for an SQL Server database:

    Server=<ServerName>\<InstanceName>;Initial Catalog=<DatabaseName>;User Id=<SqlUserName>;Password=<SqlPassword>;

    Server=<ServerName>\<InstanceName>;Database=<DatabaseName>;User Id=<SqlUserName>;Password=<SqlPassword>;

    Important

    Include the space in the User Id keyword in both examples. UserID isn't a valid keyword.

    For a Business Central database hosted on Azure SQL Database, a connection string typically looks like this:

    Server=tcp:<ServerName>.database.windows.net,1433;Initial Catalog=<DatabaseName>;Persist Security Info=False;User ID=<SqlUserName>;Password=<SqlPassword>;MultipleActiveResultSets=False;Encrypt=True;TrustServerCertificate=False;Connection Timeout=30;

    Learn more in Find the correct server or data source value for a SQL Server connection string.

    The SQL connection string is passed to Azure Data Factory (ADF). From there, it's encrypted and delivered to your Self-Hosted Integration Runtime and used to communicate with your SQL Server instance during the data migration process.

  • Integration Runtime Name:

    When SQL Configuration is set to SQL Server, you must specify the self-hosted Microsoft integration runtime instance to use to replicate the data from the defined source to Business Central online. The runtime can run on the SQL Server machine or another machine with network access to the database. Learn more in Create and configure a self-hosted integration runtime.

    • If you already have an integration runtime service instance, you can use the instance by entering its name in the Integration Runtime Name box. Then, select Next to continue Cloud Migration Setup assisted setup.

    • If you don't have an existing integration runtime service instance, leave the Integration Runtime Name field empty, then select Next to download and install the self-hosted runtime.

Download and install the self-hosted runtime

A new page appears from where you can download the self-hosted integration runtime that you must install. Follow the instructions on the page.

  1. Select Download the Self-hosted Integration Runtime to go to the Microsoft Download Center.

  2. On the Download Center, select Download > IntegrationRuntime_<LatestVersion>.msi > Next.

    The file is downloaded to your computer.

  3. Open the downloaded file to start the installation.

    When completed, the Register Integration Runtime (Self-Hosted) page opens.

  4. Go back to the Cloud Migration Setup page in Business Central and copy the value in the Authentication key field.

  5. Go back to the Register Integration Runtime (Self-Hosted) page and paste the key value in the authentication key box, then select Register.

  6. Go back to Cloud Migration Setup and select Next.

Once you choose Next, a new pipeline is created in the Azure service. This operation takes less than a minute to complete, in most cases. If you want to test your SQL string, open the Microsoft Integration Runtime Configuration Manager, and then choose the Diagnostics menu option. From there, you can test to see if the connection is good.

Rerunning cloud migration setup guide

There are some scenarios where it might be necessary for you to run the cloud migration setup guide more than once.

Tip

We recommend that you take a backup of the target environment so that you can easily restore the environment to a specific state and time, should you want to.

A common scenario is when you want to add tenants to an existing runtime service. If you're a hosting partner, you might have multiple tenants running on the same integration runtime service. Each tenant is isolated in their own data pipeline. To add tenants to an existing integration runtime service, enter the name of the existing integration runtime service into this field. The integration runtime name can be found in the Microsoft Integration Runtime Manager. Learn more in Create and configure a self-hosted integration runtime in the Azure docs.

In this scenario, you're making updates to an existing runtime service. When the assisted setup guide asks for an existing runtime, enter its name in Integration Runtime Name. The runtime service identifies that you're making updates to an existing service and doesn't create a new one.

Complete the steps in the wizard to update the runtime service. If the change was related to adding tenants to an existing service, a new data pipeline is created for that tenant. Regenerating an Azure Data Factory (ADF) key might be done using the Cloud Migration Management page in your Business Central online. Learn more in Run the assisted setup guide.

Troubleshoot and fix problems

If you run into problems with the setup, go to Cloud migration troubleshooting for Business Central.

Next steps

Run data replication.

Dynamics GP migration to Business Central online: End-to-end overview
Compare work processes in Dynamics GP to Business Central
FAQ about migrating to Business Central online from on-premises solutions