Genesys Engage to Genesys Cloud migration

A Genesys Engage to Genesys Cloud migration starts from a platform that is usually powerful, heavily customised and run by several specialist teams. Engage, known earlier as PureEngage, grew over many Framework releases, and a typical estate combines SIP Server or T-Servers, Universal Routing Server and Orchestration Server, Genesys Voice Platform, Workspace Desktop Edition, Genesys Info Mart and a long list of back-end integrations. Much of its behaviour lives in strategies, configuration objects and attached data that only a few people fully understand. Our leadership has worked in contact centre technology since 1984, including Genesys Framework estates, so QVCCS knows where that behaviour hides and plans the migration around finding it.

The timing is set by Genesys. Its end-of-life announcement for Engage on-premises and subscription products ends full-year renewals of maintenance and subscription terms on 31 December 2027, ends all renewals on 30 November 2028, and ends maintenance and support on 31 December 2028. Subscription licences stop working after that date; perpetually licensed products can still run, but without maintenance or support. Genesys supports the move with its Genesys Cloud Advantage Plan, which includes planning workshops and agent and technical training, subject to Genesys terms. QVCCS turns those dates into one shared plan for contact centre leaders and architects, with waves, owners and decisions agreed before any configuration starts.

On Engage, calls arrive at routing points and a strategy decides what happens next. Older estates use strategies built in Interaction Routing Designer and run by Universal Routing Server; newer ones use SCXML workflows built in Composer and run by Orchestration Server, often both side by side. On Genesys Cloud, numbers are assigned to Architect inbound call flows, in-queue flows control the waiting experience, and common module flows hold reusable logic that Engage teams kept in subroutines. Schedules, lists and business rules become schedule groups, data tables and data actions. We trace every routing point, strategy and subroutine into the migration inventory, so each behaviour is carried across deliberately or retired by agreement.

Targets need the same care. Engage strategies select agents through skill expressions, agent groups and virtual queues, and many estates hold hundreds of virtual queues created as much for statistics and reporting as for routing. On Genesys Cloud the queue is both the routing and the reporting object, with ACD skills, proficiency ratings and bullseye routing to widen the pool of agents over time. Our consultants rationalise rather than copy, working with planners and supervisors on a structure they can manage. Workspace Desktop Edition plug-ins and customisations are replaced with the Genesys Cloud agent workspace, scripts, CRM integrations or the Embeddable Framework, each one documented in an interface contract with its error handling agreed.

Self-service and reporting complete the picture. Genesys Voice Platform runs VoiceXML applications, usually built as Composer callflows, that collect digits, recognise speech, play prompts and query back-end systems. On Genesys Cloud these become Architect flows, with data actions for lookups and virtual agents where conversational self-service makes sense; we keep the prompt list and dialogue design so callers hear what they expect. Reporting often spans Stat Server, Genesys Info Mart and Genesys CX Insights, with feeds into a wider data warehouse. We agree a report parity list with the people who use those reports, rebuild each one with Genesys Cloud performance views, dashboards or data exports, and reconcile definitions before go-live.

Voice connectivity shapes the whole programme. Some Engage estates terminate carrier trunks on SIP Server through session border controllers; others sit on top of a PBX through a T-Server. Genesys Cloud offers Genesys Cloud Voice, where Genesys is the carrier, BYOC Cloud for your own carrier's SIP trunks, and BYOC Premises with Edge devices in your own sites. Our IT Systems, Telecoms & SIP Engineers survey carriers, SBCs, dial plans and network, then recommend the option that fits. During the migration we connect Engage and Genesys Cloud with SIP trunks, passing the customer data agents need in SIP headers, so calls can transfer in either direction while agents move team by team.

Numbers move last. Our number porting plan schedules each port with your carrier or Genesys against a cut-over wave, with test calls on every number straight after it moves. Recordings held in Genesys Interaction Recording or a third-party recorder are either kept in a searchable archive until their retention period ends or moved with their metadata, an approach we agree early with your compliance team. Agent equipment changes too: many teams move from Workspace SIP Endpoint or desk phones to WebRTC in the browser, which brings new network, firewall and headset requirements. Our site, network and telephony readiness survey covers each of these before QVCCS schedules the first wave.

Discovery comes first and goes deep. We audit the Engage configuration, including routing points, strategies, Composer projects, virtual queues, agent groups, skills, GVP applications and every integration, then hold workshops with the administrators and supervisors who run the operation day to day. Each finding enters a migration inventory with an owner, a priority and a target approach, and is carried into the Requirements Traceability Matrix. We do not rely on automatic conversion of strategies or callflows: Genesys itself advises mapping business outcomes rather than remapping old tools. So we agree, journey by journey, where to keep parity and where to transform, and record each decision in the design decision log before the High-Level Design is written.

We then muster the team from our own bench around your estate: an Enterprise Solution Architect who knows Engage Framework estates from the inside, a Solution Architect for the HLD, LLD and interface contracts, an IT Systems, Telecoms & SIP Engineer for trunks, coexistence and porting, Senior Developers for Architect flows and data actions, a Business Analyst for reporting and processes, and test leads for SIT and UAT. QVCCS takes collective responsibility for the outcome, backed by the whole practice through design authority and peer review. We build to the Low-Level Design under our engineering standards, use CX as Code for repeatable configuration, and trace every system integration test back to the Engage behaviour it replaces.

Cut-over runs in waves, scheduled well ahead of the 2028 dates so a delayed wave never meets an expired licence. Each wave has entry and exit criteria, a rehearsed runbook, test calls straight after the change and a rollback plan that can point numbers and routing back to Engage. Our remote go-live command centre and virtual floor-walking support agents and supervisors through their first shifts. Role-based training prepares agents used to Workspace Desktop Edition for the Genesys Cloud agent workspace, and gives Engage administrators, who are used to Genesys Administrator and Composer, a confident start in Genesys Cloud administration and Architect.

After the last wave, hypercare continues until the operation is stable and the Engage servers, databases and licences can be retired on your terms. Support then follows your Genesys Cloud CX consumption model: SLA-based support, up to 24x7x365 where you contract it with QVCCS, or alongside your provider's support as the specialist change and escalation layer. Many Engage teams are used to building their own capability through custom code, and on Genesys Cloud that energy moves to the Platform API, data actions and AppFoundry rather than server maintenance. We then help you add digital channels, predictive routing, virtual agents and agent assist on a platform that improves continuously.