Quick Take
Quick Take: An ASA refresh is two quotes, not one. Price a support renewal and a Threat Defense migration against the same inventory sheet, because the cheaper column often hides a support cliff, an unpriced FMC, or migration labor nobody costed. Settle that fork before any chassis PID is requested.
Renew vs Migrate — The First Gate
Quick Answer: Renew when ASA still clears feature needs and support life through go-live. Migrate when you need Threat Defense, FMC ops, or a longer hardware runway (3100/4200/220/6100 class). Dual-quote both columns on the same ASA inventory — brand loyalty without a dated support cliff is CapEx theater.
Pair this RFQ template with the Secure Firewall 10.0 hardware/FMC update, product peers such as Secure Firewall 4245, and the multi-vendor renewal SKU bundle trap. Competitive pressure from Fortinet/Palo paths belongs in a separate dual-vendor column — not as a silent swap mid-ASA RFQ.
BENQUAN GLOBAL LIMITED supplies Cisco Secure Firewall and ASA migration packages with cutover-aware RFQ support — request a free firewall BOM risk assessment.
| Signal | Lean renew ASA | Lean migrate to FTD |
|---|---|---|
| Support life | Clear past go-live + buffer | Cliff inside planning horizon |
| Threat / IPS | ASA + separate stack OK | Need integrated Threat Defense |
| Ops model | CLI / ASDM acceptable | FMC / SCC standardization |
| Hardware age | Capacity OK, spare path OK | Need new appliance class |
Do not renew blindly
A cheap ASA support renewal that expires mid-project forces emergency hardware RFQs. Write the support end date next to every line before finance signs.
Appliance and FMC Peer Map
Quick Answer: Peer ASA by firewall/VPN throughput, interface density, HA, and multi-context needs — not by “next model number.” Common FTD landings are Secure Firewall 1200, 3100, and 4200 Series; FTD 10.0 also adds 220 and 6100 options. Always price FMC (or cloud-delivered management) as a first-class BOM line.
| ASA posture | Directional Secure Firewall peer | RFQ note |
|---|---|---|
| Branch / small edge | 1200 Series or Secure Firewall 220 | Confirm VPN and port mix |
| Campus / mid enterprise | 3100 Series | HA pair + throughput headroom |
| Data center / high throughput | 4200 Series (e.g. 4245) / 6100 | Clustering / multi-instance if needed |
| Management | FMC appliance or cdFMC | Event rate + device count |
For 10.0-era hardware and FMC x800 positioning, see the Secure Firewall 10.0 update. For a concrete 4200-class datasheet-style peer, see 4245 specs.
Secure Firewall Migration Tool — What to Price
Quick Answer: The Migration Tool converts supported ASA configs toward Threat Defense managed by FMC — it is not a free one-click estate swap. Price extract, interface mapping, unsupported-feature hold-backs, pilot validation, and cutover windows. Unsupported objects left as “later” become go-live blockers.
Must-include labor
Config capture (show running-config / live connect), interface remap, ACL/NAT review, VPN/crypto-map validation, FMC deploy rehearsal, and rollback owners.
Hold-back rule
Any feature the tool cannot migrate cleanly stays on a hold-back list with a named method (rebuild, alternate path, or stay-on-ASA until redesigned). Do not bury hold-backs inside Batch-1 cutover.
Pilot first
Migrate one non-critical site or HA pair before campus edge. Prove Migration Tool output and ops runbooks before CapEx for the full estate is consumed.
Licenses and SKU Traps
Quick Answer: FTD quotes fail when hardware lands without matching threat, URL, Malware, or VPN subscription tiers. Match live ASA entitlements to target Secure Firewall license SKUs line-by-line — the same trap pattern as multi-vendor renewals. Chassis PDFs without license columns are incomplete RFQs.
- List current ASA/AnyConnect/RA-VPN entitlements
- Map to Threat Defense base + threat / URL / malware / other required tiers
- Confirm FMC license / device count headroom
- State Smart Licensing / Smart Account readiness on the RFQ
- Refuse quotes that omit subscription years or mix Essentials-style downgrades silently
See also Firewall renewal SKU bundle trap for the general renew-vs-downgrade pattern across vendors.
ASA → FTD RFQ Checklist
Quick Answer: Attach ASA inventory, renew-vs-migrate decision, target appliance + FMC peers, license SKUs, Migration Tool scope, pilot site, HA/VPN blackout windows, ATP dates, and rollback criteria. Ask vendors to price hardware, licenses, and migration labor against that package — not against a single “replace ASA Friday” slogan.
- ASA inventory (model, code, throughput, VPN, HA, support end)
- Written renew column and migrate column on the same sheet
- Target Secure Firewall model options + interface/NM needs
- FMC / cdFMC path with device and event capacity
- License / subscription SKUs with term years
- Migration Tool scope + unsupported hold-back list
- Pilot site and production batch calendar
- HA / VPN / change-window owners named
- Dated ATP for appliances and critical optics/transceivers
- Rollback / dual-path criteria before wipe of ASA
Frequently Asked Questions
Quick Answer: Dual-quote renewal and migration against one inventory sheet. The Migration Tool converts supported features but leaves unsupported objects, complex VPN maps and interface remaps needing validation labor. Peer ASA units to the 1200, 3100, 4200, 220 and 6100 families by capacity, and always price FMC alongside threat licenses.
Renew only when support life and features still clear go-live. Migrate when you need Threat Defense, FMC ops, or a longer hardware runway. Dual-quote both on one inventory sheet.
No. Supported features convert; unsupported objects, complex VPN maps, and interface remaps need validation labor. Price hold-backs and a pilot — do not assume a one-click estate swap.
Peer by throughput, VPN, HA, and ports. Common landings are 1200, 3100, and 4200 Series; 220 and 6100 appear on FTD 10.0 shortlists. Confirm against a current Cisco sizing matrix.
Inventory, renew-vs-migrate columns, appliance + FMC, license SKUs, Migration Tool scope, cutover windows, HA/VPN test plan, and dated ATP.
Send the ASA inventory and go-live via Free Compatibility & Delivery Risk Assessment or email info@benquan.hk. You receive renew vs Secure Firewall options with schedule-aware ATP notes from a global free-port hub.
Key Takeaway
Key Takeaway: Send vendors one package: the ASA estate with support end dates, both decision columns, candidate 1200/3100/4200 peers, FMC or cloud-delivered management, subscription tiers with term years, and a named hold-back list. Reject any reply that quotes chassis without licenses, cutover labor, or a dated ATP.