Why Symposium customers waited
Nortel’s contact-centre line (Symposium Call Center 6.0, Contact Center 7.x, CCMS) was deeply embedded in Saudi enterprise contact centres serving banking, telco, hospitality, and government. The platforms ran reliably, the agent training was valuable, and the cost of disrupting customer-facing operations was always high. Each year, the case for “another year of Symposium” was easier than the case for migration.
Then 2026 arrives. Avaya’s support for Symposium platforms is winding down to end-of-support windows. Hardware components are unobtainable. The agents trained on Symposium are mostly retired. The companies that built Symposium-specific applications (custom IVR scripts, reporting templates, WFM integrations) have moved on. The case for migration is now stronger than the case for waiting.
This piece walks through the realistic paths forward.
The agent training reality
Symposium agents have years of muscle memory. The terminal interface, the keyboard shortcuts, the soft-phone integration patterns — all are deeply ingrained. Migration requires retraining, and the productivity hit during the transition window is real.
Mitigations: choose a target platform with similar workflow patterns where possible; deliver structured training programmes (not just “here’s a video”); preserve agent shortcuts and quick-keys where the new platform allows configuration; phase the migration by team or shift to limit concurrent productivity disruption.
The organisations that handle this well budget 4-8 hours of training per agent and an additional 20-30% productivity buffer for the first 3-4 weeks post-cutover. Those that don’t see customer service quality dip noticeably during transition.
Migration target platforms
Five platforms dominate the modern contact-centre landscape:
Avaya Aura Contact Center (formerly Nortel Enterprise Solutions) — the direct Nortel-to-Avaya path. Avaya inherited the platform, continues development. Strongest feature parity with Symposium; minimum agent retraining. Best fit if also migrating PBX to Avaya.
Cisco UCCE (enterprise) / UCCX (mid-market) — Cisco’s contact-centre platforms. UCCE handles 1000+ agent deployments; UCCX handles up to 400. Strong integration with Cisco UCM and Webex. Best fit for Cisco-anchored deployments.
Mitel MiContact Center — Mitel’s contact-centre platform with strong hospitality and mid-market specialisation. Tighter integration with MiVoice. Best fit for hospitality and mid-market.
Microsoft Dynamics 365 Customer Service + Teams — Microsoft’s modern approach: Dynamics 365 for the CRM and case management, Teams for the calling and collaboration layer. Best fit for organisations standardising on Microsoft.
Genesys Cloud CX — pure-play contact-centre cloud platform. Strong analytics, WFM, and AI integrations. Best fit for contact-centre-led organisations not anchored to a specific PBX vendor.
The choice depends on the related PBX decision, the agent count, the regulatory requirements (SAMA recording, NCA controls), and the appetite for cloud vs on-premise.
Reporting and analytics continuity
Symposium’s reporting depth (CCMS reports, ad-hoc query capability, custom report development) is deep. Modern platforms approach reporting differently — dashboard-led, with API access for custom report development.
Migration consideration: catalogue every report Symposium produces, map each to the new platform’s reporting capability, build any custom reports needed before cutover. Operations teams who lose specific Symposium reports without warning don’t trust the new platform — even if the data is technically available, just in a different format.
Recording continuity
Saudi regulated industries (SAMA-aligned banking, healthcare, government) have call-recording obligations. Symposium typically integrates with recording platforms like NICE or Verint. The new platform must preserve:
- Recording trigger logic (which calls get recorded)
- Recording retention duration
- Recording search and retrieval interface
- Compliance audit trail
Migration of historical recordings (those already captured on Symposium-era recording infrastructure) typically goes to compliance archive rather than the new platform — preserving records for retention without forcing a complex format conversion.
WFM integration paths
Workforce management integration (Aspect, NICE WFM, Verint WFM, Genesys WFM) — the schedules, adherence tracking, forecasting — needs migration planning. Most modern WFM platforms support multiple contact-centre platforms, so the WFM stays and the contact-centre changes around it. Verify integration support before locking in target contact-centre.
Phased migration approaches
Three migration patterns work for Symposium replacement:
Big-bang cutover — risky but fastest. Single weekend or holiday window. Only suitable for very small contact centres with simple operations.
Phased by team or queue — most common for mid-market and enterprise. Migrate one team or queue at a time, run parallel for 2-3 weeks, then move next team. Total project: 3-6 months for medium-sized centres.
Phased by site — for multi-site contact centres. Migrate site-by-site, with backup routing during each transition. Total project: 6-12 months for multi-site enterprises.
Customer experience during migration
The customer-facing risk is non-trivial. Calls dropping, IVR menus working differently, agents struggling with new tools — all visible to customers. Mitigations: keep both platforms running with parallel call routing during waves, monitor customer complaints and call abandonment rates daily, and prioritise customer-facing operations recovery if metrics dip.
Get help with your Symposium migration
For a vendor-neutral Symposium migration assessment, book a discovery conversation. We deliver a written platform recommendation, agent-impact analysis, and phased migration plan. Pair with unified communications, Microsoft Teams, and VoIP installation for integrated delivery.