Framework for Migrating Applications to Cloud Computing Environment

1. A cloud migration system implemented via a back-end application computer server, comprising: (a) an enterprise application data store that contains electronic records associated with a set of enterprise applications, each electronic record including an electronic record identifier and at least one enterprise application parameter; (b) a data repository storing a catalogue of cloud computing patterns including integration patterns or templates, deployment patterns, and development, security, and operations patterns, wherein the patterns further include Multi-Page Applications (“MPA”), Event Driven Architectures (“EDA”), and microservices; (c) the back-end application computer server, coupled to the enterprise application data store and the data repository, including: a computer processor, and a computer memory, coupled to the computer processor, storing instructions that, when executed by the computer processor, cause the back-end application computer server to: (i) retrieve information from the enterprise application data store, (ii) based on at least one enterprise application parameter, automatically create a move group representing a subset of the enterprise applications in the enterprise application data store, and (iii) for each enterprise application in the move group: identify whether an appropriate cloud computing pattern exists in the catalogue of cloud computing patterns, if an appropriate cloud computing pattern is identified, use the identified cloud computing pattern to automatically create a reference implementation of the enterprise application in a cloud computing environment, and if no appropriate cloud computing pattern is identified, initiate a pattern on-boarding process to add a new cloud computing pattern to the catalogue stored in the data repository; and (d) a communication port coupled to the back-end application computer server to support an interactive graphical administrator interface display via a distributed communication network.

2. The system of claim 1, wherein the back-end application computer server, after migration of the move group is initiated, further begins to migrate a subsequent move group, and at least one appropriate cloud computing pattern for an enterprise application in the subsequent move group was added via a prior on-boarding process.

3. The system of claim 1, wherein the automatically created move group is further based on: (i) technology stacks, (ii) enterprise lines of business, and (iii) application dependencies.

4. The system of claim 1, wherein the set of enterprise applications in the enterprise application data store are associated with at least one of: (i) on-premises applications, and (ii) legacy applications.

5. The system of claim 1, wherein patterns are associated with at least one of: (i) composite patterns, and (ii) reference implementations.

6. The system of claim 5, wherein patterns are associated with at least one of: (i) an integration type, (ii) an inbound flow direction, and (iii) an outbound flow direction.

7. The system of claim 5, wherein patterns are associated with at least one of: (i) foundational patterns, (ii) primitive patterns, and (ii) guardrail patterns.

8. The system of claim 1, wherein the data repository includes version control.

9. A computerized cloud migration method implemented via a back-end application computer server, comprising: retrieving, by a computer processor of the back-end application computer server, information from an enterprise application data store that contains electronic records associated with a set of enterprise applications, each electronic record including an electronic record identifier and at least one enterprise application parameter; based on at least one enterprise application parameter, automatically creating a move group representing a subset of the enterprise applications in the enterprise application data store; and for each enterprise application in the move group: identifying whether an appropriate cloud computing pattern exists in a catalogue of cloud computing patterns stored at a data repository, wherein the catalogue includes integration patterns or templates, deployment patterns, and development, security, and operations patterns, and further wherein the patterns include, Multi-Page Applications (“MPA”), Event Driven Architectures (“EDA”), and microservices, if an appropriate cloud computing pattern is identified, using the identified cloud computing pattern to automatically create a reference implementation of the enterprise application in a cloud computing environment, and if no appropriate cloud computing pattern is identified, initiating a pattern on-boarding process to add a new cloud computing pattern to the catalogue stored in the data repository.

10. The method of claim 9, wherein the back-end application computer server, after migration of the move group is initiated, further begins to migrate a subsequent move group, and at least one appropriate cloud computing pattern for an enterprise application in the subsequent move group was added via a prior on-boarding process.

11. The method of claim 9, wherein the automatically created move group is further based on: (i) technology stacks, (ii) enterprise lines of business, and (iii) application dependencies.

12. The method of claim 9, wherein the set of enterprise applications in the enterprise application data store are associated with at least one of: (i) on-premises applications, and (ii) legacy applications.

13. A non-transitory, computer-readable medium storing instructions, that, when executed by a processor, cause the processor to perform a cloud migration method implemented via a back-end application computer server, the method comprising: retrieving, by a computer processor of the back-end application computer server, information from an enterprise application data store that contains electronic records associated with a set of enterprise applications, each electronic record including an electronic record identifier and at least one enterprise application parameter; based on at least one enterprise application parameter, automatically creating a move group representing a subset of the enterprise applications in the enterprise application data store; and for each enterprise application in the move group: identifying whether an appropriate cloud computing pattern exists in a catalogue of cloud computing patterns stored at a data repository, wherein the catalogue includes integration patterns or templates, deployment patterns, and development, security, and operations patterns, and further wherein the patterns include Multi-Page Applications (“MPA”), Event Driven Architectures (“EDA”), and microservices, if an appropriate cloud computing pattern is identified, using the identified cloud computing pattern to automatically create a reference implementation of the enterprise application in a cloud computing environment, and if no appropriate cloud computing pattern is identified, initiating a pattern on-boarding process to add a new cloud computing pattern to the catalogue stored in the data repository.

14. The medium of claim 13, wherein the back-end application computer server, after migration of the move group is initiated, further begins to migrate a subsequent move group, and at least one appropriate cloud computing pattern for an enterprise application in the subsequent move group was added via a prior on-boarding process.

15. The medium of claim 13, wherein patterns are associated with at least one of: (i) composite patterns, and (ii) reference implementations.

16. The medium of claim 15, wherein patterns are associated with at least one of: (i) an integration type, (ii) an inbound flow direction, and (iii) an outbound flow direction.

17. The medium of claim 15, wherein patterns are associated with at least one of: (i) foundational patterns, (ii) primitive patterns, and (ii) guardrail patterns.

18. The medium of claim 13, wherein the data repository includes version control.