VDOM Mapping

During conversion, after the configuration parsing, you can select the VDOMs that you want to convert and do VDOM name mapping.

If you unselect a VDOM, FortiConverter will not convert and generate the corresponding configuration in the output result.

Note: VDOM Mapping does not support adding a new empty VDOM. For 3rd party conversion, an empty VDOM can add to the tuning page.

VDOM Mode Setting

The VDOM mode switch allows you to enable the VDOM mode or vice versa.

Example

1. Convert VDOM mode from the source to a target device without VDOM.
   1. Select a VDOM you want to upload to the root of the target device
   2. Disable the VDOM mode.
   3. Continue the conversion and get the converted configuration.

   

Remark: If you want to upload the "demo" of source VDOM to the target

device's root, you can rename the target VDOM to "root" and continue with the

conversion.

2. Convert the source device without VDOM to a target device with VDOM mode.
   1. Rename the name of the VDOM to the target device's VDOM you want to import.
   2. Enable VDOM Mode.
   3. Continue with the conversion and get the converted configuration.

   

Warning

1. In Fortinet migration, when a target device without VDOM enabled migrates to a specific vdom device with VDOM mode enabled, it means there have been existing configurations on the target device and FortiConverter will ignore the global scope of the configuration to avoid overwriting the global settings on the target device. In the device mode, you can utilize the partial import or push those configurations as you want.
2. In the Fortinet migration, if you enable the vdom mode, the "config system interface" under the global scope would not import to the device, please make sure to configure the device's interfaces and do the proper interface mapping before the import process. Otherwise, the object import may fail by the improper interface setting.