FortiMail VM (Server Mode) Migration to Bare Metal – Configuration Process & Risk Factors

Hello User13,

Thank you for using the Community Forum. I will seek to get you an answer or help. We will reply to this thread with an update as soon as possible. 

If anybody else has any info or advice, please feel free to contribute!

Hello,

We are still looking for an answer to your question.

We will come back to you ASAP. If anyone else has any ideas in the meantime, please feel free to contribute!

What is the recommended process for migrating FortiMail VM (Server Mode) to hardware appliances?
>> Recommend to do all the necessary backup for the config and data before migrate.

Is configuration backup and restore between VM and hardware models fully supported, or are there limitations?
>> It was recommended to build the configuration from scratch.
>> There is an unsupported way to restore the config to other model, you can create a support ticket on this for better advice.

What is the proper approach for migrating mailbox data, mail storage, and mail queues?
>> For mail user and data, you can refer documentation here: https://docs.fortinet.com/document/fortimail/7.6.4/administration-guide/326016/migrating-email-from-other-mail-servers-server-mode-only
>> For Mail Queue you can do backup and restore. Refer system maintenance here: https://docs.fortinet.com/document/fortimail/7.6.4/administration-guide/988966/system-maintenance

Are there firmware compatibility requirements between VM and hardware before restoring configuration?
>> The firmware version must be same for both models when restoring the config.

What storage-related concerns should be considered (e.g., disk initialization, RAID configuration differences)?
>> Need to make sure the system performance is supported the mail capacity in your environment. This can refer to the FortiMail datasheet.

What are the key risk factors during this migration, especially when both zones use the same domain but are logically separated?
>> This required more study on the network environment for better advice.
>> But if the migration is only from one model to another model but still remaining the same configuration, this should be no issue.