Sign in Request access

Home · Migrations · FortiConverter alternative

Comparison / FortiGate targets

FortiConverter
and NetConverter

Fortinet publishes a FortiConverter Service and a FortiConverter Tool for moving configurations onto FortiGate, including third-party sources and FortiGate-to-FortiGate moves. NetConverter is not FortiConverter. It translates the paths published on this site and returns findings for an engineer.

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

When do people look at both?

When the target is FortiGate. Fortinet documents both a FortiConverter Service and a FortiConverter Tool. The Service page describes an uploaded source configuration and a returned FortiOS configuration. The Tool documentation publishes a conversion list. This page does not copy that list, and it does not rank the products. Sources NetConverter can translate to FortiGate are Cisco ASA, Palo Alto SET or XML, and an FMC snapshot. FortiGate can also be a source toward Palo Alto or FMC JSON.

Define the handoff

What goes in.
What you review.

Source inputs

For NetConverter, a supported source export: ASA, Palo Alto SET or XML, or an FMC snapshot ZIP. Not a live device login.

Target output

FortiGate configuration for the supported scope, or, in the other direction, Palo Alto or FMC JSON. FortiManager as a target is planned.

Path-specific boundaries

Fortinet offers both a FortiConverter Service and a FortiConverter Tool. NetConverter is neither, and it does not log in to FortiManager or push to a FortiGate. AI never sets status.

Scope the review

Check the behavior,
not just the syntax.

REVIEW 01

Direction

FortiConverter, as Fortinet describes it, aims at FortiGate. NetConverter also translates away from FortiGate, to Palo Alto and to FMC file output.

REVIEW 02

Scope

Use the supported-vendors page for NetConverter's sources. Use Fortinet's own FortiConverter document for theirs.

REVIEW 03

Review

Both kinds of migration still need an engineer. A converted file is not cutover approval.

REVIEW 04

Checks

NetConverter runs checkpoints CP0–CP4 and behavior checks BC1–BC4 on firewall paths. That is a description of NetConverter, not of FortiConverter.

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 NetConverter a FortiConverter download?

No. This site does not host FortiConverter. Fortinet distributes its own service.

Does NetConverter generate FortiManager output?

No. FortiManager as a target is planned. Per-device FortiGate configurations collected from FortiManager convert as FortiGate.

Where is the FortiGate path list?

Start with the migration hub and the supported-vendors page. ASA to FortiGate and Palo Alto to FortiGate already have guides.

Plan the next step

Bring the details
that make your migration different.

Say whether you are moving to FortiGate or away from it, and which source export you have.

Discuss your scope →Compare tools →