FortiGate Migration from 600E(HA-A/P) To 200G(HA-A/P)

Hello @orspider ,

I don't have any experience with the FortiConverter service, but I used the FortiConverter standalone version. After conversion, FortiConverter will provide all configuration parts part by part. For example, policy, address, interface, ha, etc. After getting the files, you can add HA ports to the configuration. As you know, FortiGate configurationis clear text.

Hi Spider

If I understand well, you converted the config without taking in consideration the HA config, right?

In that case I'd push the new config to one standalone 200G (without HA), and then I'd build the HA cluster.

HA config is relatively small portion under "config system ha" likely less than 20 lines. It's easy to recover even if you didn't include HA in converter conversion. It would probably skip that part. Just make sure you have backup config for that part for both units. Or if you configured in CLI originally, you probably remember what you had to configure, like priority, heartbeat interface, dedicated management gateway, monitoring interfaces, etc.
When you upload the converted standalone config to both new 200Gs with heartbeat cable disconnected, configure below in the same way the 600Es are configured:
1) hostname under "config system global"(if you set a unique hosthame for each)
2) "config system ha" part. Of course two units might have different config.
3) dedicated management interface (like mgmt) IP config

Then just connect the heartbeat cable between them. Since other parts are identical and already uploaded to both, after deciding which would be primary it should sync up leratively quickly. 

Toshi