Sign in Request access

Home · Migrations · Cisco ASA to FMC

Firewall migration / Scope first

Cisco ASA
to Cisco FMC

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

ASA configuration export and the intended FMC version, device scope and access-control policy requirements.

Target output

FMC JSON output for supported objects and policies, reviewed before on-site import.

Path-specific boundaries

FMC is the destination for this path: NetConverter writes an FMC JSON file and an import package, and the fmc_import.py and fmc_cleanup.py scripts from the portal's Tools & Downloads page push it to your FMC on site. The hosted converter does not log in to your manager; device deployment happens from FMC.

Cisco paths NetConverter supports

Cisco ASA as a source. Cisco FMC as a source through the read-only FMC collector, whose snapshot you upload for audit, optimization and migration to Palo Alto or Fortinet. Cisco FMC as a destination, as on this page. Cisco FTD on its own, including FTD show running-config text, is a roadmap item; FTD devices managed by FMC are read through the FMC collector.

Scope the review

Check the behavior,
not just the syntax.

REVIEW 01

Object and service dependencies

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

REVIEW 02

Access-control policy ordering

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

REVIEW 03

NAT requirements and target device scope

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

REVIEW 04

Import results and device deployment validation

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

What file does the ASA to FMC path write?

FMC JSON plus an import package. The import and cleanup scripts run on site. The hosted converter does not log in to FMC.

Is an FTD show running-config a source or a target?

No. FTD on its own is a roadmap item. FTD managed by FMC is read through an FMC snapshot, which is a different guide.

Does a JSON file mean the migration is complete?

No. A finished JSON file is not a completed migration. Deterministic checks do not approve deployment.

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 →