Are you planning a VMware-to-Azure migration using a tool combination that’s going to require manual intervention on every VM?

I remember being on a project where I migrated over 100 physical and virtual VMware servers to Azure using Azure Migrate Tool. At a separate engagement I migrated more than 20 VMware servers to Oracle Cloud Infrastructure using RackWare CloudMotion. Two different tools, two different cloud targets; the assessment phase looks almost identical.

Azure Migrate does the dependency mapping and sizing recommendation work well. What it doesn’t do automatically: resolve VMware VM snapshots that are stacked multiple levels deep before replication starts, or handle VMs running on hardware versions too old for the agentless replication approach. Those need to be caught in the assessment, not discovered mid-replication.

The 15 Group Policy Objects I created at STERIS Corporation to facilitate file share migration to Azure Files is a related example; Azure Migrate moves the compute, but the file share migration and GPO configuration has to run in parallel as a separate workstream.

What VMware assessment gaps have surfaced in your Azure Migrate planning?

#AzureMigrate #VMware #Migration