Sign in Request access

Home · Migrations · Cisco FMC to FortiGate

Firewall migration / Scope first

Cisco FMC
to FortiGate

Translate a per-device FMC snapshot into a FortiGate configuration you can review. The source is an uploaded snapshot. FortiManager as a target is planned; this path writes FortiGate, not a FortiManager database.

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

How does FMC to FortiGate migration work?

The supported-vendors page lists an FMC snapshot as a source for migration to Palo Alto or Fortinet. You upload the ZIP the read-only collector builds, or a per-device NetConverter Local handoff ZIP in preview. The hosted service does not log in to FMC. The target is FortiGate configuration for engineer review, with checkpoints and behavior checks.

Define the handoff

What goes in.
What you review.

Source inputs

FMC is a source only as a per-device snapshot you upload. The read-only FMC collector uses GET requests and packages one fmc_audit ZIP. NetConverter Local can also produce a per-device handoff ZIP (preview). The hosted service does not log in to FMC and does not push to it.

Target output

A FortiGate configuration for the supported scope, with findings. FortiManager as a target is planned. FortiManager-collected FortiGate devices are a different workflow: collect the FortiGate configuration and convert it as FortiGate.

Path-specific boundaries

Cisco FTD on its own, including FTD show running-config text, is a roadmap item, not a supported source or target. FTD devices managed by FMC are read through the FMC snapshot, not as a separate FTD file. FortiConverter is Fortinet's own tool for FortiGate targets. NetConverter is a separate product and does not claim FortiConverter's vendor list.

Scope the review

Check the behavior,
not just the syntax.

REVIEW 01

What the snapshot contains

Confirm the access policy, objects and NAT in the ZIP are the policy you mean to translate.

REVIEW 02

FortiGate policy order

Review how FMC rule order and sections land in FortiOS. Do not assume a one-to-one section match.

REVIEW 03

NAT and interfaces

Map interfaces and address translation explicitly. Missing interface context stays in the review.

REVIEW 04

What is not written

The hosted service does not log in to FortiManager or push the result to a FortiGate.

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

Is FMC to FortiGate a supported NetConverter path?

Yes. The supported-vendors page lists an uploaded FMC snapshot as a source for migration to Fortinet, as well as to Palo Alto.

Does this replace FortiConverter?

No. Fortinet describes FortiConverter as its service for migrating configurations to FortiGate. NetConverter is a separate product with its own supported sources and review findings.

Will this import itself into FortiManager?

No. FortiManager as a target is planned. This path produces FortiGate configuration for review.

Plan the next step

Bring the details
that make your migration different.

Bring the FMC snapshot scope and the FortiOS version you expect to review against.

Discuss your scope →FMC to Palo Alto →