<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Migration ASA to FTD in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/migration-asa-to-ftd/m-p/5366242#M1124301</link>
    <description>&lt;P&gt;The primary tool for this transition is the Cisco Secure Firewall Migration Tool (FMT). To migrate an ASA 5545 to a new FTD 3120, your prerequisites include ensuring the ASA is running version 8.4 or later and that you have a target management platform—either an on-premises Firewall Management Center (FMC) or a Cisco Security Cloud Control (formerly Cisco Defense Orchestrator/CDO) tenant. In a production environment, the tool is highly effective for bulk-migrating complex objects, ACLs, and NAT rules, which are the most time-consuming manual tasks. However, it is not "plug-and-play" for everything; you should expect to manually verify and re-configure dynamic routing (OSPF/BGP) and Site-to-Site VPNs, as these often require manual mapping or post-migration tweaks to ensure traffic flow.&lt;/P&gt;</description>
    <pubDate>Fri, 30 Jan 2026 05:55:49 GMT</pubDate>
    <dc:creator>jim65richards</dc:creator>
    <dc:date>2026-01-30T05:55:49Z</dc:date>
    <item>
      <title>Migration ASA to FTD</title>
      <link>https://community.cisco.com/t5/network-security/migration-asa-to-ftd/m-p/5365509#M1124261</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;BR /&gt;Please suggest migration tool, prerequisite and how effective it is in production environment.&lt;/P&gt;&lt;P&gt;current : ASA5545&lt;/P&gt;&lt;P&gt;new : FTD3210 (Locally managed or Cisco Security cloud control managed, both option i want to explore).&lt;/P&gt;&lt;P&gt;also I want to know can we migrate configuration from FDM to Cisco security cloud control via any tool or by exporting and importing?&amp;nbsp;&lt;/P&gt;&lt;HR /&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 27 Jan 2026 12:08:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/migration-asa-to-ftd/m-p/5365509#M1124261</guid>
      <dc:creator>KayaaKashyap</dc:creator>
      <dc:date>2026-01-27T12:08:35Z</dc:date>
    </item>
    <item>
      <title>Re: Migration ASA to FTD</title>
      <link>https://community.cisco.com/t5/network-security/migration-asa-to-ftd/m-p/5365817#M1124277</link>
      <description>&lt;P&gt;Have you explored the Secure Firewall Migration Tool:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/site/us/en/products/security/firewalls/secure-firewall-migration-tool/index.html" target="_blank"&gt;https://www.cisco.com/site/us/en/products/security/firewalls/secure-firewall-migration-tool/index.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;This is the official documentation with all of the supported migration scenarios:&amp;nbsp;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/firepower/roadmap/fp_migration_tool_roadmap.html#Cisco_Concept.dita_d5eb5fda-f2b0-4240-b38d-4e258ccdc99c" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/firepower/roadmap/fp_migration_tool_roadmap.html#Cisco_Concept.dita_d5eb5fda-f2b0-4240-b38d-4e258ccdc99c&lt;/A&gt;&lt;/P&gt;
&lt;DIV id="bodyDisplay_3" class="lia-message-body lia-component-message-view-widget-body lia-component-body-signature-highlight-escalation lia-component-message-view-widget-body-signature-highlight-escalation"&gt;
&lt;DIV class="lia-message-body-content"&gt;
&lt;P&gt;&lt;EM&gt;Thank you for rating helpful posts!&lt;/EM&gt;&lt;/P&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Wed, 28 Jan 2026 13:28:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/migration-asa-to-ftd/m-p/5365817#M1124277</guid>
      <dc:creator>nspasov</dc:creator>
      <dc:date>2026-01-28T13:28:14Z</dc:date>
    </item>
    <item>
      <title>Re: Migration ASA to FTD</title>
      <link>https://community.cisco.com/t5/network-security/migration-asa-to-ftd/m-p/5366098#M1124295</link>
      <description>&lt;P&gt;Yeah you can use the FMT but like most automatic migration utilities there is always some manual items and confirmation. A migration like this is also a perfect time to perform a rule audit an clean up as needed. I'm sure your preferred Cisco partner would love to help you with a manual migration as well.&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jan 2026 16:15:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/migration-asa-to-ftd/m-p/5366098#M1124295</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2026-01-29T16:15:54Z</dc:date>
    </item>
    <item>
      <title>Re: Migration ASA to FTD</title>
      <link>https://community.cisco.com/t5/network-security/migration-asa-to-ftd/m-p/5366242#M1124301</link>
      <description>&lt;P&gt;The primary tool for this transition is the Cisco Secure Firewall Migration Tool (FMT). To migrate an ASA 5545 to a new FTD 3120, your prerequisites include ensuring the ASA is running version 8.4 or later and that you have a target management platform—either an on-premises Firewall Management Center (FMC) or a Cisco Security Cloud Control (formerly Cisco Defense Orchestrator/CDO) tenant. In a production environment, the tool is highly effective for bulk-migrating complex objects, ACLs, and NAT rules, which are the most time-consuming manual tasks. However, it is not "plug-and-play" for everything; you should expect to manually verify and re-configure dynamic routing (OSPF/BGP) and Site-to-Site VPNs, as these often require manual mapping or post-migration tweaks to ensure traffic flow.&lt;/P&gt;</description>
      <pubDate>Fri, 30 Jan 2026 05:55:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/migration-asa-to-ftd/m-p/5366242#M1124301</guid>
      <dc:creator>jim65richards</dc:creator>
      <dc:date>2026-01-30T05:55:49Z</dc:date>
    </item>
  </channel>
</rss>

