Copper retirement is the most-announced and least-acted-on telecom story of the decade. Carriers have been signaling it for years, businesses have deferred it every year, and the result is now very concrete: companies discovering that their fax line, their card terminal, or their elevator emergency phone no longer works, without ever having received a notice they knew how to read.
The difficulty is not technical — moving business telephony to IP is straightforward. It is the shape of the timeline: there is no national cutoff date. Retirement advances wire center by wire center, and every company has its own deadline.
This guide gives the real timeline, the list of devices that fail, and the migration plan in the order it has to be executed.
POTS, copper, PSTN: getting the words straight
Three terms circulate and get used interchangeably. The confusion has practical consequences, so let us clear it now.
- POTS (Plain Old Telephone Service) is the service: the classic analog line, where each call opens a dedicated circuit and the line carries its own power.
- The PSTN is the public switched telephone network as a whole — the legacy voice network that POTS lines connect to.
- Copper is the physical infrastructure: the pairs running from the central office to your building. It is what is being retired, and retiring it takes down everything running on it, DSL included.
In other words, “POTS retirement” and “copper retirement” are two stages of the same move. The first stopped the sale; the second physically disconnects.
The real timeline
Two mechanisms operate at once, and they do not affect you the same way.
Mechanism 1: the commercial freeze
This is the end of selling. Since October 2025, AT&T has stopped accepting new orders and stopped processing adds, moves and changes on copper-based services. Other carriers have run comparable programs.
Practical effect: you cannot add a line, relocate a line, or change a circuit. Your current installation still runs — but it is frozen.
Mechanism 2: the physical retirement
This is the actual disconnection, wire center by wire center. Under Section 214(a) of the Communications Act, a carrier that wants to discontinue a service must apply to the FCC. Those applications are specific: AT&T’s July 2026 filing covered residential POTS, business POTS and certain legacy wireline VoIP services across portions of 55 wire centers in 13 states.
AT&T’s stated goal is to retire copper across most of its footprint by the end of 2029.
| What you need to know | When it happens |
|---|---|
| You can no longer order a new copper line | Already in effect |
| You can no longer move or modify what exists | Already in effect |
| Your analog lines stop working | Retirement of your wire center |
| Copper largely gone across AT&T’s footprint | End of 2029 |
What breaks, and what nobody inventoried
In nearly every failed migration, the phones were not the problem. It was the equipment plugged into a phone jack that nobody associates with telephony any more.
| Device | What happens at cutover | Common fix |
|---|---|---|
| Elevator emergency phone | No emergency call path — immediate code exposure under ASME A17.1 | Cellular replacement unit, validated by the elevator service provider |
| Fire alarm communicator | No transmission to the monitoring center | IP or cellular communicator; NFPA 72 recognizes both, confirm with your AHJ |
| Burglar alarm / monitoring panel | No signal to the central station | IP or cellular path, per the monitoring contract |
| Dial-up credit card terminal | No payment authorization | IP or LTE terminal |
| Fax machine | No send or receive | Fax over IP, or move to digital fax |
| Emergency call box | No call path | Cellular unit |
| Postage meter | No remote refill | Network connection |
| Gate intercom, door phone | No inbound call to the handset | Analog terminal adapter or cellular module |
| Out-of-band backup line | No fallback access to network gear | LTE out-of-band management |
A copper migration is not prepared in the telecom closet. It is prepared by walking the building, jack by jack.
For life-safety equipment — elevators, fire alarm communication paths, emergency call boxes — apply one rule: prefer a solution that does not depend on the site’s internet connection. An elevator whose emergency line rides the same fiber as the office network stops calling for help at exactly the moment the site has a general problem. And validate every one of those choices with the equipment’s service provider and your authority having jurisdiction, because code compliance, not telecom convenience, governs them.
The six-step migration plan
Date every site
For each location, get the copper retirement status and any notice date in writing from the carrier. You end up with a priority order that is rarely the one you expected: it is not headquarters that goes first, it is the site in the earliest wire center.
Physically inventory the jacks
Walk the buildings and list everything plugged into a phone jack, including in mechanical rooms, elevator machine rooms and storage areas. For each device: what it does, who services it, and whether losing it is an inconvenience or a safety issue.
Qualify the internet at each site
Voice needs little bandwidth but a lot of consistency. Check upstream capacity at peak and whether voice traffic can be prioritized. A site still on aging DSL makes its own connectivity upgrade the prerequisite for everything else.
Choose the target system
A cloud phone system in the large majority of cases, an on-premise IP-PBX with SIP trunking where sovereignty or connectivity demands it. The comparison is in our business phone system guide.
Handle the analog devices
One owner per device: the elevator company, the alarm monitoring provider, the bank for the card terminal. These conversations are slow. They must start early and run in parallel with the telephony work, not after it.
Port, test, cut over
Submit the LOA with a recent bill or customer service record. Configure in parallel, test every path, then cut over. Never cancel the old service before the port completes.
What it costs, and why it is usually a saving
The recurring line almost always goes down. A legacy installation stacks line charges, a PBX maintenance contract, and metered usage. A cloud system replaces all of it with one per-user subscription, $15 to $40 per month depending on feature tier, with domestic calling typically included.
The real migration costs are one-time and identifiable:
- Replacement units and adapters for retained analog devices: tens to a few hundred dollars per device, more for certified life-safety units.
- Connectivity upgrades at sites still on aging circuits.
- Internal time: inventory and testing, a few person-days depending on site count.
- Desk phones, only if you want them: softphones cover most users.
The five mistakes that turn a migration into an incident
- Waiting for the carrier’s letter. Notices exist, but they land in an account inbox and get lost. Check your own sites now, in writing.
- Only handling headquarters. Satellite sites — depots, branches, plants — carry the critical devices and are the ones IT never visits.
- Cancelling before the port. The number returns to the pool and is unrecoverable.
- Leaving the elevator until last. Lead times for certified life-safety replacements run into weeks or months. That is the project’s critical path, not a finishing touch.
- Migrating without qualifying the network. Saturated bandwidth or a router with no voice prioritization produces drops that everyone will blame on VoIP, wrongly.
What to take away
POTS retirement is not a hard technical project. It is an inventory project, with a deadline that is specific to you and a critical path that does not run through the phones but through the equipment nobody looks at.
The order is always the same: date your sites, walk the jacks, qualify the network, and only then choose the solution. The companies that suffer through this migration are the ones that started with the last step.
If the topic pushes you to compare the two worlds properly, our business VoIP guide covers the network prerequisites, real costs and rollout checklist in detail.
