Cloud Adoption Framework

Cloud migration in the Cloud Adoption Framework

Introduction

Any enterprise-scale cloud adoption plan will include workloads that do not warrant significant investments in the creation of new business logic. Those workloads could be moved to the cloud through any number of approaches: lift and shift; lift and optimize; or modernize. Each of these approaches is considered a migration.

The below steps will help establish the iterative processes to assess, migrate, optimize, secure, and manage those workloads.

To prepare you for this phase of the cloud adoption lifecycle, Vigilant Technologies recommend the following:

The Migrate methodology and the steps above build on the following assumptions:

  • The methodology governing migration sprints fits within migration waves or releases, which are defined using the Plan, Ready, and Adopt methodologies. Within each migration sprint, a batch of workloads is migrated to the cloud.
  • Before migrating workloads, at least one landing zone has been identified, configured, and deployed to meet the needs of the near-term cloud adoption plan.
  • Migration is commonly associated with the terms lift and shiftor rehost. This methodology and the above steps are built on the belief that no datacenter and few workloads should be migrated using a pure rehost approach. While many workloads can be rehosted, customers more often choose to modernize specific assets within each workload. During this iterative process, the balance between speed and modernization is a common discussion point.

Migration effort

The effort required to migrate workloads generally falls into three types of effort (or phases) for each workload:

  1. Assess workloads,
  2. Deploy workloads,
  3. and release workloads.

In a standard two-week long iteration, an experienced migration team from Vigilant Technologies can complete this process for 2-5 workloads of low-medium complexity.

More complex workloads, such as SAP, may take several two-week iterations to complete all three phases of migration effort for a single workload. Experience and complexity both have a significant impact on timelines and migration velocity.

Migration waves and iterative change management

Migration iterations deliver technical value by migrating assets and workloads. A migration wave is the smallest collection of workloads that deliver tangible and measurable business value. Each iteration should result in a report outlining the technical efforts completed.

Next steps

The steps outlined above can help you develop an approach to improve processes within each migration sprint. The approach at Vigilant Technologies can ensure that common tools and approaches needed during your first migration wave will render a successful result.

Read more about Vigilant’s Azure Cloud Migration Services

Steven headshot

Author:
Stephen Clark

Principal – Technology Strategist, Vigilant Technologies

Azure SQL Migration Roadmap

Getting Started with Azure SQL

Introduction

Vigilant Technologies can help your team successfully move your SQL Server workloads to Azure SQL Database Managed Instance and save up to 85 percent with Azure Hybrid Benefit and reserved capacity pricing.

Our team of SME DBA’s can ensure that you get a fully managed database service with built-in security and performance monitoring for managing hundreds to thousands of databases at scale. For SQL Server workloads that use SQL Server Analysis Service, SQL Server Reporting Service, and other non-engine capabilities, Vigilant Technologies can ensure a successful shift and move to SQL Server in a VM to get extended security updates at no extra charge.

The Vigilant Approach…

The Vigilant Technologies SQL Migration Roadmap consists of five stages, each encompassing several important tasks required to complete a successful migration to Azure cloud services.

The purpose of each stage can be summarized below, but we will look at each stage in more depth in the sections to follow:

  1. Initiate and discover – Understand your database footprint and potential approaches to migration
  2. Assess – Assess the discovered workload requirements and any dependencies
  3. Plan – Plan and describe the workloads to be migrated, the tool to be used for migration and the target platform for the workload
  4. Transform – Transform and optimize any workloads not currently compatible with modern data platforms. Optimize workloads to take advantage of new features
  5. Migrate, validate and remediate – Perform migration, validate successful migration, and remediate applications where required



Other Options with Vigilant Technologies – SQL PaaS

Azure SQL Database is a fully managed service that is comparable to a traditional on-premises SQL Server deployment, but greatly enhances SQL performance and robustness by making performance levels and storage capacity easily upgradable as well as providing standard high availability.

Azure SQL Database delivers predictable performance at multiple service levels that provides dynamic scalability with no downtime, built-in intelligent optimization, global scalability and availability, and advanced security options — all with near-zero administration.

These capabilities allow you to focus on rapid app development and accelerating your time to market, rather than allocating precious time and resources to managing virtual machines and infrastructure. Azure SQL Database currently resides in 38 data centers around the world, with more data centers coming online regularly, enabling you to run your database in a data center near you.

Steven headshot

Author:
Stephen Clark

Principal – Technology Strategist, Vigilant Technologies