Nortel to Genesys Cloud migration

A Nortel to Genesys Cloud migration usually begins with a switch room that has outlived its manufacturer. Meridian 1 and Communication Server 1000 PBXs, with Symposium Call Center Server or Contact Center Manager on top, still carry calls for many organisations, often on hardware kept alive by third-party maintainers and spare parts from decommissioned sites. Nortel's enterprise business passed to Avaya in 2009, and Avaya has confirmed that CS 1000 Release 7.6 software reached End of Manufacturer Support in 2019, with no further design support or new fixes. Earlier Meridian releases are long past their manufacturer's end of sale. The platform may still run well, but every year it becomes harder to change, repair and staff.

The people are often the bigger risk. The engineers who wrote the scripts, built the ACD-DNs and tuned the overlays are retiring, and much of what the estate does lives in their heads rather than in documents. Networks are changing too: Openreach plans to move all traditional phone lines in the UK to digital by 31 January 2027, so estates that still depend on traditional lines into the PBX need a plan for their trunks either way. Our leadership has worked in contact centre technology since 1984 and knows Nortel estates first-hand. QVCCS uses that experience to turn an ageing platform into a dated, owned migration plan before anything forces the timing.

On a Nortel contact centre, calls arrive at a controlled directory number, or CDN, and the switch waits for Contact Center Manager Server to tell it what to do. The Master script runs first and hands calls to primary and secondary scripts, which check time of day, play treatments, give calls a priority and queue them to skillsets. On Genesys Cloud, numbers are assigned to Architect inbound call flows, in-queue flows decide what callers hear while they wait, and time-of-day and holiday rules become schedules and schedule groups. Night treatment, overflow and intrinsics that test agents logged in or calls waiting are rebuilt as flow logic. We map every CDN and script statement in the migration inventory, so each behaviour is carried across or retired by agreement.

Skillsets and agent priority per skillset become Genesys Cloud queues, ACD skills and proficiency. We recommend rationalising rather than copying: long-lived estates gather skillsets created to work around routing or reporting limits, and network skillsets that spread calls across sites. On Genesys Cloud, one cloud organisation can hold agents from every site in the same queues, so many of those workarounds simply fall away. Our consultants work with planners and supervisors to agree the queue and skill design, decide where bullseye routing should widen the pool of agents over time, and map activity codes to wrap-up codes. Older ACD-DNs that still route calls on the switch without Symposium are inventoried too, so nothing that customers dial is forgotten.

Reporting, voicemail and integrations need the same attention. The real-time displays and historical reports in Contact Center Manager Administration are what your managers trust, so we agree a report parity list with them and rebuild each one with Genesys Cloud performance views, dashboards or data exports to your own analytics. Meridian Mail or later voicemail mailboxes move to Genesys Cloud voicemail, with greetings and retention rules agreed first. Scripts that exchange data with host systems through Host Data Exchange, and CTI links built on Meridian Link Services or Communication Control Toolkit, are redesigned around Genesys Cloud data actions and the Platform API. Each interface is written up as an interface contract, with error handling agreed before anything is built.

Voice connectivity is decided early. Genesys Cloud Voice makes Genesys your carrier and supports porting existing numbers, BYOC Cloud brings your chosen carrier's SIP trunks into Genesys Cloud, and BYOC Premises keeps media on Edge devices at your sites. Our IT Systems, Telecoms & SIP Engineers survey the switch, its trunks, dial plan and network, then design how the PBX and Genesys Cloud will talk. A CS 1000 can use its SIP signalling gateways; an older Meridian with digital trunks may need a media gateway or session border controller to present SIP. That coexistence link lets calls transfer in both directions, so extensions, receptionists and back-office teams stay on the PBX while the contact centre moves.

Numbers move last. We build a number porting plan with your carrier or Genesys, tie each port to a cut-over wave and test every number as soon as it lands. Where your trunks still run over traditional lines, we align porting with the move to digital, so the contact centre does not change twice. Recordings held in an ageing call recorder are kept in a searchable archive until their retention period ends, agreed early with your compliance team. Agent equipment changes too: digital and UNIStim desk phones usually give way to headsets and WebRTC, which brings new network, firewall and quality-of-service requirements. Our site, network and telephony readiness survey covers all of this before the first wave is booked.

Discovery is where a Nortel migration is won. We export or transcribe every script, CDN, ACD-DN, skillset, treatment, schedule and report definition, then walk through them with the people who still remember why each one exists. Overlay printouts, script listings and the habits of long-serving supervisors all feed a migration inventory, with an owner, a priority and a target approach for every item. That inventory flows into the Requirements Traceability Matrix. With it in place 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. Nothing important should depend on one engineer's memory during cut-over week.

We then muster the team from our own bench to fit your estate: an Enterprise Solution Architect who has worked on Meridian and Symposium platforms, an IT Systems, Telecoms & SIP Engineer for gateways, trunks and porting, Senior Developers for Architect flows and data actions, a Business Analyst for reports and processes, and testers for SIT and UAT. QVCCS owns the outcome end to end, 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 where repeatable configuration helps, and trace every system integration test back to the Nortel script statement or switch behaviour it replaces, including failure paths and transfers across the coexistence link.

Cut-over happens in waves, never as one weekend gamble. Each wave has entry and exit criteria, a rehearsed runbook, test calls straight after the change and a rollback plan that can point CDNs and numbers back at the PBX if anything misbehaves. 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 Incalls keys and desk phones for the Genesys Cloud agent workspace, and supervisors learn the new queue and agent views before go-live rather than during it. Hypercare continues until the operation is stable and the business is ready to let the old platform go.

Decommissioning is planned as carefully as go-live. We confirm that no number, extension, alarm line or integration still depends on the switch, archive what must be kept, and help you retire the Meridian or CS 1000 cabinets and Symposium servers 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. With the hardware gone, attention turns to what the old estate could never do: digital channels, callbacks, virtual agents, predictive routing and agent assist, on a platform that improves continuously.