VoIP Costs
VoIP Migration and Porting Costs
Switching VoIP providers is priced like signing up; it behaves like moving house. The subscription starts clean, but the move itself — porting numbers, running two systems in parallel, touching every desk, retraining every user — has its own budget that nobody's proposal volunteers. Under-budgeted migrations are the ones that end with phones down on a Monday.
This guide itemizes a realistic migration budget for a 25-user business (scale the unit costs to your size) and the sequence that keeps the cutover boring.
The migration budget (25 users, illustrative)
| Item | Typical published range / basis | Example |
|---|---|---|
| Porting fees | $5–$25 per number | 27 numbers × $15 = $405 |
| Parallel service overlap | 2–6 weeks of both bills | ~1 month hosted overlap ≈ $800 |
| New hardware (if changing) | See hardware guide | $0 if phones are standards-based & reused |
| Install & call-flow build | $500–$2,500 outsourced | $900 |
| Internal labor | 4–12 hrs coordination + per-desk touches | budget 2 staff-days |
| Training | 1 hr per team + guides | internal time; some providers include |
| Contingency (10–15%) | on the above | ~$300 |
| Total (phones reused) | ≈ $2,400 + internal time |
How porting actually works — and where it stalls
Local number portability moves numbers between providers via a Letter of Authorization (LOA) matched against the losing carrier's Customer Service Record (CSR). Ports stall for clerical reasons — a name, address or account number that does not character-match the CSR — far more often than technical ones. Request your CSR from the current provider before submitting the LOA and copy fields exactly. Ports are scheduled with a Firm Order Commitment (FOC) date; on that date, numbers swing to the new provider, which is why the new system — call flows, phones, e911 addresses — must be fully built and tested with temporary numbers before FOC. Never cancel the old service yourself: porting cancels the ported lines automatically, and premature cancellation can lose numbers permanently. Keep the old account alive (and forwarding) until every number is confirmed working on the new system.
Cutover sequence that stays boring
- Build the new system completely on temporary numbers: call flows, queues, voicemail, e911 registration, and a test phone at every location type.
- Pull CSRs, prepare LOAs from them exactly, and submit ports with an FOC date in a low-volume window (never Monday morning).
- Stage hardware: replace/rewire desks after hours; label old and new phones during the overlap so staff always have a working phone.
- On FOC day, test in order: inbound to main number, inbound DIDs, outbound caller ID, internal transfers, 911 registration data review (coordinate any test call with the PSAP non-emergency line).
- Keep the old service forwarding for 2–4 weeks, audit final bills from both providers, then close the old account in writing.
Frequently asked questions
- How long does porting take?
- Simple US local ports commonly complete in 5–10 business days once the LOA is clean; toll-free and complex multi-location ports take longer. The clock runs on paperwork accuracy, not on the switch itself.
- Can we lose our numbers if something goes wrong?
- A rejected port loses nothing — numbers stay with the old provider until a successful port. Numbers are at risk only if the old account is cancelled or lapses before porting completes. Keep it paid and active until confirmation.
- Why is there a parallel-service cost at all?
- Because reliability demands overlap: the new system must be live and tested before numbers move, and the old service must remain until they do. Two bills for 2–6 weeks is the price of a cutover with a rollback path.