Nuance End of Life: IVR Dates and Migration Paths

At a glance

Nuance end-of-life dates, by how you bought it

This is the unusual part of the Nuance wind-down and the reason so many teams have the wrong date written down. There is no single published deadline that covers everyone. The binding date depends on whether you bought direct, through Cisco, through Avaya, through Genesys, on-premises or as a service.

Milestone	Date	Practical meaning
End of sale, Avaya Nuance Speech Suite five-year subscriptions	July 11, 2023	Avaya stopped selling five-year subscriptions of Vocalizer, Recognizer, and the associated Dialog Modules.
End of sale, Avaya Nuance Speech Suite three-year subscriptions	June 30, 2024	Same products, three-year terms. Avaya stated it could not sell subscriptions running past the support date.
End of sale, Nuance Enterprise hosted and on-premises licenses	August 9, 2024	New enterprise licenses stopped being sold direct. Existing contracts continued to their own terms.
Genesys Cloud deprecation announced	November 4, 2024	Genesys announced the retirement of its Nuance recognizer, text-to-speech, and Mix Bot integrations.
Last day to purchase system expansions, Avaya route	June 30, 2025	Already passed. No additional seats, ports, languages, or capacity can be bought for an existing Avaya Nuance estate.
End of orderability via Cisco Solutions Plus	June 30, 2025	Cisco announcement 1032157 closed ordering for NUANCE-SB and the NU-SUB subscription line, following an earlier notice covering the CVP-NUANCE and NUANCE-PB perpetual offers.
End of support, hosted Nuance offerings	December 2025	Already passed. Hosted speech services are no longer supported and cannot be extended by running old software locally.
End of manufacturer support, Avaya five-year subscription estates	June 30, 2026	Avaya’s published software support date for R11 Recognizer and R7 Vocalizer bought on five-year terms.
End of sustaining support, on-premises Dialog module	June 2026	The last supported window for on-premises Recognizer and Vocalizer on the direct route. After this, fixes stop even where the software keeps running.
End of life, Nuance-as-a-Service integrations in Genesys Cloud	May 31, 2027	Genesys’s published date for Nuance Recognizer as a Service, Nuance Text to Speech as a Service, and Nuance Mix Bot.
End of manufacturer support, Avaya three-year subscription estates	June 30, 2027	Extended from June 2026. Avaya’s revision note records Nuance pushing this date out for three-year subscription customers only.

This is why you have heard two different years. The 2026 and 2027 dates are both real. Avaya originally published June 2026, then revised its notice to record that Nuance had extended support to June 30, 2027 for three-year subscription customers only. Five-year subscription estates were left on the 2026 date. Ask your reseller or account team for your specific end-of-support date in writing, with the product and part numbers named, and plan against that rather than against the later date you would prefer.

Primary sources: Avaya’s End of Sale Notices for Nuance Speech Suite five-year subscription licenses (11-Jul-2023) and three-year subscription licenses (31-Mar-2024, revised 21-Feb-2024); the Cisco Solutions Plus bulletin Announcement of End of Orderability for Nuance ASR, TTS, Vocalizer, and Insights via Solutions Plus (ID 1032157); and the Genesys Cloud notice Deprecation: Nuance Recognizer as a Service, Nuance TTS, and Nuance Mix Bot. The August 2024 direct end-of-sale and the hosted and on-premises support dates were reported by CX Today and repeated across partner migration notices.

Scope

What is actually being retired

The wind-down covers the speech layer, not a contact-center platform. That distinction matters: your ACD, your routing, and your agents are not affected. The part that stops is the software that turns a caller's speech into text and text into a spoken prompt.

