If you are running a Mitel SX-2000, SX-200, SX-50, Nortel Meridian, CS1000, Norstar, BCM, Avaya Definity, Partner, Magix, IP Office, Alcatel OmniPCX, Siemens HiPath, or Unify OpenScape system in Saudi Arabia in 2026 — you are not alone, and you have not run out of options.

EIE has supported legacy private branch exchange (PBX) systems across the Kingdom since 1985. We installed many of these platforms when they were new. We have engineering memory of the line cards, the voicemail systems, the dial plans, the failure modes, and the migration paths. When the original vendor’s support stopped — when the line card became unavailable from the manufacturer — KSA enterprises kept calling EIE because we kept the systems running.

This page is for IT and facilities directors managing a legacy PBX system in 2026. We cover what we support, what we can repair, what we migrate, and how to talk to us when something fails.

What “legacy PBX” means in 2026

A legacy PBX is a system the original manufacturer no longer sells, no longer supports, or has scheduled for end-of-support. The platforms in scope:

Mitel — SX-2000 family (SX-2000, SX-2000 Light, SX-2000 Micro, SX-2000 FD), SX-200 family (SX-200D, SX-200 ML, SX-200 ICS), SX-50, SX-100, Mitel 5000 Communications Platform, SUPERSET phones (Superset 4 series, 4001, 4015, 4025, 4150, 420, 430, 401), Mitel light system phones.

Nortel — Meridian 1 (Option 11C, 51C, 61C, 81C), Communication Server 1000 (CS1000M, CS1000S, CS1000E across all releases), Norstar (Compact ICS, Modular ICS, Norstar Plus), Business Communications Manager (BCM 50, BCM 200, BCM 400, BCM 450), CallPilot voicemail, Symposium contact center, Communication Server 2100, M-series digital phones (M2008, M2616, M3902, M3903, M3904, M3905), T-series (T7100, T7208, T7316, T7316E), Meridian Companion wireless.

Avaya — Definity (G1, G2, G3 across all V revisions), Communication Manager (legacy versions), Partner ACS, Magix, Merlin Legend, IP Office (legacy R5/R6/R7), Aura (current generation, often migrated to Mitel for hospitality and mid-enterprise consolidation).

Alcatel-Lucent — OmniPCX Office, OmniPCX Enterprise, 4400 series, 4035 phones, Reflexes phones.

Siemens / Unify — HiPath 3000, HiPath 4000, HiPath 5000, HiPath 8000, HiCom 300, HiCom 350, OpenScape Voice, OpenScape Office, OpenStage phones (15, 20, 30, 40, 60, 80), OptiPoint phones, OptiSet phones.

If your system is on this list, EIE supports it.

Three things we do for legacy PBX customers

One — keep your system running. Diagnostics on intermittent failures. Replacement line cards, power supplies, and peripherals from our parts inventory and vetted secondary-market sources. Configuration backups. Voicemail data preservation. Trunk and SIP gateway adjustments as carriers change. Dial plan adjustments. New extension provisioning on existing systems.

Two — extend the runway. When a system can serve another 12-36 months with the right intervention, we plan that runway. Fix what fails. Source parts proactively. Preserve operational continuity until the business is ready to migrate on its own schedule rather than under crisis pressure.

Three — migrate cleanly when the time is right. When the system has reached the end of its useful life — or when the business case for new capability becomes compelling — EIE delivers the migration. Mitel MX-ONE, MiVoice Business, MiContact Center are the most common destinations because of EIE’s 25-year Mitel Gold Partner depth. Cisco Unified CM, Webex Calling, and 3CX are alternatives where the wider stack supports them. Migration mechanics include dial-plan preservation (extension numbers don’t change), voicemail data migration (CallPilot to MiCollab, Modular Messaging to Mitel UC, OpenScape to MiCollab), ACD logic rebuild, hunt group preservation, parallel cutover with zero-downtime fallback, and user training in dialect Arabic.

Parts availability — what we can source

Most legacy PBX hardware is no longer manufactured. EIE maintains parts inventory and supplier relationships for:

– Line cards (analog, digital, T1/E1 trunk, BRI, PRI) – Power supplies and battery backup units – Common control cards – Switch matrix cards – Application processor cards (CallPilot AP, Symposium TPS) – Phone replacements (digital and IP from same vendor family) – Cabinets, shelves, backplanes (where structurally repairable) – DECT base stations and handsets (Meridian Companion, Mitel light, Siemens GigaSet legacy)

