Migration for Dynamics GP

One cannot underestimate the complexity of data migration for Dynamics GP. That is why we work with you to come up with a data migration strategy, one that encompasses all of the systems that house the data to be moved, the time and manpower available, and any regulations affecting your industry that will impact the historical data to be migrated. To do this we will talk to department managers to understand how they classify their data and use their input on how to best standardize the data across all departments for the migration and for use in the new system.

After the decision is made on which data will be moved, our team will work with you to extract it, clean or standardize it, and then load it into the new system. After the load, we will guide you in testing and verifying that the data is correct.

Using SQL Server Integration Services (SSIS), data can be reformatted to fit the requirements of Dynamics GP before the data is migrated. And with SSIS and Microsoft’s PSTL, which is included with GP, data cleanup can be done after the migration. For example, PSTL allows the renaming of customers/vendors, the joining of customers/vendors, and the merging of duplicates. Our team also writes pre and post routines to enhance the PSTL data cleanup.

The transformation of data can include taking the existing data and running routines against it to create and append new data to be brought back into Dynamics GP. For example, one of our clients who services equipment for over 7000 customers needed a way to get the distance from the nearest service depot added to the customer record in GP. Our team used a Google maps API and a routine they programmed to pull the street address from the customer record, then used the mapping software to calculate the distance between the customer and the nearest service depot, and enter the result back into GP for each customer record. This data enhancement has ensured and automated the proper billing for technician travel charges for our client.