Component	What it does	Where you will find it
Nuance Recognizer	Grammar-based automatic speech recognition. The engine that understands "checking account" or a spoken account number.	On-premises, connected over MRCP. Sold in tiers, part numbers beginning NU-SUB-T3 and NU-SUB-T4.
Nuance Vocalizer	Text-to-speech, including the licensed voice personas that read your prompts.	On-premises and hosted. Part numbers beginning NU-SUB-VOC, including additional-voice licenses.
Dialog modules and grammars	Pre-built recognition packs for addresses, names, email, spelling, and adaptive dialog.	NU-SUB-UAB, NU-SUB-NANM, NU-SUB-EMAIL, NU-SUB-SPELL, NU-SUB-AGM, NU-SUB-AGE and their high-availability variants.
Dragon Voice for Recognizer	Neural recognition added on top of the Recognizer tiers.	NU-SUB-DRAG-T4 and variants.
Nuance Recognizer as a Service	The cloud recognition service used inside Genesys Cloud Architect bot flows.	Genesys Cloud integrations.
Nuance Text to Speech as a Service	The cloud text-to-speech engine selectable in Genesys Cloud Architect flows.	Genesys Cloud integrations.
Nuance Mix Bot	The integration that lets Architect message flows call a Nuance Mix bot.	Genesys Cloud integrations.
Nuance Insights	Reporting and tuning analytics bundled with the Cisco Solutions Plus offer.	Included under the NUANCE-SB top-level SKU.

Voice biometrics is a separate conversation. Nuance Gatekeeper and the security portfolio have their own lifecycle communications, and a bank that authenticates callers by voiceprint should treat that as a second project with its own dates rather than assume it is covered by the speech retirement.

The awkward part

Most affected organizations do not think they are Nuance customers

Nuance spent two decades as the speech engine other vendors resold. It was bought through Cisco Solutions Plus, through Avaya, and through Genesys, and it was installed underneath the IVR rather than in front of it. The invoice says Cisco. The support call goes to Avaya. Nobody on the current team necessarily remembers a Nuance decision being made.

Per Ottosson, CEO of Teneo.ai, described the installed base bluntly on the What's Up with Tech? podcast in November 2025: many enterprises still run press-one-two-three IVR, "and that's Nuance, which is end of life anyway," adding that Genesys customers in particular "used to have Nuance in most of their customers." That is a competitor talking, and it is worth reading as such. It is also an accurate description of where the software ended up.

Check for MRCP connections

Look at what your voice browser talks to. Cisco Unified CVP and the Virtualized Voice Browser, Avaya Aura Experience Portal and Voice Portal, and Genesys Voice Platform all reach a speech server over MRCP. Find the server on the other end.

Search your part numbers

Pull the last three years of Cisco, Avaya, and Genesys line items and grep for NUANCE-SB and anything beginning NU-SUB. Those are the SKUs Cisco closed to new orders on June 30, 2025.

Open your Architect flows

In Genesys Cloud, check which recognizer, which text-to-speech engine, and which bot integration each inbound call flow selects. The Nuance options are named in the Genesys deprecation notice.

Call your own main number

The least technical test and often the fastest. If the voice reading your prompts has been the same for ten years, it is probably a licensed Vocalizer voice, and it is in scope.

If you run Cisco contact-center software, read this alongside the Cisco UCCX end-of-life dates, because the 12.5 and 12.6 platform deadlines and the Nuance speech deadline are close enough together to be worth solving once rather than twice. The same logic applies to Avaya's Aura and Experience Portal lifecycle and to Genesys Engage.

Why you were probably never told

The notices exist. They were published unevenly, and none of them landed in an operations manager’s inbox.

Avaya told customers, publicly. Two End of Sale Notices sit on the Avaya support site, dated July 2023 and March 2024, naming Vocalizer, Recognizer, and the Dialog Modules by material code. They are genuine customer-facing documents, and they are also PDFs in a support portal that nobody browses for fun.
Cisco told partners, not customers. The Solutions Plus bulletin is stamped Cisco Partner Confidential and directs questions to a Microsoft mailbox. If the reseller who sold the system did not pass it on, the end customer heard nothing at all.
Genesys posted publicly, in a feed. The Genesys Cloud deprecation notice went out in November 2024 through the product announcements channel. Visible to anyone subscribed to it, invisible to everyone else.

Assume nobody on your team saw it. Notification was technically satisfied on every route and practically missed on most of them. The absence of an internal email is not evidence that you are unaffected.

The question everyone asks first

What still works, and what is already blocked

This is on-premises software running on your own servers, so the obvious question is whether the IVR keeps working and whether you can still change it. The short answer is yes to both, with three limits that matter more than the headline date.

