Hyper-V and virtualization

Hyper-V to Azure Local migration

The most common road to Azure Local starts on a Hyper-V cluster. We move the virtual machines with replication, a test and a planned cutover for each group.

What we do

Scope of the work

  • Check source hosts, guest operating systems and virtual machine settings against the requirements
  • Deploy the migration appliances and start replication
  • Run test migrations and validate with application owners
  • Cut over in waves, each with a rollback step
  • Retire the old hosts once the owners sign off
What you receive
  • Virtual machines running as Azure Local VMs managed from Azure
  • A cutover record per wave
  • A decommission checklist for the old cluster

Billed at $150.00 per hour. Ask Keith for an estimate.

Field notes

What we check first.

Prerequisites are strict

Guest operating system, disk type and boot settings all have requirements. We list the machines that need attention up front.

Reuse the hardware

If the old hosts qualify for Azure Local, the migration needs swing capacity while they are rebuilt. We plan it.

Same network, same address

Machines keep their addresses when the VLANs are extended to the new cluster. We test one before the first wave.

How an engagement runs

Four steps, written down.

I
Scope

A call with Keith

You describe the goal, the estate and the deadline. Keith turns it into a written scope with an hour estimate at the hourly rate.

II
Design

A written design by Gus

Gus reviews the environment and gives you a written design with each decision and its reason.

III
Build

Hands-on implementation

Gus implements in your tenant and your racks, remotely or on site, with every change logged as it is made.

IV
Hand over

Documents and a named contact

You receive the as-built record and the runbooks. Keith stays on as your account and project manager.

Questions

Asked before every engagement.

How much downtime per virtual machine?

A short outage at cutover for the final sync and the start on the new cluster. The length depends on change rate; we measure it in the test migration.

Can we fall back?

Yes. The source machine is kept, powered off, until the owner signs off.

What does the consulting cost?

Consulting is billed at $150.00 per hour. Keith sends a written hour estimate after the scoping call, and work starts when you approve it.

Rate and contacts

One rate. Two people.

Consulting is billed at $150.00 per hour. Keith runs sales, project management and your account. Gus does the architecture, the design and the implementation.

Hourly rate
$150.00

per consulting hour, for every consulting service

Sales, project management and account management

Keith

keith@apexvanguard.ai
Architecture, design and implementation

Gus

gus@gusitllc.com

Independent practice, not affiliated with Microsoft. Azure Local consulting is part of the infrastructure consulting practice of Gus IT LLC, an independent firm. It is not affiliated with, endorsed by or sponsored by Microsoft Corporation, Dell Technologies, Fortinet or any other vendor named on this site. Microsoft, Azure, Azure Local, Azure Stack HCI, Azure Arc, AKS, Azure Virtual Desktop, Hyper-V and Windows Server are trademarks of Microsoft Corporation. Dell, PowerEdge, PowerSwitch and iDRAC are trademarks of Dell Inc. Microsoft Entra, Active Directory, SQL Server, FSLogix and BitLocker are also trademarks of Microsoft Corporation. Fortinet and FortiGate are trademarks of Fortinet, Inc. VMware and vSphere are trademarks of Broadcom Inc. Kubernetes is a registered trademark of The Linux Foundation. PostgreSQL is a trademark of the PostgreSQL Community Association of Canada. Linux is the registered trademark of Linus Torvalds. All other marks belong to their respective owners and are used for description only. Product capabilities follow each vendor's documentation and change between releases; we confirm the current state during scoping.