Technical

Proposal

Proposal for On-Prem to Cloud Migration Services

Date: 1-AUG-2024

1. OCI-Threads Service Methodologies

TRUE CLOUD METHODOLOGY APPROACH FOR AZURE

1|Page

Private & Confidential – Copyright © 2024 OCI-Threads

Solutions
 Technical
Proposal

OCI-THREADS M IGRATION METHODOLOGY

OCI-THREADS team of migration experts always perform migration using standard 5 steps migration
methodology along with best possible migration tools and methods to ensure smooth and successful
workload migration.

 Phase 1: Initiation

 Phase 2: Discovery

 Phase 3: Planning

 Phase 4: Execution

 Phase 5: Closeout

2|Page

Private & Confidential – Copyright © 2024 OCI-Threads

Solutions
 Technical
Proposal

SDLC FOR CUSTOM PRODUCTS

SDLC is a process for developing software. In other words, SDLC is a structured way to create and
develop high-quality software. The process starts from planning but not finishes after the delivery of the
product. SDLC is not a linear project management framework. Instead, it becomes a cycle where
feedback is made, problems are solved through repetitions, or new features are acquired. SDLC process
consists of phases like planning, designing, implementing, testing, deploying, and maintenance. The
stages of the software development life cycle are which describe how to develop and maintain particular
software. Each phase has different processes and activities.

3|Page

Private & Confidential – Copyright © 2024 OCI-Threads

Solutions
 Technical
Proposal

2. Executive Summary & Requirements

Background

Customer is currently having on-premises infrastructure on Nutanix Acropolis and is looking to migrate
to Microsoft Azure.

Purpose

This proposal aims to present a comprehensive plan for migrating the existing on-premises
infrastructure that is running on Nutanix Acropolis AHV with 175+ VMs to Microsoft Azure Cloud. This
involved discovery, inventory, planning, execution and migration of scoped workload.

Current Environment Details

 Server Virtualization Platform - Nutanix Acropolis.

 Hypervisor - AHV
 Count of Physical Nutanix Nodes: 10
 Count of current Virtual machines: 175 VMs are in scope of the project which includes Cluster 1
- Dev, Test & Production applications, Cluster 2 - IBM Open Shift Containerized VMs.
 Storage appliances - None
 Backup appliances - 3 Commvault Hyperscale appliances total 50 TB Disk capacity
 Backup solutions - Commvault with inbuilt Disk & Tape based backup using Quantum Scalar 13
Tape Library
 Databases - MSSQL 2016, MSSQL 2019, 2022 Standard & Enterprise versions for Always On
Clusters) and My SQL Enterprise
 Monitoring and Support applications - Manage Engine
 Customer currently has M365 A5 Subscription only does not include Azure subscription renewed
annually OVA Contract.
 Customer is currently hosting DR services using P2PExpress link 30 MBPS for storage replication
using native Nutanix, collocated in a different Data Center Abudhabi.
 The network architecture includes Fortinet Perimeter Firewall, Barracuda LB for load balancing,
WAF & certificate offloading & Juniper Data Center Firewall

4|Page

Private & Confidential – Copyright © 2024 OCI-Threads

Solutions
 Technical
Proposal

 The existing On-Prem Data Center is to be connected to Azure Cloud using Express Route with
unlimited plan for upload and download.
 Network core infrastructure at the customer has been recently refreshed.
 Customer Network Access & Distribution link has back-to-back the capacity of 10 Gig, ADSL links
of 900 Mops bandwidth and a lease line of 100Mbps for publishing services is leveraged by RA.
 Customer has perimeter firewalls and core firewalls configured along with IDS/IPS functionality;
VPN solution leveraged by RA is also provided by Fortinet Firewall with 2 Factor tokens.
 Stateful packet inspection happens at the firewall level and endpoint security is managed
