Migrating workloads to the AWS cloud can be a daunting task for most organizations taking their first steps into a hybrid or cloud-only future. This is where inQdo Cloud can help, providing planning, guidance and helping you perform the actual migration using a proven set of tools, best practices and most of all.. hands-on experience.

Choosing a migration strategy requires careful planning and most of all an intimate knowledge of the existing workloads and applications. The chosen migration method, complexity and existing documentation are all defining parameters to identify the effort and time frame for any workload migration
This is the main reason for our focus on performing migrations together with our customers and enabling them to make use of both our AWS prowess and access to a wealth of knowledge, gathered over the years and documented in our cloud migration methodology.

Then, before we start the actual process, we make sure all agreements between us as a migration partner and the customer are clear, with all involved teams focused on the same goals as to make the migration proceed with the least possible interruptions and uncertainties.

The inQdo Cloud migration process

Our cloud migration methodology is based on 4 individually defined phases, allowing for a clear overview of the steps needed to perform the actual migration successfully.

A successful migration however, does not end when the last workload has landed in the AWS cloud.
Continuous improvement and subsequent optimization phases make sure your journey to the cloud includes exploring the plethora of native services AWS has to offer, making you part of the cloud, not just being in the cloud.
Our migration methodology steps are

  1. Assessment (Migration Readiness Assessment)
  2. Readiness and Planning
  3. Migration
  4. Continuous Improvement and Optimizations

Together, these phases act as a clear, concise path to solid cloud migration processes.

1. Assessment (MRA)

This phase is where a structured in-depth analysis of all the existing workloads is performed. These workloads are identified and classified to prepare for migration.A series of detailed questions regarding the workload helps preparing migration by identifying all possible details and pitfalls.Assessment is based on the AWS Cloud Adoption Framework (CAF), published by AWS to help organizations identify and mitigate risks, prepare for a solid cloud platform, choose the right migration strategy and keep control of costs.The MRA assessment is the foundation for any next steps to be taken.

2. Readiness & Planning (MRP)

With the MRA as a starting platform, the Readiness & Planning phase will scrutinize each and every identified workload for the following best practices.

  • Project Control
    • Strategy (business driver)
    • Key stakeholders and team
    • Plan (Scope, Schedule, Resources)
    • Cost estimation
  • Portfolio discovery
  • Migration plan
  • Operating model
    • Security & compliance

3. Migration overview

When all preparations have been made and both the MRA and MRP have been completed, it’s time to start the actual migration process.The MRP will act as a guideline for the migration team to perform the individual workload migrations.During this phase these MRP plans will be translated to actual activities to be performed by the relevant team(s).

To make sure every phase of the migration is sufficiently monitored, inQdo Cloud has created its migration project approach, acting as an overall guideline for the migration process.

AWS Migration

Migration steps

After looking at the overall theoretical process and business impact of each migration workload, it’s time to go into detail and classify the actual method to be used for these individual workloads and applications. AWS has defined 6 common strategies, known as the “6 R’s” that are used to classify a migration workload and the involved steps.

Each of the 6 methods has it’s own pro’s and cons, as described in the overview below.

AWS Migration

Re-host

Also known as lift and shift migration, it is the most frequent migration method today. It involves taking non-cloud sources and moving them directly to the AWS cloud environment. This method is popular because it enables organizations to quickly implement migration. This makes this initially the most economical method, in any case, more integrations in the cloud will have to be made later.

In favor Re-host:

  • Rapid migration process
  • Quick wins for the organization
  • Can be highly automated and allows multiple large migrations

Against Re-host:

  • Subsequent rehosting activities can be expensive. It is important to plan within your budget to make these adjustments since not making them may cost money.
  • Not all workloads are optimized to function in a cloud environment. It might be difficult to implement important features like High Availability, scalability and implement fully managed AWS services for specific tasks.
  • Pitfall where the AWS cloud is used as simply an alternative remote datacenter, without making optimal use of all it has to offer.

Re-platform

This migration strategy is to make optimizations when migrating to the cloud by changing the application architecture. Cloud optimization is done to achieve a certain goal, such as reducing database management time or moving to a fully managed cloud.

In favor of Re-platform:

  • The benefit of being all cloud-native will immediately appear, like more availability and lower management costs.
  • Common application elements can easily be replaced by an AWS expert.

Against Re-platform:

  • Cloud migration may take more time than other approaches.
  • AWS knowledge is required, therefore collaboration with a partner / AWS will be especially important.

Re-purchase – Repurchase

A buyback is to move to a totally different product than what was used before. This is typically a move from a proprietary system to a SaaS platform. Ideally, organizations with workloads that can be easily upgraded to new versions will have a smoother implementation with this method.

In favor Re-purchase:

  • It is generally a lower cost option.
  • Free the IT team from common problems (patches, upgrades, etc).

Against Re-purchase:

  • Integrations and reconfigurations can be challenging if not planned and considered prior to migration.

Re-architect (Re-factor)

This option consists of focusing the application so that it is native to the cloud, with features such as autoscaling and high performance, this can only be achieved by rethinking the application so that it uses the cloud’s own architecture and services.

In favor of Re-architect:

  • Long-term cost reductions and high ROI as services are optimized and used optimally for the cloud.
  • AWS Management Services Allow Application to Take Advantage of Cloud Resilience.

Against Re-architect:

  • It is the longest method to complete a migration.
  • More resources are required for this approach.

Remove – Withdraw

It is so important to know which assets require more time and attention, just as it is important to determine when to withdraw assets that are no longer necessary. This increases savings in the business and helps IT teams determine who owns what.

In favor Remove:

  • Your organization will no longer use more money and resources supporting that asset.

Against Remove:

  • Some resources and time will have to be used to withdraw that asset and reorganize the team.

Retain – Retain

Many businesses may choose to retain some of their applications on their servers rather than fully migrate them to the cloud, this will lead to a hybrid approach. This should be done on a case-by-case basis, in cases where the team considers that certain applications must be in the current environment. Just migrate what makes sense to your business and continue to reevaluate regularly.

In favor of Retain:

  • There are no immediate changes that make costs predictable.

Against Retain:

  • Any issues that exist with the application will continue to be limited to the current environment without flexibility and forced to maintain the cost of the current environment.
iso 27001 & isae 3402 inQdo BV

simplifying cloud and integration together

inQdo Cloud B.V.

Coltbaan 1-19

3439 NG Nieuwegein

info@inqdo.com

+31 85 2011161

Verzend