Sign in Request access

Home · Migrations · Palo Alto to Cisco FMC

Firewall migration / Scope first

Palo Alto PAN-OS
to Cisco FMC

Translate a Palo Alto SET or XML configuration into FMC JSON plus an import package. Import and device deployment happen on site. The hosted service does not log in to FMC.

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

Can Palo Alto migrate to Cisco FMC?

Yes. The supported-vendors page lists Palo Alto, Cisco ASA and FortiGate as sources for Cisco FMC file output. NetConverter writes an FMC JSON file and an import package. The fmc_import.py script from the portal Tools and Downloads page pushes that package to your FMC on site. fmc_cleanup.py removes a test import. Nothing in the hosted converter logs in to FMC.

Define the handoff

What goes in.
What you review.

Source inputs

A Palo Alto PAN-OS configuration in SET or XML. Say which device or device-group scope you want reviewed. Panorama as a source is scoped per device through NetConverter Local (preview).

Target output

FMC JSON for supported objects and policies, plus an import package you run on site. The hosted service does not deploy to firewalls.

Path-specific boundaries

Cisco FTD show running-config is not an output format. FMC is the file-output target. A listed path does not mean every App-ID, profile or NAT form is automated.

Scope the review

Check the behavior,
not just the syntax.

REVIEW 01

Security rules and objects

Confirm address, service and rule references still resolve in the JSON you will import.

REVIEW 02

NAT

Review source, destination and static NAT against the PAN-OS intent. Unmapped NAT stays a finding.

REVIEW 03

Zones to FMC interfaces

FMC security zones are not PAN-OS zones. Confirm the interface and zone map before import.

REVIEW 04

On-site import

Use the import package on your FMC. Treat a lab import as a test, then remove it with the cleanup script if you do not intend to keep it.

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

Does the hosted service push this configuration into FMC?

No. It writes JSON and an import package. The import script runs on site. The hosted service does not log in to FMC.

Is FortiGate to FMC the same kind of output?

Yes. FortiGate to FMC is also file output. See the FortiGate to FMC guide.

Is validation complete after the JSON is produced?

No. Producing JSON is not a completed migration. Deterministic checks can report findings. They do not approve a cutover or prove live traffic.

Plan the next step

Bring the details
that make your migration different.

Bring the PAN-OS version, the policy scope, and the FMC version you will import into.

Discuss your scope →FortiGate to FMC →