Migrating data from Business Central on‑premises to the online version may seem like a complex process; in this post, I will provide an overview of how the migration works.
We will take a detailed look at the process of migrating Business Central from On‑Premise to SaaS (Software as a Service), providing you with a complete and practical guide for a successful transition.
From understanding the fundamentals of the migration to efficiently managing the process and maximizing the benefits, our goal is to provide you with the information you need for a smooth transition to the cloud.
What is the migration of Business Central from On‑Premise to the cloud?
Migrating data is the process of securely transferring data from a local SQL Server instance (or Azure SQL) to Business Central online (in the cloud)..
This process is essential to fully leverage the advantages of the cloud, such as remote accessibility, scalability, and enhanced security.
The idea is to manage the cloud migration from Business Central online through a connection to the local database and several components that establish a pipeline to replicate data.
An important aspect to keep in mind is that the on‑premise solution remains the operational environment until the cloud migration is completed.
The following figure illustrates the main components involved in the data migration process. (Source Microsoft)
Main Components of Migration
- Local database: This database is the local SQL Server database or an Azure SQL database that stores business data for companies to migrate to the cloud.
- A key component of data migration is Azure Data Factory: Azure Data Factory is a managed cloud service designed to migrate large volumes of raw data between data sources and to manage data integration projects.
Azure Data Factory migrates data directly between the on‑premises and online environments. In other words, it does not analyze any permissions within the applications between which it is transferring data—only SQL permissions.
- Pipelines are the main elements of Azure Data Factory. Pipelines are groupings of activities that copy, move, and transform data, and also organize its flow.
- The "Integration Runtime" component is the computing infrastructure of Azure Data Factory. There are two instances of Integration Runtime in the end-to-end process.
- The first instance securely copies data from the on-premises environment to the cloud, where the pipelines are created. If the local database is a SQL Server database, use a self-hosted integration runtime. This runtime is installed locally on the local network and registered in Azure Data Factory.
- If the local database is an Azure SQL database, Azure Integration Runtime is used. From the pipeline, Azure Integration Runtime moves the data to the online database for the environment.
- Online database: This is the Azure SQL Database of the Business Central environment to which you are migrating data.
What are the essential data and requirements for the migration of Business Central?
The cloud migration process transfers business data from one or more companies in the local database to the online tenant database.
Local data comes from company‑specific tables in the base application and from tables that belong to customization extensions, whether from Microsoft or other publishers.
However, it is important to keep in mind that certain requirements must be met when migrating data from extensions, which means that not all data is necessarily transferred.
What data is not migrated?
During the data migration process, Business Central does not migrate system tables, users, or permissions. In addition, record links are not currently migrated because they are associated with a user ID, and users are not transferred from the on‑premises environment to the online tenant.
How is the data migrated?
In general, data is migrated table by table. Depending on their size, tables can also be combined and migrated together for performance reasons.
In any case, the success and failure of the migration is tracked for each table. For example, tables are not migrated if they cannot be found or if the schema does not match between the cloud and on‑premises tables.
If a table cannot be migrated, the error is captured and the migration moves on to the next table until the process is complete.
How long does the migration process to Business Central in the cloud take?
Data migration can be run multiple times. The duration of the data migration process varies depending on factors such as the amount of data to be migrated, the SQL Server configuration, and connection speeds.
The initial migration takes longer to complete because all data is being migrated. After the initial migration, only changes to the data will be migrated, resulting in faster iterations.
It is not necessary to run the migration process more than once. But if users are still working in the on‑premises system, you must run at least one additional migration to ensure that all data is moved to the cloud before performing transactions in Business Central online.
How to manage the migration to Business Central in the cloud?
Business Central offers two ways to manage cloud migration: the Business Central web client in the online environment or the cloud migration API.
The web client provides an easy‑to‑use interface to manage migration runs and services through the Cloud Migration Management page, while the API offers more advanced and automated capabilities.
Both options allow users to configure, move data, track progress, and manage migration services.
Is your business management system more than 5 years old?
Read this information about the risks of not migrating to the cloud.
ABD Consulting and IT Solutions: your partner for migrations to Business Central in the cloud
At ABD, we can be your strategic partner on your journey to the cloud. With years of experience in successful migrations to Business Central, our team of experts is dedicated to providing you with the assistance and support you need to take your company to the next level.
As a Microsoft Partner, we support you in the secure upgrade of your ERP, reducing risks and timelines.
With more than 30 years of experience in consulting and IT solutions, we are here to optimize your transition to the cloud.
I hope I have helped you understand the migration process to Business Central SaaS.
If you have any questions, contact us. We are here to help you.