- Avaya filed Chapter 11 bankruptcy twice, in 2017 and again in 2023, and now puts its investment behind large-enterprise CX products rather than legacy on-premises IVR platforms.
- Enterprises running Avaya Aura, IP Office, or Avaya Contact Center have four realistic paths forward, from staying on reduced support to migrating fully to a cloud CCaaS platform.
- Amazon Connect and Google's CCAI Platform (built on Dialogflow CX) are the two most common migration destinations for Avaya IVR estates.
- A manual Avaya-to-cloud migration typically takes 6 to 12 months. AI platform-led migrations complete the same scope in 30 to 45 days.
- A structured IVR migration checklist covering discovery, design, build, test, and cutover is what prevents dropped calls and lost self-service containment along the way.
There Is No Single Shutdown Date
Avaya end of life in 2026 doesn't mean a single shutdown date. It means declining support quality after two Chapter 11 bankruptcies pushed Avaya to redirect investment toward large-enterprise CX products and away from legacy on-premises IVR platforms like Avaya Aura and IP Office.
Avaya end of life (EOL) is the point at which Avaya stops actively developing, patching, or fully supporting a specific IVR or contact center release, leaving customers on minimal or paid legacy support.
This guide covers exactly where Avaya stands in 2026, what its bankruptcy history means for your contract and support quality, and the concrete migration paths, including timelines most vendors won't volunteer, for moving your IVR to Amazon Connect or Google's CCAI Platform.
What Avaya End of Life Actually Means in 2026
Avaya hasn't announced one hard end-of-life date for its product line. Instead, it runs a rolling support model that quietly de-prioritizes older releases.
- Avaya IP Office gives full support only to its most recent releases. Older releases fall back to Basic Support only, with no major upgrades and no onsite support (Phonewire, 2026).
- Since its 2023 bankruptcy, Avaya's public strategy has centered on the Avaya Experience Platform and "Avaya Infinity," both built for large-enterprise customer experience, not small-business on-premises telephony (Phonewire, 2026).
- In November 2025, reports of company-wide voluntary redundancy signaled further cost-cutting, even though Avaya still serves over 90% of Fortune 100 organizations (UC Today, 2025).
- In February 2025, Avaya restricted its Cloud Office contact center product for accounts under 200 seats, pushing smaller customers toward alternatives (The Register, 2025).
Your specific Avaya release, not some company-wide announcement, is what actually determines how much runway you have left. That's worth checking before you plan around a date that doesn't exist.
Avaya Bankruptcy: What It Means for Customers
Avaya filed for Chapter 11 bankruptcy protection twice, first in January 2017, then again on February 14, 2023, and both times it emerged as a private company rather than shutting down.
- The 2023 filing cut Avaya's total debt from roughly $3.4 billion to about $800 million, due in 2028, backed by $780 million in new financing (Reuters, 2023).
- Avaya said during the 2023 filing that customers and partners would keep being served without interruption (Reuters, 2023).
- The restructuring forced deep cost cuts, slower product development, and a strategic pivot toward the Avaya Experience Platform for large enterprises (Carolina Digital Phone, 2024; Phonewire, 2026).
- Industry analysts, including Zeus Kerravala of ZK Research, have suggested that continued cost-cutting could be positioning Avaya for another ownership change (UC Today, 2025).
What Happens to Avaya Customers After Bankruptcy
Existing contracts and support agreements generally continue after a Chapter 11 filing, but three practical shifts follow every time.
- Support response times slow as Avaya narrows engineering resources toward its enterprise CX roadmap.
- Maintenance renewal pricing tends to rise as Avaya prioritizes higher-margin enterprise CX revenue.
- Specialized Avaya engineers and replacement hardware get scarcer and more expensive to source as time goes on.
Avaya End-of-Life Migration Options for Enterprises
Enterprises facing Avaya end of life have four realistic paths, ranked from lowest to highest long-term risk.
-
01Stay on current Avaya support.Lowest short-term cost, but risk grows as more releases drop to Basic Support only.
-
02Hire third-party Avaya maintenance.Firms such as Continuant have supported Avaya systems for decades and can extend hardware life while a migration gets planned (Continuant, 2022).
-
03Migrate voice and collaboration to a UCaaS alternative.RingCentral, Nextiva, and PanTerra Networks suit basic telephony, not complex contact-center IVR logic (CloudPhoneMatch, 2026).
-
04Migrate the contact center to a cloud CCaaS platform.Amazon Connect or Google's CCAI Platform, built on Dialogflow CX, are the two most common destinations for Avaya IVR and contact center estates (AWS Prescriptive Guidance, 2023).
For enterprises running Avaya Aura or Avaya Contact Center with complex, hand-built IVR logic, option four is the only path that both preserves existing business rules and modernizes the customer experience at the same time.
How to Migrate from Avaya to Amazon Connect
Migrating from Avaya to Amazon Connect follows a phased approach: discover the existing IVR estate, rebuild flows on Amazon Connect and Amazon Lex, run both systems in parallel, then cut over by business unit.
AWS's own prescriptive guidance recommends a multi-phased, business-unit-by-business-unit migration that keeps on-premises Avaya and the cloud environment integrated throughout the transition (AWS Prescriptive Guidance, 2023).
-
01Inventory every IVR flow, DID/DNIS number, vector, skill, and integration in the Avaya estate.
-
02Map each flow to Amazon Connect contact flows and Amazon Lex bots for natural-language self-service.
-
03Rebuild or port integrations (CRM, ticketing, and payment systems) to Amazon Connect APIs.
-
04Run Avaya and Amazon Connect in parallel, routing a small share of traffic to validate containment and accuracy.
-
05Cut over completely once containment and handle time match or beat the legacy baseline.
Manual rebuilds of this kind typically take AWS integration partners several months per business unit, because every vector and integration is mapped and coded by hand (AWS Prescriptive Guidance, 2023). Platform-led approaches automate flow discovery and generation, which is why AI-native migration platforms can complete comparable scope in weeks instead of months.
How Long Does an Avaya to Google CCAI Migration Take?
A traditional Avaya-to-Google CCAI migration takes 4 to 9 months for a mid-size contact center, depending on IVR complexity and integration count.
- Google's CCAI Platform unifies Dialogflow CX virtual agents, omnichannel routing, and agent assist into one deployment, which cuts the vendor-coordination time you'd otherwise spend stitching together separate tools (Google Cloud, 2024).
- Timelines stretch when Avaya vectors use nested logic, custom VXML, or nonstandard integrations that need to be reverse-engineered before they can be rebuilt in Dialogflow CX.
- Every additional month a legacy IVR stays live compounds cost: a contact center handling 100,000 calls a month typically pays $6 to $12 per live-agent call versus $0.25 to $0.50 per AI-resolved interaction (Aumne AI, 2026).
Migration timeline comparison
| Migration approach | Typical timeline | Best for |
|---|---|---|
| Manual SI-led rebuild | 6 to 12 months | Small, low-complexity IVRs |
| Consulting-led hybrid | 4 to 9 months | Mid-size estates with vendor support |
| AI platform-led migration | 30 to 45 days | Complex, high-volume IVR estates |
AI-generated migration platforms shorten this window by ingesting the entire Avaya estate automatically instead of documenting it by hand. Aumne ACT, for example, delivered an 8-month enterprise migration scope in 42 days for one Africa Telecom deployment (Aumne AI, 2026).
Avaya IVR Migration Checklist
A complete Avaya IVR migration checklist covers five phases: discovery, design, build, test, and cutover.
- Export every IVR flow, vector, and skill from Avaya Aura or Avaya Contact Center.
- Document all DID/DNIS numbers and their current routing destinations.
- List every integration point: CRM, workforce management, payment gateway, ticketing system.
- Capture baseline metrics: average handle time, containment rate, and call volume per flow.
- Decide which flows migrate as is, which convert to conversational AI, and which get rebuilt entirely.
- Choose the target platform (Amazon Connect, Dialogflow CX, or both) based on existing cloud investment.
- Define success metrics up front: containment rate, AHT, CSAT, and cost per contact.
- Rebuild or auto-generate flows on the target platform.
- Test every flow against real call scenarios, including edge cases and failure paths.
- Validate every integration end to end before live traffic touches the new platform.
- Run legacy Avaya and the new platform in parallel with a small share of live traffic.
- Monitor containment, AHT, and error rate against baseline for at least one full business cycle.
- Cut over completely only once the new platform matches or beats legacy performance.
Start with the discovery phase, done for you
Aumne ACT ingests your Avaya estate automatically and returns a full flow, DID and integration inventory in 48 hours.
Not a Deadline, but No Case for Waiting
Avaya's two bankruptcies didn't end the company, but they did end the case for waiting on legacy IVR investment. Enterprises still running Avaya Aura or IP Office in 2026 face rising support costs and shrinking specialist availability, not a hard deadline, which makes proactive migration the lower-risk choice.
If your IVR logic is complex and hand-coded, start with an as-is migration to Amazon Connect or Dialogflow CX to preserve business rules before layering in conversational AI. This is precisely the gap Aumne ACT was built to close: it automates the discovery and flow-generation work that normally stretches an Avaya migration to 6 to 12 months, delivering the same scope in 30 to 45 days at a fixed fee, without losing a single Vector or routing rule along the way.
Read next: Avaya Migration Options in 2026