How do I set up a VoIP system for my business?

Setting up VoIP properly is less about the technology switch itself and more about a structured migration that avoids the common pitfalls: undocumented analogue devices, connectivity that isn't ready for voice traffic, and a cutover that breaks something nobody thought to check.

Step 1: Audit What You Currently Have

Before anything else, document every extension and who owns it, every inbound number and how it's routed (main line, direct dials, after-hours), and critically, every analogue device physically connected to your current system, alarm panels, lift emergency phones, fax lines, gate intercoms. This last category is the single most common source of migration surprises, since these devices don't move to VoIP automatically and are easy to forget entirely.

Step 2: Assess Your Connectivity

VoIP call quality depends directly on internet stability and available bandwidth, budget roughly 100kbps per concurrent call. If your current connection is unreliable or already near capacity, that needs addressing before, not after, a VoIP rollout, otherwise you'll blame the phone system for a connectivity problem.

Step 3: Design the Dial Plan

This covers how calls actually flow: which extensions ring for which inbound numbers, what happens after hours, how calls escalate if unanswered, and what greeting callers hear. Getting this right before go-live avoids a chaotic first week of calls going to the wrong place.

Step 4: Port Your Numbers

If you want to keep your existing phone numbers (and almost everyone does), the porting process through ICASA-governed procedures typically takes 10 to 20 business days depending on your current carrier's responsiveness. Your numbers stay live throughout this process, the actual switch happens at cutover, not when the application is submitted, so start this early rather than leaving it to the last minute.

Step 5: Handle the Orphaned Devices

For every analogue device identified in the audit, decide: keep it on a retained analogue line, convert it via an ATA gateway (which presents an analogue port to the device while connecting over IP), or replace it with an IP-native alternative. Fax in particular is worth flagging, analogue fax over VoIP is notoriously unreliable regardless of provider, fax-to-email is usually the better answer.

Step 6: Pilot, Then Roll Out in Phases

Rather than switching the whole business over on one day, run a pilot with one department while the legacy system still serves everyone else. This surfaces configuration issues on a small scale before they affect the whole company, then roll out department by department, keeping the old system live as a fallback until you're confident.

Step 7: Cut Over and Decommission

Once every department is confirmed working well, port the main numbers, run a short parallel period with both systems technically live, then decommission the old PABX. Never decommission the legacy system on cutover day itself, always keep a fallback window.

Our Approach

We run this exact structured process for every migration, starting with a proper on-site audit rather than a remote assumption-based quote. For a typical 50 to 200 seat site, this whole process runs about 90 days from audit to full cutover, and we manage every step including the porting paperwork.