Can I reuse the existing analog cable for SIP devices?

Only after testing. A Category run in point-to-point topology may carry Ethernet, but many analog installs are daisy-chained or use non-Category wire. Certify each riser before you depend on it; do not trust the label.

Do I need 802.3at PoE or is 802.3af enough?

It depends on the device class. 802.3af (Type 1) suits low-power devices; 802.3at (Type 2) is needed when the device draws more. Match class to port class and check the switch's total budget against all ports summed.

Should the new numbers match the old analog codes?

Reusing numbers occupants know reduces training and support. Keep the plan flat with reserved blocks for doors, floors, and paging, and avoid encoding building-specific meaning that forces a later re-number.

How do I cut over without losing access?

Migrate one zone at a time with analog live in parallel until that zone passes acceptance. Document a physical or logical rollback and confirm you can restore the prior state quickly before touching anything.

What should the handover package include?

As-built VLAN IDs, PoE class per port, the dial-plan document, registration and CDR baselines, and per-zone rollback steps. Without these, the building stays dependent on the installer's memory.

Is the SIP server the hard part of migration?

Usually not. Registration and routing are straightforward; the difficult work is the building itself - surveying legacy cable, delivering power, and staging a cutover that never removes a working safety or access path.

ENGINEERING · MIGRATION · 8 min read

Migrating Analog Intercoms to SIP: A Field Plan

A field plan for moving building intercoms from analog cabling to SIP: survey first, deliver power, renumber, and cut over in stages with a real rollback.

2026-11-06 · FlySip engineering · All guides

Analog intercom systems are still installed in thousands of buildings, but spare parts and trained technicians get harder to source every year. When a manager asks to modernize, the question is not whether SIP is better on paper, but how to migrate without removing working safety and access paths.

This is a field plan, not a sales pitch. It covers four work streams that decide success: a site survey before procurement, power over structured cabling, extension numbering that survives a multi-building rollout, and a staged cutover with a real rollback. The server is the easy part; the building is the hard part.

Start With a Site Survey, Not a Bill of Materials

Before quoting hardware, walk the site with a tone tester, a cable mapper, and the existing drawings. Analog intercoms were often installed by many contractors over decades, so the documentation rarely matches reality. You are checking three things: what the cabling is, how devices are powered today, and where riser capacity is already consumed.

Cabling type decides whether you can reuse the path. A run to a door station may be Category cable of sufficient grade, or it may be daisy-chained in a topology Ethernet cannot use. The only way to know is to test, not to assume the riser label is accurate.

Cable grade. Certify each riser supports 100BASE-TX or 1000BASE-T end to end.
Topology. Ethernet needs point-to-point links; a tapped analog bus needs one port per device.
Power today. Note local supply, central UPS, or a 24V/48V common bus - it drives your PoE decision.
Existing codes. Capture apartment, floor, and door codes so the new plan maps onto what occupants know.

Power Delivery: PoE Standards and Local Supplies

Most SIP terminals and video door stations can be powered by Power over Ethernet, keeping the device, switch port, and building UPS on one bill of materials. The standards are 802.3af (Type 1, lower-power) and 802.3at (Type 2, often marketed as PoE+). A device that draws more than the 802.3af budget needs an 802.3at port, and a switch must budget PoE for every port at once, not the nameplate per-port figure.

Where the run cannot support PoE - a long legacy cable, or a device above the port class - fall back to a local supply on the same UPS that powers the analog system. The point is not which method is 'better'; it is that the access path stays powered under the same failure modes the building already plans for.

Rule of thumb: match the device class to the port class, and verify the switch's total PoE budget against all ports summed, not the per-port number.

Extension Numbering and the Dial Plan

SIP uses extensions - addresses registered to the server - instead of physical wire pairs. Reuse the model occupants know: floor, zone, room. If apartment 1203 dials '12' for the lobby today, the new extension can stay '12' or become '1200', as long as the mapping is documented and consistent.

Two mistakes dominate failures. One is letting each building pick its own scheme, causing collisions when sites are networked. The other is encoding too much meaning into digits, forcing a re-number on re-org. Keep the plan flat and documented, with reserved blocks for doors, floors, and paging.

Doors and gates: a contiguous block, e.g. 8000-8099, so access logic reads clearly in logs.
Floors and desks: a prefix per building, e.g. A = 1xxx, B = 2xxx.
Paging zones: a small block such as 9000-9099 for all-call and zone paging.
Keep a gap: leave ranges free so future phases never collide with today's assignments.

Staged Cutover and a Real Rollback

Do not migrate a whole building in one night. Cut over one floor, wing, or door at a time, keeping the analog path live in parallel until the SIP path passes acceptance for that zone. This limits the blast radius of a bad VLAN or power budget to one area, not the whole property.

Rollback is a plan, not a hope. Before touching a zone, confirm you can reconnect the original analog station and that its power and cabling were not disturbed. Photograph terminations. If you cannot restore the prior state in under an hour, that zone is not ready.

Week 1: one low-risk zone on SIP, analog still live.
Week 2: expand to busy doors only after the pilot passes call, access, and power tests.
Hold analog hot: keep the legacy controller powered and cabled until full sign-off.
Document each zone: as-built VLAN, extension map, and the exact rollback step.

Verification Before You Declare Done

Acceptance is not 'the phone rang once.' For each zone, verify registration stability over a full day, call completion both ways, door-release from designated extensions, and paging audibility at the farthest speaker. Capture registration state and a sample CDR as a baseline.

Hand over the as-built: VLAN IDs, PoE class per port, the dial-plan document, and rollback notes. A migration that leaves the building dependent on the installer's memory has not finished - it has been deferred.

Frequently asked questions

Can I reuse the existing analog cable for SIP devices?: Only after testing. A Category run in point-to-point topology may carry Ethernet, but many analog installs are daisy-chained or use non-Category wire. Certify each riser before you depend on it; do not trust the label.
Do I need 802.3at PoE or is 802.3af enough?: It depends on the device class. 802.3af (Type 1) suits low-power devices; 802.3at (Type 2) is needed when the device draws more. Match class to port class and check the switch's total budget against all ports summed.
Should the new numbers match the old analog codes?: Reusing numbers occupants know reduces training and support. Keep the plan flat with reserved blocks for doors, floors, and paging, and avoid encoding building-specific meaning that forces a later re-number.
How do I cut over without losing access?: Migrate one zone at a time with analog live in parallel until that zone passes acceptance. Document a physical or logical rollback and confirm you can restore the prior state quickly before touching anything.
What should the handover package include?: As-built VLAN IDs, PoE class per port, the dial-plan document, registration and CDR baselines, and per-zone rollback steps. Without these, the building stays dependent on the installer's memory.
Is the SIP server the hard part of migration?: Usually not. Registration and routing are straightforward; the difficult work is the building itself - surveying legacy cable, delivering power, and staging a cutover that never removes a working safety or access path.

Plan the network before you install devices - see SIP intercom network planning with VLAN and QoS. For a comparison with open-source PBX builds, read SIP appliance vs Asterisk and FreeSWITCH, and start your design from the FlySip product overview.