You can change what it says

Call flows live in Cisco Unified CVP, Avaya Experience Portal, or Genesys Voice Platform, not in Nuance. Prompt wording, menu structure, routing logic, opening hours, and holiday messages all remain yours to edit.

You cannot change what it can do

Languages are licensed one at a time; the part numbers literally separate single-language from multi-language entitlements. Adding a language, a new voice, extra capacity, or a recognition fix requires a transaction with a vendor that has stopped transacting.

Expansion has already closed

On the Avaya route, June 30, 2025 was the last day to purchase system expansions. That date has passed. An estate that needs more seats or ports cannot buy them, which turns ordinary growth into a replacement project.

Older releases are already stranded

Avaya required customers running R10 Recognizer or R6 Vocalizer to upgrade to R11 and R7 before any renewal or expansion would be allowed. If you skipped that upgrade, you were out of options earlier than the published dates suggest.

Perpetual, subscription, or hosted decides how it ends

Three commercial models are in the field, and they fail in completely different ways. Establishing which one you hold is the single most useful hour you can spend on this.

What you hold	Where it came from	How it ends
Perpetual licenses	Direct, or Cisco Solutions Plus under CVP-NUANCE and NUANCE-PB.	Slow burn. The software keeps running unsupported. Nothing switches off; it simply becomes unfixable.
Subscription licenses	Avaya Nuance Speech Suite, and the Cisco NU-SUB annual-term line.	Hard stop. Entitlement ends with the term, and Avaya stated it could not sell subscriptions extending past the support date.
Hosted and as-a-service	Hosted Nuance offerings, and the Nuance integrations inside Genesys Cloud.	Switched off. There is no local software to keep running. Hosted support ended in December 2025.

Subscription estates do not get to run late. A perpetual estate that misses its migration date carries risk. A subscription estate that misses its date carries an outage. Find out which you are before you build the plan, not after.

Why it is not a simple swap

What actually breaks when the speech engine changes

Replacing a speech engine sounds like changing a dependency. In a mature IVR it is closer to replacing the part of the system that has absorbed the most tuning and the least documentation.

Grammars are not portable in practice. Recognizer uses grammar-based recognition, and years of hand-tuned grammars, weights, confidence thresholds, and n-best handling encode how your callers actually speak. A modern large-language-model recognizer does not consume those grammars in the same way, and a compatible MRCP engine will still need its own tuning pass.
The voice is a brand asset you do not own. Vocalizer voices are licensed. No other vendor can supply the identical voice, so every prompt your customers have heard for a decade will change on cutover. Either re-record with a chosen voice actor or synthesize consistently with a new engine, and decide deliberately rather than discovering it in testing.
Confidence and barge-in behavior shift. Different engines return different confidence scores and handle interruption differently. Flows that branch on confidence thresholds will behave differently even when recognition accuracy is nominally equal or better.
Compliance flows need re-certification. Anything that captures a card number, a date of birth, or a consent statement by voice has to be retested and re-signed-off, including recording, redaction, and PCI handling.
The tuning data may not survive. Recognition logs, utterance corpora, and Insights reporting are the raw material for tuning the replacement. Export them before entitlement lapses, not after.

Test against your own caller audio, not a demo. A speech engine that scores well on clean benchmark audio can perform noticeably worse on your traffic: telephony bandwidth, hold music bleed, accents in your market, and a caller reading a policy number from a crumpled letter. Recorded production calls are the only benchmark that predicts your result.

Decision point

Four realistic paths off Nuance

Swap the engine, keep the IVR

Replace Recognizer and Vocalizer with an MRCP-compatible recognizer and text-to-speech behind the same CVP, Experience Portal, or GVP front end. The fastest route to a supported state and the least disruptive to call flows. Buys a runway; does not modernize anything.

Move to the Microsoft cloud stack

The vendor-aligned path. Microsoft points customers to Azure AI Speech, Dynamics 365 Contact Center, and Copilot Studio. Note that there is no like-for-like on-premises replacement, so this is a deployment-model change as well as a product change.

Retire the IVR into a CCaaS platform

