Genesys Engage on premises: security patches, end of support and moving to cloud

Genesys first announced the end of life of Genesys Engage on-premises and Engage subscription products to customers on 11 March 2024. The announcement sets three dates. Full-year renewals of perpetual licence maintenance end on 31 December 2027; after that, renewals are shorter and must end by 31 December 2028. All renewals, of maintenance and of subscription terms, end on 30 November 2028. And on 31 December 2028, maintenance and support end for every Engage premises perpetual and subscription product.

What happens next depends on how you licensed Engage. Genesys states that subscription licences will not function after 31 December 2028. Perpetual licences keep working, but they are no longer maintained or supported, and after that date Genesys can no longer rehost or reconfigure perpetual licence files, so moving servers or changing capacity becomes difficult. Genesys also notes that earlier product-specific end-of-life announcements remain in effect, which is why many components reached the end of support well before 2028.

Until the end of maintenance, Genesys says it will provide minimal releases of the Engage software. The announcement lists what those releases cover: compatibility with operating environments, critical security issues with no workaround, as Genesys assesses them, and bug fixes with no workaround at Genesys's discretion, with critical bugs analysed through the end of maintenance. It lists nothing beyond that, so plan on security fixes being reserved for the critical cases rather than a steady stream of hardening.

That matters for the searches we see most, such as security updates and patches for SIP Server, or CVE fixes for the rules engine. A vulnerability rated below critical, or one with a workaround, may not produce a release at all. For components already past their own end of support, no release will come. Your security team needs to know which case each server falls into, and that starts with an accurate inventory of what you run.

Genesys publishes an end-of-life table for its on-premises products and components, and it is worth reading line by line against your own estate. Several components that appear in our clients' searches reached end of support before the Engage-wide date. E-mail Server 8.1 reached end of support on 31 October 2024. Genesys Rules System 8.1, and the Rules Development Tool, on 30 April 2025. SIP Server and Network SIP Server 7.6 and 8.0 on 30 April 2025. Management Framework, versions 6.5 to 8.1, also on 30 April 2025.

The table lists many more: Interaction Server 8.5, Universal Routing Server 8.0, Orchestration Server 8.0, Outbound Contact Server 8.0, Genesys Voice Platform 8.5, Genesys Info Mart 8.1 and Genesys Pulse 8.1 all reached end of support on 31 October 2024; Genesys Administrator on 30 October 2025; and Composer 8.1.5 reaches it on 15 November 2026. Versions not listed separately, such as current SIP Server 8.1 releases, fall under the Engage-wide end of support on 31 December 2028. Check your exact versions against the table rather than the product name, because the answer often changes between 8.1 and 8.5.

Most organisations cannot move a large Engage estate overnight, so the practical question is how to run it safely in the meantime. The National Cyber Security Centre is clear that unsupported software should ideally not be used, and that continuing is a risk to manage rather than a safe option. Its guidance on obsolete products describes how to reduce that risk: strip servers down to essential services, limit their exposure with firewalls and network zoning, strengthen logging, monitoring and alerting, and plan replacement, preferring cloud services that shift much of the patching burden to the provider.

For an Engage estate we turn that into a short programme. Inventory every server, component and version, and map each to Genesys's end-of-life table. Keep the operating systems and databases underneath within their own vendors' support, because Genesys's minimal releases cover compatibility, not your Windows or Linux patching. Keep SIP Server behind session border controllers, never directly on the internet. Restrict administrative access to the few people who need it. And agree with your security team how a critical Genesys advisory will be assessed and applied, before you need it.

1. Inventory every Engage component and version, and map it to Genesys's end-of-life table
2. Keep operating systems, databases and Java runtimes within their vendors' support
3. Keep SIP Server behind session border controllers and segment the contact centre network
4. Limit administrative access and log it
5. Agree how critical advisories are assessed and applied, and who decides
6. Set a migration date that leaves time before 31 December 2028

On Genesys Cloud CX the patching question largely disappears from your side. Genesys describes its continuous delivery model: instead of releasing large batches of changes two or three times a year, it releases small batches continuously, backed by tens of thousands of automated tests a day and a tested rollback plan. Patches and security updates are among the changes it delivers that way, and Genesys says no one is locked into a specific version: every customer runs the latest.

Your responsibilities change rather than vanish. You still manage who has access, how integrations are secured, what data you record and keep, and the network and devices agents use. Genesys publishes security bulletins on highly publicised security issues and their impact on the platform, so your security team has one place to check. And there are no servers, operating systems or Engage components to keep within support.

The dates leave less room than they appear to. If you renew perpetual maintenance, the last full-year renewal ends on 31 December 2027, and a large Engage migration has a lot to fit in: discovery, design, integrations, testing and a cut-over in waves, each scheduled so that a delayed wave never meets an expired licence. How long that takes depends on the estate, so we size it in discovery and work backwards from your renewal and licence dates. Start earlier if you rely on components that are already unsupported, or on integrations with their own end dates, such as the Gplus Adapter for Salesforce.

Genesys says Engage customers are eligible to migrate to Genesys Cloud CX, and runs a migration programme with planning workshops, migration guidance and training support; terms change over time, so ask Genesys or your partner for the current offer. The Engage announcement also mentions that Engage customers can try Genesys Cloud CX for free for up to 12 months, which is a sensible way to build and test before committing a cut-over date.

There are three ways to move, and most programmes combine them. A single cut-over moves everything at once and suits smaller, simpler estates. Moving in waves, by team, site or line of business, suits larger estates and limits the risk of each change. Coexistence keeps Engage and Genesys Cloud CX connected by SIP trunks while the waves run, so calls and customer data can pass between them and transfers work in both directions until the last team moves.

Whichever path you choose, do not convert strategies and callflows mechanically. Genesys itself advises mapping business outcomes rather than remapping old tools: routing points, URS strategies, Composer projects and GVP applications become Architect flows, queues and data actions designed for how the business works today. That is also the moment to retire customisations that only existed to work around the old platform.

A question we see often, in search and in conversations, is which cloud contact centre offers the smoothest migration path from Genesys Engage or Cisco. The honest answer is that a smooth move comes from the plan more than the platform. For Engage customers, Genesys Cloud CX keeps familiar concepts, such as skills, queues and routing strategies, and a migration programme from the same vendor, but it is still a new platform to design and build, not an upgrade.

Cisco Unified Contact Center Enterprise estates face their own dates and choices, which we cover in a companion guide. In both cases the deciding factors are the same: how much routing and IVR logic you carry, how tightly agents depend on the desktop and CRM integration, what your telephony looks like, and how much time is left before support ends. We are Genesys Cloud CX specialists, so we say that plainly, and we help you compare against your own requirements.

QVCCS leadership has worked in contact centre technology since 1984, and Engage estates are familiar ground: SIP Server and T-Servers, URS and Orchestration Server strategies, GVP, Workspace Desktop Edition, Info Mart and the integrations around them. We start with an inventory mapped to Genesys's end-of-life table, so your security team knows exactly where it stands, then build a migration plan with waves, coexistence and rollback.

Every delivery team member holds, or is completing, Genesys Cloud certification, and we work remotely unless agreed otherwise. Our Genesys Engage migration page describes how we run the work, and our case studies show the same method on large estates.