Legacy Voice Migration for Businesses

Legacy voice migration is the process of moving a business's telephone service off the infrastructure it was built on decades ago — PRI (Primary Rate Interface) circuits, analog copper lines, and on-premises PBX systems — and onto modern voice platforms. The destination is usually one of two things: hosted VoIP/UCaaS, where the phone system lives in the provider's cloud and your phones connect over the internet, or SIP trunking, where you keep an on-site phone system but replace the physical carrier circuits with internet-delivered trunks.

The reason this topic has moved from 'someday' to 'now' for most businesses is that the legacy network itself is going away. Carriers across the country are retiring copper facilities and TDM (time-division multiplexing) switches, and where they haven't retired them outright, they've raised prices and reduced maintenance investment. A PRI that was a reasonable line item ten years ago is now often an expensive, fragile dependency on infrastructure the carrier would rather not keep running.

Migration is not the same as ripping everything out. A well-scoped migration is mostly a planning exercise: inventory what you have, decide what each line and number should become, port the numbers, and cut over in a controlled way. The businesses that get hurt are the ones that wait until the PBX dies or the carrier sends a retirement notice with a deadline — at that point you're migrating on someone else's schedule.

Step one: inventory everything that touches a phone line

Every successful migration starts with a line-by-line inventory, and this step surprises almost everyone. Beyond the obvious PRI or copper trunks feeding the PBX, most buildings have stray analog lines that were installed years apart and forgotten: fax lines, alarm panel communicators, elevator emergency phones, fire dialers, gate entry systems, point-of-sale fallback lines, and modems. These lines don't show up in anyone's documentation — they show up on the phone bill. Pulling several months of bills and tracing every circuit ID and phone number is unglamorous work, but skipping it is how businesses end up with a dead elevator phone two weeks after cutover.

Step two: choose the destination

There are three realistic destinations. Hosted UCaaS replaces the PBX entirely — desk phones, softphones, and mobile apps register to the provider's platform, and features like auto attendants, voicemail-to-email, call recording, and video meetings come with the seat license. SIP trunking keeps your existing (or new) on-premises PBX but delivers dial tone over your internet connection instead of PRI — a good fit when the PBX still has life in it or has features you depend on. A hybrid approach moves some sites or departments to hosted while others stay on a PBX with SIP trunks, common in multi-location rollouts and phased migrations.

Step three: number porting — the part that takes the longest

Your phone numbers belong to you, and moving them between carriers is called porting. Porting is a paperwork-driven process between the losing and gaining carriers, and it's the longest pole in most migrations. Simple ports of a few local numbers can complete in one to three weeks; large blocks, numbers spread across multiple rate centers, toll-free numbers, or accounts with incorrect records can take longer. The single biggest cause of port delays is mismatched account information — the name, address, or account number on the port request doesn't exactly match what the losing carrier has on file. Getting a customer service record (CSR) from the current carrier before submitting anything eliminates most of this pain.

Step four: network readiness

Voice over IP is only as good as the network underneath it. Before cutover, the internet connection at each site should be evaluated for bandwidth (a voice call needs relatively little — roughly 80–100 Kbps per call with common codecs — but quality, not quantity, is the issue), latency, jitter, and packet loss. Business-grade routers configured with quality of service (QoS) to prioritize voice traffic, and in many cases a dedicated or failover connection, separate a smooth migration from a year of complaints about choppy calls.

Step five: cutover and parallel running

Because porting happens at a scheduled time, migrations typically run old and new systems in parallel for a window: the new platform is fully configured and tested before the numbers move, and temporary call forwarding covers the transition. On port day, numbers move one block at a time, someone tests inbound and outbound calling on every ported block, and the old system stays powered but unused until everyone is confident. Rollback planning matters — know, before port day, what you do if the port fails or the new service misbehaves.

