After 400 VoIP deployments, I can predict within the first week whether a migration will go smoothly or become a disaster. It comes down to four numbers.
Number 1: Jitter During Peak Hours
What to measure: Run a jitter test between 10 AM and 2 PM on a Tuesday or Wednesday. Not Monday (recovery day), not Friday (light day).
| Jitter | Prediction |
|---|---|
| < 15ms | Migration will be smooth |
| 15-30ms | Minor issues expected, manageable |
| 30-50ms | Significant quality problems likely |
| > 50ms | Do NOT migrate until network is fixed |
I have never seen a successful VoIP deployment on a network with consistent jitter above 30ms. Fix the network first, then migrate.
How to test: ping -n 500 your-voip-provider.com during peak hours. Look at the variation between min and max latency. That variation IS your jitter.
Number 2: Agent-to-IT-Staff Ratio
What to measure: Count your phone users. Count your IT staff who will support the new system.
| Ratio | Prediction |
|---|---|
| < 50:1 | Smooth — IT can handle day-one issues in real-time |
| 50-100:1 | Workable with good training and documentation |
| 100-200:1 | Risky — IT will be overwhelmed on day one |
| > 200:1 | Hire temporary help for the first week |
A 200-person company with one IT person will have a bad migration. Not because VoIP is hard, but because 200 people will have 200 questions on day one, and one IT person cannot answer them all.
The fix: If your ratio is above 100:1, schedule floor walkers for the first 3 days. These can be power users from each department, trained an hour early, who help their colleagues with basic questions.
Number 3: Upload Bandwidth Utilization
What to measure: Check your upload bandwidth utilization during peak hours. Not download — upload.
| Upload Utilization | Prediction |
|---|---|
| < 40% | Plenty of room for voice traffic |
| 40-60% | Implement QoS before migration |
| 60-80% | Upgrade bandwidth OR implement strict QoS |
| > 80% | Must upgrade bandwidth — VoIP will not work |
VoIP is symmetrical — each call uses the same bandwidth up and down. Most internet connections have 5-10x more download than upload. Your upload is the bottleneck.
Example: 100 Mbps down / 10 Mbps up. You have 25 concurrent calls needing 2.5 Mbps of upload. If your staff is already using 7 Mbps of upload for cloud apps, video, and file sharing, adding 2.5 Mbps pushes you to 95% — and call quality will suffer.
Number 4: Percentage of Employees Over 50
This sounds ageist. It is not. It is a change management metric.
| % Over 50 | Prediction |
|---|---|
| < 20% | Standard training is sufficient |
| 20-40% | Need one-on-one sessions for some users |
| 40-60% | Extend training period, provide desk phones (not just softphones) |
| > 60% | Prioritize simplicity over features, give desk phones to everyone |
Older employees are not less capable. They have used the same phone for 15 years and muscle memory is powerful. They need more time to rebuild those habits, and they strongly prefer physical desk phones over softphones.
The mistake I see: companies go softphone-only to save money, and then 40% of the workforce hates the new system because they lost their familiar desk phone.
The fix: Offer desk phones as an option to anyone who wants one. The $150 per phone is worth it for adoption.
Putting It Together
Score each number 1-4:
| Score | Total | Prediction |
|---|---|---|
| 4 | 16 | Flawless migration |
| 3-4 | 12-15 | Smooth with minor bumps |
| 2-3 | 8-11 | Problems expected — address weak areas first |
| 1-2 | 4-7 | Do not migrate yet — fix fundamentals |
No VoIP provider can overcome bad network, overwhelmed IT, insufficient bandwidth, or untrained users. Fix these four numbers before signing any contract.
VestaCall runs a free network readiness assessment that measures all four factors and gives you a go/no-go recommendation before you commit.
