Why this question matters now
Meridian 1 was Nortel’s enterprise PBX platform. Saudi enterprises that bought Meridian in the 1990s and 2000s — banks, government agencies, large hospitality groups, healthcare networks — are mostly still running it. The hardware was overbuilt; the systems lasted longer than the company that made them. But the runway is finite. By 2026, every Meridian deployment in KSA is well past its design lifecycle. The question is not whether to replace, but with which platform.
Three modern targets dominate the Meridian replacement landscape: Avaya Aura, Cisco Unified Communications Manager (UCM) / Webex Calling, and Mitel MiVoice or MX-ONE. Each has a clear ideal-fit profile. This piece walks through them.
Avaya Aura as the Nortel-natural target
Avaya acquired Nortel’s enterprise solutions business in 2009. That history matters: Avaya inherited the Meridian roadmap, the engineering talent, and the customer base. Avaya Aura is positioned as the natural migration path for Meridian customers, and there are direct migration tooling and feature-mapping advantages.
Strengths: feature parity in many areas with Meridian (or close enough that change management is minimal), Avaya-direct migration tools, large installed base of Avaya engineers globally, mature contact-centre integration (Avaya Aura Contact Center, formerly NES), and continuing support roadmap.
Considerations: Avaya as a company has been through multiple bankruptcies and ownership changes; financial stability is a board-level concern for some Saudi clients. License complexity is non-trivial. Pricing in KSA tends to favour large enterprises over mid-market.
Best fit: organisations that prioritise minimum change management, value direct Nortel-to-Avaya migration tooling, and operate at sufficient scale for Avaya’s enterprise pricing model.
Cisco UCM / Webex Calling as alternative
Cisco’s UCM is a different architectural philosophy from Meridian — IP-native, deeply integrated with Cisco infrastructure, software-centric. For organisations migrating from Meridian, Cisco represents a more substantial change but pays back in integration with the broader Cisco ecosystem.
Strengths: strong integration with Cisco networking and security, robust contact-centre options (UCCX for mid-market, UCCE for enterprise), Webex Calling delivers SaaS pricing for cloud-preferred organisations, and the Cisco ecosystem (collaboration devices, video, networking) is unified.
Considerations: licensing is complex (UCM, Webex, Cisco Smart Licensing — multiple models in flight). Migration from Meridian requires more retraining than Avaya. Cost can be higher than Mitel for equivalent feature set.
Best fit: organisations already deeply Cisco-invested in networking and security, planning hybrid Microsoft Teams Phone deployments where Cisco is the on-premise anchor, or those wanting cloud-first via Webex Calling.
Mitel MiVoice / MX-ONE as alternative
Mitel sits between Avaya’s complexity and Cisco’s IP-native rebuild. MiVoice Business handles mid-market well; MX-ONE scales to large enterprises. Strong hospitality vertical specialisation. Active Mitel sub-distributor presence in Saudi Arabia (including Unifiedway).
Strengths: hospitality vertical leadership (PMS-integrated phone features, brand-standard hospitality deployments), contact-centre via MiContact Center, simpler licensing model than Avaya or Cisco, and active local KSA partner ecosystem. Cost typically lower than Avaya or Cisco for equivalent feature scope.
Considerations: smaller installed base than Avaya or Cisco globally. Some advanced enterprise features lag behind Avaya. International support footprint smaller than competitors.
Best fit: hospitality (resort and hotel groups, branded property operators), mid-market enterprises, contact-centre-heavy environments, and organisations valuing simpler licensing and lower TCO.
Decision matrix by environment
| Environment | Likely target | |—|—| | Saudi banking under SAMA, large enterprise, prioritising minimum change | Avaya Aura | | Cisco-anchored networking, hybrid Teams Phone plans | Cisco UCM / Webex Calling | | Hospitality (hotels, resorts, F&B operators), pre-opening or retrofit | Mitel MiVoice / MX-ONE | | Mid-market with cost sensitivity, simpler IT team | Mitel MiVoice | | Government, public sector, large procurement requirements | Often Avaya (legacy preference) or Cisco | | Healthcare networks with HIS integration | Cisco or Mitel depending on existing stack | | Hybrid scenarios with regulated workloads | Often Avaya or Cisco for on-prem core |
Migration risk and timeline
Enterprise Meridian migrations typically run 6-12 months end-to-end. Larger estates (5,000+ users, multi-site) extend to 12-18 months. Risks centre on: feature parity gaps requiring custom rework, integration migration with adjacent systems (CRM, ERP, contact-centre, faxing, alarm systems), and change management for users with deeply ingrained Meridian habits.
Phased migration with parallel operation between Meridian and the new platform through 6+ weeks per wave is the discipline that makes these projects work.
Why vendor neutrality matters at this decision
The three platforms are similar in capability, with different ideal-fit profiles. The integrators who push you toward the platform they happen to resell are not serving your interests at this decision point. The right partner is one who carries certifications across all three, has KSA delivery experience for each, and can recommend based on your environment.
This is what we deliver: a written platform recommendation with rationale, no preferred-vendor pressure. We hold partner status with all three; the recommendation reflects your fit, not our margin.
Get help with your Meridian replacement
For a vendor-neutral Meridian migration assessment, book a discovery conversation. We provide a written platform recommendation with TCO comparison and migration timeline. Pair with unified communications, VoIP installation, and IT consulting services for end-to-end delivery.