Dynamics SL migration to Business Central online: End-to-end overview
This article provides an overview of how the migration works and the necessary tasks for completing the migration from Dynamics SL on-premises. By gaining an understanding of the data migration basics, you're able to plan and execute a smooth transition to the cloud.
Understanding cloud migration
Data migration is the process of securely migrating data from an on-premises SQL Server instance to Business Central online. You manage cloud migration from Business Central online through a connection to the on-premises database and various components that establish a pipeline for replicating data. The on-premises solution remains the operative environment until you complete the cloud migration.
Components involved
The following figure illustrates the main components involved in the data migration process.
| Component | Description |
|---|---|
| On-premises database | This database is the on-premises SQL Server database that stores business data for the companies to migrate to the cloud. |
| Azure Data Factory | A key component of the data migration is Azure Data Factory. Azure Data Factory is a managed cloud service that's built for migrating large amounts of raw data across data sources and controlling data integration projects. Azure Data Factory migrates the data between on-premises and online directly. In other words, it doesn't look at any permissions within the applications you're transferring data between—only SQL permissions. |
| Pipelines | Pipelines are the main elements of Azure Data Factory. Pipelines are groupings of activities that copy, move, and transform data, and also orchestrate its flow. |
| Integration Runtime | The Integration Runtime component is the compute infrastructure of Azure Data Factory. There are two Integration Runtime instances in the end-to-end process. The first instance securely copies data from on-premises to the cloud, where the pipelines are created. If the on-premises database is an SQL Server database, you use a self-hosted integration runtime. This runtime is installed locally on the on-premises network and registered in Azure Data Factory. |
| Online database | This database is the Azure SQL Database of the Business Central environment to which you're migrating data. |
What data is migrated
In general, the cloud migration tool migrates the following data:
- System and company setup, accounting periods (Dynamics SL Fiscal periods), tax areas (Dynamics SL Tax Groups), and locations (Dynamics SL Inventory Sites)
- Master data for accounts, customers, vendors, and items
- Open Document amounts for customers and vendors
- Account balances by period
- Historical data
The company data that is migrated is configurable as part of the cloud migration setup. Learn more in Configure Dynamics SL company migration.
How data is migrated
Data is migrated table by table, and success and failures are tracked for each table. If a table fails to migrate, the error will be captured, and the migration moves on to the next table until completed. Tables fail to migrate if they can't be found, or if the schema doesn't match between the cloud and the on-premises tables.
Typically, you first run the migration as a test on a sandbox environment. Then, when you're ready to go live, you run the migration on the production environment. The data migration time can vary depending on factors such as the amount of data to migrate, your SQL Server configuration, and your connection speeds.
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.
End-to-end process
This section outlines the general process or phases you go through to migrate data from on-premises to online.
Migration Assessment
Before migrating your on-premises deployment to the cloud, it's essential to evaluate its readiness. To help you, we offer the Dynamics SL Analysis and Dynamics SL Repair tools that deliver valuable insight into your overall readiness to migrate. The tools provide migration options based on your needs and detect potential migration issues based on your Dynamics SL system structure. The Dynamics SL Analysis and Dynamics SL Repair tools are available to download and complete from GitHub. Here's the URL:
BCTech/Samples/DynamicsSLMigrationTools/Analysis and Repair Tool at master · microsoft/BC Tech
The Analysis Tool connects to a Microsoft Dynamics SL database and generates an analysis report text file.
The report outlines and provides an overview of the modules in use and examines the data that can be migrated to Business Central.
Analysis Report information example:
- Microsoft Dynamics SL version
- Microsoft SQL version
- Overview of Microsoft Dynamics SL modules being used
- Module details including the number of:
- Records in master tables
- Records in transaction tables
The Repair Tool connects to a Microsoft Dynamics SL database.
- The Repair tool is used to validate Microsoft Dynamics SL data to identify any issues that require repair before using the online Business Central tool to migrate Microsoft Dynamics SL data to Microsoft Dynamics Business Central.
- Repair Tool:
- Includes automated fixes to the Microsoft Dynamics SL data.
- Includes repair items that need to be addressed.
Preparation
The preparation phase helps ensure the migration runs as fast and problem-free. Preparation typically includes these tasks:
Plan
Develop a migration plan that includes a detailed timeline, resource requirements, and migration approach. A well-crafted plan can help minimize downtime and prevent users from losing work. You should plan to run cloud migration between environment updates.
To get started, go to Plan.
Verify prerequisites
Prepare your on-premises environment for migration, which includes ensuring that it meets the prerequisites for migration, such as using SL 2015 or later. This step is crucial in ensuring that your environment is ready for the migration process.
To get started, go to Prerequisites.
Verify that data is in the best state possible to complete the migration:
This step involves reviewing your data to ensure that it's clean, accurate, and in the best possible state for migration.
Cloud migration setup
The phase doesn't migrate any data, but it gets the environment ready for migration by establishing the connection and pipeline between the on-premises database and the online tenant database. You also specify which companies to migrate. This phase starts when you run the Set up Cloud Migration assisted setup guide in Business Central online.
To get started, refer to Set up cloud migration.
Configure Dynamics SL company migration
The step is part of the setup phase in which you select the companies and data that you want to migrate.
To get started, refer to Configure Dynamics SL company migration.
Data replication
This step migrates data from on-premises to online. It starts when you run the Run data replication assisted setup guide in Business Central online. At the end of the process, you have a copy of the on-premises data in the relevant Business Central online environment.
At this point in the process, you can verify whether the migration went well or not, fix any problems, and rerun the replication multiple times if you want to. Once the data replicates to the sandbox environment, you can use the troubleshooting tools in the Business Central administration center.
To get started, refer to Replicate data.
Data upgrade
After data replication is complete, the cloud migration might have the status Upgrade Pending on the Cloud Migration Management page. This step starts when you choose the Run Data Upgrade Now action in the Cloud Migration Management page in Business Central online for the specific environment.
To get started, refer to Upgrade data.
Important
Before running data upgrade, ensure that data from all companies has been replicated to the online database. Once you run data upgrade successfully, you can’t run data replication again from an earlier version, because you risk corrupting data in the online database by mixing non-upgraded records with upgraded records.
Completion and follow-up
Completion and follow-up are crucial steps in the cloud migration process, as they involve setting up and optimizing your new Business Central online environment. Here are some essential tasks to consider:
Optimize your Business Central online environment
Configure the system to meet your business needs. This task might include setting up security, customizing forms and reports, and integrating with other systems. By taking the time to optimize your new environment, you can ensure that it meets your specific requirements and works seamlessly with your existing systems.
Set up user access
Grant access to your new Business Central online system for all relevant users. This task includes creating new user accounts, setting up permissions, and defining roles and responsibilities.
Go live
Once you're satisfied that your new environment is set up correctly, it's time to switch over to the new Business Central online system. This task involves decommissioning the on-premises deployment and ensuring that all users are using the new system.
To get started, refer to Complete cloud migration.
By completing these tasks, you can ensure a successful migration to the cloud-based Business Central solution.
Working with environments during cloud migration
You manage the cloud migration from Business Central online. But once you start the migration phase, the on-premises solution remains the operative environment until you complete the migration. 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.
Any existing data in Business Central online is overwritten with data from your on-premises solution, or source, once the data replication is run.
If you don't want data in Business Central online to be overwritten, don't configure the connection.
Limited data entry during the migration period
Once the cloud migration is set up and underway, the data that you can enter in the Business Central online tenant is limited to data that isn't included in data migration from on-premises. Otherwise, any data that was written to the tenant database would be continuously overwritten during the migration process.
To make setting up this read-only tenant more efficient, we created the Intelligent Cloud Permission Set. Once the cloud migration environment is configured, existing users in the online tenant who don't have SUPER permissions are automatically assigned to the Intelligent Cloud Permission Set. Only users with SUPER permissions will be allowed to make modifications to the system at this point. If you add any online users later, make sure you assign them the Intelligent Cloud Permission Set. They're not assigned automatically.
Note
Before you configure a connection from on-premises to Business Central online, make sure that at least one user in each company is assigned SUPER permissions.
Users that are reassigned to the Intelligent Cloud Permission Set have access to read ALL data by default. If you need to further restrict what data a user should be able to read, the SUPER user can create new user groups and Permission Sets and assign users accordingly. It's highly recommended to create any new Permission Sets from a copy of the Intelligent Cloud Permission Set and then take away permissions you don't want users to have.
Warning
If you grant insert, modify or delete permissions to any resource in the application that was set to read-only, it could have a negative impact on the data in Business Central online. If this occurs, you may have to clear all your data and rerun a full migration to correct this.
Related information
Migrate Dynamics SL Data to the Cloud
FAQ about Migrating to the Cloud from on-premises Solutions
Managing Capacity