Maps every VMware vSphere dependency in Terraform, Packer and Ansible files (vsphere provider, vsphere-iso builder, community.vmware tasks) to the exact Proxmox VE replacement line. Runs entirely in your browser — nothing is uploaded.
Same engine as the VS Code extension, byte for byte.
The whole workspace in one dated Proxmox migration plan (each vSphere item mapped to its replacement) you keep, plus a team key with a CI gate that fails a build adding new vSphere use. $29 once.
One payment, one licence key for this tool. The key is shown right after payment.
One sysadmin day reading the repo by hand: 8 h x $47.66 = $381.28 (BLS OEWS 2025 median, network and computer systems administrators).
Buy the full version — $29Paste this code into your page. It runs in your visitor’s browser and stays up to date. Nothing your visitors type is stored.
For businesses: your name and logo instead of ours, and each visitor’s result + e-mail in your inbox (only when they tick consent) — Pro from $19/month. See Pro →
· ReadyStack
Real numbers from this tool, line by line.
15 vSphere lines sat in the sample edge-site repo, the kind of Terraform and Packer files an infrastructure engineer in the US or the EU keeps for a two-host branch cluster. Here is what Proxmox Migration Check printed for the bundled sample _fixtures/dirty.tf:
| Line | VMware vSphere line | Proxmox VE line |
|---|---|---|
| 5 | source = "hashicorp/vsphere" | source = "bpg/proxmox" |
| 11 | provider "vsphere" | provider "proxmox" { endpoint = "https://pve.example.com:8006/" } |
| 42 | resource "vsphere_virtual_machine" | resource "proxmox_virtual_environment_vm" |
| 27 | data "vsphere_datastore" | disk { datastore_id = "local-lvm" } |
| 66 | source "vsphere-iso" | source "proxmox-iso" |
| 61 | github.com/hashicorp/vsphere | github.com/hashicorp/proxmox |
That is 11 Terraform findings and 4 Packer findings. The clean version of the same file, _fixtures/clean.tf, gives 0.
Broadcom licenses VMware Cloud Foundation and vSphere Foundation per physical core, with a minimum of 16 cores for each CPU in every ESXi host. That rule is in Broadcom KB 313548, and its own example counts a host with 2 CPUs x 8 cores as 32 cores. An edge site with small CPUs pays for cores it does not have. In April 2025 a distributor memo also reported a 72-core minimum per order. Broadcom did not confirm it publicly, so the extension does not use that number.
Teams moving those sites to Proxmox VE, XCP-ng or Harvester usually start with the hardware. The code is the part that drags: every vsphere provider block, vsphere-iso builder and community.vmware task left in a repo is a pipeline that still talks to vCenter. Miss one and the site cannot be switched off.
grep -r vsphere finds the word. It does not tell you that data "vsphere_datacenter" has no Proxmox object at all and becomes node_name = "pve" on each VM, or that a vSphere clone from a template becomes clone { vm_id = ... } inside proxmox_virtual_environment_vm. A chatbot can guess these, but it cannot see your repository, and provider names change: the replacement lines here were read from the bpg/proxmox provider docs (version 0.116.0), the hashicorp/packer-plugin-proxmox README (v1.2.4) and the community.proxmox 2.1.0 module list.
27 rules: 12 for Terraform, 5 for Packer, 10 for Ansible. On the Ansible side it maps community.vmware.vmware_guest to community.proxmox.proxmox_kvm, vmware_guest_snapshot to community.proxmox.proxmox_snap, vmware_guest_disk to community.proxmox.proxmox_disk and the community.vmware.vmware_vm_inventory plugin to community.proxmox.proxmox. Credentials move too: vcenter_hostname becomes api_host, VSPHERE_SERVER becomes PROXMOX_VE_ENDPOINT.
It runs offline inside VS Code and on the free web page with the same engine. Nothing is uploaded.
The open file is free with no key: every vSphere line, its line number and the replacement. A licence key adds the whole workspace in one dated migration plan you keep, plus a team CI gate that fails a build that adds new vSphere use. Doing the same read by hand costs a sysadmin day: 8 hours x $47.66 = $381.28 at the BLS OEWS 2025 median for network and computer systems administrators.
It reads text line by line. It does not log in to vCenter, count your cores or estimate a Broadcom quote, and it does not follow module calls built from variables.
It reads Terraform, Packer and Ansible files and flags every VMware vSphere dependency: the hashicorp/vsphere provider, vsphere_virtual_machine resources, vsphere-iso builders and community.vmware modules. Next to each line it prints the Proxmox VE replacement, such as source = "bpg/proxmox" or community.proxmox.proxmox_kvm. The bundled sample _fixtures/dirty.tf gives 15 findings from 27 rules.
Infrastructure and DevOps engineers who run VMware vSphere at edge or branch sites and are moving them to Proxmox VE, XCP-ng or Harvester. It suits teams whose VMs, templates and images are defined in Terraform, Packer and Ansible, and who need to know which files still talk to vCenter before the next VMware renewal.
Grep finds the word vsphere but not what replaces it, and a chatbot cannot see your repository. This extension maps each line to a named Proxmox VE replacement read from the bpg/proxmox provider docs, the Packer proxmox plugin and community.proxmox 2.1.0. Broadcom KB 313548 bills at least 16 cores per CPU, so a 2 x 8-core host counts as 32 cores.
Free with no key: the open file, with every vSphere line, its line number and the exact Proxmox VE replacement line. A licence key, $29 once and one key per person or team seat, adds the whole workspace in one dated migration plan you keep, plus a CI gate that fails a build adding new vSphere use.
A US network and computer systems administrator earns a median $47.66 an hour (BLS OEWS 2025). One 8-hour day of reading Terraform, Packer and Ansible files for vSphere lines costs $381.28 in salary alone. The free tier covers the open file in seconds, and a $29 key covers the whole workspace in one pass.
No dated change is published. The rule this tool cites is Broadcom KB 313548: at least 16 physical cores per CPU in every ESXi host. In April 2025 a distributor memo reported a 72-core minimum per order, which Broadcom did not confirm publicly, so the extension does not use that number.
One question, answered by the person who built it. Your email only if you want the answer sent.