Sign in Request access

Home · Migrations · Cisco ASA to Palo Alto

Firewall migration / Scope first

Cisco ASA
to Palo Alto PAN-OS

Translate a Cisco ASA configuration to PAN-OS SET commands or XML, for a standalone firewall or Panorama. 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.

The short answer

Which tool migrates
Cisco ASA to Palo Alto?

There is no single best tool; it depends on how much review you want to own. Palo Alto Expedition was the usual free choice and is end of life since January 2025 (what that means). The realistic options now:

OPTION 01

Palo Alto Professional Services or a partner

Palo Alto Networks and its partners run ASA migrations as a service. Good when you want a delivery team to own the project; scoped and priced by them.

OPTION 02

Policy-management platforms such as Tufin

Tufin publishes a firewall migration solution inside its policy-management platform. Fits teams that already run it across many vendors.

OPTION 03

PAN-OS API and scripting

Maximum control and no tool cost, but you write and verify NAT, zone and object translation yourself.

OPTION 04

NetConverter

Translates an ASA configuration to PAN-OS as SET commands or XML, for a standalone firewall or for Panorama, and runs it through checkpoints CP0–CP4 and behavior checks BC1–BC4. Findings marked NEEDS REVIEW or BLOCKED go to an engineer before deployment. There is no public price list; access is scoped per engagement and subject to account approval.

Define the handoff

What goes in.
What you review.

Source inputs

ASA configuration export and the device/software version. Include interface context and operational captures needed to review routing and NAT.

Target output

Reviewable PAN-OS output as SET commands or XML, for a standalone firewall or for Panorama. Output is subject to findings and supported features.

Path-specific boundaries

Cisco ASA is a source platform. Target-device validation and live traffic checks remain necessary; Local ASA preparation is a separate preview workflow.

Scope the review

Check the behavior,
not just the syntax.

REVIEW 01

Interface security levels and target zones

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

REVIEW 02

Object, service and policy references

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

REVIEW 03

Manual, object and identity NAT behavior

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

REVIEW 04

Routing, application dependencies and target import

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

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 →

Questions

Common questions

Which Palo Alto formats does this ASA path produce?

PAN-OS SET commands or XML, for a standalone firewall or for Panorama. The hosted service does not log in to the firewall or to Panorama.

Is Expedition required?

No. Palo Alto marks Expedition end of life on 31 December 2024 and stopped supporting it in January 2025. NetConverter is a separate tool. It is not an Expedition download.

Are all ASA features translated?

No. ASA VPN is not claimed as translated. A listed path does not cover every model, version or feature. NEEDS REVIEW and BLOCKED findings go to an engineer.

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 →