• End-of-life risk: PBX systems whose manufacturers have ended support, where a failed card or power supply can mean days without phones while you hunt for refurbished parts
• Legacy cost creep: carriers raising PRI and copper line rates — sometimes dramatically — as they decommission the TDM network
• Copper retirement notices: forced deadlines from carriers exiting copper service in your area
• No remote capability: a premises PBX ties phone service to a building; hosted voice follows the employee to home offices and mobile devices
• Missing modern features: no voicemail-to-email, no call analytics, no easy auto-attendant changes, no integration with CRM or collaboration tools
• Maintenance skill gap: the person who understood the PBX retired, and every change now requires an expensive truck roll from a shrinking pool of legacy technicians
• Disaster vulnerability: a building problem — fire, flood, power — takes the entire phone system with it, with no automatic rerouting

Underneath all of these is one structural shift: the public switched telephone network is being rebuilt around IP. Businesses can ride that transition on their own terms and timeline, or be pushed by a hardware failure or carrier notice. The technology to replace legacy voice is mature — hosted voice and SIP trunking are well-established, not experiments — so the risk calculus has flipped from 'is the new stuff ready?' to 'how much longer do we want to carry the old stuff?'

The obvious candidates are businesses with aging PBX hardware — systems from manufacturers or product lines that have reached end of support — and anyone paying for PRI circuits, whose per-line economics have deteriorated as carriers push customers off TDM. If your monthly bill includes line items like 'PRI,' 'T1,' 'business line,' or a surprising number of individual analog lines, you're carrying legacy voice.

Less obvious candidates: businesses whose PBX works fine but can't support hybrid work; companies that have been acquired or merged and are running two or three incompatible phone systems; multi-site organizations paying a different local carrier at every location; and anyone who has received a copper retirement or price-increase notice from their carrier. Growth is another trigger — if adding ten employees means buying PBX expansion hardware, that's the moment to compare it against a per-seat hosted model.

Who might reasonably wait? A business that recently invested in a modern, supported IP-PBX can often get most of the benefit by moving to SIP trunking now and deferring a full hosted migration. And sites with genuinely critical analog dependencies — certain alarm, elevator, or emergency communication lines — may keep a small number of purpose-built replacement lines even while everything else migrates. 'Migrate' doesn't have to mean 'everything, all at once.'

1. Full PBX replacement with hosted UCaaS: the most common path — the closet hardware goes away, every employee gets a desk phone and/or softphone, and features like auto attendant, ring groups, and voicemail-to-email come standard
2. PRI to SIP trunk conversion: keep the PBX, kill the PRI — the carrier circuit is replaced by SIP trunks delivered over the internet connection, typically at a meaningfully lower monthly cost
3. Carrier-forced migration: responding to a copper retirement or tariff change notice with a planned move instead of an emergency one
4. Merger and multi-site consolidation: replacing several inherited phone systems and carrier contracts with one platform, one bill, and four- or five-digit dialing between locations
5. Hybrid phased migration: headquarters moves to hosted voice first while branch sites convert to SIP trunking on their existing PBXs, with full migration over the following quarters
6. Special-line remediation: moving fax to an ATA or e-fax service, and alarm/elevator lines to purpose-built cellular or IP communicators, as part of the same project

Exact pricing varies by provider, seat count, features, and term — treat any number quoted without a real proposal as a rough estimate. That said, the cost structure of a migration is predictable, and it has both one-time and recurring components.

On the recurring side, hosted UCaaS is typically priced per user per month in tiers: a basic voice tier, a mid tier that adds video meetings and integrations, and premium tiers with call recording, analytics, and contact-center features. Volume matters — per-seat pricing usually improves at higher seat counts and longer terms. SIP trunking is typically priced per trunk (call path) plus usage or in bundled minute packages, and commonly costs a fraction of the PRI it replaces. Either way, most businesses find the new recurring cost lands at or below the old bill, sometimes substantially below when legacy line charges have been climbing.

