Technical Tip: Import error when migrating provisioning templates between ADOMs or FortiManagers

[omorenomartin]

Description	This article explains the error that occurs when migrating provisioning templates between ADOMs or FortiManagers. The error is caused by a version mismatch between the source and destination ADOMs.
Scope	FortiManager.
Solution	Provisioning templates export/import is supported via GUI in v7.0+. Administrators can export templates as an unencrypted JSON file, that can be then, imported into another ADOM or FortiManager. When importing the JSON file into the destination ADOM/FortiManager, the following error may appear when the system performs a file check (numbers might be different depending on version): mr mismatch, 2 vs 0 This error is caused by a version mismatch between the source and destination ADOMs. In this example, provisioning templates were exported from a v7.0 ADOM, and then tried to import into a v7.2 ADOM To resolve the error, follow these steps: Check the version of the source ADOM. If it is not on the same version as the destination ADOM, upgrade the source ADOM to the same version. For example, if the destination ADOM is on version v7.4, upgrade the source ADOM to version v7.4. Once the source ADOM is upgraded, try exporting and importing the provisioning templates again. The import should succeed without issues. Note: Another option is to start from an earlier version in the destination ADOM, and after successfully importing the provisioning templates, upgrade everything to the desired version. Refer to the FortiManager documentation for more information on upgrading an ADOM.