Never V2V a domain controller. Converting a DC's disk risks USN rollback, and the only recovery from that is rebuilding the domain.
What I did instead when moving off Hyper-V was a leapfrog:
1. Move all 5 FSMO roles to DC2
2. Delete DC1, build fresh on Proxmox, promote, let AD replicate
3. Move the roles to the new DC1
4. Repeat for DC2
Run repadmin /showrepl after every step. Both DCs moved with no downtime.
The writeup covers the rest: Linux V2V, DFS ripped out for GPO drive maps, UniFi moved into an LXC, SCCM swapped for FOG, and the Wazuh/Cortex/TheHive/MISP stack. 4 standalone hosts plus a 6-node cluster. Hypervisor licensing: $0.
https://solomonneas.dev/blog/hyperv-to-proxmox-migration-guide
Solomon NeasI Migrated Our Entire Infrastructure from Hyper-V to Proxmox. Here's Everything I Learned.Domain controllers, file servers, network monitoring, imaging, WiFi controllers. All of it moved from Microsoft to open source. No downtime. No data loss. Here's the complete playbook.