One-time costs are where budgets get surprised. They can include new phones (if you're not reusing IP phones or going softphone-only), network upgrades (PoE switches, a router that handles QoS properly, possibly a better internet circuit or failover), installation and onboarding fees, number porting fees in some cases, and analog telephone adapters (ATAs) or replacement communicators for fax, alarm, and elevator lines. A proper proposal itemizes all of this; a quote that only shows the per-seat price is incomplete.

Two financial traps to check before signing anything. First, the early termination liability on your existing contracts — legacy carriers often auto-renew PRI and circuit contracts, and the ETF can be significant; some providers offer contract buyout credits, so this is negotiable territory. Second, overlapping service: you'll pay for old and new during the migration window, which is normal and correct, but plan for one to two months of overlap, not six.

A well-run migration follows a predictable sequence. It begins with discovery: the inventory of lines, numbers, features in use (hunt groups, auto attendants, call flows, overhead paging, door phones), and the contracts and CSRs behind them. From that comes a design: which destination platform, how many seats or trunks, what the call flows should be on the new system — often a rare chance to fix call routing that has annoyed customers for years.

Next comes network preparation and provisioning: the internet connection is validated or upgraded, QoS is configured, phones and equipment are ordered and staged, and the new platform is fully configured — users, extensions, auto attendants, ring groups — before any number moves. In parallel, the port request is submitted with clean, CSR-matched records, and a firm port date (called a FOC date) is confirmed by the losing carrier.

Cutover executes against that port date: numbers move, inbound and outbound test calls are made on every block, call flows are walked end to end, and staff get hands-on orientation — the first week of 'how do I transfer a call?' questions is predictable, so plan floor-walking or office-hours support. The old system stays in place, powered but idle, until the new service has run clean. Only then do you formally disconnect legacy circuits — and confirm in writing that the carrier actually stopped billing them, because disconnected-but-still-billed circuits are a genuine and common phenomenon.

Timelines vary with port complexity and site count, but a realistic shape for a single-site small or mid-size business is four to eight weeks from kickoff to cutover. The gating item is almost always number porting, not technology: the new platform can usually be configured in days, while the port takes as long as the losing carrier takes.

• Weeks 1–2: discovery, line inventory, CSR pulls, design, and contract signature
• Weeks 2–4: equipment ordering and staging, network prep, platform configuration, port order submission
• Weeks 3–6: FOC date confirmed; user training scheduled; parallel running begins
• Port day: numbers cut over, testing, on-site or remote support
• Weeks 6–8: stabilization, old system standby, then legacy disconnection and billing verification

What stretches timelines: ports rejected for mismatched records (each rejection can add a week or more), toll-free numbers (a separate process through the toll-free numbering system), numbers in multiple rate centers or from multiple losing carriers, network construction if a better internet circuit is part of the project, and multi-site rollouts, which typically run as a sequence of single-site migrations. What compresses them: clean records, a provider with a disciplined porting desk, and a customer who makes the inventory available on day one. If you're under a carrier retirement deadline, say so at kickoff — expedited handling is sometimes possible, but only if the clock is visible to everyone.

• Skipping the line inventory and discovering — after cutover — an alarm panel, elevator phone, or fax line that still pointed at a disconnected copper line
• Submitting port orders without pulling a CSR first, then losing weeks to rejections over an account name or service address mismatch
• Treating the internet connection as an afterthought: running voice over a congested or lossy connection and blaming the phone system for the resulting quality
• Porting everything at once instead of in testable blocks, leaving no clean rollback position
• Disconnecting the legacy service before the new one has run stable — or forgetting to disconnect it at all and paying both bills for months
• Rebuilding the old call flows exactly, including the bad parts, instead of using the migration to fix routing
• Under-training staff: the technology works, but nobody knows how to park a call, so adoption sours in week one
• Assuming fax will 'just work' over VoIP — it often doesn't without an ATA configured for it or a move to e-fax, and it needs to be tested explicitly
• Signing the new contract before checking the old one's auto-renewal and early termination exposure

1. Who manages number porting, and what's your process when a port is rejected? Will you pull our CSR before submitting?
2. Can we port numbers in blocks and schedule the port date, rather than taking whatever date the losing carrier assigns?
3. What happens to our fax, alarm, elevator, and other analog lines? Show me exactly how each one is handled.
4. What are the network requirements at each site, and will you assess our connection before we commit?
5. What's included in the per-seat price, and what costs extra — phones, installation, training, porting fees, e911, taxes and surcharges?
6. What's the failover story if our internet goes down — automatic call forwarding, mobile app fallback, LTE backup options?
7. What are the contract terms, renewal mechanics, and early termination liability — yours, and can you help offset the ETF on our existing contract?
8. What does onboarding support look like: dedicated project manager, on-site installation, end-user training, and who do we call in week one?
9. If we keep our PBX and take SIP trunks instead, what are the compatibility requirements, and do you support our specific system?

The strategic decision in any legacy voice migration is the destination. Each path makes different trade-offs between cost, control, features, and how much of the old world you keep. The right answer depends on your PBX's remaining life, your appetite for managing equipment, and how much you value bundled features versus simplicity.

One common false alternative worth naming: doing nothing. Given carrier copper retirements and legacy price escalations, standing still is itself a decision — and usually the most expensive one over a two-to-three-year horizon. Even a business that defers a full migration should remediate its special lines and get its contract situation under control.

Healthcare and dental

Medical and dental offices run on the phone: scheduling, reminders, referrals, pharmacies, and after-hours on-call routing. Legacy PBXs in this space often have fragile after-hours answering-service integrations and no call recording. Migration typically brings voicemail-to-email triage, better on-call routing, and call analytics on missed calls — missed calls in a practice are missed appointments. Practices handling patient information should evaluate vendors' security features and business associate agreement availability as part of a broader HIPAA security program; no phone system by itself makes an organization compliant.

Legal

Law firms care about three things from voice: never missing a client call, documenting communication, and number stability — a firm's main number is an asset built over decades. Porting discipline matters enormously here, and features like call recording (where appropriate), voicemail transcription, and mobile apps that let attorneys take office calls from court without giving out a personal cell number map directly onto how firms work.

Manufacturing and warehousing

Industrial sites have the messiest inventories: overhead paging systems, intercoms, door phones, gate intercoms, and alarm lines tangled into the same PBX as the office phones. Migration here is as much a facilities project as an IT project — paging and intercom integrations need explicit design (often via analog adapters or paging gateways), and the noisy floor environment makes ruggedized or loud-ringing endpoints a real consideration.

Hospitality

Hotels carry some of the most specialized legacy voice: guest-room phones, front-desk consoles, wake-up calls, and PBX-to-property-management-system integration. The guest-room side is migrating slowly and deliberately (many properties keep room phones simple), but the administrative side — reservations, the front desk, back office — moves to hosted voice readily, and multi-property groups gain centralized management and consistent call handling across locations.

TechSellers International is a technology advisor, not a carrier or a phone-system vendor. Our job in a legacy voice migration is to be the person on your side of the table who has done this before. That starts with the unglamorous work that determines success: helping you build the line inventory, pulling bills and customer service records, and documenting every number and special circuit before anyone signs anything.

From there we help you compare available options across leading technology providers — hosted UCaaS platforms, SIP trunk providers, or a hybrid — with real pricing at your actual seat counts and sites, not list prices. We surface the differences that don't fit on a brochure: porting desk quality, onboarding depth, how each provider handles fax and alarm lines, contract and ETF exposure, and what week-one support actually looks like.

Through the migration itself, we coordinate the moving parts — the provider's project team, the port schedule, your internet service readiness, installation, and cutover-day testing — and stay engaged through stabilization and the final disconnection of legacy circuits, including verifying the old billing actually stops. Because we're compensated by the providers, this guidance and project coordination doesn't add a line to your bill: you get an experienced advisor for the same price you'd pay going direct, and usually a better outcome on both cost and timeline.