Technical Tip: Migrating a FortiADC VM License from VMware to Nutanix (KVM)
Description
This article describes the expected licensing behavior and the correct migration procedure when moving a FortiADC-VM instance from VMware ESXi to Nutanix AHV (KVM).
FortiADC-VM licenses are bound to a hypervisor-derived virtual hardware identifier. Because VMware ESXi and KVM generate different virtual hardware signatures, a license issued for a VMware-based FortiADC-VM cannot be directly applied to a Nutanix-based instance.
As a result, after migration, the newly deployed FortiADC-VM will initially operate under a trial license, even when a valid license exists for the source VMware instance. This behavior is expected and aligns with the FortiADC-VM licensing model for virtualized environments.
This document outlines the supported workflow to properly de-register the original VM instance and reapply the existing license on the target Nutanix deployment.
Scope
FortiADC-VM.
Solution
FortiADC-VM licensing is bound to a hypervisor-specific virtual hardware ID. When migrating from VMware ESXi to Nutanix AHV (KVM), the license cannot be directly transferred due to the change in the underlying hardware fingerprint. The supported procedure relies on license deregistration from the original VM followed by reapplication on the new instance.
Procedure:
Power off the source FortiADC-VM (VMware).
Perform a complete shutdown of the original VM.
Ensure the instance remains powered off during the migration process.
Allow a license de-registration period.
Maintain the VM in a powered-off state for a minimum of 90 minutes.
This allows the FortiGuard licensing back-end to automatically release the license association tied to the original virtual hardware ID.
Apply license on the target VM (Nutanix AHV).
Deploy the existing FortiADC-VM license file on the new KVM-based instance.
No modification or re-issuance of the license file is required in normal scenarios.
Validate the license activation.
Execute the following command:
get system status
Confirm:
The correct serial number is displayed (non-trial).
License status reflects a valid licensed state.
System is no longer operating under trial mode.
Operational notes:
License reuse is dependent on successful de-registration of the source VM instance.
Concurrent operation of source and target VMs using the same license is not supported.
The 90-minute de-registration window is required for back-end synchronization.
Configuration migration (backup/restore) is independent of licensing behavior and remains fully supported across hypervisors.
This approach minimizes downtime risk and maintains licensing compliance. For production HA migrations, plan a maintenance window and consider migrating nodes sequentially. If any questions arise or further assistance is needed regarding the migration process, the support team is available to help. Reach out via the Support Portal.
