The SMB-class Nortel reality
Across Saudi Arabia, hundreds of mid-market organisations still operate Nortel Norstar or Business Communications Manager (BCM) phone systems. The Norstar/BCM family was the dominant SMB phone system in KSA from the late 1990s through the late 2000s. Many deployments are now 15-20 years old, running on the original hardware, with the original engineering team long since moved on. The systems work, mostly. Until they don’t.
This is a roadmap for moving Norstar/BCM organisations to modern phone systems, written for the SMB and lower-mid-market reality where IT teams are small, budgets are tight, and disruption tolerance is low.
Why now
Three forces converge in 2026 to make Norstar/BCM migration timely:
Diminishing parts. The Norstar Compact ICS, Modular ICS, and BCM 50/200/400/450 chassis components are no longer manufactured. Refurbished parts are available but at premium pricing with longer lead times. When a backplane or feature card fails, the wait may exceed business tolerance.
Retired engineers. The administrators who knew Norstar configuration and BCM Element Manager are retiring or moving to other technology stacks. New engineers don’t learn Nortel — there’s no training, no certification path, and no career future in legacy Nortel work.
Compliance pressure. Insurance carriers, brand standards (for hospitality), and B2B customer due-diligence increasingly flag Nortel-era systems as risk indicators. Audits get harder.
Modern feature gap. Mobile UC, video integration, modern CRM dialing, presence, instant messaging — the things SMB workers expect daily aren’t available on Norstar/BCM at any reasonable cost.
The migration target options
For Norstar/BCM migration in Saudi Arabia, four target platforms cover the realistic options:
Mitel MiVoice Office 250 — the natural successor for organisations comfortable in the Nortel feature world. Mitel’s SMB platform handles 25-250 user organisations well. On-premise or hosted. Strong hospitality vertical features. Mitel is also a sub-distributor channel partner in KSA, so support is local.
3CX — the budget-friendly alternative. Software-based phone system that runs on standard server hardware or cloud. License pricing is simple (per simultaneous call, not per user). Strong for SMBs prioritising cost and simplicity over enterprise feature breadth.
Microsoft Teams Phone — the right answer if your team already uses Microsoft 365 heavily. Teams becomes the soft-phone, Teams Phone licenses add calling, calling plans handle the SIP trunk to Saudi carriers. The cleanest UX integration for knowledge-worker SMBs.
Hosted PBX (e.g., Avaya Cloud Office, RingCentral) — fully cloud-hosted, no on-premise gear. Subscription pricing. Best for organisations that don’t want to maintain any phone-system infrastructure on their own.
The right choice depends on user count, existing Microsoft 365 footprint, hospitality or specialist requirements, and budget profile (CapEx vs OpEx preference).
The 90-day SMB migration plan
A typical 100-200 user Norstar/BCM migration runs about 90 days end-to-end:
Days 1-15 — Discovery and design
Inventory: every extension, every external number, every feature in use (call queues, IVR, voicemail boxes, hunt groups, ring-down circuits, fax lines, alarm systems on phone lines). Document the dial plan completely. Identify CRM and other system integrations. Choose the migration target platform.
Days 16-30 — Procurement and pre-staging
Order new platform hardware (or provision cloud licenses). Pre-stage configuration in lab or vendor environment. Order replacement phones if you’re refreshing handsets too. Begin number-porting paperwork with STC, Mobily, or Salam — port lead times in KSA are typically 4-6 weeks, so start early.
Days 31-50 — Pilot deployment
Deploy the new platform to a pilot group of 30-50 users (typically one department, one floor, or one office). Run pilot for 1-2 weeks, capture issues, refine configuration. Pilot users continue on Norstar for parallel operation.
Days 51-75 — Phased rollout
Migrate remaining users in waves of 50-100. Each wave: cutover users to new platform, run parallel for 3-5 days, decommission their Norstar extensions. The final wave includes the legacy fax and alarm-system lines, which need careful handling.
Days 76-90 — Cutover, decommission, optimise
Final cutover. Decommission Norstar/BCM hardware (with disposal documentation for any retention requirements). Tune the new platform based on usage patterns observed in week 1. Conduct end-user training reinforcement. Begin operational support contract.
Number porting from STC, Mobily, Salam
Saudi number porting is more bureaucratically structured than in some markets. Process steps:
- New platform vendor (or your integrator) submits port request to current carrier
- Current carrier validates and accepts (1-2 weeks)
- Port date scheduled with both carriers (1-2 weeks lead time after acceptance)
- Port completes (typically overnight or weekend; 1-3 hour cutover window)
Common pitfalls: company-name mismatches between current bill and CR (Commercial Registration) cause rejections, special number ranges (toll-free, premium) follow different paths, and minimum-term contract penalties apply in some carrier agreements.
Best practice: initiate porting paperwork in week 1 of the project, not at week 8. Porting paperwork delays don’t slow your project if started early.
Common gotchas
The patterns that surprise migration teams: Norstar feature codes (like *2 for transfer) are muscle memory that doesn’t translate cleanly to all modern platforms — provide a feature-code translation guide. Fax lines need explicit replacement (T.38 over IP for low fax volume; analog lines via FXS gateway for higher volume). Alarm systems and elevator phones often connect via legacy analog ports — verify replacement path. Door-entry systems integrated with Norstar may need replacement.
Cost expectations
Indicative ranges for KSA SMB migration projects:
- 50 users: SAR 60K-150K total project (platform + phones + installation + training)
- 100 users: SAR 100K-250K
- 200 users: SAR 180K-400K
Variance reflects platform choice (cloud vs on-prem), phone refresh decisions (reuse vs replace), and integration complexity. Cloud platforms shift cost from capex to monthly opex.
Get help with your Norstar/BCM migration
For a vendor-neutral SMB migration assessment, book a discovery conversation. We deliver a written project plan with target platform recommendation, fixed-fee proposal, and migration timeline. Pair Norstar/BCM migration with VoIP installation, Microsoft Teams, and unified communications services for integrated delivery.