Rebuild self-service on the speech and bot services native to a cloud contact-center platform, and stop running a separate speech tier at all. Largest scope, but it removes the whole category of problem rather than deferring it.

Rebuild self-service as AI voice agents

Treat the deadline as the trigger to replace menu-driven containment with conversational handling. Highest ceiling and highest risk: the constraint is rarely the model, it is the integration to the systems that hold the answer.

The third and fourth options are the ones where a forced migration can pay for itself, and they are also where most of the disappointment lives. Vendors selling into this exact moment are candid about why. Pierce Buckley of Babelforce, speaking on the same podcast series in October 2025, put the failure mode on the data rather than the model: a deployable bot can still be "terrible, not because of the AI, but because of the data." Per Ottosson's version was shorter: "if it looks simple in an hour, it's gonna fail in a month." Our guide to contact center AI covers what separates the deployments that work from the ones that stall.

Whichever direction you choose, run it as a scored comparison rather than a renewal conversation. The contact center RFP template holds every bidder to the same requirements, and what CCaaS is explains the cloud model if part of the buying team is new to it.

Work backward from the deadline

A practical timeline to mid-2027

From August 2026, on-premises sustaining support has either just ended or is about to, and the final retirement is roughly nine to eleven months out. That is enough time for a controlled engine replacement and tight for a full self-service rebuild.

Now: establish your license model and your real date. Confirm whether you hold perpetual, subscription, or hosted entitlement, then get the end-of-support date for your exact products and material codes in writing from whoever sold them to you. Do not plan from an article, including this one.
Now: inventory and export. Capture every grammar, prompt, voice license, dialog module, recognition tuning parameter, MRCP endpoint, and Insights report while entitlement and the people who built them are still available.
September–November 2026: choose the destination. Decide between an engine swap, the Microsoft path, a CCaaS rebuild, or AI voice agents. Score them against your compliance, language, and integration requirements rather than a feature list.
November 2026–February 2027: build and tune. Stand up the replacement, port grammars or rebuild intents, select and apply the new voice, and tune against recorded production audio rather than scripted test calls.
February–April 2027: test and certify. Regression-test every flow, re-certify payment and consent handling, validate barge-in and confidence behavior, and confirm reporting continuity.
By April 2027: cut over in waves. Move by call flow or by line of business with rollback routing available, and leave the final weeks for stabilization rather than scheduling the last flow against the retirement date.

If that schedule is already tight for your estate, the honest move is to make it visible now. Sequence by call volume, stabilize text-to-speech first to protect prompts and menus, and finish recognition second. That order keeps the caller-facing experience stable while the harder work continues.

Budget lines

What a Nuance replacement actually costs

The license line is usually the smallest number in the project. Put these workstreams into every quote so proposals can be compared honestly:

Discovery and inventory. Finding every grammar, prompt, voice license, and MRCP dependency, particularly where the original implementer has left.
Grammar and intent rework. Porting, rebuilding, or replacing recognition logic, including the dialog modules that were bundled rather than bought explicitly.
Voice and prompt production. New voice selection, prompt regeneration or re-recording, pronunciation dictionaries, and brand sign-off.
Recognition tuning. Iterative tuning against production audio, which is the work most often left out of a fixed-price quote and most often overruns.
Integration and telephony. MRCP or API connections, SBC and media path changes, certificates, and failover behavior.
Testing and certification. Regression, load, disaster recovery, PCI and consent flows, accessibility, and business acceptance.
Parallel running. Two speech tiers live during phased cutover, with duplicated licensing and administration.

If the replacement also moves you to a cloud contact-center platform, the CCaaS pricing guide covers the recurring seat and consumption bands you will be quoting against. Start with a quick estimate of agents, call flows, and integrations.

FAQ

Quick answers

When is the Nuance end-of-life date?

There is no single date, and the two years you may have heard are both real. Avaya published June 30, 2026 as end of manufacturer support for estates bought on five-year subscriptions, then revised its notice to record that Nuance had extended support to June 30, 2027 for three-year subscription customers only. Genesys published May 31, 2027 for its Nuance-as-a-Service integrations. Hosted support ended in December 2025, and on-premises sustaining support on the direct route ends around June 2026. Because the binding date depends on your contract and how you bought the software, get your own date confirmed in writing and plan against the earliest one that could apply to you.

