Many offices, hospitals, schools and factories in India still run an EPABX installed ten or fifteen years ago. It works, mostly, but spares are hard to find, programming needs a specialist, and features like call recording, IVR, remote extensions or WhatsApp calls are out of reach. The worry that stops most upgrades is disruption: rewiring the building, replacing every phone and losing calls during the change. It does not have to be like that. This guide is a practical project plan to upgrade an EPABX to an IP PBX in phases, keeping your existing analog phones and wiring where it makes sense.
If you are still deciding whether to move at all, start with our comparison of EPABX vs IP PBX. This article assumes you have decided and want to know how to do it.
Step 1: Survey what you have today
Before ordering anything, list what the current system does. Walk the building with the EPABX programming sheet if you have one.
| Item | What to record |
|---|---|
| Extensions | Number, location, who uses each one, analog or digital key phone |
| Wiring | Where the MDF and cable runs are, which cables are in good condition |
| External lines | Number of analog lines, PRI lines, DID numbers and providers |
| Special phones | Lift phones, gate and security phones, fax machines, emergency phones |
| Call flows | Who answers first, night service, hunting groups, operator console |
| Restrictions | Which extensions can dial STD, ISD and mobiles |
| Network | Switches, PoE, LAN points at desks, internet links |
This survey decides how many analog ports and IP phones you need, and avoids surprises on cutover day.
Step 2: Decide what stays analog and what goes IP
You do not have to replace every phone on day one. A mixed setup is common and works well:
- Keep analog phones where there is good copper wiring and no LAN point: wards, hostels, shop floors, guard rooms, lifts and fax machines. Connect them to the new IP PBX through BitVoice VoIP gateways, which have FXS ports (8, 16, 24 or 32 ports, TEC certified) and plug into the existing wiring at the MDF.
- Move to IP phones where people use the phone heavily and need features: reception, managers, sales, accounts and the operator desk. BitVoice IP phones with PoE need only one network cable per desk.
- Use softphones or mobile apps for staff who move around or work from home.
Our guide to connecting analog phones to an IP PBX explains FXS and FXO ports and how gateways are set up.
Step 3: Plan numbers and extensions
Keep users’ familiar extension numbers if you can. People remember them, and they are printed on notices and visiting cards. If the old scheme is messy, this is the time to clean it up with a simple plan by department or floor. See our guide to PBX dial plans and extension numbering.
Also decide:
- Which numbers callers dial and where those calls land (reception, IVR, ring group).
- Night and holiday routing.
- Who may dial mobiles, STD and ISD, using call restriction rules.
Step 4: Plan your external lines
Your existing lines can usually move to the new system:
- PRI lines connect to a PRI (E1) interface on the IP PBX.
- Analog lines from your provider can connect through FXO ports on a gateway.
- SIP trunks can be added for lower call costs and more channels.
Many organisations use the upgrade to start moving from PRI to SIP, one step at a time. Our PRI to SIP trunk migration guide covers that in detail. Keep your existing numbers; if you change provider, check porting with the new one before you cancel anything.
Step 5: Install and run in parallel
The safest upgrades run the old and new systems side by side for a short period:
- Install the IP PBX, gateways and network switches.
- Build the configuration: extensions, ring groups, IVR, time conditions, routes and restrictions.
- Connect a test trunk or one line and make test calls both ways.
- Move a pilot group, such as one department or floor, and let them use it for a few days.
- Fix any issues before moving everyone else.
On Voxdial IP PBX, BitVoice IP phones and BitVoice gateways can be auto provisioned from the PBX. You register each gateway by its MAC address, assign an extension to each port and generate the configuration, which saves a lot of manual work on a large site.
Step 6: Cut over in phases
Plan the main cutover for a quiet time, such as a Sunday or a holiday:
- Move the external lines from the old EPABX to the new PBX.
- Re-terminate analog extensions at the MDF from the EPABX to the gateway ports, floor by floor.
- Test every critical phone: reception, emergency numbers, lift, security and the operator console.
- Keep the old EPABX connected but idle for a week or two, so you can fall back quickly if needed.
Label the MDF as you go. Clear labels save hours on every future fault.
Step 7: Train users and the operator
Most complaints after an upgrade come from small differences: how to transfer, pick up a colleague’s call or check voicemail. Plan short sessions:
- Operator or receptionist: answering, transferring, parking calls and using the operator console.
- Staff: transfer, pickup, conference and voicemail, with a one-page cheat sheet of feature codes.
- Administrator: adding users, changing IVR messages, reading reports and running backups.
Step 8: After the upgrade
Once everyone is on the new system:
- Remove the old EPABX and update the wiring records.
- Set up scheduled configuration backups and a UPS for the PBX, switches and gateways. See PBX backup and failover.
- Review call reports after the first month to tune ring groups and IVR.
- Add the next features when you are ready: call recording, a small contact centre, or WhatsApp calls answered in the same queues.
Common mistakes to avoid
- Skipping the survey and discovering a forgotten lift or fire panel phone on cutover day.
- Moving every user on the same day without a pilot group.
- Forgetting PoE or UPS for the new network switches.
- Not asking for a TEC certified PBX when the tender or policy needs one.
- No training, so staff keep calling the operator to transfer calls.
Planning to replace an old EPABX? Talk to BitVoice for a site survey and migration plan.
FAQs
Can I keep my old analog phones when moving to an IP PBX?
Yes. Analog phones connect to the IP PBX through VoIP gateways with FXS ports, using the existing wiring. You can replace them with IP phones later, one area at a time.
Will I lose my existing phone numbers?
No. PRI and analog lines can connect to the new PBX, and if you move to SIP trunks your provider can usually port or map your existing numbers.
How long does an EPABX to IP PBX upgrade take?
A small office can move in a day after the configuration is ready. Larger sites usually take a few weeks, with a pilot group first and the cutover done floor by floor.
Do I need new cabling for an IP PBX?
Not always. Analog extensions keep their copper wiring through gateways. IP phones need a LAN point, and PoE switches avoid separate power adapters.
