The following configuration elements are supported for migration:

• Network objects and groups

• Service objects, except for those service objects configured for a source and destination

  Note	Though the Secure Firewall migration tool does not migrate extended service objects (configured for a source and destination), referenced ACL and NAT rules are migrated with full functionality.

• Service object groups, except for nested service object groups

  Note	Since nesting is not supported on the management center, the Secure Firewall migration tool expands the content of the referenced rules. The rules however are migrated with full functionality.

• IPv4 and IPv6 FQDN objects and groups

• IPv6 conversion support (Interface, Static Routes, Objects, ACL, and NAT)

• Access rules that are applied to interfaces in the inbound direction and global ACL

• Auto NAT, Manual NAT, and object NAT (conditional)

• Static routes, ECMP routes, and PBR

• Physical interfaces

• Secondary VLANs on ASA or ASA with FirePOWER Services interfaces will not migrate to threat defense.

• Subinterfaces (subinterface ID will always be set to the same number as the VLAN ID on migration)

• Port channels

• Virtual tunnel interface (VTI)

• Bridge groups (transparent mode only)

• IP SLA Monitor

  The Secure Firewall migration tool creates IP SLA objects, maps the objects with the specific static routes, and migrates these objects to management center.

  Note	IP SLA Monitor is not supported for non-threat defense flow.

• Object Group Search

  Note	Object Group Search is unavailable for management center or threat defense version earlier than 6.6. Object Group Search will not be supported for non-threat defense flow and will be disabled.

• Time-based objects

  Note

  You must manually migrate timezone configuration from source ASA, ASA with FirePOWER Services, and FDM-managed device to target threat defense. Time-based object is not supported for non-threat defense flow and will be disabled. Time-based objects are supported on management center version 6.6 and above.

• Site-to-Site VPN Tunnels

  • Site-to-Site VPN—When the Secure Firewall migration tool detects crypto map configuration in the source ASA and FDM-managed device, the Secure Firewall migration tool migrates the crypto map to management center VPN as point-to-point topology.

  • Crypto map (static/dynamic) based VPN from ASA and FDM-managed device.

  • Route-based (VTI) ASA and FDM VPN

  • Certificate-based VPN migration from ASA and FDM-managed device.

  • ASA and FDM-managed device trustpoint or certificates migration to management center must be performed manually and is part of the pre-migration activity.

• Dynamic Route objects, BGP, and EIGRP

  • Policy-List

  • Prefix-List

  • Community-List

  • Autonomous System (AS)-Path

  • Route-Map

• Remote Access VPN

  • SSL and IKEv2 protocol.

  • Authentication methods—AAA only, Client Certificate only, SAML, AAA, and Client Certificate.

  • AAA—Radius, Local, LDAP, and AD.

  • Connection Profiles, Group-Policy, Dynamic Access Policy, LDAP Attribute Map, and Certificate Map.

  • Standard and Extended ACL.

  • RA VPN Custom Attributes and VPN load balancing

  • As part of pre-migration activity, perform the following:

    • Migrate the ASA and FDM-managed device trustpoints manually to the management center as PKI objects.

    • Retrieve AnyConnect packages, Hostscan Files (Dap.xml, Data.xml, Hostscan Package), External Browser package, and AnyConnect profiles from the source ASA and FDM-managed device.

    • Upload all AnyConnect packages to the management center.

    • Upload AnyConnect profiles directly to the management center or from the Secure Firewall migration tool.

    • Enable the ssh scopy enable command on the ASA to allow retrieval of profiles from the Live Connect ASA.

• ACL optimization

  ACL optimization supports the following ACL types:

  • Redundant ACL—When two ACLs have the same set of configurations and rules, then removing the non-base ACL will not impact the network.

  • Shadow ACL—The first ACL completely shadows the configurations of the second ACL.

  Note	ACL optimization is currently not available for Palo Alto Networks and ASA with FirePower Services (FPS).

For information on the supported configurations of the Secure Firewall migration tool, see:

• Supported ASA Configurations

• Supported ASA with FirePOWER Services Configurations

• Supported Check Point Configurations

• Supported PAN Configurations

• Supported Fortinet Configuration

• Supported FDM-Managed Device Configuration

For information on the migration workflow of the Secure Firewall migration tool, see:

• Export the ASA Configuration File

• Export the ASA with FirePOWER Services Configuration File

• Export the Check Point Configuration Files

• Export the Configuration from Palo Alto Networks Firewall

• Export the Configuration from Fortinet Firewall

• Export the FDM-Managed Device Configuration File

The Secure Firewall migration tool provides the following reports in HTML format with details of the migration:

• Pre-Migration Report

• Post-Migration Report

The Secure Firewall migration tool provides the following capabilities:

• Validation throughout the migration, including parse and push operations

• Object re-use capability

• Object conflict resolution

• Interface mapping

• Subinterface limit check for the target threat defense device

• Platforms supported

  —FDM Virtual to Threat Defense Virtual

  —Same hardware migration (X to X device migration)

  —X to Y device migration (Y having higher number of interfaces)

• ACL optimization for source ASA, FDM-managed device, Fortinet, and Checkpoint for ACP rule action.