SIC keys survive a migrate_server and a migrate export/import (limited to the same version). All your firewalls will trust the management VM, though if you change IPs, they won't know about the new IP until you push policy to them. If the new VM has a different hostname from the old physical server, you will need to reset the certificate authority, which also wipes the SIC keys.
The licenses also survive this process. You will need a new open server management license to run the system legally. The existing management license should work well enough to let you test your migration process while waiting for an open server management license to be purchased. For example, you can set up a Windows VM with SmartConsole and confirm all your rules and objects made it to the management VM.
If you use central licensing for your firewalls, that will be tied to the management server's IP. If that IP changes, you will need to generate all of your firewall licenses again and reattach them. This can be disruptive. Not always, but can be. You can avoid any chance of disruption by generating a 30-day eval license for each firewall and applying it locally.
If you keep the same IP address and hostname, it's a really simple process.