The success of a PRI-to-SIP migration depends less on bandwidth or equipment than on one piece of preparation: knowing everything that is connected to your existing phone lines. That includes the devices nobody has thought about for years, such as alarm panels and elevator phones, which often stop working when old lines are switched off.
A PRI-to-SIP migration replaces legacy digital phone circuits, known as PRI or ISDN lines, with SIP trunks that carry calls over an internet or private IP connection. In most cases your phone numbers stay the same, and you can either keep your existing phone system (PBX) or replace it. The technical side of the change is well understood. Where migrations usually go wrong is in the inventory at the start, the cutover in the middle and the cancellation of old services at the end, so this runbook gives those stages the most attention.
Many countries are retiring their legacy phone networks, and those deadlines often arrive sooner than an organization’s buying cycle allows for. Following a clear plan from the start is much cheaper than recovering from an unplanned outage.
Why migrations fail: the lines nobody remembers
The most common cause of a failed migration is a device that depended on the old lines and stopped working when they were switched off. Teams usually plan carefully for voice calls, but these other devices are easy to overlook.
Typical examples include:
- alarm panels that report to a monitoring center over a phone line
- elevator emergency phones, which may be covered by safety regulations
- fax machines, which are still common in healthcare, legal and logistics
- door entry systems and gate intercoms
- payment terminals and older ATMs that connect by dial-up
- modems used for building management, utility meters or remote equipment
- emergency or courtesy phones in car parks and reception areas
Some of these devices use separate analog lines rather than the PRI itself. However, they are often affected by the same network retirement and belong in the same project, so find them all before anything is disconnected.
Phase 1: audit every line
Before choosing any new technology, build a complete list of your existing lines. For each circuit and phone number, record the following information:
| Field | Why it matters |
|---|---|
| Circuit or line ID and type | Shows whether it’s PRI, ISDN or analog, and which lines the provider will retire |
| Numbers and number ranges on it | Shows what needs to be moved to the new provider |
| What’s connected | Identifies the PBX, alarm, fax, elevator phone or terminal on the line |
| Current use and owner | Identifies who will notice if the line stops working |
| Contract end date and notice period | Shows when you can cancel without paying a penalty |
| Migration path | Records whether it moves to a SIP trunk, an adapter, a mobile replacement or is retired |
It helps to walk through each building with the facilities team as well as the IT team. You should also compare what you find against your provider’s bills. Bills often list lines that everyone has forgotten, while staff often know about devices that the billing records don’t explain.
Phase 2: choose the target setup
There are three common ways to set up the new system, and the audit usually makes the right choice clear.
Keep the existing PBX and add SIP trunks. If your PBX is still supported and working well, you can connect it to SIP trunks through a session border controller (SBC) or a gateway that converts PRI to SIP. This approach causes the least disruption and is often the fastest.
Replace the PBX with a cloud phone system. If your PBX is close to the end of its life, you can move users to a cloud PBX or unified communications platform and connect SIP trunks to it, or use the platform’s own calling service. This is a larger project and involves more change for users.
Use a mix of both. Some organizations keep their PBX at certain sites and move others to the cloud. This approach is common when different locations are on different timelines.
For devices other than phones, choose a separate path for each type. Alarm panels are best moved to the alarm vendor’s internet or mobile communication units, because sending alarm signals over a voice-over-IP line can be unreliable. Fax machines can move to T.38, a standard for sending fax over SIP, or to a cloud fax service. Elevator and emergency phones often move to dedicated mobile units. Finally, if nobody can name an owner for a device, confirm that it isn’t in use and then retire it.
Phase 3: size capacity from your actual traffic
When planning capacity, avoid simply matching each old circuit with the same number of SIP channels. A US T1 PRI carries 23 voice channels and a European E1 PRI carries 30, but those numbers reflect how the circuits were sold rather than how much capacity you need.
Instead, size your SIP channels from your busy-hour traffic. You may discover that you need fewer channels than your PRIs provided, or that you need more because some calls were being blocked without anyone noticing. Our guide to sizing SIP trunk channels explains how to calculate this, including why time spent in IVR menus and queues needs to be counted.
Phase 4: prepare the network
Because SIP trunks carry calls over your data network, that network now supports your phone service and needs to be prepared for it.
Start by calculating how much bandwidth each call uses with the codec you plan to use, then multiply that figure by your peak number of simultaneous calls and add a safety margin. Our post on G.711, G.729 and Opus gives the bandwidth used per call by each codec. Next, configure quality of service settings so that voice traffic is given priority over large file transfers and other data. You also need to decide whether calls will use a dedicated connection or shared internet access, and what will happen if that connection fails.
Resilience becomes more important after the migration, because internet connections tend to fail in different ways from PRI circuits. Plan a second route for calls, such as a backup connection, a second site or automatic forwarding of incoming numbers to another destination. Our guide to geo-redundant SIP trunks describes the options.
Phase 5: move your phone numbers
Your existing numbers are moved from the old provider to the new SIP provider through a process called number porting. Porting usually takes longer to arrange than any other step, so it’s worth starting early.
To begin, collect your account details from a recent bill, prepare a letter of authorization, and decide which numbers will move, which will stay and which will be cancelled. Then plan the cutover around the date the old provider confirms for the port. Our guide to porting numbers with an LOA and FOC explains the process and the most common reasons ports are rejected.
Before the port takes place, use temporary numbers on the new trunks for testing. This lets you confirm that calls work in both directions before your real numbers are moved.
Phase 6: set up emergency calling
Every number that will be used to make outbound calls needs the correct emergency address on the new service. On a PRI, the location was often tied to the physical address of the circuit. On SIP trunks, however, the location is information you have to configure, which makes it easy to get wrong.
Record the address of each site, and for users who move between sites or work from home, decide how their location will be identified. Test emergency call routing using your provider’s test procedure, and never by making a real call to emergency services. Because the rules vary from country to country, get advice on the requirements wherever you operate.
Phase 7: run a pilot alongside the old lines
Rather than moving everything at once, start with one site or one department. Run the new trunks alongside the old lines for a period of time, with real users making real calls, before cutting anything over.
During the pilot, test the features users rely on day to day. These include inbound and outbound calls, the caller ID that recipients see, transfers, voicemail, conference calls, hunt groups, call recording, fax if you’ve kept it, and calls to mobile and international numbers. Record each problem with the time and the number involved, and fix it before moving the next site.
Phase 8: plan the cutover day
A well-planned cutover day should be uneventful. To make it that way, write a plan and follow it:
- Confirm the date and time of the port with the provider.
- Set up call routing for every number on the new system before the port.
- Tell users and the help desk what will change and who to contact with problems.
- Make sure someone is available at the time of the port to check incoming calls to each number.
- Run through your list of test calls as soon as the port is complete.
- Keep a way to roll back for any numbers that haven’t moved yet.
The rollback plan is particularly important. If only part of the port succeeds, you need to know which numbers have moved and which are still on the old lines.
Phase 9: cancel old services carefully
Don’t cancel your old service until every number has been ported and tested. If you cancel first, numbers can be released before they move, and getting them back is slow or sometimes impossible.
Once every number has been checked, cancel the remaining lines in line with the notice period in each contract, and get written confirmation of what has been terminated. Then check the next bill carefully, because forgotten circuits can stay on invoices for months after a migration.
Keeping users informed
Users tend to notice a phone migration more than most IT changes, so clear communication makes a big difference. Tell them what will change and when, what will stay the same (usually their phone numbers), and who to contact if something seems wrong after the cutover. A one-page summary and a named contact for the first week will prevent most of the confusion that would otherwise reach the help desk.
The most costly mistakes to avoid
The most expensive migration mistakes are rarely technical. Listed roughly in order of how much they cost to fix, they are:
- Cancelling old lines before the numbers have ported, which can mean losing numbers permanently.
- Missing a safety device, such as an alarm panel or elevator phone that stops working without anyone noticing. This is a safety and liability issue rather than a routine IT problem.
- Leaving emergency addresses off the new trunks, which can send emergency calls to the wrong place.
- Sizing channels from old circuits rather than actual traffic, which leads either to blocked calls or to paying for capacity you don’t use.
- Having no backup network connection, so the first internet outage also takes the phones down.
- Skipping the pilot, which means every problem appears at once across every site.
Each of these is prevented by one of the phases in this runbook, which is why it’s worth completing all of them even when the timeline is tight.
Choosing a SIP provider
The provider you move to should be able to handle number porting, changes in capacity and multiple sites without requiring a new contract each time. When comparing providers, ask whether they have points of presence close to your sites, how quickly they can change your channel count, how they handle number porting and how they manage emergency addresses.
IDT Express provides SIP trunking from 40+ locations, which helps organizations with several sites connect each one to a nearby point of presence. Our comparison of SIP trunk pricing models can help you decide how to buy capacity, and our SIP trunking page describes the service in more detail.
Frequently asked questions
What is a PRI to SIP migration?
A PRI to SIP migration replaces legacy digital phone circuits with SIP trunks that carry calls over an IP connection. Numbers are usually ported to the new provider, and the existing PBX can either be kept with a gateway or replaced with a cloud phone system.
How many SIP channels replace a PRI?
Not necessarily the same number. A T1 PRI carries 23 channels and an E1 PRI carries 30, but SIP channels should be sized from your busy-hour traffic, which may require more or fewer.
Can I keep my phone numbers when moving from PRI to SIP?
Usually, yes. Numbers are moved to the SIP provider through number porting, which requires a signed letter of authorization and account details that match the current provider’s records.
What happens to alarms and fax machines when PRI lines are retired?
They stop working unless they’re migrated. Alarm panels are best moved to the alarm vendor’s internet or mobile communication units, and fax can move to T.38 over SIP or to a cloud fax service.
Should I cancel my PRI before porting numbers?
No. Cancelling first can release the numbers before they move. Wait until the port is complete, check calls to every number, and then cancel the remaining service.
Request SIP trunk pricing
If you’re planning a move away from PRI or ISDN, request SIP trunk pricing from IDT Express for your sites and channel counts.


