When a business decides to move off its old phone lines and onto a modern voice platform, the conversation almost always starts with the phones. Which handsets? How many extensions? Which features? Those are fair questions — but they’re not the questions that decide whether your new system actually works on day one.
The truth that gets overlooked in nearly every VoIP migration in Philadelphia is this: a VoIP phone is only as good as the cabling and power sitting behind it. Your phones now ride on the same network as your computers, your access points, and increasingly your cameras and door readers. If the wiring underneath that network is undersized, aging, or improperly powered, no amount of premium handset hardware will save the call quality.
This guide walks through what a cabling-and-PoE-first approach to a VoIP migration actually looks like in a real Philadelphia office — the kind of planning that turns a stressful cutover into a non-event.
A VoIP migration in Philadelphia is really an infrastructure project
Traditional phone systems ran on dedicated copper pairs that had nothing to do with your computer network. When you switch to Voice over IP, that separation disappears. Your “phone lines” become data packets traveling over the same Ethernet cabling and switches that carry everything else in the building. In practical terms, your network is your phone line now.
That’s exactly why so many voice problems — choppy audio, calls that drop after a few minutes, phones that randomly reboot mid-conversation — almost never trace back to the VoIP platform itself. They trace back to the physical layer: a marginal cable run, a switch that’s run out of power budget, or a network that was never configured to treat voice traffic as a priority. Solve the infrastructure and you solve the vast majority of “phone problems” before they ever happen.
For a Philadelphia office, this matters even more because of the buildings we work in. The region is a patchwork of historic Center City and Old City spaces with plaster walls and limited conduit, alongside modern multi-tenant towers where the wiring closet might be shared and the cable risers tightly controlled. You cannot assume the cabling already in the walls is ready for a voice migration. You have to look.
Step one: a real site survey, not a guess
Before a single phone is ordered, the building needs to be assessed. A proper survey for a VoIP migration in Philadelphia answers a specific set of questions:
- What cabling is already in place, and what condition is it in? Category, age, how it was terminated, and whether it was ever certified.
- How long are the cable runs? Ethernet has a hard 100-meter (about 328-foot) limit per channel — roughly 90 meters of in-wall cable plus patch cords on each end. In a larger floor plate or a deep building, that limit determines where your equipment has to live.
- Where are the MDF and IDF closets? The main distribution frame and any intermediate closets dictate how cable is routed and where switches and power need to go.
- What does the existing switch and power situation look like? Is there capacity to power a full set of IP phones, or is the closet already maxed out?
- What are the building’s quirks? Conduit availability, riser access, plenum spaces above the ceiling, fire-stopping requirements, and the realities of working in an occupied, multi-tenant space.
This is the step that separates a migration that runs on schedule from one that stalls halfway through because someone discovered the cable can’t reach where the phone needs to be. Walking the space first is the least glamorous part of the project and the one that pays off the most.
Cabling: getting the category right
Once you know what’s there, you can decide what to run. For voice alone, the bar is honestly low — even older Cat5e cabling carries a phone call without complaint. But that’s the wrong way to think about it. You’re not wiring for the phone on the desk today; you’re wiring for everything that desk drop will need to do for the next decade.
A few principles guide that decision:
Run Cat6 or Cat6a as the sensible baseline for new drops. Cat6 comfortably handles gigabit speeds throughout the building and supports 10-gigabit over shorter runs, while Cat6a carries 10-gigabit across a full-length run. The incremental cost of better cable during an install is trivial compared to the cost of pulling new cable later because you under-spec’d it.
Treat every drop as multi-purpose. The same cable that connects and powers an IP phone today might power a wireless access point or a security camera tomorrow. Designing the cabling plant around that flexibility is the whole point of a structured cabling system — it gives the network room to grow without tearing into walls again.
Plan for the phone-and-PC pass-through. Most desk phones include a second Ethernet port so a computer can connect through the phone, letting a single drop serve both. It’s a clean way to avoid doubling your cable count, but it has consequences for how you size power and bandwidth — the phone and the PC are now sharing one path back to the switch.
Use the right rated cable for the space. Commercial buildings have code requirements about where plenum-rated versus riser-rated cabling must be used, particularly in the air-handling spaces above drop ceilings. This isn’t optional, and getting it right is part of keeping the building safe and inspection-ready.
Power over Ethernet: powering phones through the cable
Here’s where the electrical side of a voice migration becomes its own discipline. Power over Ethernet, or PoE, lets a single Ethernet cable carry both data and electrical power to a device. For VoIP, that’s transformative: your phones draw their power from the network switch in the closet rather than from a wall adapter at every desk. No power brick under every workstation, no electrician needed at each location, and a single, centrally managed source of power for the entire phone fleet.
But “PoE” isn’t one thing — it’s a family of standards, and matching the right one to your devices is essential:
- 802.3af (standard PoE) delivers up to about 15.4 watts from the switch port. That’s plenty for a basic IP desk phone.
- 802.3at (PoE+) delivers up to roughly 30 watts per port. This covers higher-draw devices like phones with color touchscreens, video-capable units, and many wireless access points.
- 802.3bt (PoE++, sometimes called 4PPoE) pushes up to 60 or even 90-plus watts by using all four pairs in the cable. This is the headroom you want for power-hungry conference room systems, advanced video endpoints, and future devices.
A standard desk phone is a light load. A conference-room video unit, a reception phone with a large display, or a shared device can draw considerably more. The mistake is assuming all phones are equal — they aren’t, and your power plan has to account for the heaviest hitters on the network.
Sizing the PoE switch and its power budget
This is the single most common planning error in a voice migration, so it’s worth slowing down on. A PoE switch has two separate limits that people tend to conflate: the number of ports, and the total power budget shared across all of them. You cannot simply count phones and buy a switch with that many ports.
Consider a 48-port PoE switch. It has 48 ports, yes — but its internal power supply might offer a PoE budget that can’t actually drive all 48 ports at full power simultaneously. If every device is a heavier PoE+ load, you may exhaust the power budget long before you run out of ports. The correct approach is to add up the real-world draw of every device you intend to power, compare that to the switch’s stated PoE budget, and leave meaningful headroom on top.
That headroom matters because the phones rarely have the network closet to themselves. Wireless access points and IP cameras pull from the same PoE budget, and in most modern offices they’re sharing the same switches as the phones. Plan the power as though the whole building’s powered devices live on that budget, because over time, they will.
Finally, the switches you choose should be managed switches — equipment capable of the traffic segmentation and prioritization the next section depends on. That capability is what turns a pile of connected phones into a phone system that sounds good under load.
Designing the network for clean call quality
Cabling and power get the phones connected and running. Two more pieces of network design determine whether they sound good.
The first is a voice VLAN — a virtual separation that puts voice traffic on its own logical lane, apart from general data. Keeping voice and data segmented improves both performance and security, and it makes the whole system far easier to manage and troubleshoot.
The second is Quality of Service (QoS) — the rules that tell your network equipment to prioritize voice packets over less time-sensitive traffic. Voice is unforgiving: a packet that arrives late is effectively a packet that’s lost, and the listener hears it as a gap or a garble. Without QoS, a single large file upload or a backup job kicking off in the background can degrade everyone’s calls. With it, voice gets a protected path and conversations stay crisp even when the network is busy. Properly configured provisioning protocols then let new phones come online and pull their settings automatically, which keeps both the initial rollout and future additions painless.
None of this is exotic — it’s standard practice for anyone who designs networks for a living. But it has to be deliberately built in. It does not happen by plugging phones into whatever switch was already there.
Don’t forget power continuity
There’s one consequence of going to VoIP that catches businesses off guard: when the power goes out, so do your phones. Old analog lines were powered by the phone company and often kept working through a local outage. VoIP phones depend on your switches being powered, so if the network closet loses power, you lose dial tone.
For most offices the answer is a properly sized uninterruptible power supply (UPS) protecting the network closet and core switches, so a brief outage or a flicker doesn’t take the phones down. For operations where staying reachable is mission-critical, that protection extends to backup generator power so communication continues through a sustained outage. Either way, power continuity should be designed into the migration from the start, not bolted on after the first time the lights go out and the phones go silent.
Planning the cutover to minimize downtime
Good planning makes the actual switch-over almost boring, which is exactly what you want. A few practices keep a business running through the transition:
Run the new cabling in parallel with the old system wherever possible, so the new infrastructure is fully in place and tested before anyone relies on it. Start the number-porting process early — moving your existing phone numbers to the new platform involves carrier lead times that are outside anyone’s direct control, and you don’t want that to be the thing holding up your go-live date. Test every drop and every phone before the cutover rather than discovering problems live. And label and document the entire system — every cable, every port, every closet — so that future support, moves, and additions are quick instead of a guessing game.
Why the cabling layer is where you shouldn’t cut corners
It’s tempting to treat the wiring as a commodity and spend the budget on the phones. That instinct gets it backwards. The phones can be swapped out in an afternoon years from now. The cabling and power infrastructure is what you live with — and what every future device, not just the phones, will depend on.
That’s the case for handling the whole project under one roof. When the same team designs the cabling, runs the power, and stands up the phone system, there’s a single point of accountability instead of finger-pointing between a cabling crew, an electrician, and a phone vendor. As a full-service electrical and structured cabling contractor, Positive Wiring handles every layer of a voice migration — from the cable in the wall to the phone on the desk — and certifies the cabling we install. Every install is backed by our Lifetime Wiring Warranty, which is our way of saying the foundation under your phone system is built to last. That’s the Positive way to migrate.
Ready to plan your VoIP migration the right way?
A VoIP migration succeeds or fails on the infrastructure beneath it. Get the cabling category, the PoE budget, the network design, and the power continuity right, and the phones simply work — on day one and for years after.
If you’re planning a move to VoIP for your Philadelphia office, our team can assess your space, design the cabling and power to match how your business actually operates, and integrate it cleanly with your data and security systems. Learn more about our business phone systems in Philadelphia, or request a free consultation and estimate and we’ll help you build it right from the ground up.
When you call, you’ll always reach a live person — no menus, no waiting. That’s Positive.