through Forti Client
 ZTNA, Trellix AV, PAM for Privilege Access mgmt.
 Patch management is performed leveraging Desktop Central from ManageEngine (For on Prem-
workloads & end points)
 Inventory details of all the VMs to be migrated to cloud platform are available as (to be shared
later stage). The file includes details application server, name of the application,
overprovisioning % for all resources (CPU, RAM & Disk platform details along with database
server details.

3. Proposed Migration Methodology & Approach

Migration Solution Literature

1. Nutanix AHV
Since the source environment is on Nutanix AHV we strongly recommend to utilize Nutanix Move for
infrastructure (VMs) and for databases native approach will be used. However, if need arises we may
recommend 3rd party migration tool such as Rackware etc.
Nutanix AHV to Microsoft Azure:
When migrating a VM from Nutanix AHV to Microsoft Azure, Nutanix Move provides the flexibility to
migrate workloads between on-prem and public cloud.
Nutanix Move Operations:
Nutanix Move helps in performing the following operations.
 Migrate powered on or powered off virtual machines (VMs).
 Pause and resume migration.
 Schedule data seeding.
 Manage VM migrations between multiple clusters from a single management interface.
 Sort and group VMs for easy migration.
 Monitor progress of migrations for individual VMs as well as migration plans.
 Cancel in-progress migration for individual VMs.

5|Page

Private & Confidential – Copyright © 2024 OCI-Threads

Solutions
 Technical
Proposal

 Migrate all AHV-certified guest operating systems.

2. Microsoft Azure Migrate & Azure Database Migration Service:

Azure Migrate is purpose-built for server migration. Azure Migrate provides a centralized hub for
discovery, assessment, and migration of on-premises machines to Azure.
Azure Database Migration Service is a tool that helps you simplify, guide, and automate your database
migration to Azure. Easily migrate your data, schema, and objects from multiple sources to the cloud at
scale.

3. Converting to Azure from Nutanix AHV using Commvault Backup

We can also consider third option for migrating AHV virtual machines to Azure using existing Commvault
Backup solution.
When restoring a virtual machine from a backup for Nutanix AHV, you can convert the VM to Azure
Resource Manager.
This feature can also be used to migrate workloads to the Azure cloud, or to recover VMs in Azure if the
Nutanix AHV deployment is unavailable.
You can perform VM conversions from streaming backups, from secondary copies, or from IntelliSnap
backup copies. You cannot perform a conversion from a Snap copy.
Migration Considerations for Nutanix Move

6|Page

Private & Confidential – Copyright © 2024 OCI-Threads

Solutions
 Technical
Proposal

You must consider the supported guest operating systems, requirements, recommendations,
unsupported features, and limitations provided in this section before starting the migration process.
Supported Guest Operating Systems for BIOS (AHV to Azure)
Move supports some common operating systems. Unless otherwise specified, Nutanix has qualified the
following 64- bit guest operating system versions.
Fully Supported
 Windows Server 2012 R2 DC, 2016, 2019, and 2022
 CentOS 6.8 to 6.10, 7.0 to 7.7, and 8.0 to 8.3
 RHEL 6.8 to 6.10, 7.0 to 7.7, and 8.0 to 8.5
 Ubuntu 14.0.4, 16.0.4, 18.0.4, and 20.0.4
 SLES 11 SP4, 12, and 15
 OEL 7.5 to 8.4

Supported Operating Systems for UEFI-Enabled VMs (AHV to Azure)

 Move supports the following operating systems for UEFI-enabled VMs.

Migration Considerations for Microsoft Azure Migrate

Microsoft Azure considers Nutanix VMs as physical machines and use Azure Migrate Service to migrate
to replicate and migrate the VMs from Nutanix to Azure. We will also use the azure migrate agent-based
approach for this scenario.

Downtime & Cut over

As we know the infrastructure underneath is different on both source and target, a small downtime is
incurred during cutover from any of the preceding sources to targets.
Actual downtime and cut-over plans will be submitted upon completion of Part 1: Discovery, Inventory &
Planning.

4. Scope of Work

OCI-THREADS with their expertise in Multi-Clouds domain analyzed requirement and derived following
scope of work.

7|Page

Private & Confidential – Copyright © 2024 OCI-Threads

Solutions
 Technical
Proposal

In-Scope

Project Assumptions

 Customer yet to share with final list of VMs / inventory for migration apart from the information
that is already shared. Additional information will help in smooth migration.
 Customer to provide us with priorities per workloads, to consider it in the migration plan. Since
customer requested migration plan to be per workload priority.
 Customer has valid vendor Support ID/CSI/contracts to download binaries/patches/opening SR.
 Environment is not having any critical Application/Database/Configuration issues before
Migration.
 All Change requests should be frozen during Implementation and Migration.
 Enable connections for user pc’s on ssh/rdm for all needed environments within scope.
 Customer to provide jump PC required tools, Credentials, VPN access for Techvisions team to
work on migration project.

Customer Responsibility:

The customer will provide the necessary Azure cloud tenancy that will help OCI-THREADS initiate design,
deploy, implement and migrate workload. This includes all compute, storage, network resources, and
any additional Azure services required to deploy and operate the OEM Applications.

The customer is responsible for all costs associated with the Azure cloud infrastructure, 3 rd party
migration tool (if any required during project) and any other licenses that will be essential for project
completion.

Technologies & Tools

 Microsoft Azure Cloud

 Nutanix Move
 Commvault Backup Solution
 Fortinet Firewall,
 Barracuda WAF & LB
 Manage Engine
 Native Database Migration
 3rd Party Migration tool (as per need basis)

Part I: Discovery, Inventory & Planning

8|Page

Private & Confidential – Copyright © 2024 OCI-Threads

Solutions
 Technical
Proposal

 Assess, recommend, validate and ensure enough service limits for 1 x OCI tenancy is available
for provisioning required network and Compute Instances to host and migrate scoped
environment.

Part II: Target Cloud Microsoft Azure Readiness

Azure Readiness, setup and configuration

 Assess, recommend, validate and ensure enough service limits for 1 x OCI tenancy is available
for provisioning required network and Compute Instances to host and migrate scoped
environment.
 Prepare required compute instances as per inventory list.
 Prepare and configure cloud firewall.
 Establish connectivity between OCI and existing Datacenter for preparing workload migration.
 Implementing the environment specific backup strategy post the provisioning & migration of the
scoped environment.

Implementation & Configuration of Essential IT components in Azure, Security & Backup

 Implementation and configuration of WAF/Load Balancer.

 Design & Deployment of SIEM solution in OCI.
 Discovery of Targets and configuration of targets to collect logs.
 Store logs as per requirement in SIEM solution.
 Configure Patch Management using OS Management Agent for all OCI native compute
instances.
 Setup Backup of 30 VMs with 3 months retention

Active Directory Implementation & Configuration

 Implement Active Directory in OCI Landscape.
 Prepare two Compute Instances with Active Directory role.
 Prepare four Compute Instances with Active Directory Federation Services role.
 Active Directory Setup & Configurations.
 Link On-premises Active Directory with OCI Active Directory.
 Active Directory user creation.

9|Page

Private & Confidential – Copyright © 2024 OCI-Threads

Solutions
 Technical
Proposal

 Apply best practices in AD systems.

Part III: Migration of Workload

OCI-THREADS team of migration experts will perform migration using standard 5 steps migration
methodology along with best possible migration tools and native methods to ensure smooth and
successful workload migration.

Having worked with some of the largest Migration projects across the globe, we understand that
deciding which approach to implement will require a lot of information gathering from all sides of a
business.

VM Migration Scope

 Migration of 178 VMs as per provided List

 Ensuring workload is bundled and wave-wise migration
 Non-Production VMs Migration
 Production VMs Migration

OpenShift Migration

 Set Up Azure Environment

o Azure Infrastructure: Set up the Azure environment including the creation of VMs,
configuration of Virtual Networks, and setup of storage accounts.
o OpenShift Installation: Install OpenShift on Azure either through Azure Red Hat
OpenShift (ARO) which offers a managed service or set up a self-managed OpenShift
using IPI or UPI methods as per your requirements.
 Data and Application Preparation
 Container Images: Ensure all container images are available in Azure Container Registry or
another accessible registry.

10 | P a g
e

Private & Confidential – Copyright © 2024 OCI-Threads

Solutions
 Technical
Proposal

 Data Backup: Use tools like Velero to back up existing Kubernetes resources and persistent
volumes.

Migration Execution

Migrate Infrastructure
 Network Configuration: Establish VPN or ExpressRoute between Source and Azure for secure
data transfer during migration.
 Security Policies: Reconfigure RBAC, security contexts, and network policies in the Azure
environment.

Migrate Data
 Persistent Data Transfer: Migrate data using Velero or Azure Site Recovery for a seamless
transfer of persistent volumes and stateful applications.
 Database Migration: Utilize database migration services like Azure Database Migration Service
to ensure a smooth transition.

Migrate Applications
 Deploy Applications: Redeploy applications using updated configurations that target the new
Azure resources.
 Testing: Extensively test the applications to ensure they are functioning correctly in the new
environment.

11 | P a g
e

Private & Confidential – Copyright © 2024 OCI-Threads

Solutions
 Technical
Proposal

Migration Execution:

Cutover and Validation

DNS and Traffic Management

 DNS Update: Update DNS records to point to the Azure Load Balancers or Application Gateways.
 Validation: Conduct final testing to ensure all systems are operational and meet performance
criteria.

Monitoring and Optimization

 Performance Monitoring: Implement monitoring using Azure Monitor and Azure Insights to
track performance and resource usage.
 Optimization: Continuously optimize resources based on performance data to manage costs and
efficiency.

Documentation and Training

 Update Documentation: Revise operational and technical documentation to reflect the new
Azure environment.
 Training: Provide necessary training and support to teams to adapt to the new Azure
infrastructure.

Recommended Tools and Services

12 | P a g
e

Private & Confidential – Copyright © 2024 OCI-Threads

Solutions
 Technical
Proposal

 Migration Tools: Velero for Kubernetes backups, Azure Site Recovery for VMs, Azure Database
Migration Service for databases.
 Azure Services: Azure Kubernetes Service (AKS), Azure Virtual Network, Azure VPN Gateway,
Azure Load Balancer, Azure Container Registry.

Database Migration Scope

 Pre-Migration Activities
 Migration Activities
 Post-Migration Activities

Migration Close-out phase

Part IV: Transition Plan for Operational Support

 Establish a Transition Team:

o Form a dedicated transition team comprising key stakeholders from both Vendor side
and customer side.
o Assign roles and responsibilities for each team member.
 Stakeholder Communication:
o Develop a communication plan to keep stakeholders informed throughout the
transition.
o Schedule regular updates and review meetings.

13 | P a g
e

Private & Confidential – Copyright © 2024 OCI-Threads

Solutions
 Technical
Proposal

 Staff Training & Knowledge Transfer:

o Conduct comprehensive training programs for existing Infrastructure staff on Microsoft
Azure and scoped tools and technologies.
o Facilitate knowledge transfer sessions.
o Document best practices and operational procedures.
 Optimization:
o Conduct a post-transition review to identify areas for improvement.
 Handover Operations:
o Hand-over operations to existing customer staff.

Out of Scope
• Azure tenancy subscription
• Application License is to be purchased separately from Oracle.
• Any application, database upgrade.
• Organization change management would be the responsibility of the business.
• Any other Custom Module will be considered out of scope.

5. Project Deliverables, Resources & Timeline

# Document Name
1 Design Documents of Cloud Architecture (HLD & LLD)
2 Data collection templates for inventory gathering
3 Solution Design and Configuration Documentation
Project Management and Implementation
4
Documentation
5 Project Plan (with detailed schedule)
6 Project Status Reports
7 Risk Log
8 Issue Log
9 Action Log
10 User Acceptance Certificate
Test Scenarios, Test Scripts (both capability and failure
11
testing), Test Reports

14 | P a g
e

Private & Confidential – Copyright © 2024 OCI-Threads

Solutions
 Technical
Proposal

Data Migration Strategy (e.g. Extract & Migration design,

12 Mapping rules and Testing approach including a smooth
data migration offboarding solution)
13 Data Migration Templates
14 Integration Strategy & Design Documentation
15 System Integration Test Scripts, Cases and Report
16 Training Plan, Sessions and User Guides/ Videos
17 Project Closure Sign Off
18 Hand-over and Transition Support Post Go-Live

Resource Summary (Implementation & Migration)

S.No. Title Qty Mode

1 Project Manager 1 Offshore
2 Cloud Solution Architect 1 Offshore
3 Nutanix Specialist 1 Offshore
4 Sr. Cloud Engineer 1 Offshore
5 Network Security Specialist 1 Offshore
6 Backup Specialist 1 Offshore
7 Migration Specialist 1 Offshore
8 Redhat OpenShift / DevOps Specialist 2 Offshore
9 Sr. Systems Engineer 1 Offshore

*Resources will be made available as per need basis and their responsibilities during the project.

Resource Summary (Support)

S.No. Title Qty Mode

1 Account Manager 1 Offshore
2 Sr. Cloud Engineer 1 Offshore
3 Network Security Specialist 1 Offshore
4 Backup Specialist 1 Offshore
5 Redhat OpenShift Specialist 1 Offshore
6 Sr. Systems Engineer 1 Offshore

15 | P a g
e

Private & Confidential – Copyright © 2024 OCI-Threads

Solutions
 Technical
Proposal

Project Timelines:

OCI-THREADS Team proposes 10-12 Months for the entire project.

A detailed real-time Project Plan based on mutually agreed start date, customer readiness and other
factors will be prepared, discussed, and agreed with client project manager once the project is
awarded to us.

Timelines to be decided and calculated once final inventory is received.

Important Notes:

 Entire migration will follow iterative/pilot approach before actual production environment
migration.
 Workload priorities will be followed as aper workloads priority which shall be shared by the
customer and will be agreed upon.

Milestone # Phase Description Duration

1 Project initiation and planning 15 Days
2 Implementation & Readiness of MS Azure Cloud Tenancy & 1 Month
Landing Zone
3 IT Essentials, Backup Solution & Security tools Implementation 15 Days
4 Migration of non-production Workload 8 Months
5 Migration of Production Workload
6 Hypercare 2 Months
TOTAL 12 Month(s)

*Timelines are estimated strictly only from technical execution perspective, any customer specific
change processes approvals, procedures delay will not be considered in above timelines.

16 | P a g
e

Private & Confidential – Copyright © 2024 OCI-Threads

Solutions
 Technical
Proposal

6. Project Commercials:

Cost for Professional Services

S.NO. ITEM DESCRIPTION AMOUNT (USD)

1 Professional Services:
 Assessment, Discovery, Planning
 Migration of VMs to Azure
 Database Migration
2 Two-months Hyper Care
Sub-Total
Taxes
Total Cost
*Taxes as applicable

Cost for Managed Support Services

S.NO. ITEM DESCRIPTION AMOUNT (USD)

1 Managed Support Services – 1 Year Support
Sub-Total
Taxes
Total Cost
* Taxes as applicable

17 | P a g
e

Private & Confidential – Copyright © 2024 OCI-Threads

Solutions
 Technical
Proposal

7. General Terms & Conditions

1. This proposal is valid for 30 days from the date of submission.

2. Taxes as applicable.
3. Any delays are not part of the project timeline, and payments.
4. The service provider has no responsibility over the project delay due to requirements not
fulfilled or any delay caused by service seeker and so any extra days apart from quoted days will
be charged separately.
5. Payment Terms: Net 30 Days from date of invoice and invoice will be as per below schedule

a. Professional Services: As per milestone

Milestones Deliverable Payment %

Contract Signing Contract Signing 10%
Solution Design & Project Plan HLD & LLD, Project Plan Submission 20%
Implementation Completion of Azure Cloud Setup 20%
Migration Migration of Non-Production Workload 20%
Migration Migration of Production Workload 10%
Go-Live Completion of Transaction in Production 10%
Project Completion Completion of Hyper Care 10%

b. Managed Support Services: Quarterly Advance

18 | P a g
e

Private & Confidential – Copyright © 2024 OCI-Threads

Solutions