Migration from VMware to Hyper V for old p2v server

I'm posting here because it seems like this might be the best place to get help because it isn't really a VMware issue or a Hyper V issue.

An old physical server that contains a database and LOB app was converted to VMware using the VMware converter a number of years ago. It was running 2008 R2 on an old HPE ML350. The conversion went great and for the last few years we just turn on the VM whenever accounting decides they need something from this server and then turn it right back off again.

This company is now getting rid of VMware and switching to Hyper V. The VM's are being migrated using Veeam quick migration and it has been working fine. We attempted to migrate this server and the first issue was an error related to secure boot. We disabled secure boot and now the server wants to run a repair and never completes the boot process. Just sits on Windows is loading files for endless hours.

We are having a debate about how to proceed. There is an argument for just keeping Esxi on this one server with this VM and turning the entire thing on when needed and then off again. The extra boot time to load Esxi and then the VM is minimal. Accounting says they will likely need access to it for three more years.

I would like to get this VM working in Hyper V to keep the environment as clean as possible and not worry about booting the hardware to get Esxi running each time we need it for five minutes. Any suggestions for how to get this thing to boot in Hyper V that will be as easy as just leaving it in Esxi? Asking that question makes me think I should have posted this in Shittysysadmin lol