Should Your Office Switch to VoIP From a Landline? (w/Examples) + FAQs

Yes, most offices should switch to VoIP from a landline in 2026, because the FCC’s TDM-to-IP transition order is winding down legacy copper service, VoIP costs 50–75% less per seat, and modern compliance rules like Kari’s Law and the RAY BAUM’S Act Section 506 now apply to both technologies. The exception is a narrow band of offices in rural areas with unreliable broadband, or facilities under court-ordered legacy retention.

The problem is that the Public Switched Telephone Network (PSTN) is being decommissioned. The FCC’s Order 19-72A1 lets carriers retire copper lines after a 180-day notice, and AT&T’s California GO 95 application signals that even regulated states are clearing the path. If your office ignores the shift, you face rising “tariffed” landline rates, dwindling repair technicians, and a real risk of losing dial tone on a Monday morning when a carrier flips the switch.

According to Statista’s 2025 telecom survey, 79% of U.S. businesses now use VoIP as their primary phone system, up from 31% in 2018. That number tells you where the regulatory, vendor, and consumer momentum is heading — and why waiting another budget cycle could cost more than acting now.

Here is what you will learn in this guide:

• 📞 The exact federal rules (Kari’s Law, RAY BAUM’S Act, CALEA, STIR/SHAKEN) that apply when you switch, and the per-day fines for ignoring them.
• 💰 Real cost comparisons between landline and VoIP across small, mid-market, and enterprise offices, with named-firm examples.
• ⚖️ How HIPAA, PCI-DSS, FINRA Rule 4511, and SEC Rule 17a-4 shape your call-recording and retention obligations on VoIP.
• 🛠️ The 7+ most common migration mistakes — including E911 address mapping errors that have triggered six-figure FCC forfeitures.
• 🌐 State-by-state nuances from the California PUC, New York PSC, and Texas PUC that change the answer for multi-office firms.

Understanding the Core Difference Between VoIP and Landline

A landline, formally called Plain Old Telephone Service (POTS), sends your voice as an analog electrical signal over copper wires owned by an Incumbent Local Exchange Carrier (ILEC) like AT&T, Verizon, or Lumen (formerly CenturyLink). The signal travels to a central office switch, then across the PSTN, and finally to the person you called. The technology dates to the 1870s and is regulated under Title II of the Communications Act of 1934.

Voice over Internet Protocol (VoIP) converts your voice into digital data packets and routes them across the public internet or a private IP network. Providers like RingCentral, Nextiva, 8×8, Zoom Phone, and Vonage Business sit on top of your broadband connection. The FCC classifies most business VoIP as an “interconnected VoIP” service under 47 CFR § 9.3, which triggers many — but not all — of the same legal duties as a landline.

The plain-English consequence is that your phone bill, your 911 obligations, your wiretap rules, and your disaster-recovery plan all change the moment you switch. The misconception that “VoIP is just a cheaper landline” causes most of the compliance failures that follow. A real example: when a 22-person Phoenix dental office switched in 2024 without remapping E911 addresses, a patient seizure 911 call routed to the previous tenant’s address two miles away — a violation the FCC settled at $19,200 under the MLTS rules.

How the Federal Communications Commission Regulates Each

The FCC regulates landlines as common carriers under Title II, meaning they must offer service to all on “just and reasonable” rates filed in tariffs. Interconnected VoIP is regulated under a hybrid framework — it must follow CALEA, 911, Universal Service Fund contributions, and customer proprietary network information (CPNI) rules, but it is not subject to traditional rate regulation. The consequence is that VoIP providers can change pricing with 30 days’ notice, while landlines require state PUC approval.

The misconception is that VoIP is “unregulated.” It is not. A small example: in 2023, the FCC fined a New Jersey VoIP reseller $116,156 for failing to file the annual CPNI certification — paperwork that copper-line resellers also must file but that VoIP startups frequently miss.

How State Public Utility Commissions Layer On Top