Sourcing varies by platform and quantity. Mitel SX series and Nortel CS1000 / Norstar / BCM are the most commonly stocked because of KSA install volume. Avaya Definity, Alcatel OmniPCX, and Siemens HiPath parts are sourced as required.

For each customer engagement we open a parts conversation early — before a critical failure forces an emergency. Proactive spare-part inventory at the customer site reduces incident-resolution time from days to hours.

Migration paths we have delivered in KSA

The platforms below have been migrated dozens of times by EIE engineers. Each has its own discipline:

Mitel SX-2000 → Mitel MX-ONE — same vendor lineage, dial plan ports natively, voicemail moves through MiCollab data import, Mitel SUPERSET phones can be transitioned to Mitel 6900 series in scheduled waves. Migration timeline: 4-12 weeks depending on size.

Mitel SX-200 → Mitel MiVoice Business — mid-market path, simpler than SX-2000 due to smaller scale, hospitality customers retain HSIM PMS integration patterns.

Nortel CS1000 → Mitel MX-ONE — extension dial plan preserved through MX-ONE numbering plan import, CallPilot voicemail data migrates to MiCollab via supported data export, ACD/Symposium logic rebuilt on MiContact Center Enterprise. Timeline: 8-16 weeks for large estates.

Nortel Meridian / Option 11C/61C/81C → Mitel MX-ONE — similar to CS1000 but with additional voicemail data path complexity for older CallPilot versions.

Nortel Norstar / BCM → Mitel MiVoice Business — small/mid-market path, BCM voicemail data migration through structured export, Norstar handsets transition to Mitel 6800i or 6900 series.

Avaya Definity → Mitel MX-ONE — TDM-to-IP migration with significant change-management discipline, voicemail (Modular Messaging or AUDIX) data migration to MiCollab, ACD (Avaya Call Center / CMS) replacement on MiContact Center.

Avaya Aura → Mitel MX-ONE — current-to-current migration usually driven by hospitality vertical specialization, vendor consolidation, or licensing TCO improvement.

Avaya Partner / Magix / Merlin → Mitel MiVoice Business or 3CX — small business migrations, simpler scope.

Alcatel-Lucent OmniPCX → Mitel — common in KSA hospitality estates from chain refurbs, dial plan and voicemail migration similar to Avaya path.

Siemens HiPath 3000/4000 → Mitel MX-ONE — German-engineered platform with structured data migration, OpenStage phones transitioned to Mitel 6800i or 6900 series.

Unify OpenScape → Mitel MX-ONE — current Unify customers (now part of the Mitel family post-acquisition) often migrate to Mitel MX-ONE for vendor consolidation and roadmap clarity.

Migration mechanics across all paths share the same disciplines: dial plan preservation, voicemail data continuity, ACD rebuild, parallel cutover, user training, certified handset transition. The difference is the source-platform-specific data formats and configuration ports.

When to repair vs migrate

The decision is rarely about the technology. It’s about the business case.

Repair makes sense when: – The system is otherwise stable and has 18+ months of expected useful life – Spare parts are available at reasonable cost – The business has no immediate driver for new functionality (contact center, mobility, video integration) – Capital budget for migration is not in the next 12 months – Operational risk of migration project exceeds the operational risk of continued legacy operation

Migration makes sense when: – Spare parts have become unobtainable or prohibitively expensive – The system has experienced multiple failures in the last 12 months – Vendor end-of-support has passed and security patches are unavailable – Business is acquiring/expanding (capacity ceiling reached) – Regulatory drivers require modern features (recording, encryption, integration) – Hospitality refurb, banking branch refresh, or other capital event creates the budget envelope – 5+ years of TCO analysis favours new platform (typical break-even: 2-4 years)

Most KSA legacy customers fall in a middle zone where staged migration over 18-24 months is the right answer: keep the legacy stable for the larger sites and migrate the smaller/branch sites first to build operational confidence and team familiarity with the new platform.

EIE’s role is providing the honest scoping conversation that picks the right path for the specific customer, not selling the migration regardless.

What working with EIE on legacy PBX looks like

