Sign in Request access

Analyze firewalls, routers and switches

Run pre-migration analysis to understand configuration complexity, policy overlap, and object cleanup opportunities before converting to supported Palo Alto, Fortinet, or FMC targets.

Get started View Validation Options

Migration Readiness Scoring

Identify high-risk rule sets, object dependencies, and cleanup priorities before executing large migration waves.

Policy and Object Coverage

Map source policies, NAT patterns, and object references into a structured analysis report your engineering team can action.

Platform-Specific Recommendations

Get targeted guidance for ASA to FMC, Panorama to SCM, and multi-vendor transition programs with clear next steps.

Related Analysis & Optimization

What a pre-migration analysis can tell you

Analysis reads the configuration you upload. It does not discover live topology, and it does not log in to a firewall or a manager. Use it to see object fan-out, policy overlap and cleanup candidates before you pick a target. The score is a way to order the work. It is not a conversion percentage and it is not a promise that the later translation will be complete.

Firewall sources and targets that are published today include Cisco ASA, Palo Alto SET and XML, Panorama, FortiGate and Cisco FMC file output. Check Point is source-only, through a Handoff Bundle, toward Palo Alto. An FMC snapshot can be analyzed and can be a source toward Palo Alto or Fortinet. Palo Alto and FortiGate can be sources toward FMC JSON. Strata Cloud Manager conversion is supported on request. The hosted platform does not read SCM configuration and does not accept SCM as a self-service target.

Router and switch analysis follows the same rule as translation. Cisco IOS-XE and Juniper Junos are the router pair. Switch paths are Cisco IOS-XE, Aruba CX and Junos, plus ArubaOS as a source only. There is no direct IOS-XE switch to Junos switch path. Every hosted router and switch result stays in NEEDS REVIEW. EIGRP is not translated to Junos. BGP on an Aruba CX target is partial.

Start from the migration hub if you already know the pair, or from supported platforms if you are checking whether the pair exists. Findings still need an engineer. AI does not set status.