When you move to a new calling platform, the project plan covers number porting, call flows, hardware, and user training. It almost never covers the one thing that can cost you $10,000 per violation: whether 911 still works the way the law requires the day after cutover.
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 keeps "working" — into a void.
- 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 — 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 lets you verify routing and the location delivered to the PSAP without placing a live 911 call — is the one check that would catch the problem, and it's 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, and again after any later change.
- Document all of it. If the FCC asks, "we migrated and assumed it carried over" is not an answer.
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 Call 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 — and 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 Call Manager, Microsoft Teams, and BroadWorks. Echo, 9Line's AI-powered transcription and alerting service, is made possible because 9Line sits in the call path — where safety actually gets handled.
