When a Mikrotik CHR ( with the license ) is moved to another location on the hypervisor or to another hypervisor ( either manually or by automatically ) the new spun-up CHR will no longer retain the original license.
There are two possible work-arounds options to retain the license ( for a CHR move ).
#1; Create a virtual hypervisor on you primary hypervisor. Install your CHR on the virtual hypervisor.
With this #1 method - you move the virtual hypervisor and spin it up. Any virtaul machines ( CHR ) running on the virtual hypervisor will still be there.
The disadvantage of this is everything is slower.
#2; I am not certain but I think this might work: Instead of using a CHR , try using an x86 ROS virtual router.
The x86-ROS router uses a different license system from the CHR-ROS router. This might keep the license.
A disadvantage of of x86-ROS is that it wants to be a 32-Bit system when installed and a CHR-ROS system wants to be a 64-Bit system ( both are almost identical ).
EDIT - also - I don't think x86-ROS supports para-virtual NICs ( aka 10-Gig vmnic anything ) which might limit you to a 1-Gig E1000e Nic.
IMO - I have dozens of CHRs in my network and the Mikrotik license system on those CHRs is a pain-in-the-azz when you move a CHR and don't check the license after the move
It's a pretty bad day when you move your CHR that is pushing 8+ gig throughput to another location and the CHR license suddenly defaults to ---gone--- and your now spun-up CHR can only push 1-Meg maximum
North Idaho Tom Jones