Podría interesarle…

How to Migrate from VMware to Proxmox: A Practical Guide for Latin American Organizations

The complete migration methodology GLADiiUM uses for production VMware-to-Proxmox migrations — from initial assessment through cutover, with specific considerations for Latin American regulatory environments

Migrating a production VMware environment to Proxmox VE is not a button-click operation. It requires careful planning, lab validation, VM-by-VM analysis and a phased execution that minimizes production risk. Organizations that attempt to rush the migration — moving all VMs in a single weekend — consistently encounter problems. Organizations that follow a structured methodology consistently achieve successful migrations with acceptable downtime and no data loss.

This guide documents the methodology GLADiiUM Technology Partners uses for production VMware-to-Proxmox migrations across Latin America. It is based on real migrations executed for Honduran cooperativas, Costa Rican BPOs, Panamanian financial institutions and Miami healthcare organizations.

Phase 1: VMware Environment Assessment (Week 1-2)

The assessment phase produces the migration plan’s foundation. A rushed assessment produces an incomplete plan; a thorough assessment prevents surprises during execution.

VM Inventory and Classification

Export the complete VM inventory from vSphere, including: OS version, vCPU and RAM allocation, storage consumption, VMware Tools version, network adapter type (VMXNET3, E1000), and any PCI passthrough devices. Classify each VM by:

Complexity: Standard (Windows Server or Linux, no special hardware) vs Complex (PCI passthrough, VMware-specific customization)
Criticality: Non-production (dev/test), Production Secondary, Production Primary, Mission Critical
VMware feature dependency: Uses vSAN, vMotion only, uses NSX networking, etc.

Identify VMware-Specific Blockers

Some configurations cannot be migrated to Proxmox directly:

VMware Horizon VDI: Cannot run on Proxmox. Requires separate evaluation of Azure Virtual Desktop or Citrix as alternatives before migration.
NSX-T micro-segmentation: Proxmox uses standard Linux bridges and OVS for networking. NSX micro-segmentation policies must be replicated as Linux firewall rules or OVS flow rules in Proxmox.
vSAN RAID configurations: vSAN RAID 5/6 erasure coding requires 4+ nodes. If you use vSAN RAID 5/6, Ceph erasure coding is the Proxmox equivalent but requires careful capacity planning.

Phase 2: Proxmox Lab Validation (Week 2-3)

Before touching production, validate Proxmox on a single test node. Even repurposing one VMware host temporarily provides the validation needed.

Deploy Proxmox on Test Hardware

Install Proxmox VE on one available server (physical or a borrowed VMware host temporarily removed from the cluster). Configure networking to match your production VLAN structure. Install Proxmox Backup Server on a separate VM or dedicated hardware.

Migrate 3 Test VMs

Choose 3 representative VMs from your VMware inventory: one simple Linux VM, one Windows Server VM, and one application server. Migrate them using the process below and validate:

VM boots and applications function normally in Proxmox
Network connectivity works as expected
Storage I/O performance is acceptable (benchmark with fio or CrystalDiskMark)
PBS backup and restore works for all 3 VMs

Phase 3: VM Conversion — The Technical Process

VMware VMs are stored as VMDK disk images. Proxmox uses qcow2 or raw disk images for KVM VMs. Conversion happens via two main methods:

Method A: OVF/OVA Export + Import (Recommended for Smaller VMs)

In vSphere, right-click VM → Export OVF Template. Select OVA format.
Transfer OVA to Proxmox host via SCP or shared storage mount.
On Proxmox: qm importovf {VMID} {filename}.ova {storage}
Adjust VM configuration in Proxmox (change network adapter to VirtIO if original was VMXNET3, adjust disk bus to VirtIO-SCSI)
Install Proxmox QEMU guest agent (replaces VMware Tools)

Method B: VMDK Direct Conversion (For Large VMs)

Power off the VM in VMware
Copy VMDK files to Proxmox host storage
qemu-img convert -f vmdk -O qcow2 {source}.vmdk {output}.qcow2
Create a new VM in Proxmox and attach the converted disk
Boot and install guest agent

Phase 4: Production Migration Waves

With lab validation complete, execute production migration in 4 waves ordered by criticality:

Wave 1: Dev/Test VMs — lowest risk, maximum learning value
Wave 2: Production secondary systems (monitoring, secondary DNS, backup targets)
Wave 3: Production primary applications (ERP, CRM, email)
Wave 4: Mission-critical systems (core banking, payment processing)

Need Expert Help with Your VMware to Proxmox Migration?

GLADiiUM has executed production VMware-to-Proxmox migrations for Honduran banks, Costa Rican BPOs and Miami healthcare organizations. We can manage your migration from assessment through go-live.