Hello All!  Today I want to walk thru what the migration from GP to BC looks like, and some things to look for to ensure you are getting the results of a successful migration.

Here are some basic steps for you to follow to get started:

https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migration-tool

Although they are a great way to start, I wanted to offer some details that can help as you work thru the migration process.

It is recommended to setup and run the migration from a company other than what you are attempting to migrate.  i.e. Use Cronus

  1. Navigate to Assisted Setup

a. Use the Set-up Cloud Migration wizard to connect BC to the GP SQL database.

You will need your SQL string for the GP database that would look something like this:

Server=DESEREEK0801;DATABASE=DYNAMICS;User Id=sa;Password=yourpassword;

                        *It is very touchy, don’t leave out any semi-colons or equal signs.

b. You will be creating an IR connection during this process – keep track of this!

- If you are using an existing IR, this sometimes can be tricky but doable. You want to ensure the IR is running and located on the machine that holds the SQL database.  If you want to test your SQL string, find the Microsoft Integration Runtime Configuration Manager, then navigate to the Diagnostics menu option.  From here you can test to see if the connection is good:

 

c. At this point, BE PATIENT WHILE BC CREATES THE COMPANY. (this can take up to an hour)

 

  1. Navigate to the Cloud Migration Management page in a company other than the company you are attempting to migrate. (i.e. Cronus)
    1. Have all users out of the GP database and the BC database.
    2. From the ribbon, choose Run Migration Now.
    3. Once this is triggered, give the process time to complete! This could take up to a day which is based on the size of your GP database and performance of the tool.

 

  1. Check if the migration was successful. This is done in 2 separate locations.

a. Sign into the company you migrated in BC, and then to the Table Migration Success Rate Review the date and time you recently ran the migration for, look for a status of ‘Completed’.

-Review the Fact Boxes to the right of the page and insure you have no errors. I encourage you to drill into each of those boxes to be sure.

-If you have errors, these need to be addressed in GP before the migration can be run again. Please see my previous blog to assist with common data issues that can been seen in GP. https://community.dynamics.com/business/b/d365businesscentral/posts/dynamics-gp-to-dynamics-business-central-migration-tips

 b. Navigate to the Data Migration Overview

-This page will show you what came from GP, (Migrated Number) and what made it to BC (Total Number). If you do not see 100%-Completed for all modules that are currently being migrated, the process was either not successful and you should see errors, or the migration is still running. 

-If you have errors, these need to be addressed in GP before the migration can be run again. Please see my previous blog to assist with common data issues that can been seen in GP.

https://community.dynamics.com/business/b/d365businesscentral/posts/dynamics-gp-to-dynamics-business-central-migration-tips

There are 3 types of migrations and those are defined here:

  • Diagnostic - this will not copy data to Saas from the SQL database.  This is for a test run only.
  • Full - this option will do a full replication to Saas.
  • Normal - this option would take into account the SQL change tracking version of the previous migration, and try to migrate only the delta, the changes that happened after that tracking version.

Once you have successfully migrated your GP data over to Business Central, you are ready to being your implementation of BC.  The last step of the migration process is to break the connection between GP and BC.  To do so, navigate to the Table Migration Success Rate page, and from the Actions menu, select Disable Cloud Migration. This will allow you to change permissions for all users linked to the ‘intelligent cloud’ Permission Set, to their appropriate BC Permission Set.   This can be done from the Actions menu.  It is not recommended to do any setup or data entry in your BC database until you are done migrating from GP.  Each time the tool is run, it is deleting tables and migrating the information again, so you could lose the data you have entered. 

Once you have changed the permission set, simply choose the disclaimer on the bottom of the page, then ‘Disable Cloud Migration’ from the menu.  This is a vital action to perform as if you don’t, and someone attempts to run the migration again in error, it will wipe out anything that has been set up in BC after the GP data has been migrated over.  Each time you run the migration, we are wiping the outstanding documents for vendors and customers, your GL account numbers and inventory items from the BC database.  These will be written again during the migration from GP.  For example, if you enter a vendor, in BC that does not exist in GP, that vendor will be removed during the migration so it’s important to not enter new information until you are happy with what as been brought over from GP.

The Migration tool was designed to get a great starting with information from GP.  There will be some instances where the tool is not the way to go.  Things to keep in mind, when you migrate, it is all or nothing.  For example, if you have a highly complex GL structure that will need to be addressed before you start in Business Central, the tool will not be a good fit for you.  Currently, we migrate the GL, Vendors, Customers and Inventory items.  If you are unable to process the GL, then you will not be able to do Vendors, Customers and Inventory items.  There is no way to choose which modules you would like to include. 

I hope this information helps get you thru the GP migration process.  Happy migrating!