Sign in Request access

Home · Migrations · Cisco ASA to FortiGate

Firewall migration / Scope first

Cisco ASA
to Fortinet FortiGate

Prepare the source, review the translated configuration and validate the behavior that matters to your network. Start with the device, software version and features in scope.

Discuss this migration →Open the platform →

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

Define the handoff

What goes in.
What you review.

Source inputs

ASA configuration export, source version and the intended FortiGate model, FortiOS version and VDOM scope.

Target output

FortiOS configuration output for the supported scope, with findings to review before on-site import.

Path-specific boundaries

ASA security behavior and FortiGate policy behavior differ. Confirm supported features and resolve manual steps before deployment.

Scope the review

Check the behavior,
not just the syntax.

REVIEW 01

Interface and VDOM mapping

Confirm the intended behavior, supported scope and target-platform requirements.

REVIEW 02

Access-policy ordering and service behavior

Confirm the intended behavior, supported scope and target-platform requirements.

REVIEW 03

NAT and address translation

Confirm the intended behavior, supported scope and target-platform requirements.

REVIEW 04

Routing and features with no direct equivalent

Confirm the intended behavior, supported scope and target-platform requirements.

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.

See the current product

Explore the workflow.

View dated product captures and a clearly labeled synthetic verification example. A screenshot of an interface does not establish acceptance of this migration path.

See the product tour →

Understand your result

Read the findings and their limits alongside the output. Address blockers, validate device acceptance and test affected traffic before seeking deployment approval.

Read the result guide →

Questions

Common questions

Is the source ASA or IOS?

This guide is Cisco ASA to FortiGate. ASA is source-only. NetConverter does not generate an ASA configuration.

Does the hosted service log in to either firewall?

No. Conversion starts from the ASA export and produces FortiGate configuration for review.

What remains an engineer decision?

Service objects, NAT and anything the findings mark NEEDS REVIEW or BLOCKED. AI can explain findings but never sets status.

Plan the next step

Bring the details
that make your migration different.

Source and target models, software versions, critical features and the change window help establish a realistic scope.

Discuss your scope →Compare migration paths →