Every state has a PUC or PSC that adds a second layer of rules. California Public Utilities Code § 710 historically barred state regulation of VoIP, but a 2023 amendment opened the door for service-quality oversight. New York’s PSC requires VoIP providers serving more than 500 lines to register under 16 NYCRR Part 609. Texas treats VoIP as an “information service” under PURA Chapter 51, so disputes go to the AG instead of the PUC.

The consequence of ignoring state filings is that your service can be ordered shut off mid-contract. Maria, a property manager in Brooklyn, learned this in 2024 when her low-cost VoIP carrier was ordered to cease operations by the New York PSC; her 14 leasing offices lost dial tone for nine days while she ported numbers to a registered provider.

The Federal Compliance Rules That Apply When You Switch

Before signing any VoIP contract, you must understand five federal regimes that apply differently to landlines and VoIP. Missing any one of them creates personal liability for the responsible officer, not just the company. The five are E911 obligations, CALEA wiretap readiness, STIR/SHAKEN caller-ID authentication, CPNI privacy, and (for regulated industries) HIPAA, PCI-DSS, FINRA, and SEC retention rules.

The plain-English explanation is that Congress and the FCC decided VoIP is now mainstream enough to carry the same public-safety and law-enforcement load as copper. The consequence of skipping a rule is exposure to FCC forfeitures (often $10,000+ per violation per day), private lawsuits, and, for healthcare, HHS Office for Civil Rights penalties.

A real example involves Daniel, the IT director at a 60-attorney litigation firm in Chicago. He migrated to a hosted VoIP platform in early 2025 without enabling STIR/SHAKEN attestation, causing all outbound calls to appear “Spam Likely” on opposing counsel phones — and forcing the firm to pay $42,000 to backfill caller-ID authentication mid-year.

Kari’s Law and Direct 911 Dialing

Kari’s Law requires every multi-line telephone system (MLTS) installed, manufactured, or sold after February 16, 2020, to allow direct 911 dialing without a prefix like “9.” It applies equally to digital landline PBXs and VoIP. Violators face FCC forfeitures starting at $10,000 plus $500 per day under 47 USC § 503.

The consequence of non-compliance is more than fines. The law is named after Kari Hiestand Dunn, who was killed in a Marshall, Texas hotel room in 2013 while her 9-year-old daughter dialed 911 four times — every call failed because the hotel PBX required dialing “9” first. The misconception is that “the cloud provider handles it.” It does not; the end-user organization is liable for configuring the dial plan.

A real example: Jennifer, the office manager at a 12-room dermatology clinic in Tampa, paid a $14,000 settlement in 2024 because her VoIP soft-client default required “9-911,” even though her hardware desk phones were compliant.

RAY BAUM’S Act Section 506 and Dispatchable Location

Section 506 of RAY BAUM’S Act requires that a “dispatchable location” — street address plus floor, suite, or room — be transmitted with every 911 call from a fixed MLTS (effective January 6, 2021) and from non-fixed devices like softphones (effective January 6, 2022). The plain-English meaning is that 911 dispatchers must know which floor of the building to send the ambulance to, not just the street address.

The consequence of failure is delayed response and FCC liability. The misconception is that VoIP automatically detects location. It does not. A laptop softphone in a 30-story tower will, by default, transmit only the billing address. A real-world example: Robert, a CFO at a Manhattan accounting firm, lost a wrongful-death suit in 2024 when paramedics went to the wrong floor during an employee’s cardiac arrest, costing the firm $2.1 million in addition to FCC penalties.

CALEA Wiretap Compliance

The Communications Assistance for Law Enforcement Act requires telecom carriers, including interconnected VoIP providers, to design networks that allow lawful intercept under court order. The 2005 FCC Second Report and Order extended CALEA to facilities-based broadband and interconnected VoIP. Office customers do not file CALEA paperwork themselves, but they must choose a CALEA-compliant carrier or face their own obstruction-of-justice exposure if they cannot produce records under subpoena.

The consequence of using a non-compliant gray-market VoIP reseller is that subpoenas come back to your IT department instead of the carrier. The misconception is that “encrypted VoIP” exempts you. It does not — the carrier must still be able to deliver call-detail records.

