POTS Replacement: What IT Teams Must Migrate Before the Copper Goes Dark

Introduction

POTS replacement is the process of moving devices off analog copper phone lines onto cellular, IP, or managed alternatives before the carrier switches those lines off. It has quietly become an infrastructure project rather than a telecom line item, because the equipment still hanging off those lines – fire alarm panels, elevator phones, gate intercoms, card terminals and fax machines – was never designed to live anywhere else.

Most IT teams discover the problem the same way: a bill arrives with an analog line priced several times higher than last year, or a carrier notice announces that a copper facility is being retired at a specific address. By then, the migration is on someone else’s clock. This guide covers what POTS replacement actually involves, which devices are hardest to move, and how to sequence the work so nothing critical goes silent.

What is POTS, and Why is It Being Retired?

POTS stands for Plain Old Telephone Service – the analog voice circuit that has run over copper pairs for more than a century. The telephone exchange powers it, which is why a POTS handset keeps working during a building power cut. That single property is why so much life-safety equipment was standardized on it.

Carriers are retiring copper for three converging reasons:

• Regulation no longer forces them to keep it. Under the FCC’s technology-transition rules, notably Order 19-72, carriers can retire copper facilities after notifying affected customers, and are no longer held to the old price-cap regime on legacy analog service.
• The economics collapsed. Copper plant requires field technicians, physical splices, and exchange equipment that serves a shrinking number of lines. The cost per remaining line rises every year.
• The skills are retiring too. The workforce that maintains the analog outside plant is aging out, and carriers are not replacing it.

The practical effect is that analog lines are being repriced rather than merely switched off. Many organizations report per-line costs rising from a modest monthly fee to hundreds of dollars. A building with a dozen analog lines can see a five-figure annual increase without any service change.

What is Still Plugged into a POTS Line?

Almost every organization underestimates this number. Analog lines accumulate over decades and rarely appear in any asset register. A physical audit routinely finds twice as many live lines as the finance system shows.

The usual inventory:

The devices in the “High” row are the ones that turn a telecom refresh into a compliance project. Engineering judgment alone can’t move them.

Why Fire Alarm and Elevator Lines Need Special Handling

Fire alarm communications in the United States are governed by NFPA 72, which historically required two dedicated telephone lines for a digital alarm communicator and now permits alternative supervised transmission paths. Elevator emergency communication falls under ASME A17.1, which requires a two-way path to a monitoring point that answers around the clock.

For a migration, what matters is that both standards focus on supervision and power, not copper specifically. A replacement path must prove it is alive and survive a building power failure. That means the authority having jurisdiction – usually the local fire marshal or elevator inspector – signs off on the replacement, not the IT department. Build that approval into the schedule; it is often the longest lead time in the whole project.

How Do You Run a POTS Audit?

Start with the invoice, then physically verify every line. Carrier billing is the only complete list of what you are paying for, but it will not tell you what each line does. The audit closes that gap.

1. Pull twelve months of carrier invoices for every site and extract each billed telephone number, its circuit identifier, and its monthly cost.
2. Call each number from a mobile and record what answers – a modem tone, a fax handshake, a ring with no answer, an intercept message. This alone classifies a large share of the inventory.
3. Walk the demarcation point at each building. Trace live pairs to the device they terminate on and photograph the labeling.
4. Tag each line with its device, its owner, whether it is code-governed, and whether it carries data or only voice.
5. Flag the dead ones. Lines with no device attached are common and the fastest to save – disconnect them before designing anything.

The output should be one row per line. Anything you cannot identify stays live until you can, because the unidentified line is disproportionately likely to be the one holding up a fire panel.

What are the POTS Replacement Options?

Four approaches cover nearly every device. The right one depends on whether the device needs to survive a power cut, whether it is code-governed, and whether it is passing data rather than voice.

A realistic estimate is that a mixed estate ends up using three of the four. Standardizing on a single approach is the most common design mistake, because it forces either overspending on trivial devices or under-engineering the code-governed ones.

Why is Fax the Awkward One?

Fax is the device most likely to be quietly broken by a VoIP migration, because analog fax was designed for a circuit that never varies and IP networks vary constantly. A fax session is a real-time negotiation between two modems. Packet loss, jitter, or a transcoding step that voice callers would never notice will drop the page mid-transmission or corrupt it.

Teams usually try the technical fixes in this order:

• T.38 relay, the fax-over-IP protocol, which demodulates the fax signal and carries it as data. It works when both ends and every device in between implement it correctly – which is often not the case, since you control only your half of the call.
• G.711 pass-through, where the analog tones ride an uncompressed voice codec. This is more fragile still and needs a clean, low-jitter path end to end.
• Lowering the modem speed to 9600 baud and disabling error correction, which improves reliability at the cost of throughput and is a clear sign the underlying transport is unsuitable.

All three keep hardware, a line, and a failure mode in the estate to support a workflow that is usually a handful of pages a week. Before engineering around it, count the actual volume. When the requirement turns out to be occasional documents to counterparties who still insist on a fax number – clinics, law offices, insurers, government desks – you can drop the transport and send the document from software instead.

The mechanics are the same regardless of the provider: the file is converted to fax format, the call is negotiated on the provider’s side, and a delivery receipt is returned to the sender, so the receiving machine still sees an ordinary fax. mFax’s guide to sending a fax without a machine lays out that flow step by step, including what replaces the confirmation page.

Where fax volume is genuinely high, or where the receiving system is integrated into a records platform, keep it as a managed service with an API rather than as analog hardware. Either way, the goal is the same: the fax requirement survives; the copper does not.

How Should the Migration be Sequenced?

Order the work by consequence of failure, not by ease. The cheapest lines to move are rarely the ones with a deadline attached.

1. Disconnect dead lines: Immediate savings, no risk, and a smaller project.
2. Move low-stakes devices: Intercoms, courtesy phones, payment terminals. This builds operational familiarity with the chosen gateway before it matters.
3. Start the code-governed approvals in parallel: Fire and elevator sign-off runs on the inspector’s calendar, so open it early even though the cutover happens last.
4. Retire fax hardware once the replacement path is proven with real recipients, not just internal tests.
5. Cut over life-safety devices with the authority having jurisdiction present, and keep the copper line live in parallel until the new path has been supervised through a full test cycle.
6. Close the account only after you’ve verified every dependent device. Carrier disconnection is difficult to reverse.

What Does POTS Replacement Cost?

The honest answer is that it usually pays for itself, but not evenly across devices. A cellular analog gateway carries a hardware cost plus a monthly cellular plan, which is typically well below what a repriced analog line now costs. So life-safety lines often show the fastest payback despite being the most complex. Devices moved onto an existing SIP trunk cost almost nothing incrementally. Functions retired into a cloud service usually remove both the line and the hardware refresh from the budget.

The costs that get missed are labor and approval: the site walk, the inspector’s time, out-of-hours cutover windows, and the parallel-running period where you pay for both paths at once. Budget for that overlap explicitly rather than assuming a clean switch.

Frequently Asked Questions (FAQs)

The Takeaway

POTS replacement is not a telecom refresh with a compliance footnote – it is a compliance project with a telecom component. The technical choices are well understood, and the hardware is mature. What sinks schedules is discovering an unlabelled line under a fire panel three weeks before a carrier cutover, or assuming a fax workflow will survive a VoIP migration that it will not.

Audit first, sequence by consequence, and let each device end up on the transport that suits it. The organizations that treat this as an inventory problem finish it calmly. The ones that treat it as a billing problem finish it in an outage.