Solutions · PBX migration
PBX migration step by step
We migrate your old PBX to a new platform or to Teams, step by step. We inventory everything connected to the PBX, let old and new run side by side and move one group at a time.
What we do
The hard part is what you can’t see
A PBX is rarely just phones. Alarms, door entry phones, lift emergency phones, fax machines, the contact centre, attendant consoles and integrations with other systems often depend on it, and they are what gets forgotten when a PBX is replaced.
So we start with a thorough inventory and then build the transition so that old and new work together. Each stage is tested against a test protocol that your organisation approves, and each stage has a rollback plan. We have long experience of migrations from all the platforms we work with.
What’s included
- Inventory of extensions, numbers and dependencies
- Target design: platform, deployment, redundancy and SBC
- Pilot with deliberately difficult cases
- Old and new side by side, with a shared numbering plan
- Phased move with test protocols
- Rollback plan and decommissioning
Benefits
What you get
Everything included from the start
Alarms, lifts and door entry phones are part of the inventory, not just the phones.
Move at your own pace
Old and new work side by side, and you move one group at a time.
Tested before go-live
Each stage is tested and approved by your organisation before it counts as complete.
A way back
With a rollback plan, a stage can be rolled back if something doesn’t work.
How it works
Eight steps from old PBX to new
| Step | What it covers |
|---|---|
| 1. Inventory | Extensions by type, numbering plan, trunks and operator contracts, licences and all dependencies |
| 2. Target design | Platform, deployment model, redundancy, SBC, numbering plan and security, and what is to be replaced, kept or decommissioned |
| 3. Pilot | A limited group with deliberately difficult cases, such as an attendant console, a queue and an analogue device |
| 4. Coexistence | Old and new platforms are connected via SIP and share a numbering plan, so that calls work wherever the user is |
| 5. Phased move | By site, department or number range, in agreed change windows, with information and training before each stage |
| 6. Verification | Test protocol per stage: inbound and outbound calls, caller ID, 112, alarms, lifts, door entry phones, fax, queues, attendant consoles, voicemail and recording |
| 7. Rollback plan | Agreed criteria for when a stage is rolled back, and a named person who makes the decision |
| 8. Decommissioning | Old trunks and licences are shut down only when everything has been verified, and the documentation is handed over |
Dependencies that are often forgotten: intruder and fire alarms, telecare alarms, door entry and access control systems, lift emergency phones, fax, card terminals, paging, wireless DECT phones and integrations with CRM and other systems.
Products
Products we work with
Product
Mitel OpenScape Voice
The SIP platform for large and distributed environments, with redundancy.
Common questions
Frequently asked questions about PBX migration
How long does a migration take?
It depends on size and dependencies. The inventory and the pilot show how many stages are needed, and the stages are scheduled in change windows that suit your organisation.
Can we move to Teams instead of a new PBX?
Yes, and it often ends up as a combination: Teams for most users, while the contact centre, alarms and analogue devices get a separate solution or stay on a PBX.
What happens to our numbers?
As a rule, you keep them. During the transition, the old and new platforms share a numbering plan. If you change operator, number porting is planned together with the new operator.
What do we do about alarms and lift emergency phones?
They are part of the inventory from the start and are tested at every stage. Lift alarms follow their own standard, so we check with the lift supplier.
Does everything have to move at once?
No. That is the whole point of coexistence: you move one group at a time and switch off the old system only when everything works.
Further reading
Guide
Upgrade or replace your PBX?
Decision support for organisations that run MX-ONE or OpenScape today.
Guide
Teams and your existing PBX: coexistence and gradual migration
How to let Teams and your PBX work together while you move at your own pace.
Guide
Redundancy and failover for telephony
Dependencies, backup routes and how to test that continuity holds.
Solution
PBX and telephony
Delivery, upgrades and operation of PBXs from Mitel and Alcatel-Lucent Enterprise, such as MX-ONE, OpenScape and OmniPCX Enterprise.
Solution
Teams Phone
Make and receive calls directly in Microsoft Teams, with Direct Routing via AudioCodes and a connection to your PBX.
Solution
Support contracts and managed services
Support contracts with agreed response times, so that your communications work every day.
Let’s talk about your communications
Tell us where you stand today with your PBX, Teams or contact centre, and we will come back to you with a proposal. It costs nothing to ask.