Migrating the configuration

You can back up the system of one FortiManager model, and then use the CLI and the FTP, SCP, or SFTP protocol to migrate the settings to another FortiManager model.

If you encrypted the FortiManager configuration file when you created it, you need the password to decrypt the configuration file when you migrate the file to another FortiManager model.

The execute migrate all-settings command migrates all configurations except the CLI system settings. These system settings must be manually copied from the original FortiManager model to the other FortiManager model.

To migrate the FortiManager configuration:

1. In one FortiManager model, go to System Settings > Dashboard.
2. Back up the system. See Backing up the system.
3. In the other FortiManager model, go to System Settings > Dashboard.

4. If the configuration file is for multiple ADOMs, enable Administrative Domains in the System Information widget before migrating.

5. Open the CLI Console, and enter the following command:

   execute migrate all-settings <ftp | scp | sftp> <server> <filepath> <user> <password> [cryptpasswd]

6. After migrating, update the CLI system settings, as needed.

7. Re-establish the FGFM tunnels. See Appendix B - Re-establishing the FGFM tunnel after VM license migration.

If the original FortiManager has databases from FortiGuard (antivirus, antispam, webfilter, etc.), they will not be included in the configuration file. After migrating, export the packages from the original FortiManager and import them to the other FortiManager. For example, see Exporting web filter databases example and Importing web filter databases example.