Choosing to migrate your on-premises Microsoft Dynamics GP 2010 database to Microsoft's cloud-based Business Central database is a great way to take advantage of the benefits of a centralized, online data storage and administration solution. However, while the migration process can be straightforward, there are some considerations you should make to ensure a smooth transition. Listed below are some of the most common challenges and solutions to consider:
Replication of data from Business Central on-premises to Business Central online
The Business Central on-premises version is licensed by the user, with fixed costs. Customers have two options: a perpetual license, which has advantages, or a subscription license, which has disadvantages. There are several advantages to the subscription license, such as the ability to upgrade to new versions of Business Central, but there are also disadvantages. Regardless of which license type you choose, you should keep in mind that there are certain aspects of data replication that you should evaluate carefully.
buisnesscloud.comBusiness Central on-premises requires SQL Server 2016, or a later version. You can test updates and upgrades in a sandbox environment before actually implementing them on your production instance. Microsoft also provides free training modules for users to learn more about the product.
To replicate data from Business Central on-premises to Business Central online, you will first need to install the Self-Hosted Integration Runtime. After installation, you will be able to use the Cloud Migration Management page in the SaaS tenant to perform the replication. This includes running the Sync Table Extensions action and repairing companion table records. However, this is just one of the steps in the process. It is also important to run the migration tool in a sandbox environment. If you do not, you may run into problems with replication.
You will also need to update the extensions in the cloud environment, depending on which on-premises solution you are using. For example, if you are upgrading from a previous version of Dynamics NAV, you will need to replace the C/AL customizations with new extensions. Before completing this step, you will need to ensure that the extension contains the same count of records as the base application table. If the extension does not have the same number of records, the data will not be migrated.