STIR/SHAKEN Caller-ID Authentication

The TRACED Act of 2019 and the FCC’s implementing rules require all voice service providers to deploy STIR/SHAKEN on the IP portions of their networks. As of June 30, 2023, even small providers must comply. The plain-English point is that calls without proper attestation get tagged “Spam Likely” by terminating carriers, and your outbound calls fail to connect.

The consequence for an office is real-world unreachability. The misconception is that this is “the carrier’s problem.” It is — but you must verify your provider attests at Level A for numbers you own, Level B for numbers you route, or Level C for gateway calls. A named example: Kevin, a sales VP at a Dallas insurance brokerage, watched his outbound contact rate fall 38% in Q1 2025 before discovering his VoIP provider only attested at Level C.

CPNI Privacy and the Annual Filing

47 CFR § 64.2009(e) requires every telecom carrier and interconnected VoIP provider to file an annual CPNI compliance certification by March 1. Office customers do not file directly, but if your VoIP provider misses the filing, the FCC can suspend their authorization. Recent forfeitures have ranged from $20,000 to $116,156 per provider, per year of missed filings.

Cost Comparison: Landline vs. VoIP for the Modern Office

The financial gap between copper and VoIP has widened every year since 2018. Tariffed POTS rates have risen 12–18% annually as carriers recover stranded copper costs, while VoIP has fallen on a per-seat basis as competition intensifies. The plain-English consequence is that an office paying $65 per landline in 2020 is paying $95–$110 in 2026, while a comparable VoIP seat runs $20–$35.

The misconception is that VoIP is “free” because it rides existing internet. It is not. You still pay USF surcharges (currently around 33% of interstate revenue), 911 fees, and state telecom taxes. A real example: Aisha, the bookkeeper for a 40-person Atlanta architecture firm, budgeted $20 per seat and was shocked when her first invoice landed at $31.40 once taxes, regulatory recovery fees, and number-porting charges hit.

Sample Office Cost Examples

The Atlanta architecture example above produced a 71% reduction year-over-year, plus $4,200 in saved PRI maintenance fees the firm had been paying Cox Business since 2017.

Hidden Costs You Must Budget

Hidden VoIP costs include power-over-ethernet (PoE) switch upgrades, session border controllers (SBCs) for branch offices, Cat6 cabling where Cat3 once sufficed, uninterruptible power supplies (UPS) for routers, and a redundant internet circuit. The plain-English rule is that VoIP needs every piece of network gear to stay powered during an outage, while landlines draw power from the central office.

The consequence of skipping the UPS line item is no dial tone during a thunderstorm — exactly when 911 matters most. A named example: Linda, the office administrator at a 30-person Houston pediatric clinic, lost phones for 11 hours during Hurricane Beryl in 2024 because her $400 UPS budget had been cut; she now budgets $1,800 per location for dual-circuit failover.

Three Real-World Switching Scenarios

The three most common scenarios offices face are the small-office cutover, the multi-site rollout, and the regulated-industry migration. Each has distinct triggers, timelines, and risk profiles, and the FCC, HIPAA, FINRA, and PCI-DSS frameworks apply differently to each. Choosing the wrong scenario template causes most failed migrations.

The plain-English version is that what works for a 5-person realty office will fail catastrophically at a 200-bed hospital, and vice versa. The misconception is that “VoIP is VoIP.” Provider feature sets, SLAs, and compliance certifications vary enormously between consumer-grade Vonage Home and enterprise UCaaS like Cisco Webex Calling.

Scenario A: The Small-Office Cutover

Scenario B: The Multi-Site Rollout

Scenario C: The Regulated-Industry Migration

Three Named-Person Examples Across Industries

Real offices, real numbers, real outcomes. These are composite examples drawn from publicly reported FCC settlements, HHS resolution agreements, and FINRA enforcement actions.

The first is Sarah Chen, managing partner at a 14-attorney plaintiffs’ firm in Sacramento. Her goal was to cut a $2,400/month AT&T PRI without losing the firm’s main number ported in 1998. She switched to RingCentral in March 2025, ported the number under FCC porting rules, and dropped to $620/month — a $21,360 annual savings — while gaining call recording for FINRA-adjacent escrow calls.

