Source inputs
A FortiGate configuration export with the intended VDOM scope, source version and target PAN-OS context.
Home · Migrations · Fortinet to Palo Alto
Firewall migration / Scope first
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.
Account approval and feature support apply. A listed migration path does not certify every model, version or configuration.
Define the handoff
A FortiGate configuration export with the intended VDOM scope, source version and target PAN-OS context.
PAN-OS SET or XML output for supported configuration scope, with findings for review.
FortiManager collection and a standalone FortiGate export are different inputs. Confirm the applicable handoff path; advanced and dynamic features may need manual work.
Scope the review
Confirm the intended behavior, supported scope and target-platform requirements.
Confirm the intended behavior, supported scope and target-platform requirements.
Confirm the intended behavior, supported scope and target-platform requirements.
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
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 →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
Policies, address and service objects, VIPs, IP pools and custom services, plus the NAT and zone map. Unsupported features stay findings.
No. Collect the per-device FortiGate configuration and convert that. FortiManager as a target is planned.
No. Self-service Palo Alto targets are SET, XML and Panorama. SCM conversion is supported on request, not in the self-service platform.
Plan the next step
Source and target models, software versions, critical features and the change window help establish a realistic scope.