Sign in Request access

Home · Migrations · FortiGate to Cisco FMC

Firewall migration / Scope first

FortiGate
to Cisco FMC

Translate a FortiGate configuration into FMC JSON for review and on-site import. FortiManager-managed FortiGates start from the per-device FortiGate configuration, not from a FortiManager database write.

Discuss this migration →Compare migration paths →

Account approval and feature support apply. A listed migration path does not certify every model, version or configuration.

The short answer

Is FortiGate to FMC offered?

Yes. The supported-vendors page lists FortiGate, with Cisco ASA and Palo Alto, as a source for FMC JSON file output. The hosted converter does not log in to FMC. You review the JSON, then import it on site with the package from Tools and Downloads.

Define the handoff

What goes in.
What you review.

Source inputs

A FortiGate configuration export. If FortiManager holds the device, collect the per-device FortiGate configuration and convert that. FortiManager as a target is planned and is not the output of this path.

Target output

FMC JSON and an import package for on-site import. Device deployment stays in FMC, under your change process.

Path-specific boundaries

This path does not claim every FortiOS profile, VPN or proxy feature. Findings mark what was not translated. AI does not set the result status.

Scope the review

Check the behavior,
not just the syntax.

REVIEW 01

Policies and objects

Confirm firewall policies, addresses and services in the JSON match the FortiGate scope you selected.

REVIEW 02

VIP and IP pool NAT

Review VIPs and pools as destination and source NAT. Unmapped translation stays in the findings.

REVIEW 03

Interfaces

Map FortiGate interfaces to the FMC security zones you will use before import.

REVIEW 04

Import and cleanup

Import on site. Use the cleanup script if a test import should not remain.

Each result's status comes from deterministic checkpoints (CP0–CP4) and, on firewall paths, behavior checks (BC1–BC4); AI can explain findings but never sets status. These are review areas, not a guarantee that every construct in them is automated. Unsupported features, missing captures and conditional behavior remain part of the engineering review.

Questions

Common questions

Why is this not the same as FortiConverter?

FortiConverter, as Fortinet describes it, migrates configurations to FortiGate. This path goes the other way: FortiGate to Cisco FMC file output.

Does NetConverter log in to FortiManager?

No. Collect the FortiGate configuration, then convert that file. The hosted service does not log in to FortiManager or FMC.

What should engineers review before import?

NEEDS REVIEW and BLOCKED findings. A JSON file is not deployment approval.

Plan the next step

Bring the details
that make your migration different.

Bring the FortiOS version, whether FortiManager is only the collector, and the FMC version for the import test.

Discuss your scope →Palo Alto to FMC →