{"title":"Run cloud migration setup for Dynamics SL migration","url":"https://jonas-paprotka.de/docs/dev-itpro/administration/migration-setup-sl/","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-sl, 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-sl","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":"Learn how to connect Dynamics SL to Business Central online, select companies, configure migration data, and obtain delegated administrator consent.","date":"2026-11-17","meta":{"topic":"how-to"},"outline":[{"level":1,"title":"Run cloud migration setup for Dynamics SL migration","slug":"run-cloud-migration-setup-for-dynamics-sl-migration","at":0,"chars":9596},{"level":2,"title":"About delegated administrators","slug":"about-delegated-administrators","at":440,"chars":675},{"level":2,"title":"Prepare for migration setup","slug":"prepare-for-migration-setup","at":1115,"chars":1400},{"level":2,"title":"Run the cloud migration setup","slug":"run-the-cloud-migration-setup","at":2515,"chars":1141},{"level":2,"title":"Define SQL database connection and integration runtime","slug":"define-sql-database-connection-and-integration-runtime","at":3656,"chars":3800},{"level":3,"title":"Download and install the self-hosted runtime","slug":"download-and-install-the-self-hosted-runtime","at":6295,"chars":1161},{"level":2,"title":"Rerunning cloud migration setup guide","slug":"rerunning-cloud-migration-setup-guide","at":7456,"chars":1533},{"level":2,"title":"Troubleshoot and fix problems","slug":"troubleshoot-and-fix-problems","at":8989,"chars":240},{"level":2,"title":"Next steps","slug":"next-steps","at":9229,"chars":76},{"level":2,"title":"Related information","slug":"related-information","at":9305,"chars":291}],"text":"# Run cloud migration setup for Dynamics SL migration\nThis article explains how to run the Cloud Migration Setup guide to configure the components and connection for migrating data from a Dynamics SL on-premises database to a Business Central online environment. See Cloud migration setup overview<migration-setup-overview>.\nSee Dynamics SL migration to Business Central online: End-to-end overview<migrate-sl-overview#end-to-end-process>.\n## About delegated administrators\nAny user running the cloud migration setup flow as a delegated administrator must get 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 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.\n## Prepare for migration setup\n Review Cloud migration prerequisites for Dynamics SL<cloud-migration-prerequisites-sl> and make sure the environments meet the requirements. You must have the SUPER permission set in Business Central.\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 Review existing users' access to the target companies. Dynamics SL migration retains existing Business Central permissions rather than automatically assigning a read-only permission set. Restrict data entry until migration is complete.\n> TIP\n> 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.\n> Be aware of the storage capacity of your online tenant. If you need more than your included capacity, you can buy additional environments or storage capacity. Storage capacity is 80 GB plus allowances per licensed Essentials/Premium user and any storage capacity licenses. See Managing capacity<tenant-admin-center-capacity>.\n## Run the cloud migration setup\n1. Sign in to Business Central online<https://businesscentral.dynamics.com> and open the environment to which you're migrating the data.\n1. Search for and open the Cloud Migration Setup assisted setup guide.\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 to Dynamics SL, then select Next.\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.\n1. 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.\n1. Select Finish to complete the setup guide and open the SL company migration configuration.\n1. Configure the companies and data to migrate. See Configure Dynamics SL company migration<migrate-sl-configure-companies>.\n## Define SQL database connection and integration runtime\nIf your product requires an SQL connection, the Define your SQL database connection page appears during the Cloud Migration Setup. Other source applications might need different connection information. The Define your SQL database connection page shows the connection information based on the product you specified on the Choose your product page. The information comes from the installed extensions for the selected product. The following list provides more details about the fields in this part of the setup guide.\n SQL Configuration:\n  Specify SQL Server if the database is installed locally on an SQL Server instance.\n SQL Connection String:\n  Enter the connection string to your SQL Server, including the server name, instance name, database name, and user account.\n  For example, `Server=MyServer\\SLDEMO;Database=SLAppDb;User Id=MySQLAccount;Password=<SqlPassword>;`.\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.\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, specify the self-hosted Microsoft integration runtime instance 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, download the current installer, `IntegrationRuntime_<LatestVersion>.msi`.\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.\nAfter you select Next, a new pipeline is created in the Azure service. This operation usually takes less than a minute. To test your SQL string, open the Microsoft Integration Runtime Configuration Manager and select the Diagnostics menu option. From there, you can test the connection.\n## Rerunning cloud migration setup guide\nThere are some scenarios where it might be necessary for you to run the cloud migration setup guide more than once.\n> TIP\n> 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 do so.\nA 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. See Create and configure a self-hosted integration runtime<https://learn.microsoft.com/azure/data-factory/create-self-hosted-integration-runtime> in the Azure docs.\nIn 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.\nComplete the steps in the wizard to update the runtime service. If the change is related to adding tenants to an existing service, a new data pipeline is created for that tenant. To regenerate the integration runtime keys, use Reset runtime service key on Cloud Migration Management.\n## Troubleshoot and fix problems\nIf you encounter problems with the setup, learn more in Cloud migration troubleshooting for Business Central<https://learn.microsoft.com/troubleshoot/dynamics-365/business-central/welcome-business-central>.\n## Next steps\nRun and manage data replication<migrate-data-replication-run>\n## Related information\nDynamics SL migration to Business Central online: End-to-end overview<migrate-sl-overview>\nCompare work processes in Dynamics SL to Business Central<migrate-dynamics-sl-videos>\nFAQ about migrating to Business Central online from on-premises solutions<faq-migrate-data>"}