Replicating Data from Microsoft Dynamics NAV On Premises to Dynamics Business Central SaaS
To replicate a database from Microsoft Dynamics NAV on premises to Dynamics Business Central SaaS, follow these steps:
NOTE: In this example, a Microsoft Dynamics NAV (on premises) Name Database has been restored as BC SaaS Testing.
- Copy the company “Cronus USA” using the Copy function, Create a New Company, and name it BCSaasTesting.
- Open the Business Central Tenant and login with the user name provided.Figure 1 – Microsoft Dynamics Business Central login
- Create the Sandbox environment.
- Search – Sandxxxxxxxxxxxxxxxxxx
- Click “Sandbox Environment (Preview)”
Figure 2- Creating a sandbox environment in Microsoft Dynamics Business Central
The Sandbox Environment (Preview) window will open.
Figure 3 – The sandbox environment Preview in Microsoft Dynamics Business Central
- Click “Create” (to create the sandbox).
You are now in the Sandbox environment.
Figure 4 – The sandbox environment in Microsoft Dynamics Business Central
- Click “Assisted Setup.”
- Click “Set up Intelligent Cloud.”
- Accept the INTELLIGENT CLOUD SETUP and click “Next.”
- Select the Product: Click on the 3 dots to get a list of Products.
- Select “Dynamics 365 Business Central” and click “OK;” then click “Next.”
- Select the SQL Configuration from the drop down and select “SQL Server.
- Enter the SQL Connection String. There are 2 ways to do this:
- or Data Source= WinSrv1SQL2008;Initial Catalog=myDataBase;User Id=myUsername;Password=myPassword;
This example uses the first option:
Server=bcdev01NAVDEMO;Database= BC Saas Testing; UID=sa;PWD=xxx;
- Paste this string in SQL Connection String and click “Next”.
- ”Click “Download the Self Hosted Integration Runtime (SHIR).”
- Copy the Authentication Key and put it in your notepad.
- Self-Hosted Integration Runtime (SHIR) is downloaded. Run and Install the Setup.
Figure 5 – Self-hosted Integration Runtime Setup Wizard in Microsoft Dynamics Business Central
- When the Setup is installed, click “Finish.”
- Paste the Authentication key you copied into your notepad and click “Register.”
- Click “Finish.”
Integration Runtime has been successfully registered.
- Click “Launch Configuration Manager.”
Microsoft Integration Runtime Configuration Manager window will open to Test Connection.
- Click “Test.”
- Click “Next.”
The system will ask you which company you want to replicate.
- Select the company you want to replicate and click “Next.”
- Activate automatic schedule to replicate the Data by toggling the button. Click “Next.”
- Click “Finish” to replicate the company.
- Type in the first few letters of “Intelligent Cloud Management and click on it when it appears.
- Initialization of the company is completed. The company is replicated, but as now it’s blank.
- To set the system manually to replicate the data, click “Action,” then click “Run Replication Now.”
- Note the time you started the data replication. Time on Virtual Machine: 2:35 PM.
- The system will ask “Are you sure you want to trigger replication?” Click “Yes.”
- A box with the message, “Replication has been successfully triggered; you can track the status on the Management page” will appear. Click “OK.”
- On the Intelligent Cloud Management page, you can check the completion of the Data replication status.
Figure 6 – Intelligent Cloud Management page in Microsoft Dynamics Business Central
- Refresh the page in between to check the status.
Figure 7 – Refreshing the status of the Intelligent Cloud Management page in Microsoft Dynamics Business Central
The process ends @ 2:42 PM. The data is replicated.
- Click the tile “482 Tables Successful” on the right side of the page to find which table data was replicated.
Figure 8 – Table data successfully replicated in Microsoft Dynamics Business Central
- Click tile “12 Tables Failed” to find out which table data was not replicated.
Figure 9 – Table data NOT successfully replicated in Microsoft Dynamics Business Central
Why did the data in these 12 tables fail to replicate in this example? This example is an on-premises version of Business Central, so either a CU has been applied to the on-premises system before the update made it to the cloud tenant, or the cloud tenant has an update for which the corresponding CU has not been applied on premises.
If you have any questions about this process, contact ArcherPoint.
Read more “How To” blogs from ArcherPoint for practical advice on using Microsoft Dynamics Business Central or NAV. If you are interested in NAV/Business Central development, check out our collection of NAV Development Blogs.