A method, framework, and computer program product are provided in order to migrate data files associated with a source enterprise application to a target enterprise application. A migration utility framework including processing circuitry may be configured to: generate a migration map to map a plurality of data files from a source enterprise application to a target enterprise application; validate the migration map, where the processing circuitry to validate the migration map includes processing circuitry to determine if target enterprise application requirements are met for both 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 map, where 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.
Drawings
Claims20
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.
4 more elements
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.
4 more elements
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.
1 Apr 2037Estimated · howhide20 years from earliest known nonprovisional domestic filing plus recorded patent term adjustment, including 372 days of adjustment. Maintenance-fee lapses, terminal disclaimers and statutory extensions have not been checked. The continuity chain may be incomplete; this is not an enforceability determination.
About 10 years 5 months of term left · ends 1 Apr 2037 (estimated)
Priority25 Mar 2016
Published28 Sep 2017
Granted26 Mar 2019
Today12 Oct 2026
Term ends1 Apr 2037
Priority25 Mar 2016
Granted26 Mar 2019
Term ends1 Apr 2037
Application filedUS 15/081,347
Assigned to Mckesson Corporationassignment of assignor's interest
Assigned to Mckesson Financial Holdingsassignment of assignor's interest
Assigned to Mckesson Financial Holdings Unlimited Companychange of name
Assigned to Mckesson Corporationassignment of assignor's interest
PublishedUS 2017/0277698 A1
Assigned to Allscripts Healthcare, LLCassignment of assignor's interest
Assigned to Allscripts Healthcare US, LPassignment of assignor's interest
Assigned to Allscripts Software, LLCassignment of assignor's interest
Assigned to Pf2 Mckesson Technologies Inc.assignment of assignor's interest
Assigned to Pf2 Eis LLCassignment of assignor's interest
Assigned to Jpmorgan Chase Bank, N.A., AS Administrative Agentsecurity interest
Assigned to Hyland Software, Inc.assignment of assignor's interest
Assigned to Credit Suisseintellectual property security agreement supplement (second lien)
Assigned to Credit Suisseintellectual property security agreement supplement (first lien)
GrantedUS 10,242,010 B2
Assigned to Allscripts Software, LLCrelease and reassignment of certain patents recorded at r/f 044096/0852
Assigned to Golub Capital Markets LLC, AS Collateral Agentsecurity interest
Assigned to Hyland Software, Inc.release of security interest recorded at reel/frame 045870/0395
Assigned to Hyland Software, Inc.release of security interest recorded at reel/frame 045870/0389
TodayWithin its term
Term endsEstimated, includes 372 days of adjustment
Description8,796 words
Summary1,696 words
#An example embodiment of the present invention relates generally to the migration of data between enterprise applications, and more particularly, to more reliably and efficiently migrating data between enterprise applications using a conversion plan including validated migration maps.
#Enterprise applications may be used in numerous environments to store various types of data. These enterprise applications may routinely be updated and revised, or replaced with alternative enterprise applications. However, data from an original enterprise application may be needed in the updated, revised, or replacement enterprise application in order to maintain continuity between enterprise applications. Further, most businesses employing enterprise applications cannot afford substantial downtime to accomplish a transition between an original enterprise application and a new enterprise application. Further, it is often imperative that no data is lost in a transition between enterprise applications. When the volume of data files is high, particularly when those data files may have numerous versions and associated metadata, the transition between enterprise applications is complex, time consuming, and error prone.
#A method, framework, and computer program product are provided according to an example embodiment in order to migrate data files associated with a source enterprise application to a target enterprise application. Embodiments may include a migration utility framework including 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; validate the migration map, where the processing circuitry to validate the migration map includes processing circuitry to determine if target enterprise application requirements are met for both 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 map, where 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.
Brief description of the drawings4 figures
#Having thus described certain example embodiments of the invention in general terms, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:
#FIG. 1 is a schematic representation of a system for implementing a migration utility in accordance with an example embodiment of the present invention;
#FIG. 2 is a block diagram of a computing device that may be specifically configured in accordance with an example embodiment of the present invention;
Detailed description6,956 words
#The present invention now will be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments of the inventions are shown. Indeed, these inventions may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like numbers refer to like elements throughout.
#A method, framework, and computer program product are provided in accordance with an example embodiment in order to migrate data files from a source enterprise application to a target enterprise application by establishing a conversion plan, generating a migration map for mapping a plurality of data files from the source enterprise application to the target enterprise application, validating the migration map, and using that validated migration map to perform the migration. Enterprise applications are typically applications used by businesses to manage various activities. Enterprise applications can include financial management or accounting applications, computer-aided-design (CAD) applications, health information management systems, docketing systems, email applications, file-sharing applications, or virtually any application in which data is stored. As businesses develop and as software development progresses, new enterprise applications become available as do revised versions of existing enterprise applications. However, businesses or individuals may be reluctant to change their enterprise applications or upgrade their enterprise applications due to the complexities involved in managing such a change or upgrade, including the potential to lose or damage large amounts of information related to their existing enterprise application. As described herein, embodiments of the present invention provide a reliable and repeatable mechanism to migrate data files from a source enterprise application to a target enterprise application.
#Migrating data files from one enterprise application to another involves numerous difficulties and barriers that must be overcome for the successful migration of the data files. Barriers may include the need for specialized development resources to develop software to execute the migration, and the migration process may take a substantial amount of time to complete, when sufficient downtime on many enterprise applications is unavailable or unacceptable. Further, a substantial portion of the time to complete the migration of data files may be spent troubleshooting or triaging lost or improperly transferred data. Implementation resources may lack sufficient expertise to complete the migration successfully due to the specialized nature of many migration projects. Each of these barriers may further dissuade businesses from updating or changing their enterprise applications, which may leave some companies technologically behind the state of the art, including related potential security issues, but may also reduce the likelihood of a customer purchasing and implementing a new enterprise application.