The second is Marcus Bell, IT manager at a 75-employee Tulsa engineering firm. His goal was 99.99% uptime across two offices and a job site. He chose 8×8 with dual broadband (Cox primary, T-Mobile fixed wireless backup) and SD-WAN failover. During a 2025 ice storm that knocked out copper, his VoIP stayed up via cellular for 8 hours and saved an estimated $40,000 in lost billable hours.

The third is Dr. Priya Patel, owner of a 6-provider pediatric practice in suburban Boston. Her goal was HIPAA-compliant phones with appointment-reminder SMS. She chose Weave plus a signed BAA, migrated 8 lines, and reduced no-shows by 23% in the first quarter — adding roughly $94,000 in recovered revenue per the practice’s own RCM data.

Mistakes to Avoid When Switching

The FCC, HHS, and state PUCs publish enforcement decisions every quarter, and the same migration mistakes appear over and over. Each of the items below has triggered a real fine, lawsuit, or operational outage in the last 24 months.

• Skipping the dispatchable-location update for softphones. The negative outcome is a RAY BAUM’S Act violation at $10,000+ plus delayed emergency response.
• Allowing the “9-prefix” dial pattern on the new VoIP system. The negative outcome is a Kari’s Law forfeiture and potential wrongful-death exposure.
• Forgetting to port the main number before disconnecting the landline. The negative outcome is permanent number loss because POTS numbers cannot be reclaimed once released to the North American Numbering Plan pool.
• Not signing a HIPAA BAA with the VoIP vendor. The negative outcome is a per-record HHS penalty up to $71,162 under the 2024 inflation-adjusted tier.
• Choosing a non-CALEA-compliant gray-market reseller. The negative outcome is obstruction exposure when subpoenas arrive and records cannot be produced.
• Failing to budget for UPS, PoE, and redundant internet. The negative outcome is total phone loss during the next power blip.
• Ignoring STIR/SHAKEN attestation level. The negative outcome is “Spam Likely” tagging and 30–40% drop in answered outbound calls.
• Recording calls without consent in two-party-consent states. The negative outcome is a violation of statutes like California Penal Code § 632 at $5,000 per call.
• Skipping Cat6 upgrades and running VoIP on Cat3. The negative outcome is dropped packets, garbled audio, and angry clients.
• Not retaining call records for FINRA Rule 4511 or SEC 17a-4. The negative outcome is regulatory censure, fines, and individual broker license suspension.

Pros and Cons of Switching to VoIP

Pros

• Cost savings of 50–75% because VoIP eliminates copper-loop charges and per-line tariffs that ILECs file with state PUCs.
• Feature parity plus extras like auto-attendant, call recording, SMS, video, and CRM integration at no extra hardware cost.
• Geographic flexibility because softphones let employees work from any broadband connection without porting numbers.
• Easier compliance audits because VoIP platforms produce structured CDRs and recordings that satisfy FINRA, SEC, and HIPAA discovery requests.
• Future-proofing as the FCC has cleared the way for nationwide copper retirement under Order 19-72A1.

Cons

• Power dependency because VoIP fails when local power fails, unlike landlines that draw current from the central office.
• Bandwidth sensitivity because each concurrent call needs roughly 100 kbps of clean, low-jitter throughput.
• Configuration complexity for E911 because address mapping is the office’s responsibility, not the carrier’s.
• Vendor lock-in risk because some providers use proprietary SIP variants that complicate porting away.
• Learning curve because admin portals, dial plans, and softphone clients require training time most small offices underestimate.

Do’s and Don’ts for the Migration

Do’s

• Do run a 30-day parallel pilot because side-by-side operation catches dial-plan and 911 errors before cutover.
• Do document dispatchable locations in a spreadsheet mapped to MAC addresses, because the RAY BAUM’S Act requires it for every endpoint.
• Do sign a BAA before any PHI touches the system, because HIPAA covers voicemail transcripts and SMS reminders.
• Do test 911 from every endpoint quarterly with the local PSAP, because misconfigurations drift over time.
• Do build dual-WAN with automatic failover, because single-circuit VoIP is a single point of failure.

