Cisco to Genesys Cloud migration

A Cisco to Genesys Cloud migration rarely starts from a blank sheet. Unified Contact Center Enterprise, Packaged CCE, Unified Contact Center Express, Hosted Collaboration Solution and Webex Contact Center estates have often been extended for many years by capable teams, and each change left something behind: a routing script branch for a seasonal campaign, a peripheral variable that a CRM screen pop depends on, a supervisor report built for one regional manager. That accumulated knowledge is what makes the contact centre work, and much of it lives only in configuration. Our leadership has worked in contact centre technology since 1984, and QVCCS has carried Cisco customers to Genesys Cloud CX, so we plan the move around finding that knowledge before anything is rebuilt.

The reasons to move vary by platform. Customers on premises-based Cisco contact centres often face a version upgrade, a server or virtualisation refresh, or a maintenance renewal, and choose to spend that effort on a cloud platform instead. Customers already in the cloud on Webex Contact Center or a hosted service may want to consolidate onto one platform, or to adopt capabilities across digital channels, workforce engagement and AI in one place. Genesys Cloud is cloud-native and multi-region, so there is no hardware to refresh and new capabilities arrive continuously. Whatever the trigger, QVCCS turns it into one shared plan for contact centre leaders and architects, with waves, owners, contract dates and decisions agreed before configuration starts.

On Unified CCE and Packaged CCE, a call usually reaches Customer Voice Portal, a routing script built in Script Editor decides what happens next, and the caller hears prompts or self-service from micro-applications or Call Studio VoiceXML applications. Call variables and expanded call context variables carry data between script, IVR and desktop. On Genesys Cloud, numbers are assigned to Architect inbound call flows, in-queue flows control the waiting experience, schedules replace time-of-day nodes, and data actions call your systems through APIs. Scripts written in the Unified CCX Editor and flows built in Webex Contact Center Flow Designer map in the same way. We record every script node, application and variable in the migration inventory, so each behaviour is carried across or retired by agreement.

Routing targets need more thought than a one-to-one copy. Skill groups translate naturally into Genesys Cloud queues, while precision queues, which select agents by attributes and relax their criteria step by step as a call waits, have a close cousin in skills with proficiency ratings and bullseye routing, where each ring widens the pool of eligible agents over time. Many Cisco estates also carry skill groups created for reporting rather than routing, and moving those unchanged reproduces old complexity. Our consultants work with your planners and supervisors to rationalise queues and skills, map not-ready reason codes to presence statuses, and map wrap-up reasons to wrap-up codes. The outcome is routing your own team can read, report on and adjust.

Desktops and reporting are where agents and managers feel the change most. Finesse layouts often include gadgets that show customer details, launch CRM records or call internal tools. On Genesys Cloud, those become interaction widgets that display a web application beside the conversation, agent scripts that guide the call and capture data, or Genesys Cloud embedded inside the CRM itself. Each integration that used the Finesse or CTI interfaces is redesigned and recorded in an interface contract. Unified Intelligence Center reports are catalogued and agreed as a report parity list with the people who use them, then rebuilt with performance views, dashboards or exports to your own analytics, with any differences in how service level or abandonment are calculated explained before go-live.

Many organisations keep Cisco Unified Communications Manager for enterprise telephony while the contact centre moves, so coexistence is designed from the start. Genesys Cloud Voice makes Genesys the carrier, BYOC Cloud brings your own carrier's SIP trunks into Genesys Cloud over the internet, and BYOC Premises keeps media on Edge devices in your own sites. Our IT Systems, Telecoms & SIP Engineers review your carriers, session border controllers, dial plan and CUCM routing, then recommend the option that fits. During the migration we connect CUCM and Genesys Cloud with SIP trunks, so back-office staff on Cisco phones can still take transfers, and calls can move between the two contact centres in either direction while teams change over.

Numbers move only when the routing behind them has been proven. We build a number porting plan with your carrier or Genesys, align each port to a cut-over wave and test every number straight after it moves. Where a hosted service provider runs your Hosted Collaboration Solution, we plan trunks, numbers and data extracts with that provider so responsibilities are clear. Historical recordings, whichever recorder captured them, are either kept in a searchable archive until their retention period ends or moved with their metadata, as agreed early with your compliance team. Agent equipment is reviewed too: many teams move from Cisco desk phones to headsets and the WebRTC phone, which changes network, firewall and quality-of-service requirements, all covered by our site, network and telephony readiness survey.

Discovery comes first and is thorough. We audit the Cisco configuration, including call types, dialled numbers, routing scripts, skill groups, precision queues and attributes, CVP and UCCX applications, Finesse layouts and gadgets, and every CTI and CRM integration, alongside the CUIC report catalogue. Workshops with the people who run the contact centre day to day uncover the behaviour nobody has written down. Each finding is recorded in a migration inventory with an owner, a priority and a target approach, then carried into the Requirements Traceability Matrix. From there we agree, journey by journey, where to keep parity and where to transform, and record each choice and its reasoning in the design decision log before the High-Level Design is written.

We then muster the team from our own bench to suit your estate: an Enterprise Solution Architect who has worked through Cisco contact centre programmes, an IT Systems, Telecoms & SIP Engineer for CUCM coexistence, trunks and numbers, Senior Developers for Architect flows, data actions and interaction widgets, a Business Analyst for reports and processes, and test leads for SIT and UAT. Every delivery team member holds, or is completing, Genesys Cloud certification. 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 and Archy where repeatable configuration helps, and trace every system integration test back to the Cisco behaviour it replaces.

Cut-over runs in waves by site, team or number range, never as one large weekend change. Each wave has entry and exit criteria, a rehearsed runbook, test calls immediately afterwards and a rollback plan that can point numbers and routing back to the Cisco platform if something unexpected appears. Our remote go-live command centre and virtual floor-walking support agents and supervisors through their first shifts. Role-based training prepares people used to Finesse for the Genesys Cloud agent workspace, and supervisors learn the new queue and agent views before go-live, so nobody meets an unfamiliar dashboard for the first time while customers are waiting. Reports are compared side by side during the early waves, so leaders trust the new figures.

After the last wave, hypercare continues until the operation is stable, and the Cisco contact centre components can be decommissioned on your terms, while CUCM stays in place for as long as your wider telephony plan needs it. 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. With the move complete, attention turns to what the new platform makes possible. We help you add digital channels, predictive routing, virtual agents and agent assist, each delivered with the same discovery, design and testing discipline, so the migration becomes the starting point for steady improvement.