Practical tools for system, network, security, and operations administrators.

NET-C0921 · Migrations & Audits

Cisco ASA to FortiGate Migration Guide

Convert one ASA rule toward FortiGate on paper, and do not install it on a gateway.

Updated 25 October 2026 · Migration Guide

This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.

What this hour is for

The converter drafts a FortiGate-side reading of an ASA object you paste. You paste a lab object or a redacted object you are allowed to hold. A live policy install is not this page.

Read names, zones, and the service. ASA interfaces and FortiGate zones are not the same words. Write the map. A rule that becomes any-to-any in the draft is a rule you delete.

One object. Keep the ASA source. Two systems must not own one production rule after a careless paste.

Secrets in the export are rotated and removed. The draft is not committed with a key.

The change you can finish

Apply nothing during the writing of the note. When the lab window opens, it is one change on the device named in the ticket. Read the draft, then the device, then decide.

Rollback is the file or the revision you saved first. You do not invent a rollback after the only copy is gone.

  1. Choose one lab or redacted object.
  2. Convert.
  3. Write the zone map.
  4. Delete any any-any the draft invented.
  5. Keep the source file.
  6. Do not install a policy.

Mistakes that outlive the command

Cisco ASA to FortiGate Migration Guide goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.

Decisions to write down

One decision for Cisco ASA to FortiGate Migration Guide: One object was converted. Zones are mapped. Any-any is gone. The source remains. Nothing was installed. And secrets are gone.

Checks before you call it done

Confirm this before you call the change done: The object name is in the ticket. The zone map is a sentence. No install ran. The ASA still owns production. And a second person read the draft. If one of those fails, stop.

One object. No policy install.
Delete an any-any the converter invented.

Before you leave the device

Cisco ASA to FortiGate Migration Guide ends when the hostname on the device matches the hostname in the ticket. If it does not, you are on the wrong box. Stop. A command that succeeded on the wrong box is not progress.

The draft stays a draft until a person has read the names in it. A generator does not log into the device and does not know which interface is the uplink. You delete a line that names a device, a zone, or a prefix you did not write down.

0.0.0.0/0 is not kept because a sample included it. A source you can say is the source you keep. 192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. They belong in the note. They are not prefixes you type onto a production device because they appeared in a draft.

prompt-for-this is a reminder that a secret is missing. It is not a password, a key, a community string, or a pre-shared key you save in the ticket or in git. The real secret stays in the store.

One change is the window. A VLAN and a routing protocol and a VPN do not share it. If two things move and the result is wrong, you will not know which one did it. The next feature waits for its own page.

If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied config produces a device nobody can rebuild. Restore the copy you took first.

A second person reads the device name and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the device alone.

This page is a planning guide. It is not a vendor manual, not an official standard, and not a permission to touch a network you do not administer. The pillar guide owns the wider design. This page owns one lab proof.

Tools for this guide

These tools run in the browser on this site. They do not log into your machines.

More in this cluster

The pillar for this page, and the next published pages filed with it.