Home · Migrations · Cisco FMC to Palo Alto
Firewall migration / Scope first
Cisco FMC
to Palo Alto PAN-OS
Translate a per-device FMC snapshot toward Palo Alto SET commands, XML, or Panorama. You upload the snapshot. NetConverter does not log in to FMC, and a standalone FTD show running-config is not this path.
Account approval and feature support apply. A listed migration path does not certify every model, version or configuration.
The short answer
What does an FMC to Palo Alto migration start from?
It starts from a configuration snapshot, not a live FMC session. The public collectors repository documents a read-only FMC collector that pulls configuration with GET requests and packages one fmc_audit ZIP for audit, optimization and migration to Palo Alto or Fortinet. NetConverter Local can also produce a per-device handoff ZIP in preview. Supported Palo Alto targets on this path are SET, XML and Panorama.
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
Reviewable PAN-OS output as SET commands or XML, for a standalone firewall or for Panorama. Output is subject to findings and to the features the snapshot actually contained.
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. SCM is a different path and is supported on request, not in the self-service platform. This page does not read SCM.
Scope the review
Check the behavior,
not just the syntax.
REVIEW 01Snapshot completeness
A partial or failed collector capture is a gap. Do not treat a partial ZIP as a full FMC domain.
REVIEW 02Policy and object references
Confirm access rules, objects and services in the snapshot still match the policy you intend to move.
REVIEW 03NAT and zones
Map FMC interfaces and security zones to the Palo Alto zones you will use.
REVIEW 04Panorama placement
If the target is Panorama, review device-group and template placement before import. NetConverter does not log in to Panorama.
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 NetConverter log in to Cisco FMC for this migration?
No. You upload a per-device snapshot. The hosted service does not log in to FMC or push a configuration to it.
Can I paste an FTD show running-config instead of an FMC snapshot?
No. Cisco FTD on its own, including FTD show running-config text, is a roadmap item. FTD devices managed by FMC are read through the FMC snapshot.
Which Palo Alto formats can this path target?
Palo Alto SET commands, XML, or Panorama. Strata Cloud Manager is supported on request and is not the self-service target for this page.
Plan the next step
Bring the details
that make your migration different.
Bring the FMC version, the domains in the snapshot, and whether the target is a standalone PAN-OS firewall or Panorama.