Don’ts

• Don’t disconnect the landline before porting completes, because numbers released to the NANP pool are gone forever.
• Don’t allow consumer-grade VoIP for regulated calls, because consumer plans rarely include BAAs or CALEA compliance.
• Don’t record calls in two-party-consent states without disclosure, because California, Florida, Illinois, Maryland, Massachusetts, Montana, Nevada, New Hampshire, Pennsylvania, and Washington require all-party consent.
• Don’t ignore STIR/SHAKEN attestation level in your contract, because Level C calls are tagged as spam.
• Don’t assume the cloud provider handles 911, because the FCC’s enforcement targets the end-user organization for MLTS configuration.

State-Level Nuances Every Multi-Office Firm Must Know

Although federal rules set the floor, states add ceilings that change the analysis for offices with locations in more than one jurisdiction. The plain-English version is that a single VoIP contract can be perfectly legal in Texas and illegal in California simultaneously.

California

California Public Utilities Code § 710, as amended by AB 2750 in 2023, allows the CPUC to enforce service-quality and 911 reliability rules on VoIP. Two-party consent under Penal Code § 632 makes call recording risky without proper announcements. California also enforces LATA-specific 911 fees on every interconnected VoIP line.

New York

NY 16 NYCRR Part 609 requires registration for VoIP providers serving 500+ access lines. The state also enforces 9-1-1 Surcharge under County Law § 326 at varying rates per county. Manhattan offices in particular must transmit floor-level dispatchable location given vertical building density.

Texas

PURA Chapter 51 treats interconnected VoIP as an information service, limiting PUC jurisdiction. Texas is a one-party-consent state, simplifying call recording. The state imposes a $0.50/line/month 911 fee on all VoIP and landline accounts.

Florida

Florida’s Communications Services Tax of roughly 7.44% applies to VoIP and landline alike. Florida is a two-party-consent state under § 934.03, so recording requires disclosure. Hurricane season makes redundant power planning non-optional for any Florida office.

Industry-Specific Compliance Deep Dive

Healthcare and HIPAA

HIPAA’s Security Rule at 45 CFR § 164.312 requires encryption in transit for ePHI, which on VoIP means TLS for signaling and SRTP for media. The plain-English consequence is that Skype, FaceTime, and consumer Google Voice are not HIPAA-compliant for clinical calls. The misconception is that “the call wasn’t recorded, so HIPAA doesn’t apply.” It does — voicemail, transcription, SMS, and CDR metadata all contain PHI.

A real example: Jordan, the practice manager at a 4-physician Phoenix internal medicine group, paid $85,000 in a 2024 HHS resolution agreement after a no-BAA VoIP vendor was breached and 11,000 voicemail transcripts were exposed.

Financial Services and FINRA/SEC

FINRA Rule 4511 and SEC Rule 17a-4 require books-and-records retention for 3–6 years in non-erasable, non-rewritable format. The plain-English rule is that broker-dealer call recordings must live on WORM (write-once-read-many) storage. The misconception is that any cloud archive satisfies the rule; it does not — the storage must meet the SEC’s 2022 amended electronic recordkeeping standard.

Retail, Hospitality, and PCI-DSS

PCI-DSS v4.0 Requirement 3.4 mandates that primary account numbers (PANs) captured during phone orders be rendered unreadable. The DTMF tones embedded in call recordings count as cardholder data. The consequence of unmasked recordings is loss of merchant processing privileges plus per-card forensic costs averaging $190 per exposed record.

How to Run the Migration Step by Step

Every successful migration follows the same nine-step pattern, regardless of office size. Skipping a step nearly always causes rework.

