
Cisco has developed a Firepower migration tool, which is a utility that converts supported [ASA](/asa) configurations to supported Firepower Threat Defense (FTD) platform configurations.  This utility helps automate the migration of supported ASA features and policies. You may have to manually migrate any unsupported features.

The migration tool can be used in conjunction with [ASA to Firepower reimaging](/asa-and-firepower-reimaging) to convert a compatible ASA platform to an FTD platform.

Links:

https://forum.networklessons.com/t/reimage-cisco-firepower-to-cisco-asa/27428/5?u=lagapides

https://www.cisco.com/c/en/us/td/docs/security/firepower/migration-tool/migration-guide/ASA2FTD-with-FP-Migration-Tool/b_Migration_Guide_ASA2FTD_chapter_00.html

ASA to Firepower migration

ARP - determining the next hop MAC address

ARP - promiscuous mode

ARP - what is Proxy ARP

ARP table default timeout

ARP table

ASA - ASDM Cipher security levels

ASA - ASDM

ASA - AnyConnect Management VPN Tunnel

ASA - Clientless VPN

ASA - Crypto key size for Version 9.16

ASA - IKE proposal parameters

ASA - RADIUS common password

ASA - Using FQDN in an ACL for VPN split tunnelling

ASA - VTI VPN and MSS

ASA - crypto hardware processing

ASA - emulating an ASA device

ASA - multiple AnyConnect packages

ASA - multiple VPNs between the same endpoints

ASA - number of crypto maps per interface

ASA - object group protocol vs service

ASA - split-tunnel-policy command

ASA - using FQDN in an ACL

ASA CTM ipsec poll ctl DU_IOCTL_RESUME_POLL ioctl failed error

ASA Contexts operate as separate virtual devices

ASA DDoS protection

ASA DMZ

ASA ECMP static routing

ASA Manual NAT and Auto NAT

ASA NAT control

ASA NAT port forwarding multiple ports to same IP

ASA NAT with DHCP assigned IP address on the  outside interface

ASA NAT with multiple inside subnets

ASA Site-to-Site IKEv1 IPSec VPN recv errors

ASA Static one to one NAT on a range of addresses

ASA Troubleshoot HTTP and ASDM access

ASA VPN with overlapping IP address spaces

ASA active-standby failover preemption

ASA and Firepower reimaging

ASA crypto map and tunnel group preshared keys

ASA group policies

ASA implicit rule

ASA limit CLI and ASDM access to specific users

ASA packet processing algorithm

ASA prerequisites for high availability

ASA redirect IP SLA messages to log buffer

ASA redundant interface

ASA security levels

ASA syslog logging in multiple context mode

ASA troubleshooting IPSec

ASA tunnel-group

ASA understanding version numbers

ASA what triggers an active-standby failover

ASA won't respond to pings from different subnet

Anycast

Automation - Ansible connection plugins

BFD - intervals and timers

BFD - with multiple routing protocols

BFD echo mode and operation details

BFD how an administrative change differs from a failure

BFD one-arm echo

BGP - 4-byte ASN Backward Compatibility

BGP - AFI and SAFI

BGP - AS_Path filtering use cases

BGP - AS_SET and AS_CONFED_SET are deprecated

BGP - Accumulated IGP metric

BGP - Atomic Aggregate Attribute

BGP - Attributes and path selection

BGP - Autonomous System (AS)

BGP - Autonomous System Number

BGP - BGP Algorithm within confederations

BGP - Discontiguous Autonomous Systems

BGP - ECMP for specific prefixes

BGP - End-of-RIB marker

BGP - FSM - Active state

BGP - Finite State Machine (FSM)

BGP - Flowspec

BGP - Graceful Restart Mechanism

BGP - Handling Multiple Communities on a Single Route

BGP - IGP-BGP redistribution best practices

BGP - Labeled Unicast

BGP - Large BGP communities

BGP - Leaking more specific routes

BGP - Loop Prevention

BGP - MED vs AS Prepending

BGP - Multipath Attribute Prerequisites

BGP - Network Layer Reachability Information (NLRI)

BGP - Next Hop Address Tracking vs Route Dampening

BGP - Outbound Route Filtering

BGP - RRs vs confederations

BGP - Synchronization Rule

BGP - TCP Peering Session Process

BGP - The BGP Table

BGP - Why is MED non-transitive

BGP - aggregate-address command in action

BGP - aggregate-address default route

BGP - aggregate-address with a single subnet

BGP - auto-summary best practices