NetApp end of support and ONTAP lifecycle dates: what they mean and what to do next
Every NetApp system and every ONTAP release has a support clock. Knowing where yours sit decides when you need to refresh, which upgrade path is open to you, and how much negotiating room you have. This guide sets out how NetApp lifecycle dates work, the ONTAP support dates by release, which older platforms stop at which ONTAP release, and your realistic options at end of support. C4C is an official NetApp partner, disclosed up front.
NetApp hardware gets new ONTAP feature releases for two years after end of availability, then patch releases for three more years, so end of support usually lands about five years after end of availability. Each ONTAP release gets three years of full support, two of limited support and three of self service. Several widely deployed systems, including the AFF A300 and FAS8200, are listed by third party maintenance providers as reaching end of support on 30 November 2026. Plan the refresh a year ahead of the date, not in the last quarter, because time is what gives you options.
C4C is an independent technology consultancy and an official NetApp partner. We supply, implement and support NetApp, with hardware break fix support from NetApp as normal for enterprise arrays. Nick Watson and Paul Smith spent over a decade at EMC selling enterprise arrays to finance, banking and telcos, in the same market as NetApp, so we know how these refreshes are sold and where the room is. We also partner with Dell, HPE and VAST Data and are tied to none. Talk to us about your refresh.
How does NetApp end of availability and end of support work?
NetApp manages hardware in three stages after a platform stops being sold. Its own knowledge base sets out the periods:
- End of availability (EOA). The date the platform can no longer be ordered.
- Feature release period. “2 years after EOA date for ONTAP hardware.” New ONTAP releases still support the platform.
- Patch and fix release period. “3 years following the 2 year Feature Release period ... This period ends at the End of Support (EOS) date, typically 5 years after the EOA date.”
NetApp's own worked example is the AFF A700s: end of availability on 15 November 2021, end of the feature release period on 30 November 2023, and end of support on 31 December 2026. Source: NetApp KB, modified 21 March 2026.
Which ONTAP release does my older NetApp system stop at?
Once a platform leaves the feature release period, new ONTAP releases stop supporting it. NetApp lists the release from which each older platform is no longer supported, so the platform stays on the release before it.
| Platform | Not supported from |
|---|---|
| AFF A700, FAS9000, FAS500f | ONTAP 9.19.1 |
| AFF A300, FAS8200 | ONTAP 9.17.1 |
| AFF A320, AFF A700s | ONTAP 9.15.1 |
| AFF A200, FAS2650, FAS2620 | ONTAP 9.12.1 |
| AFF8000, FAS8000, FAS2500 | ONTAP 9.9.1 |
| IOM6 disk shelves | ONTAP 9.16.1 |
Source: NetApp docs, ONTAP hardware systems no longer supported, dated 4 August 2026.
How long is each ONTAP release supported?
NetApp says “New ONTAP releases are entitled to full support for 3 years.” After that comes limited support in years four and five, with technical support, root cause analysis and downloads but no new patch releases, and self service in years six to eight, with documentation only. Source: NetApp docs, when to upgrade ONTAP.
| ONTAP release | End of full support | End of limited support | End of self service |
|---|---|---|---|
| 9.19.1 | 31 July 2029 | 31 July 2031 | 31 July 2034 |
| 9.18.1 | 31 January 2029 | 31 January 2031 | 31 January 2034 |
| 9.17.1 | 30 September 2028 | 30 September 2030 | 30 September 2033 |
| 9.16.1 | 26 February 2028 | 31 January 2030 | 31 January 2033 |
| 9.15.1 | 31 July 2027 | 31 July 2029 | 31 July 2032 |
| 9.14.1 | 31 January 2027 | 31 January 2029 | 31 January 2032 |
| 9.13.1 | 30 June 2026 (passed) | 30 June 2028 | 30 June 2031 |
| 9.12.1 | 28 February 2026 (passed) | 28 February 2028 | 28 February 2031 |
Source: NetApp KB, ONTAP software version support dates, modified 10 October 2026. If you are on 9.12.1 or 9.13.1, you are already in limited support and receive no new patch releases.
When does support end for common NetApp systems?
NetApp publishes end of support dates per model on its Support Site, behind a login, so check your own serial numbers there. The dates below are as published by third party maintenance providers, except the AFF A700s, where we use NetApp's own date.
| System | End of support |
|---|---|
| FAS8000 series | 31 January 2023 (passed) |
| AFF A200, FAS2620, FAS2650 | 31 May 2024 (passed) |
| AFF A300, FAS8200, AFF A220 | 30 November 2026 |
| AFF A700s | 31 December 2026 (NetApp KB) |
| AFF A700, FAS9000 | 30 November 2028 |
| FAS2720 | 30 September 2029 |
| AFF A400, AFF A800, FAS8300 | 30 November 2030 |
As published by third party maintenance providers, for example the Park Place Technologies EOSL list; confirm on the NetApp Support Site. The AFF A700s date is from the NetApp KB, modified 21 March 2026.
If your systems are on the 2026 line, the refresh conversation should already be under way. Talk to us about timing it so the deadline does not decide the price.
How does a NetApp tech refresh work?
NetApp documents three ways to move to new controllers: “You upgrade either by relocating aggregates or moving volumes (both nondisruptive procedures), or by moving the storage (a disruptive procedure).” Source: NetApp docs, choosing a controller upgrade procedure.
- Move volumes. Add the new nodes to the cluster, move the volumes and network interfaces across, then remove the old nodes. Non disruptive, and the usual route when the new system brings new disks.
- Aggregate relocation. A replacement procedure that moves aggregates to new controllers. Also non disruptive.
- Move the storage. Moving the disk shelves to the new controllers. Disruptive, so it needs a planned window.
One rule shapes the plan: nodes in a cluster may not differ by more than four ONTAP releases. NetApp's example is that 9.8 can run alongside 9.12.1 but not alongside 9.13.1. If your old system is several releases behind, the upgrade sequence matters as much as the hardware choice.
Can I move to NetApp in the cloud instead?
For some workloads, yes. Each of the big clouds offers ONTAP based storage, which keeps your data services and replication familiar:
- Amazon FSx for NetApp ONTAP: a fully managed service built on ONTAP. Source: AWS documentation.
- Azure NetApp Files: an Azure native, first party file storage service. Source: Microsoft documentation.
- Google Cloud NetApp Volumes: a fully managed, cloud based data storage service. Source: Google Cloud documentation.
- Cloud Volumes ONTAP: ONTAP software running in the cloud as a software only appliance. Source: NetApp documentation.
Whether it is cheaper depends on capacity, performance and how long you will run it. We model it on the same basis as a refresh, so the comparison is real.
What are your options at end of support?
- Refresh to current NetApp systems. Often the lowest risk path for an estate built on ONTAP data services, snapshots and replication, and the migration can be non disruptive.
- Move some or all of it to cloud ONTAP services. Sensible for workloads already heading to the cloud.
- Move to a different platform. Sometimes the right answer, for example where performance needs, scale or cost point elsewhere. Our Dell vs NetApp vs Pure comparison covers the trade offs, and we will say so if another platform fits better.
- Extend with third party maintenance for a period. Covered below, with its trade offs.
Is third party maintenance a sensible bridge?
For a stable system near the end of its life, third party maintenance can buy time at lower cost while you plan the refresh. Providers commonly quote large savings against vendor support. The trade offs are real, and worth weighing honestly:
- You stay on your current ONTAP release. NetApp says an active support contract is required to download software from its support site, and that versions which have reached end of support are no longer available to download. Source: NetApp KB.
- AutoSupport stops opening cases. NetApp says AutoSupport messages will not generate support cases once the support entitlement has expired, and resume after renewal. Source: NetApp KB.
- A different escalation path. Serious faults are handled by the provider rather than NetApp engineering.
- Returning to NetApp support costs more than staying. NetApp’s support terms say a customer reinstating lapsed support pays the support fees that would have been due during the lapse, any applicable reinstatement fee and the new support term, so price the return before you lapse.
Used deliberately, as a bridge with an exit plan, it can be the right call. Used as a default, it tends to delay a decision that only gets harder. We talk it through with you either way.
How should you plan a NetApp refresh?
- Inventory the dates. Hardware end of support per system, the ONTAP release each runs, and its software support stage.
- Start twelve months out. Enough time to compare options, run a proper proof of concept if needed, and negotiate without a deadline.
- Size from real usage. Capacity growth, performance and data reduction measured on your data, not assumed.
- Compare like for like. Refresh, cloud and alternative platforms on the same fully loaded basis, including migration effort and support. Our storage migration cost guide sets out the cost lines.
- Choose the migration route and the team: C4C, NetApp professional services, or a mix with your own people.
NetApp support ending? Let’s plan the refresh.
We will help you work out what to refresh, when, and onto what, then supply and implement it with you. Independent, and partnered with NetApp, Dell, HPE and VAST Data, so the recommendation follows your estate.
Prefer email? Reach us directly at hello@c4cgroup.co.uk.
Frequently asked questions
When does NetApp support end for my hardware?
NetApp sets an end of availability (EOA) date when a platform stops being sold. New ONTAP feature releases continue to support it for two years after EOA, then patch releases for three more years, ending at the end of support (EOS) date, typically five years after EOA. NetApp publishes the exact dates per model on its Support Site, which needs a login.
When does support end for the AFF A300 and FAS8200?
Third party maintenance providers list 30 November 2026 as the end of support date for the AFF A300 and FAS8200. Confirm the date for your serial numbers on the NetApp Support Site. Both platforms are not supported from ONTAP 9.17.1 onwards, so they cannot move beyond the release before it.
How long is an ONTAP release supported?
NetApp says new ONTAP releases are entitled to full support for three years. Years four and five are limited support, with technical support and downloads but no new patch releases, and years six to eight are self service, with documentation only.
Can I keep running a NetApp system after end of support?
Yes, the system keeps working, but you lose NetApp hardware support, new ONTAP releases and fixes. Some organisations extend older systems with third party maintenance for a period while they plan a refresh. It can save money, but it usually means staying on your current ONTAP release, and you should plan the exit before relying on it.
Is a NetApp tech refresh disruptive?
It does not have to be. NetApp documents two non disruptive routes: adding new nodes and moving volumes and network interfaces across before removing the old nodes, or relocating aggregates to new controllers. Moving the storage itself is the disruptive option. Nodes in a cluster may not differ by more than four ONTAP releases.
Should we refresh NetApp or move to something else?
Decide on fit and full cost, not habit. A current NetApp system is often the lowest risk path for an estate built on ONTAP data services, and cloud ONTAP services are an option for some workloads. For others a different platform fits better. We partner with NetApp, Dell, HPE and VAST Data and are tied to none, so we compare them on your numbers.
Is third party maintenance a good idea for NetApp?
It can be, for a stable system near the end of its life that does not need new features. Providers commonly quote large savings against vendor support. The trade offs are no new ONTAP releases, a different escalation path for serious faults, and uncertainty over the cost of returning to NetApp support later. We talk through the pros and cons honestly.
Can C4C help with a NetApp refresh?
Yes. C4C is an official NetApp partner. We supply, implement and support NetApp, with hardware break fix support from NetApp as normal for enterprise arrays. The refresh can be run by us, by NetApp professional services, or as a mix with your own team, whichever is best for you.