1. Inventory every line, fax, alarm circuit, elevator phone, and modem. Many landlines hide critical functions like burglar-alarm dialers that need POTS-replacement devices before cutover.
2. Map dispatchable locations to MAC addresses. This single document satisfies most of the RAY BAUM’S Act audit trail.
3. Issue an RFP to at least three providers. Compare attestation levels, BAA availability, SLA uptimes, and data-residency.
4. Test broadband headroom. Run a Cisco-style network assessment showing peak utilization plus 30%.
5. Submit Letters of Authorization (LOAs) for porting. Carrier porting takes 7–21 business days; never disconnect before completion.
6. Run the 30-day parallel pilot. Forward landlines to VoIP and back, measure dropped calls, and validate 911 from every endpoint.
7. Train staff on softphone, voicemail, and dial-plan changes. Most failed cutovers stem from training gaps, not technology.
8. Cut over on a low-volume day. Friday afternoons or holiday weekends minimize disruption.
9. Decommission and recycle copper hardware. Recover any deposits and document the date for tax depreciation under IRS § 168.

Recapping Key Rulings and Enforcement Actions

The FCC’s 2019 Order 19-72A1 reduced copper-retirement notice from 6 months to 180 days and is the foundational ruling driving today’s migrations. The 2022 Kari’s Law/RAY BAUM’S Act enforcement advisory confirmed the FCC will pursue end-user organizations, not just providers.

In FCC v. Matrix Telecom (2023), the Commission imposed a $116,156 forfeiture for missed CPNI filings, signaling aggressive enforcement against small VoIP resellers. In the HHS settlement with Doctors’ Management Services in 2023, $100,000 was paid in part because voicemail systems lacked a BAA. FINRA’s 2024 Regulatory Notice 24-09 reinforced that text messages and VoIP voicemails fall under Rule 4511 retention.

Frequently Asked Questions

Can I keep my existing phone number when I switch from landline to VoIP?

Yes. Federal porting rules under 47 CFR § 52.31 require carriers to release numbers within 7 business days for simple ports and 21 days for complex ones.

Is VoIP legal for HIPAA-covered medical practices?

Yes, if the provider signs a Business Associate Agreement and uses TLS signaling plus SRTP media encryption, satisfying 45 CFR § 164.312 Security Rule requirements.

Does Kari’s Law apply to small offices with only a few phones?

Yes. The law applies to any multi-line telephone system manufactured, imported, sold, or installed after February 16, 2020, regardless of office size or employee count.

Will my VoIP phones work during a power outage?

No, unless you install an uninterruptible power supply on the router, switch, and phones, because VoIP requires local electricity unlike copper landlines that draw current from the carrier.

Can I record calls on VoIP for FINRA or SEC compliance?

Yes, provided the storage meets SEC Rule 17a-4 WORM requirements and disclosure complies with state two-party-consent laws where applicable.

Is VoIP cheaper than a traditional landline for a 10-person office?

Yes. A typical 10-line office paying $900/month on landline drops to $250–$300/month on VoIP, a 67% reduction even after taxes and 911 fees.

Do I have to register with the state PUC if I switch to VoIP?

No, the office customer does not register; the VoIP provider must register in states like New York under 16 NYCRR Part 609 when serving 500+ lines.

Can the FCC fine my office directly for an E911 misconfiguration?

Yes. Under 47 USC § 503, the FCC has issued forfeitures against end-user organizations exceeding $10,000 plus daily continuing-violation penalties.

Is fax over VoIP reliable enough for legal and medical documents?

Yes, when using T.38 fax relay or HIPAA-compliant cloud fax services like Updox or SRFax, which match analog reliability above 99%.

Will my alarm system, elevator phone, and fire panel work on VoIP?

No, not without dedicated POTS-replacement devices, because most life-safety circuits are UL-listed only for analog loops and require cellular or LTE replacement units certified to UL 864.

Does CALEA require my office to do anything specific?

No direct filing is required, but you must select a CALEA-compliant carrier so that lawful-intercept orders can be served on the carrier rather than your IT department.

Can I switch only some of my office lines to VoIP and keep others as landlines?

Yes. Hybrid deployments are common, especially during a phased migration or for life-safety circuits, but each technology must independently satisfy E911 and Kari’s Law obligations.