Avaya Aura to Cloud Migration 2026

The clock that's actually ticking

Source: Avaya Support EoMS Notice. Avaya emerged from Chapter 11 on May 1, 2023 under Apollo Global Management and Brigade Capital. Avaya has not publicly committed a final end-of-support date for the entire Aura family — only release-level EoMS notices have been published. Long-tail Aura support beyond Aura 10.3 is unverifiable from public sources.

Aura customers have three paths:

1. Stay on-prem — upgrade to Aura 10.2 or wait for 10.3 (industry-reported October 2026). Buys time; doesn't solve the strategic question.
2. Move to Avaya Infinity — Avaya's official cloud destination, positioned private/on-prem/hybrid rather than pure public-cloud SaaS. Pricing not disclosed.
3. Migrate to a third-party CCaaS — NICE, Genesys, Five9, Amazon Connect or Cisco Webex Contact Center.

Avaya Infinity Platform — the official destination

Announced and "available today" April 22, 2025 (Avaya Newsroom).

Architecture: Unified orchestration over "systems, data, AI, and workflows." Event-driven engine. No-code/low-code journey design. AI-agnostic via Model Context Protocol (MCP) — Avaya describes itself as among the first major CX platforms to adopt MCP for production agentic-AI orchestration; joined the Linux Foundation's Agentic AI project.

Hosting: Marketed across private, on-prem, and hybrid. Avaya's PR explicitly emphasizes "private, on-prem and hybrid" rather than pure public-cloud SaaS — a notable contrast with NICE, Genesys and Five9 which are all multi-tenant cloud-native.

Features at launch: Unified voice + digital channel threading, Tandem Care (human/AI co-handling), AI Performance Index (APIx), Databricks-based Enterprise Data Activation, RBAC, audit trails, BYOK (Avaya Infinity product page).

Ecosystem at launch: Verint CX Automation full integration; Sabio as evolution partner.

Disclosed gaps:

• Pricing not publicly disclosed
• Specific certification status at launch is not disclosed publicly — HIPAA, FedRAMP, PCI-DSS, SOC 2 Type II are not publicly confirmed
• GA-vs-roadmap delineation in Avaya's own marketing is unclear

Migration commitments: Avaya talks about "backward-compatible paths" and "phased modernization" for CC Elite / Aura customers but does not publish a formal Aura→Infinity migration SLA or timeline.

Market context: Avaya leads on-prem revenue but install base is dispersing

Per Metrigy's 1Q25 Customer Experience MetriCast, Avaya leads dedicated contact-center platform vendors with 35.7% of global revenue, ahead of Genesys (13.8%) and Cisco (9.4%) (Metrigy MetriCast 2025, CX Today).

The 35.7% revenue share reflects historic on-prem dominance and ongoing maintenance, not new-logo wins. The 2025 Gartner CCaaS Magic Quadrant (September 8, 2025) named five Leaders — NICE, Genesys, Five9, Talkdesk, Amazon Connect — and Avaya did not appear in the Leaders quadrant. The market signal is consistent: Aura is a renewal-and-defend platform; new contact center buys are landing in the Leaders quadrant.

Third-party destinations: top 5

1. NICE CXone

Why customers choose it: highest Ability to Execute in 2025 Gartner CCaaS MQ; native WEM stack; FedRAMP Moderate; healthcare, financial services and government Industry Solutions; AI ARR $328M FY2025 (+66% YoY).

Vendor migration program: NICE Avaya Migration Solutions ships CMS Report Parity Mapping and Call Flow Export tools. NICE claims customers can "go-live in as little as 60 days" for certain profiles. NICE also acquired Cognigy in 2025, adding agentic-AI for migration prospects.

Typical migration window: 4-9 months for mid-market Aura estates; 12-24+ months for global enterprises. See the implementation timeline pillar.

Best for: enterprise Aura shops that want a single-vendor WEM + AI + CCaaS stack with federal-eligible compliance. See the NICE review and NICE vs Genesys comparison.

2. Genesys Cloud CX

Why customers choose it: 11-time consecutive Gartner CCaaS Leader; broadest AI Experience platform; FedRAMP Moderate; AI ARR >$250M Q2 FY2026.

Vendor migration program: industry-reported as offering 12-24 months of reduced pricing, professional services credits, and training waivers for Cisco UCCE, Avaya Aura and Aspect migrations (CX Today). Genesys reportedly closed "50 seven-figure CCaaS deals in a single quarter" with ARR reaching ~$2.5B by early 2026.

Typical migration window: 6-12 months for mid-market; 12-18 months for enterprise.

Best for: enterprise Aura shops with complex multi-region routing and Salesforce-anchored CRM. See the Genesys review.

3. Five9

Why customers choose it: deepest outbound DNA in CCaaS (since 2001); published per-concurrent-user pricing ($119-$229); $100M Enterprise AI ARR.

Vendor migration program: dedicated Avaya migration toolkit covering both Avaya IP Office and Aura. Five9 explicitly positions itself as "seat-count agnostic" in direct contrast to Avaya's 200-seat AXP minimum — a real differentiator for sub-200-seat Aura shops.

