After completing the previous points, you can begin to transfer data, services, and other intangible components of the IT infrastructure. At the final stage, the work of all systems in the cloud environment is tested and fixed in case errors arose during the migration process. It is important to understand whether the service turned out to be really functional.
Enterprise applications move to the cloud is a phased process that is a collaborative effort between the customer and the cloud provider. In most cases, the move is performed not from hardware, but from a working virtualization system, but, despite this, the process requires special preparation.
Analyzing the application migration best practices, we can single out several main stages. Each of them has its own nuances, and knowing these will help you to avoid making mistakes.
Choosing a transfer method
- Preparation phase. Preparation begins with an assessment of the existing infrastructure and a migration plan. You need to calculate the exact capacity of the resources that you plan to move to the cloud. Often they may be smaller than what is currently used. Working with your own physical or virtual infrastructure, you build capacity in order to anticipate future growth in business demands, as well as level out optimization flaws that are excluded in a cloud provider environment. Renting a virtual infrastructure allows you to add additional resources only when the need arises, therefore, if you calculated that a certain service requires 2 cores, 16GB of RAM and 500 GB of disk space, then only that much needs to be rented, and when you need to increase performance - adjust the specification.
- Transfer plan. It is necessary to create a table listing all the transferred services, specify the consumed resources for each, determine the transfer priority, and the criticality of the stop at the time of transfer. The usual practice is that first, non-critical services are transferred to the cloud, those on which you can test work with a cloud provider, and only after a while the rest of the infrastructure is migrated.
. Basically, the applications migration method depends on the source platform (the type of virtualization in the case of a private cloud migration or an iron server) and data activity (will it be an offline move or it is necessary to transfer hot data). The speed of the Internet channel between the source infrastructure and the cloud provider's data center also plays a role. If the speed or quality of the communication line is low, it makes sense to consider the option of migrating using an external NAS. After the services that will migrate to the cloud have been identified, their power consumption has been calculated, a migration plan has been drawn up taking into account the priority, the data transfer method has been selected and an agreement has been concluded with a cloud provider, you can start moving to the cloud. At this stage, the services are transferred to the provider's cloud. There are many options for how this can happen, each suitable for specific infrastructure.