Blog

PBX Migration and 911: Why Cutover Resets Your Compliance

A PBX or cloud phone system migration can quietly break 911 compliance. What changes at cutover, and how to keep Kari's Law and RAY BAUM's Act intact.

June 25, 2026

Reading time

Product

When you move to a new calling platform, whether it's a PBX migration or a move to the cloud, the project plan covers number porting, call flows, hardware, and user training. It almost never covers the one thing with federal penalties attached: whether 911 still works the way the law requires the day after cutover. FCC penalties are $10,000 per violation, plus $500 for each day the violation continues.

Phone system migrations are some of the most carefully managed projects an IT team runs. There are runbooks, rollback plans, and weeks of testing. And yet the single most consequential call a system will ever place, 911, is routinely the one nobody validates. Compliance that took months to build under the old platform is quietly assumed to carry over to the new one. It usually doesn't.

Migration is the moment compliance quietly breaks

Kari's Law and RAY BAUM's Act don't regulate your old system or your new system. They regulate whatever is carrying the call right now. A migration rebuilds the dial plan, re-homes users onto new network paths, and changes how location is determined. Every assumption your previous compliance setup depended on is back on the table. The legal obligation doesn't pause for the cutover weekend.

"The new platform handles 911" is doing a lot of work in that sentence

Most modern calling platforms can route a 911 call. That is not the same as being compliant. Direct dialing without a prefix, on-site notification to a person who can respond, and a dispatchable location specific enough to find the caller are three separate requirements, and a platform that technically connects 911 may default to satisfying none of them. "It's included" and "it's configured correctly for your buildings" are very different statements, and the gap between them is where organizations get caught.

Three things that silently change during a cutover

  • Dispatchable location mapping. Location data is often tied to the old network: switch ports, subnets, wireless access points, or manual address assignments. Re-home those users onto new infrastructure and the mapping can break or revert to a single building-level address that tells a responder nothing.
  • On-site notification routing. The alert that's supposed to reach a front desk, security desk, or on-call phone is frequently pointed at a system or workstation that is being decommissioned in the same project. The notification still "works," but nobody receives it.
  • Direct-dial behavior. A new PBX or calling platform can reintroduce an outside-line prefix or an access-code default. Suddenly dialing 911 alone doesn't connect. That's the exact failure Kari's Law was written to prevent.

Why the gap is invisible until someone dials 911

Standard migration testing confirms that ordinary calls connect, voicemail works, and call flows route. None of that exercises the 911 path. A 933 test, which reads back the address and callback number on file, followed by a scheduled live test call through your 911 center to confirm routing, is the check that would catch the problem. It's also the one most often skipped under cutover time pressure. The result is a compliance gap that looks invisible on every dashboard until the worst possible moment reveals it.

What to do before, during, and after a migration

  • Inventory every location, building, floor, and zone before you start, not just every user.
  • Re-map dispatchable location on the new platform and confirm it resolves to a room or zone, not just a street address.
  • Re-point on-site notification to a device someone is actually watching, and confirm delivery on the new system.
  • Run a 933 test from every location and zone after cutover, then schedule a live test call through your 911 center to confirm routing. Repeat after any later change.
  • Document all of it. If the FCC asks, "we migrated and assumed it carried over" is not an answer.

Frequently asked questions

Does a phone system migration affect 911 compliance?

Yes. Kari's Law and RAY BAUM's Act regulate whatever system is carrying the 911 call, so a PBX or cloud phone system migration that rebuilds the dial plan, re-homes users onto new network paths, and changes how location is determined can break 911 compliance at cutover.

What can break in 911 during a PBX or cloud cutover?

Three things commonly break during a PBX or cloud cutover: dispatchable location mapping tied to old switch ports, subnets, or access points can revert to a building-level address; on-site notification can stay pointed at a system being decommissioned; and a new platform can reintroduce an outside-line prefix so dialing 911 alone doesn't connect.

Is a calling platform that routes 911 automatically compliant?

No. Routing a 911 call is not the same as compliance. Direct dialing without a prefix, on-site notification to someone who can respond, and a dispatchable location specific enough to find the caller are three separate requirements, and a platform that connects 911 may default to satisfying none of them.

How should you test 911 after a phone system migration?

After a phone system migration, run a 933 test from every location and zone to read back the address and callback number on file, then schedule a live test call through your 911 center to confirm routing. Repeat the tests after any later change and document the results.

What are the penalties for 911 non-compliance after a migration?

FCC penalties are $10,000 per violation, plus $500 for each day the violation continues. Kari's Law and RAY BAUM's Act apply to whatever system is carrying the call, so the obligation doesn't pause for a cutover.

Keep compliance independent of the platform

The cleanest way to avoid a migration resetting your compliance is to keep the compliance layer independent of the platform you happen to be running. Because 9Line works across Cisco Unified Communications Manager, Microsoft Teams Direct Routing, and BroadWorks and sits in the call path itself, dispatchable location and notification follow your users through the migration instead of being rebuilt from scratch. Echo adds real-time understanding of the call on top, so your team isn't just compliant, they're actually ready.

Talk to 9Line about your migration and keep 911 compliance intact through the cutover.

9Line Software is the cloud-based E911 compliance platform built for Cisco Unified Communications Manager, Microsoft Teams, and BroadWorks. Echo, which gives on-site teams live context from the 911 call itself, is made possible because 9Line sits in the call path, where safety actually gets handled.

See Echo on a live call

Echo works with Cisco Unified CM, Cisco Emergency Responder, Microsoft Teams Direct Routing and Cisco BroadWorks, with no software to install.

See how Pinpoint works on your property

9Line Pinpoint draws geofences around your buildings, detects cellular 911 calls made inside them and tells your on-site team which building the call came from.

Make your phone system 911 compliant

9Line Dispatch sends a dispatchable location with every 911 call and alerts on-site staff the moment 911 is dialed, for Microsoft Teams, Cisco UCM, Cisco BroadWorks and Cisco Emergency Responder.

Talk to a 911 compliance specialist

Tell us about your property and phone system, and we will show you where 9Line Pinpoint and 9Line Dispatch fit.