The challenge with the backup and convert from VMware to HyperV Just Work(tm)-ing might at the least be state files that are stored on the appliance. Fundamentally they are the same appliance, same software, but once you boot an appliance it "remembers" things like MAC addresses and interfaces, they'd require manual effort from the support team to clear. It might work if you have a reliable VMware to VHD converter (I've seen a few and they do work relatively well), but there's no way to know whether it'll work completely - I'd be prepared for it to not work and to have to start from scratch.
There exists a KB about migrating from hardware to virtual, and the process should theoretically be similar. The downside is that this does not migrate the database (by design), that requires manual effort.
In the end, for the VMware to HyperV case, the support team put up a KB that recommends standing up a brand new LEM VHD and involving manual effort/assistance from the support team to finish the migration job: Migrate LEM from VMware to Hyper-V
Thanks for the respons! I will contact the support team.
You can try the 5-nine V2V converter.
I use the 5-nine manager (free edition) for my Hyper-V too.
This tool is free and can convert from VMWare to HYPER-V
Hope this helps!