Initial diagnostic call — 30 minutes, free. We learn what platform, version, scale, current symptoms, and business context. We tell you whether what you have is genuinely legacy (end-of-life) or just old (still serviceable).

Site visit (where required) — engineer attendance for diagnostic depth, parts inventory, hardware inspection, configuration backup. Typically half-day to one day.

Findings document — a clear written summary of what is on site, what is failing or at risk, what we can repair, what parts we can source, what migration paths exist with rough effort estimates.

Engagement options — repair only, repair + parts inventory, support contract (annual), or migration project. We quote each separately so you can choose the path that matches your business case.

Continuity — when EIE supports your legacy PBX, the same engineer who knows your system is the same engineer who answers when you call. We do not rotate accounts. The institutional memory matters when something fails at 2 AM and the diagnostic depends on knowing what was changed three years ago.

Frequently asked questions

Is Mitel SX-2000 still supported by Mitel? Mitel withdrew SX-2000 support in stages through the late 2010s; full vendor support has ended. EIE continues to support SX-2000 estates through engineer expertise, parts sourcing, and configuration knowledge accumulated over decades of installations.

Can I still buy spare parts for Nortel CS1000? Nortel-branded new parts are no longer manufactured. The secondary market and remanufactured-part suppliers continue to provide line cards, power supplies, and common control. EIE sources from vetted suppliers and maintains internal parts inventory for the common failure components.

My Avaya Definity has been running for 25 years. Should I migrate now or keep it running? Depends on parts availability for your specific cabinet generation, your business growth requirements, and whether you have a regulatory or capability driver. EIE can do a 30-minute call to scope this honestly — repair if it makes sense, migrate if the business case is there.

Can Mitel MX-ONE preserve my existing extension numbers when I migrate from Nortel? Yes. MX-ONE numbering plan import preserves extension dial patterns, hunt group structures, and time-of-day routing. Users continue dialing the same internal numbers post-migration.

How long does a Nortel CS1000 to Mitel MX-ONE migration typically take? 6-16 weeks depending on size, voicemail data migration scope, and whether ACD/Symposium replacement is included. Large multi-site estates with contact-center scope can extend to 20+ weeks. Migration runs in parallel-cutover style — the legacy and new system co-exist during transition for zero-downtime fallback.

What happens to my CallPilot voicemail data when we migrate? EIE migrates CallPilot greetings, message histories, and mailbox configurations to Mitel MiCollab using supported data export tools and custom transformation scripts where required. Voicemail continuity is one of the more sensitive parts of any UC migration and we plan it explicitly.

Will my existing Nortel digital phones work on Mitel? Generally no — Nortel digital phones are proprietary to the Nortel platform. Migration includes phone replacement, typically Mitel 6800i or 6900 series for office desks and Mitel hospitality phones for hotel rooms. We schedule phone replacements to align with the cutover plan and budget.

Do you support Mitel SUPERSET phones in 2026? Yes, where the underlying SX-series PBX is still operational. Replacement SUPERSETs are sourced from secondary market when needed. SUPERSET handsets transition to Mitel 5300 series, 6800i, or 6900 series at migration.

My Siemens HiPath 4000 is critical to a KSA factory operation. What support do you offer? HiPath 4000 support includes diagnostic, parts sourcing through European secondary-market suppliers, configuration backup, and migration path planning. For factory environments, we recommend annual support contract with on-site spares to minimize incident resolution time.

We’re a hospitality group with old Alcatel OmniPCX systems across multiple properties. Migration plan? Phased migration is normal — pick one property as the pilot, prove the path, replicate. We build the project plan with hospitality cutover discipline (no service interruption during peak season, PMS integration retained, brand-standard phone selection, multi-language voice prompts in Arabic and English).

Talk to EIE about your legacy PBX

Forty years of KSA enterprise IT means EIE has installed, maintained, and migrated more legacy PBX systems in Saudi Arabia than any other firm. Mitel Gold Partner since 2001. Nortel-trained engineers from the Meridian era. Avaya, Alcatel, Siemens, Unify expertise built across the same span.

Three KSA offices: Jeddah HQ, Madinah, Riyadh. On-site engineers across the central, western, and northern regions. 24/7 incident response for support contract customers.

Phone: +966 12 6522 996 Email: info@eliteideas.net Website: eliteideas.net

Schedule a 30-minute legacy PBX scoping call.

—