Migration Strategies

  1. Re-Host: Simply move assets without change, e.g. on-prem MySQL to EC2. (Lift and Shift)
  2. Re-Platform: Move assets but change underlying platform, e.g. Migrate MySQL DB to RDS MySQL. (Lift and Reshape)
  3. Re-Purchase: Abandon existing and purchase new. (Drop and Shop)
  4. Rearchitect: Redesign application in a cloud-native manner, e.g. create Serverless version of legacy application.
  5. Retire: Get rid of applications which are not needed.
  6. Retain: Do nothing - decide to reevaluate at a future date.

Cloud Adoption Framework


The Open Group Architectural Framework

  • Approach for designing, planning, implementing and governing enterprise IT architectures
  • Started development in 1995
  • De-facto standard in Enterprise Architecture practice
  • Favored EA framework for most Fortune 500 companies

Cloud Adoption Phases

  • Project Running projects to get familiar and experience the benefits from the cloud.
  • Foundation Build foundation to scale the cloud adoption. Creating landing zone (pre-configured, secure, multi-account AWS environment), Cloud Center of Excellence (CCoE), operations model, as well as assuring security and compliance readiness.
  • Migration Migrate existing applications including mission-critical applications or entire data centers to the cloud as you scale your adoption across a growing portion of your IT portfolio.
  • Reinvention Focus on reinvention by taking advantage of the flexibility and capabilities of AWS to transform your business by speeding time to market and increasing the attention on innovation.

Holistic Approach to Cloud Adoption Framework:

  • Business
    • Creation of a strong business case for Cloud Adoption
    • Business goals are in harmony with cloud objectives
    • Ability to measure benefits (ROI - Return on Investment, TCO - Total cost of Ownership)
  • People
    • Evaluate organizational roles and structures, new skills and process needs and identify gaps
    • Incentives and Career Management aligned with evolving roles
    • Training options appropriate for learning styles
  • Governance
    • Portfolio Management geared for determining cloud eligibility and priority
    • Program and Project management more agile projects
    • Align KPI’s with newly enabled business capabilities
  • Platform
    • Resource provisioning can happen with standardization
    • Architecture patterns adjusted to leverage cloud-native
    • New application development skills and processes enable more agility
  • Security
    • Identiy and Access Management modes change
    • Logging and Audit capabilities evolve
    • Shared Responsibility Model removes and adds some facets
  • Operations
    • Service monitoring has potential to be highly automated
    • Performance management can scale as needed
    • Business continuity and disaster recovery takes on new methods in the cloud

Hybrid Architectures

  • Using cloud resources along with on-prem resources
  • First step as a pilot for cloud migrations
  • VMWare - infrastructure can be extended to the cloud
  • Integrations should be loosely coupled


  • Storage Gateway
    • Creates a bridge between on-prem and AWS
    • Seamless to end users
    • Common first step due to low risk and appealing economics
  • Middleware
    • Great way to leverage cloud services
    • Loosely coupled, canonical-based
    • Example: Can publish messages from Corporate Landscape to SQS to be consumed on the other side by a worker
  • VMWare vCenter Plugin
    • Allows transparent migration of VMs to and from AWS
    • VMWare Cloud furthers this concept with more public-native features

Migration Tools

  • Storage Migration
    • AWS Storage Gateway
    • AWS Snowball
  • Server Migration Service
    • Automates migration of on-prem VMWare vSphere or Microsoft Hyper-V/SCVMM virtual machines to AWS
    • Replaces VMs to AWS, sync volumes and create periodic AMIs
    • Minimizes cutover downtime by syncing VMs incrementally
    • Supports Windows and Linux VMs only (like AWS)
    • The Server Migration Connector is downloaded as a virtual appliance into your on-prem vSphere or Hyper-V setup
  • Database Migration Service (DMS)
    • Along with Schema Conversion Tool (SCT) helps customers migrate databases to AWS RDS or EC2-based databases
    • SCT can copy database for homogenous migrations and covert schemas for heterogenous migrations
    • DMS is used for smaller, simpler conversions and also supports MongoDB and DynamoDB
    • SCT used for larger, more complex datasets like data warehouses
    • DMS has replication function for on-prem to AWS or to Snowball or S3
  • Application Discovery Service
    • Gathers information about on-prem data centers to help in cloud migration planning
    • Collects configs, usage and behavior data from your servers to help in estimating TCO of running on AWS
    • Can run agent-less (VMWare Environment) or agent-based (non-VMWare Environment)
    • Only supports those OSes that AWS Supports
  • AWS Migration Hub

Network Migrations and Cutovers

  • Ensure there’s no overlap between VPC and on-prem
  • Most migrations start with VPN to AWS
  • With higher usage, you may choose AWS Direct Connect and keep the VPN as backup
  • Transition from VPN to Direct Connect can be done seamlessly using BGP (BGP weighing or static routes)

Amazon Snow Family

  • Evolution of AWS Import/Export process
  • Move massive amount of data to and from AWS
  • Data is encrypted at rest
  • Data is encrypted at transit


  • AWS Import/Export Ship an external hard drive to AWS. AWS plugs it in and copies the data to S3.
  • AWS Snowball NAS in a box AWS ships to you. You can copy over 80TB of data and ship it back. Data will be available on S3.
  • AWS Snowball Edge Similar to Snowball with some computing power, like Lambda and Clustering.
  • AWS Snowmobile Shipping container full of storage (up to 100PB) and a truck to transport it.