Types of Migrations
There are six application migration strategies in AWS:
If an organization is looking to scale its migration quickly to meet a business case, then rehosting is the best strategy.
A few cloud (or other) optimizations are implemented in order to achieve some tangible benefit, but the core architecture of the application isn’t changed.
When an application is moved to a different product, for example, moving a CMS to Drupal.
Re-imagining how the application is architected and developed, for example, migrating from a monolithic architecture to a serverless architecture to boost agility or improve business continuity.
An application is explicitly phased out when the capabilities it provides are not needed anymore or are now redundant.
When you’re not quite ready to migrate your application at this stage.
Also known as Revisit, this strategy is followed when you do not want/need to migrate your application to the cloud, as it would not make sense, or you do not have all the needed factors.