Sign in Get started

Firewall migration / Scope first

Fortinet FortiGate
to Palo Alto PAN-OS

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

A FortiGate configuration export with the intended VDOM scope, source version and target PAN-OS context.

Target output

PAN-OS SET or XML output for supported configuration scope, with findings for review.

Path-specific boundaries

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

Check the behavior,
not just the syntax.

REVIEW 01

VDOM, interface and target-zone scope

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

REVIEW 02

Address and service-object behavior

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

REVIEW 03

Policy order, NAT and routing

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

REVIEW 04

Application and security-profile dependencies

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

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 →

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 →