The first time I migrated a sprawling analog CCTV system to an IP-based surveillance setup, I learned two immediate truths. One, coax doesn’t forgive poor planning. Two, the camera you choose is rarely the problem, it’s what sits between that lens and your switch. Cabling makes or breaks these projects. Get it right, and your system runs quietly for years. Cut corners, and you’ll chase gremlins across ceilings at 2 a.m.
This guide is grounded in jobs where we replaced decades-old infrastructure, salvaged what we could, and brought security networks into the present. You’ll find what holds up in the field, where the traps are, and how to tackle the real migration work so you finish once, not twice.
Why people move from coax to IP
Better image quality gets most of the attention, but the cabling advantages are what shift budgets. With IP, a single category cable carries data and power when you use PoE. That means fewer power supplies, fewer outlets in strange places, and less voltage drop gymnastics. You also gain flexibility. A network drop can serve a camera, a PoE access device, or an intercom unit. Bandwidth is the constraint, not conductor count.
Analog was forgiving in one way. If a run worked on day one, it often kept working unless someone nicked a jacket. IP is different. Noise margins, bend radius, crosstalk, and terminations matter. Treat cabling like an afterthought and the flakiness will haunt you.
Can you reuse existing coax with Ethernet-over-coax adapters?
Yes, and sometimes you should. Ethernet-over-coax (EoC) transceivers can push 100 Mbps or more over quality RG59 or RG6 for several hundred meters. I’ve used them in historic buildings where we couldn’t open walls, and in parking structures where conduit was packed to the last millimeter. The extra hardware cost per channel, usually in the low hundreds, often beats pulling new cable across active areas or through asbestos-laden fireproofing.
That said, be honest about the coax. Old foil shields peel. Copper-clad steel center conductors corrode. If the coax fails a simple DC resistance check or shows high attenuation, expect intermittent drops when humidity swings. Also, protect the transceivers with surge suppression at both ends. Coax can act like a long antenna in an electrical storm.
Where EoC shines: long exterior runs to poles, heritage interiors, and any place with sealed, certified penetrations you don’t want to touch. Where it stumbles: dense switch rooms with dozens of PoE ports, because you end up managing many small powered injectors unless you use centralized EoC switches.
Picking the right category cable for security camera cabling
For new pulls, Category 6 is the workhorse. It handles https://penzu.com/p/2f4e17e6c92a7376 gigabit with headroom and is widely available in plenum and riser ratings. Category 6A makes sense for runs near strong interference or when you’re future proofing for multi-gig uplinks or cameras that push higher bitrates. Category 5e will work for many 1080p cameras, but I don’t specify it anymore in commercial work. What you save up front, you pay later if you ever need to jump to 2.5 Gbps or power something hungrier.
Pay attention to jacket ratings. Use plenum (CMP) in air plenums, riser (CMR) in risers, and outdoor/direct-burial for exterior runs. In garages, I prefer industrial-rated jackets that resist oil and salt. Cables labeled “CM” and “CMG” are fine for general use, but inspectors can and do flag them in the wrong spots.
Shielding is a judgment call. Unshielded twisted pair handles most indoor runs. Go with F/UTP or U/FTP when you run parallel to variable-frequency drives, elevator motors, or heavy electrical feeders. Keep 12 inches of separation from power where possible. Crossing at ninety degrees helps when you can’t maintain spacing.
On copper quality: solid copper conductors only. Avoid copper-clad aluminum. It fails punchdowns, heats under PoE load, and breaks at terminations. Anyone who has re-terminated a CCA cable after a few summers knows that brittle snap.
PoE, power budgets, and heat
PoE is the main reason IP-based systems simplify installs. But not all PoE is equal. For typical fixed cameras, 802.3af is fine. PTZs and cameras with built-in IR arrays often need 802.3at. Going beyond that, 802.3bt (Type 3 or 4) feeds high-draw devices like multi-sensor panoramic cameras or combined intercom and camera units with heaters.
Look at the switch budget, not only the per-port rating. A 24-port switch labeled as PoE+ might advertise 30 watts per port, but only offer a total of 370 watts across all ports. Fill it with hungry devices and you’ll brown out at odd times. Mix in access control cabling needs and other networked security controls, and the math matters. I keep a simple spreadsheet that tallies worst-case draw per device with 10 to 20 percent overhead. It saves mystery outages.
Heat hides in bundles. A tray with sixty powered links will run hotter than you think, especially above a ceiling in summer. Heat raises cable resistance and can tip marginal runs over the edge. Use larger gauge conductors when possible and avoid tightly zip-tying bundles. If a ceiling grid measures like a sauna, I add separation or move higher-draw links to separate pathways. On long PoE runs, check voltage at the device under load. Manufacturers publish maximum lengths, but conditions vary. A camera that boots at 48 V idle might fail when IR kicks on.
Structured cabling pays you back
It is tempting to chase the shortest path from switch to camera. Resist that. Home-run everything to a known intermediary point, whether that’s an IDF, a small enclosure, or a consolidated conduit drop per area. Label both ends with a consistent scheme that matches your drawings. I prefer printed wrap labels with a unique ID that carries through to the switch port description. Six months later, when a midnight alarm points to Camera 2W Lobby, you’ll be glad you can find its cable in under a minute.
I’ve walked into sites where every junction box hid a rat’s nest of couplers. Those cheap in-line connectors are fault multipliers. If you must extend a run, use a proper keystone jack in a surface box and test it.
Testing is not optional. Certify category runs when possible. At a minimum, use a qualifier that measures length, wiremap, and signal-to-noise. I keep a tone and probe for quick traces and a fluke-level certifier for final acceptance. When a run fails intermittently, I test during the hottest part of the day, not at 8 a.m. when the building is cool.
Migration tactics that reduce downtime
In occupied buildings, ripping out the old and installing the new rarely flies. The least painful approach is parallel overlay. Leave analog running while you pull new cable, mount new cameras next to the old, and swing devices one area at a time. With an IP-based surveillance setup, you can stage VLANs and recorders in advance. On cutover day, you point DNS or update routes, and the system shifts with little visible drama.
If ceilings are finished or sensitive, chase vertical paths first. Feed floors from corridors or shafts, then branch into spaces with minimal opening. Heal any firestopping as you go. Having the right fire caulk and intumescent pads on hand saves last-minute scrambles.
When you need to reuse coax temporarily, hybrid cameras that output analog and IP can bridge the gap while you modernize downstream components. I’ve used them to keep security teams familiar with their wall of monitors while the backend moved to software clients.
Surges, grounding, and lightning
Cameras on poles or at building edges invite surges. Ethernet doesn’t like voltage spikes. Use outdoor-rated surge protectors with replaceable modules at the device end and at the entry to the building or enclosure with the switch. Bond them properly. In older properties, grounding is often a patchwork. A clean bonding path from pole to building ground drastically reduces weird dropouts after storms.
On metal poles, isolation mounts can help, but I’d rather spend on good surge hardware and proper bonding. For long exterior runs without fiber, shielded cable with a drain wire tied correctly can reduce induced noise. Fiber itself is the best electrical isolation. If vandal risk is high and you can afford the optics, a media converter at the pole head gives you that calm.
When fiber earns its keep
Any time you approach or exceed the 100 meter copper limit, consider fiber. Parking lots, long corridors, and campus links benefit from SFP-based fiber uplinks back to a closet. Media converters and small PoE fiber switches are straightforward to deploy. Single-mode versus multimode depends on distance and existing infrastructure. For new campus work, single-mode gives you range and future options at similar cost.
We often run a small-count fiber along with spare category cables to camera clusters, then install a compact switch in a rated enclosure. That enclosure becomes a serviceable point for cameras, intercom and entry systems, and even PoE access devices. If someone later adds electronic door locks nearby, you already have an upstream link with bandwidth to spare.
The access control puzzle near your cameras
Video rarely lives alone anymore. Card reader wiring often shares pathways with camera cables, and biometric door systems add power needs and device counts near doors. Keep high-current lock power separate from data where you can. A maglock pulling inrush on the same bundle as a camera drop has a way of showing itself on your recordings as a little ripple or a momentary disconnect.
For access control cabling, 18/2 or 18/4 handles most lock power, while readers usually need 22/6 or similar depending on the protocol. I keep reader and camera cabling physically separated by a few inches in trays and avoid sharing metal conduits when locks are high-current. If an EEM relay is nearby, ferrules and proper termination reduce oscillation. Alarm integration wiring complicates things further. Dry contacts are forgiving, but powered loops need clear documentation. Label each conductor at the panel. When a guard calls about a door held alarm at 3 a.m., you want to rule out wiring in seconds.
Compression, bandwidth, and what that means for the wire
H.265 helps, but it is not magic. A 4 MP camera with WDR in a busy lobby can still push 6 to 10 Mbps if you want crisp footage. Multiply that by dozens of cameras and your uplinks, switches, and storage will show the load. The cable doesn’t care about codec, but the devices at both ends do. Long, marginal runs show their weakness under sustained throughput. If a link drops only during the lunch rush when motion spiking drives bitrates up, suspect the physical layer first.
I run two streams per camera commonly. The primary for recording, the secondary for live walls and mobile clients. Size your backbones accordingly. If you have a cluster of cameras feeding a 1 Gbps uplink, check your aggregate bitrate with some real scenes, not just the spec sheet. If you’re close to the edge, a 2.5 Gbps uplink on Cat6 can buy breathing room without jumping to 10 Gbps optics.
Labeling, documentation, and the load-in day test
Good drawings, tied to labels, cut your labor months later. On the last job where we took over a partially installed system, the cables had room names and sharpie scrawls on them. Half the rooms had been renamed. We spent hours confirming pairs. A simple scheme like CAM-03-2W-014 carries the device type, floor, wing, and ID. If you mirror that in the NVR channel name, the switch port description, and the drawing, your team will work faster and break less.
Before you hand off, do a load-in day test. Push the system. Turn on IR at all cameras, enable motion detection analytics, open every door connected to the controller, trigger intercoms, and run the recording engine at full tilt. Watch for any camera that blinks or any switch that logs PoE faults. Better to find the marginal terminations and undersized PoE budgets on your time.
Making the cut through tricky building types
Hospitals and labs fight you on penetrations and infection control. Work above ceilings is closely monitored. Prefabricate as much as possible and limit open time. Use dust covers, HEPA carts, and coordinate with facilities for room shutdowns. When a ceiling can only be opened forty minutes at a time, your staging must be tight.
Historic properties limit conduit and hub locations. I’ve hidden small switches behind millwork with ventilation paths and code-compliant power. Painters hate popping panels, so provide maintenance access that does not require tools or ladders if possible. In those projects, reusing coax with EoC or pulling microduct for future fiber becomes a negotiation with preservation boards and inspectors.
Warehouses and distribution centers give you distance and RF noise from conveyors. I default to shielded Cat6A for long parallel runs near motors and push more segments to fiber. Cameras over dock doors need heaters in cold climates and surge protection everywhere. Reels and lifts save hours if you plan anchor points before the day of install.
Integrating intercom and entry systems with video
Intercoms tie neatly into camera networks when you think ahead. Many modern door stations support SIP and PoE video. They draw more power than a small dome camera and live near locks that pull heavy current. Give them their own PoE budget headroom and protect them from back-EMF. If you use a separate analog audio path for legacy systems, isolate that wiring from network cabling even within the same backbox.
Pair intercoms with a nearby camera that has a view of the entire approach, not just the person at the mic. That usually means two drops, or one drop to a small enclosure feeding both devices. With networked security controls, you can tie call events to camera bookmarks. If the wiring supports reliable signaling, your operators can jump to relevant footage instantly.
The realities of cost and phasing
Clients ask if they can save money by reusing everything that looks like a cable. Sometimes yes, often no. I view reuse in tiers. First, reuse raceways and pathways. Second, reuse coax with EoC if it tests well. Third, reuse power for accessories that don’t need PoE. When budgets are tight, phase by criticality. Exterior coverage and main entries come first, high-traffic interiors next, then the long tail of ancillary areas.
Your time is worth more than a spool. Pulling fresh Cat6 in a clean pathway often beats hours of troubleshooting old conductors. I put a price on risk. If a reused cable fails during warranty, it becomes your problem. That price helps clients understand why new cable is not a luxury.
Security beyond cameras: planned coexistence
Once the network is trustworthy, it becomes the backbone for more than video. PoE access devices, smart readers, and small edge controllers can ride the same infrastructure. The trick is to plan segmentation. Use VLANs and QoS, document port roles, and keep access control traffic isolated from bulk video streams. Electronic door locks still need robust power separate from data, and supervision loops for life-safety doors have their own rules.
For alarm integration wiring, dry contact inputs between panels and VMS servers are low bandwidth but high consequence. If you must traverse the same pathways as cameras, keep conductor pairs twisted and dress them cleanly. Grounds for alarm panels, access controllers, and camera switches should not fight each other. When they do, you’ll see ghost inputs and chatter that wastes time.
A realistic migration path in practice
A typical mid-sized office might start with forty analog cameras, a few DVRs, and a mess of power supplies tucked into ceiling spaces. The path I’d choose:
- Survey all existing paths and coax conditions, test suspect runs, and tag which can be reused with EoC. Decide early where fiber makes sense for distant clusters. Build a cabling plan around floor-by-floor IDFs, with Cat6 to each camera location and spare drops to strategic points for future intercoms or readers. Specify switch models with PoE budgets that exceed worst-case draw by at least 20 percent.
With that foundation, week one focuses on backbone and IDFs. Week two pushes new cable to exteriors and main corridors. As runs are certified, mount the new cameras adjacent to old ones and bring them online to a staging network. Security staff can begin using the new VMS while the old DVRs still record.
Only after the core is stable do we cut over area by area, starting with exterior doors that benefit from higher quality and better night performance. Each night, a handful of analog cameras retire. If any reused coax creates noise, we swap in Category 6 during the next window. Parallel systems overlap just long enough to remove pressure from the cut.
That same plan usually accommodates a few access control upgrades. If an entrance needs a new reader or video intercom, the cable is already there. Card reader wiring goes to the controller panel, the camera and intercom ride the PoE switch, and event integration gets tested before the door goes live.
Troubleshooting the gremlins you will meet
A camera that drops every hour on the hour often points to a PoE budget reset or scheduled switch process. Check logs. If it drops when the HVAC kicks in, suspect EMI or a grounding issue on the run’s path. If it drops only during rain, water ingress at a midspan or a poorly sealed jack is likely. For cold-weather IR issues, I’ve seen voltage sag on marginal 100 meter runs that only shows when the heater and IR turn on together. Shorten the run with a closer switch or raise PoE class and measure voltage at the device.
For picture noise that won’t quit, swap in a short test lead directly to the switch. If the noise vanishes, the long run has a shielding or interference problem. If the noise stays, the camera sensor or its internal power regulation may be at fault. Avoid using PoE extenders back-to-back. Each one adds failure points. Better to place a small fiber-fed switch nearer the load.
What success looks like
When a migration lands well, the network feels quiet. Cameras stay up through storms. Intercom and entry systems ring reliably. Guards stop calling about phantom alarms. Your maintenance tickets drop by half. Months later, you add a camera in an area that security flagged, and it takes thirty minutes because the pathway, labels, and PoE are already in place.
That stability starts with the wire. Whether you reuse coax with care or pull fresh Cat6A, treat cabling as infrastructure, not a consumable. Plan for the power you will need, not just the power you need today. Respect grounding. Document as if a stranger will service the system next week. And when budgets push you to compromise, make those compromises in places you can reach without a lift and a prayer.
Migration is not a single recipe. It is a set of judgments informed by the building’s bones, the demands of your cameras and controls, and the tolerance for downtime. Get those judgments right, and the rest of the project moves the way a good network should, quietly, in the background, doing its job while everyone else focuses on theirs.