VMware to STACKIT migration

From a spreadsheet of VMs to a target draft

An inventory lists what exists. A migration needs to know what each machine becomes on the target and which values someone still has to choose. StackToIT connects the two.

1. Reads RVTools

   Import an RVTools export as .xlsx or as a CSV directory to establish the baseline of your virtual estate.

2. Plans the rehost

   VMs become servers with volumes and network interfaces. Disks are exported and converted to qcow2 or raw, and VMware Tools, vmxnet3 and PVSCSI drivers are replaced.

3. Surfaces missing values

   RVTools exports no subnet masks, so IP prefixes are set explicitly. Machine types, disk sizes and server addresses become named decisions.

Where your services go

Typical outcomes from the StackToIT knowledge base. The treatment of each resource depends on its configuration, and the report states the reason.

What it gives the business

1. A real option before renewal

   A licence renewal is a fixed date. A STACKIT target plan built from your own inventory gives you a second option before it arrives.

2. No agent in your estate

   StackToIT reads the export on your own computer. Nothing is installed in your VMware environment, and StackToIT needs no vCenter access.

3. A fast first baseline

   One export produces a STACKIT Terraform draft, target diagrams and an execution plan your team can work through.

RVTools describes infrastructure, not application behavior. Application dependencies and cutover timing come from your workload owners.