Treat the migration as a platform redesign
A hypervisor migration is not only a VM conversion exercise. Inventory networking, storage, backup, clustering, monitoring, guest dependencies, recovery procedures and operational tooling before selecting the target design.
Map VMware concepts deliberately
HA, distributed switching, storage behaviour, snapshots and backup integration do not map one-for-one between platforms. Decide what business requirement each existing feature satisfies and design the Proxmox equivalent around that requirement.
Pilot representative workloads
Test Windows, Linux, high-I/O and application-sensitive workloads before bulk migration. Validate drivers, performance, backup, monitoring and recovery. A controlled migration wave with rollback criteria is safer than a single large conversion event.
AL Group can assess, design, implement and operate the underlying technology rather than stopping at advice.
Talk to an engineer