Why now — the inflection point in 2026

Saudi enterprises with Avaya, Nortel, Panasonic, or early-generation Cisco PBX systems are facing a hard choice: invest in dwindling parts inventories and end-of-support hardware, or migrate to IP-based telephony. The economics tipped over the last 18 months. Spare parts for legacy systems cost 3-4x premium prices when available. Vendor support has formally ended on most pre-2015 platforms. And the operational efficiency gap between legacy and modern systems — measured in IT hours per phone change — has widened to the point where the legacy maintenance cost alone justifies migration.

The 90-day project plan below assumes a typical 200-500 user organisation with one to three sites. Larger enterprises scale the timeline proportionally; smaller organisations compress it.

Phase 0 — discovery: documenting what you actually have

The single most overlooked phase. Before you can plan a migration, you need an honest accounting of your current state. Inventory: every extension and its assigned user, every external number and which extension it routes to, every special-purpose number (call queues, IVR menus, fax lines), every feature in use (hot-desking, voicemail, call recording, call accounting), and the integration points (CRM dial-out, contact-centre, paging systems).

This phase typically takes 1-2 weeks and surfaces the surprises every project encounters: the fax line nobody documented but that’s still receiving regulatory submissions, the queue that handles a critical customer-facing function that nobody wrote down, the executive’s preferred call-screening behaviour.

Phase 1 — design: SIP trunking, SBC, survivability

The architecture decisions made in Phase 1 commit you for the next decade. Key choices: which VoIP platform (Mitel, Cisco, Microsoft Teams Phone, 3CX, Avaya), SIP trunk provider (STC, Mobily, Salam, or international carrier), session border controller for security and survivability, and the deployment model (on-premise, hosted, hybrid).

For Saudi enterprises, the design must account for: international call quality (KSA peering quality varies by carrier and destination), survivability under internet outage (critical for organisations dependent on phone-based workflows), and integration with existing systems (CRM, contact centre, billing).

Phase 2 — number porting from STC, Mobily, Salam

Number porting in Saudi Arabia is more bureaucratically structured than in many markets. Allow 4-6 weeks for porting from your existing carrier to your new SIP trunk provider. Pitfalls: some legacy contracts have minimum-term penalties, certain “special” number ranges (toll-free, premium) follow different porting paths, and porting is sensitive to documentation accuracy — a mismatch in the company name or CR number can delay porting by weeks.

Best practice: initiate porting in parallel with infrastructure deployment, not sequentially. Numbers are ready when you’re ready to cut over.

Phase 3 — pilot: 30-50 user trial

Never cut over the entire organisation in one event. The pilot phase typically runs 2-3 weeks with a representative user group: 30-50 users covering different roles (knowledge workers, frontline support, executives). Test: call quality (domestic and international), call recording (where required), voicemail-to-email, mobile/softphone usage, integration with CRM if applicable.

Document failures, fix them in pilot, then proceed.

Phase 4 — phased rollout strategy

The rollout sequence matters as much as the rollout itself. Standard pattern: by department for organisations with clear functional boundaries, by floor for organisations in single buildings, by site for multi-site enterprises. Cut over departments or sites in waves of 50-200 users with 1-2 weeks between waves to surface issues before they cascade.

Always maintain dual-platform operation during cutover — old PBX still active, new VoIP active in parallel — until each wave confirms stable.

Phase 5 — adoption + training (where most projects fail)

Technology cutover is the easy part. User adoption is where most VoIP projects under-deliver. Plan for: training sessions per user role (executive assistants and call queue staff need different training than back-office workers), quick-reference guides in Arabic and English, dedicated support during cutover week, and an internal champions programme.

Budget: 4-8 hours of training per user, more for power users. Most organisations underspend here and pay for it in productivity loss for months.

Common KSA-specific gotchas

Two specific patterns that repeatedly surprise migration teams: the legacy fax dependency (regulators, banks, and government still receive certain submissions by fax — your VoIP must support fax-over-IP or maintain a separate fax solution); and the integration with hospitality systems if you operate hotels (PMS-integrated phone systems require specific software at every tier — verify compatibility before committing).

Vendor-by-vendor decision (Mitel, Cisco, Teams, 3CX, Yealink)

Mitel: strongest in mid-market mass deployment, robust international support, heavy KSA install base. Cisco: dominant for organisations already deeply Cisco-invested. Microsoft Teams Phone: best when M365 is already strategic and call patterns lean office-based. 3CX: budget-friendly, often the right answer for SMBs and mid-market with limited budgets. Yealink: hardware specialist that pairs with multiple platforms.

For a written PBX-to-VoIP migration plan tailored to your environment, book a VoIP discovery session. We provide a fixed-fee proposal covering all five phases. Pair VoIP with Microsoft Teams, unified communications, and networking services for integrated communications.