# US 10,311,030 B1 · Method and system for implementing an automated migration tool > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,311,030 B1 - Document ID: US10311030B1 - Status: Granted - Kind: B1 - Application number: 15/587,849 - Filed: 2017-05-05 - Granted: 2019-06-04 - Earliest claimed: 2017-05-05 - Assignees: JPMorgan Chase Bank, N.A. - Applicants: JPMorgan Chase Bank, N.A. - Inventors: James Todd Barnes; Farhan Ahmed; Chandrasekharan N. Mana; Ajay K. Gupta; Rahul D. Kulkarni - Web page: https://patentgrep.com/patent/US10311030B1 ## CPC - G06F 16/214: {Database migration support} - G06F 8/71: Version control (security arrangements therefor G06F21/57); Configuration management - G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract An embodiment of the present invention is directed to an automated migration tool. A system that implements an automated migration tool comprises: a memory component; an interactive web-based interface; and an application server configured to perform the steps comprising: submit a request for source code migration from a source platform to a target platform; schedule the migration for a time period; upon approval of the migration for the time period, identify the source code and associated metadata for migration, wherein the metadata comprises history data, code reviews and permissions; execute the migration of the source code and the associated metadata from the source platform to the target platform; and perform validation of the migration. ## Claims ### Claim 1 An automated computer implemented method that implements an automated migration tool comprises the steps of: submitting, via interactive web-based interface, a request for source code migration from a source platform to a target platform; scheduling, via an application server, the migration for a time period; upon approval of the migration for the time period, identifying the source code and associated metadata for migration, wherein the metadata comprises history data, code reviews, underlying links, configuration data, and permissions; executing, via the application server, the migration of the source code and the associated metadata from the source platform to the target platform; and performing, via the application server, validation of the migration, the validation comprises validating the permissions to ensure project level permissions have been migrated and validating pull request logs and audit logs. ### Claim 2 (depends on 1) The method of claim 1, wherein the source platform comprises a Git repository management system. ### Claim 3 (depends on 1) The method of claim 1, wherein the target platform represents a web-based hosted service for source code and development projects. ### Claim 4 (depends on 1) The method of claim 1, wherein the interactive web-based interface is configured to receive a source project key and a target project key. ### Claim 5 (depends on 1) The method of claim 1, wherein the migration further comprises migration of associated repositories from the source platform to the target platform. ### Claim 6 (depends on 1) The method of claim 1, further comprising the step of: generating a log of actions that are performed during the migration. ### Claim 7 (depends on 1) The method of claim 1, wherein the metadata further comprises underlying links and hyperlinks associated with the source code. ### Claim 8 (depends on 1) The method of claim 1, wherein the interactive web-based interface comprises a migrate project and repository step and a migrate permissions step. ### Claim 9 (depends on 1) The method of claim 1, wherein the migration tool supports HTTPs communication. ### Claim 10 (depends on 1) The method of claim 1, wherein the validation comprises multiple validations of the source code. ### Claim 11 An automated computer implemented system that implements an automated migration tool of source code and associated metadata, the system comprises: a memory component; an interactive web-based interface that receives one or more user inputs; and an application server comprising a processor, coupled to the memory component and the interactive interface, the application server configured to perform the steps comprising: submit a request for source code migration from a source platform to a target platform; schedule the migration for a time period; upon approval of the migration for the time period, identify the source code and associated metadata for migration, wherein the metadata comprises history data, code reviews, underlying links, configuration data, and permissions; execute the migration of the source code and the associated metadata from the source platform to the target platform; and perform validation of the migration, the validation comprises validating the permissions to ensure project level permissions have been migrated and validating pull request logs and audit logs. ### Claim 12 (depends on 11) The system of claim 11, wherein the source platform represents a Git repository management system. ### Claim 13 (depends on 11) The system of claim 11, wherein the target platform represents a web-based hosted service for source code and development projects. ### Claim 14 (depends on 11) The system of claim 11, wherein the interactive web-based interface is configured to receive a source project key and a target project key. ### Claim 15 (depends on 11) The system of claim 11, wherein the migration further comprises migration of associated repositories from the source platform to the target platform. ### Claim 16 (depends on 11) The system of claim 11, wherein the processor is further configured to perform: generate a log of actions that are performed during the migration. ### Claim 17 (depends on 11) The system of claim 11, wherein the metadata further comprises underlying links and hyperlinks associated with the source code. ### Claim 18 (depends on 11) The system of claim 11, wherein the interactive web-based interface comprises a migrate project and repository step and a migrate permissions step. ### Claim 19 (depends on 11) The system of claim 11, wherein the system supports HTTPs communication. ### Claim 20 (depends on 11) The system of claim 11, wherein the validation comprises multiple validations of the source code.