Which Nuance products are being retired?

The retirement covers the enterprise speech stack: Nuance Recognizer, the grammar-based speech recognition engine; Nuance Vocalizer, the text-to-speech engine and its voices; the Dialog module that packages them; the dialog modules and grammars sold alongside them, including US Address, North American Name, Email, Spelling, Nuance Adaptive Dialog Modules, and the Nuance Adaptive Grammar Engine; and the as-a-service equivalents, including Nuance Recognizer as a Service, Nuance Text to Speech as a Service, and Nuance Mix Bot.

How do I know if my contact center uses Nuance?

Many organizations own Nuance without a Nuance contract, because it was bought through Cisco, Avaya, or Genesys and sits underneath the IVR rather than in front of it. Check for MRCP connections from Cisco Unified CVP or Cisco Virtualized Voice Browser, from Avaya Aura Experience Portal or Avaya Voice Portal, or from Genesys Voice Platform. Check your Cisco Solutions Plus line items for the part number NUANCE-SB or any part number beginning NU-SUB. Check Genesys Cloud Architect flows for a Nuance recognizer, Nuance text-to-speech engine, or Nuance Mix bot. Finally, listen to your own main phone number: if the voice has not changed in a decade, it is very likely a Vocalizer voice.

Does the IVR stop working on the end-of-life date?

It depends entirely on your license model. Perpetual on-premises licenses usually keep running unsupported, so the risk is not a sudden stop but an unfixable one: no security patches, no new language or voice support, and no vendor help when an operating system, certificate, or MRCP dependency changes underneath it. Subscription licenses are different, because entitlement ends with the term and Avaya stated it could not sell subscriptions extending past the support date. Hosted and as-a-service components are simply switched off, with no local software left to run.

Can we still make changes to our IVR?

Yes, for the most part. The call flows live in Cisco Unified CVP, Avaya Experience Portal, or Genesys Voice Platform rather than in Nuance, so prompt wording, menu structure, routing logic, opening hours, and holiday messages all remain editable. What you cannot change is what the system is capable of. Languages are licensed individually, and adding a language, a new voice, extra capacity, or a recognition fix all require a vendor transaction that is no longer available. On the Avaya route the last day to purchase system expansions was June 30, 2025, so an estate that needs to grow cannot buy its way there.

Does it matter whether our Nuance licenses are perpetual or subscription?

It is the most important thing to establish. A perpetual estate that misses its migration date carries risk, because the software keeps running without support. A subscription estate that misses its date carries an outage, because entitlement ends when the term does. Avaya sold Nuance Speech Suite as subscriptions and Cisco sold both perpetual and annual-term lines, so two organizations running identical software can face completely different consequences on the same day.

What does Microsoft want Nuance customers to move to?

Microsoft points customers toward Azure AI Speech, Dynamics 365 Contact Center, and Copilot Studio. Through the Cisco Solutions Plus channel the named replacement offers were the hosted Nuance services, listed as Nuance Dialog as a Service and the hosted text-to-speech equivalent, rather than a like-for-like on-premises product. There is no on-premises Microsoft replacement that drops into an existing MRCP deployment unchanged.

Can I just swap the speech engine and keep my existing IVR?

Sometimes, and it is the fastest option when it works. Several vendors offer MRCP-compatible recognition and text-to-speech that can stand in for Recognizer and Vocalizer without rebuilding the call flows. The catches are grammar compatibility, recognition tuning that was accumulated over years, and the voice itself, since no other vendor can license the exact Vocalizer voice your customers currently hear. Treat an engine swap as a way to buy a supported runway, not as a substitute for deciding what the IVR should become.

How long does a Nuance IVR migration take?

Plan six to twelve months for a straight engine replacement in a stable IVR, and twelve to twenty-four months if you are also moving the IVR to a cloud platform or rebuilding self-service as AI voice agents. Grammar and prompt inventory, recognition tuning, regression testing against real caller audio, and compliance sign-off usually set the pace rather than the software installation.

Related guides

Nuance end of life: the speech engines under your IVR are being switched off.