Sign in Request access

Palo Alto Expedition Alternative

Expedition reached end of life in December 2024 (Palo Alto Networks announcement). NetConverter translates to PAN-OS and Panorama, with findings for engineer review.

Get started See Comparison

Expedition Alternatives: Your Options

NetConverter is one option among several. Which fits depends on who owns the migration work.

OptionBest whenTrade-off
Palo Alto's successor toolingYou want the vendor's own path. Palo Alto says Expedition's functions are moving into new products.Check current scope and source-vendor coverage in Palo Alto's documentation.
Palo Alto Professional Services or a partnerYou want a delivery team to own the project.Scoped and priced by the provider; you depend on their schedule.
Tufin or similar policy-management platformsYou already run the platform across many vendors.Platform licensing and setup come first.
PAN-OS API and scriptingYou have the engineering time and want full control.You write and verify NAT, zone and object translation yourself.
NetConverterYou want ASA, FortiGate or PAN-OS configs translated to PAN-OS or Panorama with checkpoint and behavior-check findings. Hosted platform, plus NetConverter Local, a Docker image that runs on your own network.Engineer review of NEEDS REVIEW and BLOCKED findings is required. No public price list; scoped per engagement, subject to account approval.

Expedition ran as a VM inside your network. The closest NetConverter equivalent is NetConverter Local: a Docker workspace on your own network for collecting vendor-native configurations, inspecting device scope and preparing inputs. You choose when to submit a supported migration to the hosted platform for translation and validation. Local is a development preview and is available on request; ask about a Local evaluation.

What Happened to Expedition?

What Palo Alto Networks announced about its migration tool.

EOL'd December 2024

Starting January 2025, Palo Alto Networks no longer supports Expedition, including all Expedition1 and Expedition2 versions (announcement).

End of life

Expedition is end of life. Use Palo Alto's own advisories for vulnerability detail. Do not deploy an unsupported migration VM.

Review the findings

NetConverter does not publish an accuracy percentage. Engineer review of NEEDS REVIEW and BLOCKED findings is required before deployment.

Moving to New Products

Palo Alto Networks says it is transferring Expedition's core functionalities into new products (announcement). NetConverter is an independent option for the migration paths below.

Expedition vs. NetConverter

How NetConverter replaces and improves upon Expedition's capabilities.

Capability Palo Alto Expedition NetConverter.ai
Migration Paths ASA, CheckPoint, Fortinet → PAN-OS Firewall paths, plus router and switch paths that stay in NEEDS REVIEW
Target Platforms PAN-OS XML PAN-OS, Panorama, FMC, FortiGate, and more
Accuracy End of life. No accuracy figure cited here Findings plus a confidence score. Engineer review of NEEDS REVIEW and BLOCKED findings is required before deployment.
Validation Not assessed here Deterministic checks. An engineer reviews NEEDS REVIEW and BLOCKED findings before deployment
App-ID Mapping Not assessed here App-ID mapping for supported source services, with findings for review
Security Critical CVEs, cleartext storage (PAN-SA-2024-0010) SaaS. Device logins are not stored. SOC 2 Type II is on the roadmap and is not claimed today
Cost Model Free (but EOL, unsupported) Scoped per engagement. Platform access is subject to account approval

Available Migration Paths

NetConverter supports the paths Expedition handled, plus many more.

Your Expedition Migration Path, Without Expedition

Expedition's job was to turn a legacy firewall config into a PAN-OS candidate. NetConverter does the same job through a vendor-neutral intermediate representation: the source — Cisco ASA, FortiGate, or an existing PAN-OS / Panorama config — is parsed into a normalized model, then serialized to your target (PAN-OS set, PAN-OS XML, or Panorama). Address and service objects are de-duplicated, object-groups are preserved, NAT is translated in place, and security zones are mapped rather than left as raw interface names.

The difference is what happens after translation. Expedition handed you output and left verification manual. NetConverter runs every conversion through named checkpoints (CP0–CP4) and behavior checks (BC1–BC4) before you deploy. Deterministic checks run first and decide the status; AI is confined to declared corrections and advisory notes:

Migrating off a different platform first? See the Cisco ASA → Palo Alto and Fortinet → Palo Alto guides, or the Cisco FMT alternative.

Expedition EOL — Frequently Asked Questions

Is Palo Alto Expedition still supported?
No. Palo Alto Networks announced that, starting January 2025, it no longer supports Expedition, including all versions of the Expedition1 and Expedition2 branches (end-of-life announcement, checked 2026-10-27). Use Palo Alto's advisories for vulnerability detail, and do not keep running it.
What replaces Palo Alto Expedition after EOL?
Palo Alto Networks says it is transferring Expedition's core functionalities into new products (end-of-life announcement). NetConverter is an independent SaaS alternative that covers the migration paths Expedition handled — Cisco ASA, FortiGate, and PAN-OS into PAN-OS set/XML or Panorama — and adds named checkpoints (CP0–CP4) and behavior checks (BC1–BC4) with confidence scoring. Deterministic checks decide the status; AI never sets it. Findings go to engineer review.
Can I migrate Cisco ASA to Palo Alto without Expedition?
Yes. NetConverter parses ASA access-lists, NAT statements, and object-groups into a vendor-neutral model and serializes them to PAN-OS (set or XML) or Panorama, with zone mapping and object de-duplication. Each translation passes named checkpoints (CP0–CP4) and behavior checks (BC1–BC4) before you deploy. Deterministic checks decide the status; AI never sets it.
Does NetConverter map App-IDs like Expedition did?
NetConverter maps App-ID for supported source services, with findings for review. It derives App-ID candidates from the source policy's ports and services during translation, so application-based rules are proposed from the configuration rather than only learned from live traffic later.
How should a result be reviewed?
NetConverter does not publish an accuracy percentage against Expedition. It uses deterministic mapping and reports findings. Engineer review of NEEDS REVIEW and BLOCKED findings is required before deployment.
Is NetConverter safe given Expedition's security history?
NetConverter is SaaS-based and does not store device credentials. You upload or paste a configuration to convert it — there is no on-prem appliance to patch and no stored device credentials. For Expedition's security history, see Palo Alto Networks advisory PAN-SA-2024-0010.

Ready to Migrate without Expedition?

Checked output and an evidence report, without running end-of-life Expedition. Engineer review of NEEDS REVIEW and BLOCKED findings is required before deployment.