Source inputs
ASA configuration export and the intended FMC/FTD versions, device scope and access-control policy requirements.
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.
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.
Target output
FMC JSON output for supported objects and policies, reviewed before on-site import.
Path-specific boundaries
FMC is a destination for this hosted migration path. The hosted converter does not log in to your manager; import and device deployment happen on-site through the applicable workflow.
Scope the review
Check the behavior,
not just the syntax.
Object and service dependencies
Confirm the intended behavior, supported scope and target-platform requirements.
Access-control policy ordering
Confirm the intended behavior, supported scope and target-platform requirements.
NAT requirements and target device scope
Confirm the intended behavior, supported scope and target-platform requirements.
Import results and device deployment validation
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.