{"title":"Run cloud migration setup","url":"https://jonas-paprotka.de/docs/dev-itpro/administration/migration-setup/","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/administration/migration-setup, 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/administration/migration-setup","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":"Run the Cloud Migration Setup guide to connect a Business Central on-premises database to an online environment and select the companies to migrate.","date":"2026-11-17","meta":{"topic":"how-to"},"outline":[{"level":1,"title":"Run cloud migration setup","slug":"run-cloud-migration-setup","at":0,"chars":12288},{"level":2,"title":"About delegated administrators","slug":"about-delegated-administrators","at":518,"chars":814},{"level":2,"title":"Prepare for migration setup","slug":"prepare-for-migration-setup","at":1332,"chars":1669},{"level":2,"title":"Run the cloud migration setup","slug":"run-the-cloud-migration-setup","at":3001,"chars":1719},{"level":2,"title":"Define SQL database connection and integration runtime","slug":"define-sql-database-connection-and-integration-runtime","at":4720,"chars":4569},{"level":3,"title":"Download and install the self-hosted runtime","slug":"download-and-install-the-self-hosted-runtime","at":8081,"chars":1208},{"level":2,"title":"Rerunning cloud migration setup guide","slug":"rerunning-cloud-migration-setup-guide","at":9289,"chars":2365},{"level":2,"title":"Troubleshoot and fix problems","slug":"troubleshoot-and-fix-problems","at":11654,"chars":293},{"level":2,"title":"Next steps","slug":"next-steps","at":11947,"chars":341}],"text":"# Run cloud migration setup\nThis article explains how to run the Cloud Migration Setup assisted setup guide to configure the components and connection for migrating data from a Business Central on-premises database to Business Central online environment. To learn more about the mechanics behind the Cloud Migration Setup, go to Cloud migration setup overview<migration-setup-overview>.\nSee Business Central on-premises to online migration: end-to-end overview<migrate-business-central-on-premises#migration-roadmap>.\n## About delegated administrators\nAny user running the cloud migration setup flow as a delegated administrator must receive approval from a licensed user in order to run the cloud migration. The licensed user must have the Essentials or the Premium license and SUPER permissions. In this case, 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 for approval. Once the licensed user has approved the request, the delegated administrator must restart the setup guide to continue. The licensed user can revoke the permission by opening the same approval link or the Delegated admin consent for cloud migration page and selecting Revoke Consent. Revoking consent stops the cloud migration.\n## Prepare for migration setup\n Review Check Prerequisites<cloud-migration-prerequisites> and make sure the environments meet the requirements.\n> IMPORTANT\n> 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.\n Create table mappings if you need to rename a table during the cloud migration or to move a subset of fields to a different table or table extension. See Define cloud migration table mappings<migration-table-mapping>.\n If you have any users already in your Business Central online environment and you want them to be able to work as usual during cloud migration, learn more in migration-retain-permissions.\n> TIP\n> You must run the assisted setup from a company that you aren't migrating data to. For example, sign in to the demonstration company, CRONUS, and start the process there. Make sure that other users are signed out of the target companies before replication.\n> TIP\n> You can migrate all the data that you want to take with you to the cloud, but be aware of the storage capacity of your online tenant. If you need more storage than the default 80 GB, you can buy another environment or extra storage capacity. Storage capacity includes 80 GB, allowances per Essentials, Premium, Device, or Partner Sandbox license, and extra capacity from purchased environments and storage capacity licenses. See Managing capacity<tenant-admin-center-capacity>.\n## Run the cloud migration setup\n1. Sign in to the Microsoft 365 tenant<https://admin.microsoft.com> used by Business Central online.\n The person who sets up and runs the cloud migration must be signed in as an administrator of the Microsoft Entra (Microsoft 365) tenant and Business Central online.\n1. Sign in to Business Central online<https://businesscentral.dynamics.com> and open the environment that you want to migrate the data to.\n1. Select Search (Alt+Q) in the upper-right corner, enter Cloud Migration Setup, and then select the related link.\n1. Read the information on the page and provided links. If you consent, switch on I accept warning & privacy notice, then select Next.\n1. Set Product option to the version that matches the on-premises product that you're migrating, then select Next.\n Select the current-version option only if the source and destination use the same major version. Select the earlier-versions option if the source uses an earlier supported major version.\n1. On the Define your SQL database connection page, fill in the information about the SQL database connection and integration runtime.\n See #define-sql-database-connection-and-integration-runtime.\n Select Next when done. Once you choose Next, a new pipeline is created in the Azure service. When completed successfully, the Select companies to migrate page appears.\n1. On the Select companies to migrate page, select one or more companies to migrate or, if available, switch on Migrate all companies, then select Next.\n You can always return to the page to add more companies.\n1. Select Finish to complete the cloud migration setup.\n If you want to open Cloud Migration Management, where you can run the migration, select Yes.\n## Define SQL database connection and integration runtime\nIf 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.\n SQL Configuration:\n  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.\n SQL Connection String:\n  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.\n  For example, `Server=MyServer\\BCDEMO;Database=BC210;User Id=MySQLAccount;Password=<SqlPassword>;`, if you're migrating from Business Central on-premises.\n  The following snippets illustrate a couple of connection strings with different formats for an SQL Server database:\n  `Server=<ServerName>\\<InstanceName>;Initial Catalog=<DatabaseName>;User Id=<SqlUserName>;Password=<SqlPassword>;`\n  `Server=<ServerName>\\<InstanceName>;Database=<DatabaseName>;User Id=<SqlUserName>;Password=<SqlPassword>;`\n> IMPORTANT\n> Include the space in the `User Id` keyword in both examples. UserID isn't a valid keyword.\nFor a Business Central database hosted on Azure SQL Database, a connection string typically looks like this:\n`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;`\nSee https://learn.microsoft.com/archive/blogs/sqlforum/faq-how-do-i-find-the-correct-server-or-data-source-value-for-an-sql-server-instance-in-a-connection-string.\nThe 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.\n Integration Runtime Name:\n  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. See Create and configure a self-hosted integration runtime<https://learn.microsoft.com/azure/data-factory/create-self-hosted-integration-runtime>.\n   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.\n   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.\n### Download and install the self-hosted runtime\nA new page appears from where you can download the self-hosted integration runtime that you must install. Follow the instructions on the page.\n1. Select Download the Self-hosted Integration Runtime to go to the Microsoft Download Center.\n1. On the Download Center, select Download > `IntegrationRuntime_<LatestVersion>.msi` > Next.\n The file is downloaded to your computer.\n1. Open the downloaded file to start the installation.\n When completed, the Register Integration Runtime (Self-Hosted) page opens.\n1. Go back to the Cloud Migration Setup page in Business Central and copy the value in the Authentication key field.\n1. Go back to the Register Integration Runtime (Self-Hosted) page and paste the key value in the authentication key box, then select Register.\n1. Go back to Cloud Migration Setup and select Next.\nOnce 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.\n## Rerunning cloud migration setup guide\nThere are some scenarios where it may be necessary for you to run the cloud migration setup guide more than once.\n> TIP\n> Before changing the setup, review how to restore the target environment to a specific point in time. See Restoring an environment<tenant-admin-center-backup-restore>.\nThe following list highlights a few examples:\n Multiple companies in Business Central on-premises\n  One example is if you want to add more companies to the migration, or if you want to change the companies to migrate, run the assisted setup guide again. A more efficient option, though, is to use the Select Companies to Migrate action from the Cloud Migration Management page.\n Add tenants to an existing runtime service\n  If you're a hosting partner, you may have multiple tenants running on the same integration runtime service. Each tenant is isolated in its 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 Configuration Manager. See Create and configure a self-hosted integration runtime<https://learn.microsoft.com/azure/data-factory/create-self-hosted-integration-runtime>.\nIn both examples, you're making updates to an existing runtime service. When the assisted setup guide asks for an existing runtime service name, open the Microsoft Integration Runtime Configuration Manager to find the name. Enter that name in the Integration Runtime Name field to reuse the existing service rather than create a new one.\nComplete 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. You can regenerate an Azure Data Factory key from the Cloud Migration Management page in Business Central online. See Manage cloud migration<migration-manage>.\n> TIP\n> If you're using Business Central on-premises, the same setup guide is also available in your on-premises solution. You'll automatically be redirected to Business Central online to continue the configuration process.\n> CAUTION\n> If you have mapped users in the first run of the cloud migration setup guide, then do not choose the Define User Mappings action again in subsequent runs.\n## Troubleshoot and fix problems\nIf you have any problems during setup, refer to the Cloud migration troubleshooting documentation for Business Central<https://learn.microsoft.com/troubleshoot/dynamics-365/business-central/welcome-business-central> in Microsoft troubleshooting documentation.\n## Next steps\nOnce the setup guide is complete and data migration is activated, the initial data migration is ready to be run from the Cloud Migration Management page.\n Change cloud migration data replication in Business Central online<cloud-migration-change-replication> (advanced, optional)\n Run Data Migration<migration-data-replication>."}