Data migration can be a tricky task. With Microsoft Dynamics 365, several tools were developed to assist with converting or migrating data. The integration tools available are The Import Wizard, Dynamics to CRM Adaptor, Scribe, and SSIS packages. The steps involved in migrating to Microsoft Dynamics 365 include the identification of the required data to be migrated, map the existing data to the Microsoft Dynamics 365 data, create the integration, test the integration, verify the data, and then perform the product migration. After each step is completed, a check point should be established to evaluate how the migration is proceeding.
Define the Data Required
The first element required for any data migration is to define what data you will be migrating. This definition will include the source of the data, the tables being used, and the data type being migrated.
The source of the data is the existing Accounting system. This will include a definition of how to connect to the data to export or link to it in order to extract the required data to push the data into Microsoft Dynamics 365. Within the source, the tables being used will define which table from the existing Accounting system contains the required data that needs to be extracted. This may be limited based on the data fields and how they match to Microsoft Dynamics 365.
With the data source and available data for extraction defined, the destination tables in Microsoft Dynamics 365 can be analyzed to match the existing Accounting system with Microsoft Dynamics 365 data fields. This is also the point that decisions are made to migrate specifics such as open vs. history transactions or to address any data processing requirement changes and data corruption issues. Exception should be identified and addressed to minimize lost or corrupt data being transferred.
Map the Existing Data with the New Microsoft Dynamics 365 Data
Once the base elements for the data are defined, then the mapping of the data can occur to match the data from the existing Accounting system with Microsoft Dynamics 365. This will result in a data mapping document. The data mapping should define what data points or key fields are required for each data type being mapped, such as Vendor IDs, GL Accounts, Customer IDs, etc. It should also include the additional fields desired based on what data is available in the existing system. The mapping document should not only contain the fields to be mapped but will also include the data formatting requirements and any scripting required for translation of the data. The mapping document of the fields can be used to create an integration for the migration of data using the various tools available.
Create Integration
When the mapping document is complete and the source is defined to map to the Microsoft Dynamics 365 data, you are ready to create the Integration to get the data from the source and into the Destination. The data from the source file can be extracted in several different ways such as an ODBC connection, SQL connection, Text file export, Excel workbooks, etc. The integration tool will determine how the source data is connected and migrated to the destination of Microsoft Dynamics 365. The various integration tools available are: The Import Wizard, Dynamics to CRM Adaptor, Scribe, and SSIS packages.
Perform a Test Migration
With the integration completed according to the mapping document, a test migration can be conducted. The test migration is used to confirm the migrated data meets the requirements laid out in the previous sections of this blog. The test migration should include either a complete file or a large sample of the data records being migrated to Microsoft Dynamics 365 to ensure the data is migrated successfully.
Verify the Test Migration
Two independent verifications should take place. The first verification should be conducted by the individual integrating the data. This verification checks to confirm the correct number of records are integrated, the format of the records is correct, all the appropriate fields have the correct data, and the translation scripts are working as intended. The first verification is used as a self-audit prior to passing the data to the end user for a full validation.
Once the initial verification has been completed satisfactorily, the end user verification and validation can take place. This validation step compares the data in the existing system with the data now migrated to Microsoft Dynamics 365. The end user verification should check each field data and format to confirm the data meets the initial data requirements defined.
Perform Production Migration
With the integration completed according to the mapping document, a test migration conducted, and the test migration validated, the actual production migration can take place to pull the data from the current Accounting system to Microsoft Dynamics 365. The production migration should include all of the data records being migrated to Microsoft Dynamics 365 to ensure the data is migrated successfully.
Verify the Production Migration
Similar to the test migration, two independent verifications should once again take place. As before, the first verification should be conducted by the individual integrating the data. This verification again checks to confirm the correct number of records are integrated, the format of the records is correct, all the appropriate fields have the correct data, and the translation scripts are still working as intended. The first verification is used as a self-audit prior to passing the data to the end user for a final full validation.
Once the initial verification has been satisfactory completed, the end user verification and validation can take place for the second time. This validation step compares the data in the existing system with the data now migrated to Microsoft Dynamics 365. The end user verification should check each field data and format to confirm the data meets the initial data requirements defined as they did in the test migration.
To summarize, data migrations can be difficult to complete correctly and oftentimes has missing or corrupt data. With Microsoft Dynamics 365, several tools were developed to assist with this migration to make this task simpler. The integration tools available are The Import Wizard, Dynamics to CRM Adaptor, Scribe, and SSIS packages. The steps involved in migrating to Microsoft Dynamics 365 include the identification of the required data to be migrated, map the existing data to the Microsoft Dynamics 365 data, create the integration, test the integration, verify the data, and then perform the production migration.
The team at KTL Solutions has years of experience in data migration. We’ve developed a system to help our clients migrate to Microsoft Dynamics 365 that minimizes data corruption. If you’re looking for a team to help you with data migration, give us a call today. We’re here to help.
