Granted Patent B2

US 10,242,010 · App. 15/081,347 · Granted Mar 26, 2019

Abstract

Claims (71)

1. A migration utility framework comprising processing circuitry configured to:

generate a migration map to map a plurality of data files from a source enterprise application to a target enterprise application, wherein at least one data file of the plurality of data files in the source enterprise application includes two or more versions, wherein each version of the at least one data file comprises metadata;

validate the migration map, wherein the processing circuitry configured to validate the migration map comprises processing circuitry configured to:

determine if target enterprise application requirements are met for file types of the plurality of data files and metadata of the plurality of data files;

generate a hash value of a validated map in response to validating the migration map, wherein the hash value represents only the validated map; and

migrate the plurality of data files from the source enterprise application to the target enterprise application according to the validated map, wherein migrating the plurality of data files from the source enterprise application to the target enterprise application comprises migrating each of the two or more versions of the at least one data file to the target enterprise application, wherein in response to the processing circuitry determining that metadata of the two or more versions of the at least one data file provides an indication that a version of the at least one data file is missing, the processing circuitry is configured to:

generate a replacement version of the at least one data file for the missing version of the at least one data file, wherein metadata for the missing version is generated based on the metadata from the two or more versions of the at least one data file.

2. The migration utility framework of claim 1 , wherein the processing circuitry is further configured to:

generate a reconciliation report of the plurality of data files migrated from the source enterprise application to the target enterprise application; and

confirm that each file of the plurality of data files from the source enterprise application exists in the target enterprise application.

3. The migration utility framework of claim 2 , wherein the processing circuitry is further configured to:

determine if any file in the target enterprise application is duplicated within the target enterprise application; and

provide an alert in response to a file in the target enterprise application having a duplicate in the target enterprise application.

4. The migration utility framework of claim 1 , wherein the processing circuitry is further configured to:

compare a hash value of a migration map against the hash value of the validated map;

perform the migration of the plurality of data files of the migration map in response to the hash value of the migration map corresponding to the hash value of the validated map; and

provide an alert in response to the hash value of the migration map failing to correspond to the hash value of the validated map.

5. The migration utility framework of claim 1 , wherein the processing circuitry is further configured to check for data type exceptions between the source enterprise application and the target enterprise application.

6. The migration utility framework of claim 1 , wherein the migration map is generated based upon a mapping template, where the mapping template enables a client computing device to link metadata elements from the source enterprise application to metadata elements in the target enterprise application.

7. The migration utility framework of claim 1 , wherein the processing circuitry is further configured to:

perform a mock migration of the plurality of data files from the source enterprise application according to the validated map;

generate a report of successes and failures of the mock migration; and

provide the report for user review.

8. A method comprising:

generating a migration map to map a plurality of data files from a source enterprise application to a target enterprise application, wherein at least one data file of the plurality of data files in the source enterprise application includes two or more versions, wherein each version of the at least one data file comprises metadata;

validating the migration map, wherein validating the migration map comprises:

determining if target enterprise application requirements are met for file types of the plurality of data files and metadata of the plurality of data files;

generating a hash value of a validated map in response to validating the migration map, wherein the hash value represents only the validated map;

migrating the plurality of data files from the source enterprise application to the target enterprise application according to the validated map, wherein migrating the plurality of data files from the source enterprise application to the target enterprise application comprises migrating each of the two or more versions of the at least one data file to the target enterprise application; and

in response to determining that metadata of the two or more versions of the at least one data file provides an indication that a version of the at least one data file is missing, generating a replacement version of the at least one data file for the missing version of the at least one data file, wherein metadata for the missing version is generated based on the metadata from the two or more versions of the at least one data file.

9. The method of claim 8 , further comprising:

generating a reconciliation report of the plurality of data files migrated from the source enterprise application to the target enterprise application; and

confirming that each file of the plurality of data files from the source enterprise application exists in the target enterprise application.

10. The method of claim 9 , further comprising:

determining if any file in the target enterprise application is duplicated within the target enterprise application; and

providing an alert in response to a file in the target enterprise application having a duplicate in the target enterprise application.

11. The method of claim 8 , further comprising:

performing a mock migration of the plurality of data files from the source enterprise application according to the validated map;

generating a report of successes and failures of the mock migration; and

providing the report for user review.

12. The method of claim 8 , further comprising:

comparing a hash value of a migration map against the hash value of the validated map;

performing the migration of the plurality of data files of the migration map in response to the hash value of the migration map corresponding to the hash value of the validated map; and

providing an alert in response to the hash value of the migration map failing to correspond to the hash value of the validated map.

13. The method of claim 8 further comprising:

checking for data type exceptions between the source enterprise application and the target enterprise application.

14. The method of claim 8 , wherein the migration map is generated based upon a mapping template, where the mapping template enables a client computing device to link metadata elements from the source enterprise application to metadata elements in the target enterprise application.

15. A computer program product comprising a non-transitory computer readable storage medium having program code portions stored therein, the program code portions configured, upon execution, to:

generate a migration map to map a plurality of data files from a source enterprise application to a target enterprise application, wherein at least one data file of the plurality of data files in the source enterprise application includes two or more versions, wherein each version of the at least one data file comprises metadata;

validate the migration map, wherein the program code portions to validate the migration map comprise program code portions configured to:

determine if target enterprise application requirements are met for file types of the plurality of data files and metadata of the plurality of data files;

generate a hash value of a validated map in response to validating the migration map, wherein the hash value represents only the validated map; and

migrate the plurality of data files from the source enterprise application to the target enterprise application according to the validated map, wherein the program code instructions configured to migrate the plurality of data files from the source enterprise application to the target enterprise application are configured to migrate each of the two or more versions of the at least one data file to the target enterprise application, wherein in response to the program code portions determining that metadata of the two or more versions of the at least one data file provides an indication that a version of the at least one data file is missing;

the computer program product further comprising program code instructions configured to:

generate a replacement version of the at least one data file for the missing version of the at least one data file, wherein metadata for the missing version is generated based on the metadata from the two or more versions of the at least one data file.

16. The computer program product of claim 15 , further comprising program code portions configured to:

generate a reconciliation report of the plurality of data files migrated from the source enterprise application to the target enterprise application; and

confirm that each file of the plurality of data files from the source enterprise application exists in the target enterprise application.

17. The computer program product of claim 16 , further comprising program code portions configured to:

determine if any file in the target enterprise application is duplicated within the target enterprise application; and

provide an alert in response to a file in the target enterprise application having a duplicate in the target enterprise application.

18. The computer program product of claim 15 , further comprising program code portions configured to:

perform a mock migration of the plurality of data files from the source enterprise application according to the validated map;

generate a report of successes and failures of the mock migration; and

provide the report for user review.

19. The computer program product of claim of claim 15 , further comprising program code portions configured to:

compare a hash value of a migration map against the hash value of the validated map;

perform the migration of the plurality of data files of the migration map in response to the hash value of the migration map corresponding to the hash value of the validated map; and

provide an alert in response to the hash value of the migration map failing to correspond to the hash value of the validated map.

20. The computer program product of claim of claim 15 , wherein the program code instructions are further configured to:

check for data type exceptions between the source enterprise application and the target enterprise application.

Assignments (17)