Typical migration window: 4-9 months mid-market; 9-15 months enterprise.

Best for: outbound-heavy Aura shops (collections, sales, lead-gen) and mid-market Aura estates priced out of Avaya's AXP Public Cloud minimum. See the Five9 review and best dialer for collections.

4. Amazon Connect

Why customers choose it: 3rd-time consecutive Gartner CCaaS Leader; per-minute pricing ($0.018-$0.038); FedRAMP Moderate + AWS GovCloud High; bundled AI (Lex, Comprehend, Transcribe).

Vendor migration program: less formalized than Five9's or NICE's — customers typically work through AWS Partners or system integrators. Industry case studies report typical mid-market Connect migrations in 5-week sprints.

Best for: AWS-anchored Aura shops with internal engineering teams; CAT-surge-heavy P&C insurance with seasonal call volume spikes. See the Amazon Connect review.

5. Cisco Webex Contact Center

Why customers choose it: Cisco maintains parallel on-prem (UCCE/PCCE) and cloud (Webex Contact Center) SKUs — attracts Aura customers wanting hybrid optionality similar to Infinity's pitch; FedRAMP Moderate (Webex Contact Center for Government).

Best for: Cisco-anchored Aura shops; Webex-heavy organizations. Note Cisco was downgraded Challenger (2024) → Niche Player (2025) in Gartner MQ. See the Webex Contact Center review.

What actually goes wrong in Aura migrations

Verifiable customer pain points (per NICE Avaya migration page and CX Today):

1. CMS report parity — historical agent-state and KPI definitions in Avaya CMS rarely map 1:1 to cloud reporting. NICE explicitly markets parity mapping because the gap is real.
2. Call flow / IVR rebuild — vector/VDN logic in Communication Manager often must be re-authored in the new platform's flow designer rather than mechanically converted.
3. Recordings and retention — moving years of call recordings (often Verint or NICE-attached) while preserving legal hold and PCI redaction is a frequent stall point.
4. Telephony porting and SIP carrier untangling — Aura's SBC/trunking topology is rarely simple; cutover risk to 24/7 operations is the most-cited migration hesitation.
5. Integration rebuild — Salesforce, ServiceNow and custom CTI screen-pops typically need rewriting against the new platform's SDK.
6. Agent retraining — UI/UX shift from Avaya one-X / Workspaces is a measurable productivity hit during ramp.
7. Dual-vendor period — running Aura plus the new platform during phased cutover compounds maintenance + subscription costs.

Migration cost reality

Industry-reported ranges (not Avaya-published):

• Professional services for CCaaS migrations: 50-200% of Year-1 subscription cost (InflectionCX CCaaS Migration Guide)
• Hidden fees (PS, migration, configuration) add 20-40% on top of advertised license cost; advertised price ≈ 60% of true 5-year spend (InflectionCX TCO Guide)
• Dual-vendor overlap: small CC 6-12 weeks; mid-market 3-6 months; enterprise 6-12 months
• Aberdeen-cited 5-year TCO 25-45% lower than on-prem post-migration
• Migration-incentive packages from vendors like Genesys: industry-reported 12-24 months of reduced pricing plus PS credits

Run the TCO calculator to model the new-platform 3-year cost. Add the dual-vendor overlap line manually based on your phasing.

Buyer playbook

1. Decide on-prem vs cloud first. Avaya Infinity's private/on-prem/hybrid positioning keeps you in the Avaya ecosystem; NICE/Genesys/Five9/Amazon Connect move you to multi-tenant cloud.
2. If staying with Avaya: confirm Aura 10.2 vs waiting for 10.3 timing against your refresh budget.
3. If leaving Avaya: vendor selection matters less than migration program depth. NICE and Five9 ship formal Aura migration tooling; Genesys provides commercial incentives; Amazon Connect is system-integrator-led.
4. Budget the dual-vendor period explicitly — 6-12 months of overlap is the default assumption for enterprise migrations.
5. CMS report parity is the hidden tax — surface it in the RFP early. NICE's tooling is the most-documented; other vendors require custom build.
6. Reservation about Avaya Infinity at GA: pricing not disclosed, certifications not disclosed, GA scope unclear. Defer commitment until Avaya publishes specifics or wait for second-half 2026 product maturity.

For deeper context: CCaaS implementation timeline, Avaya vendor review, vendor shortlister.

Bottom line

Avaya Aura 10.1 EoMS January 1, 2026 forces the decision. Aura 10.2 buys time; Avaya Infinity is the official cloud destination but with disclosed gaps (pricing, certifications, GA scope) that many enterprise buyers will want resolved before commitment. Third-party destinations — NICE CXone (deepest Aura migration tooling), Genesys Cloud CX (broadest platform), Five9 (seat-count agnostic, outbound depth), Amazon Connect (AWS-anchored, per-minute economics), Cisco Webex Contact Center (hybrid optionality) — each address a different Aura subsegment. Dual-vendor overlap of 6-12 months and migration cost of 50-200% of Year-1 license are the default assumptions; vendor incentive packages can shift the math.