Mitel to Genesys Cloud migration

A Mitel to Genesys Cloud migration rarely starts from a single product. Many estates run MiContact Center Business alongside MiVoice Business or MiVoice Connect, with IVR Routing for self-service and Ignite or Contact Center Client on agent desktops. Others use MiVoice Connect Contact Center, or older Mitel and Aastra platforms that have grown through acquisitions and site moves. Each holds years of decisions: an ACD path added for a campaign, an overflow rule tuned after a busy winter, a holiday announcement nobody has reviewed since. Our leadership has worked in contact centre technology since 1984, so QVCCS knows how these estates grow and where their most important behaviour tends to sit.

Mitel's own plans often set the timing: new sales of MiContact Center Business ended on 31 December 2025, add-on sales end on 31 December 2027, and the product reaches end of life on 28 February 2030. Others move at a server refresh, a maintenance renewal or a wider move to cloud services. Genesys Cloud is cloud-native and multi-region, so there is no contact centre hardware to replace and new capabilities arrive continuously. One decision shapes almost everything else: many organisations keep their Mitel phone system for general staff and move only the contact centre. That is a sound choice, and it means the two platforms will work together for a long time, not just during cut-over. We help contact centre leaders and architects plan for that from the first workshop, with waves, owners, dates and coexistence decisions agreed before configuration starts.

On MiVoice Business, calls arrive at ACD paths, which set the priority of each call and the agent skill groups it queues for, with overflow and interflow rules deciding what happens when those groups are busy. On Genesys Cloud, numbers point to Architect inbound call flows, which route to queues, while ACD skills, proficiency ratings and bullseye routing decide which agents are offered each call. We rationalise rather than copy. Skill groups created as workarounds for reporting or overflow limits often collapse into fewer, clearer queues, and agents' skill levels become proficiencies supervisors can adjust themselves. Make Busy and account codes are mapped to presence statuses and wrap-up codes, and work timers to after-call work settings.

IVR Routing workflows, built in a drag-and-drop editor, route callers by schedule, by the number dialled or dialled from, by collected digits and by queue conditions. They play recorded announcements, report position in queue and offer callbacks. On Genesys Cloud, the same logic becomes Architect inbound call flows, schedules and schedule groups, prompts and in-queue flows that control the waiting experience and offer callbacks. Database lookups become data actions that call your systems through APIs, documented in interface contracts with agreed error handling. Email, chat and SMS routed through MiContact Center Business workflows move to Architect flows for each channel, so every interaction type keeps a clear route and an owner.

Reporting needs equal care, because MiContact Center Business reports, Flexible Reporting views and real-time monitors are how many managers see their operation. We agree a report parity list with the people who use them, rebuild each one with Genesys Cloud performance views, dashboards or data exports to your own analytics, and reconcile definitions such as service level and abandonment before go-live, so leaders know which numbers will shift for that reason alone. Workforce scheduling, screen pops and CRM integrations get the same treatment: each is catalogued, given a target design on Genesys Cloud, whether native, an AppFoundry partner app, data actions or bespoke development, and tested before its users move.

When the Mitel PBX stays for general staff, agents still need to reach colleagues on Mitel extensions, and colleagues need to transfer customers into the contact centre. We connect your MiVoice Business or MiVoice Connect system to Genesys Cloud with SIP trunks over BYOC Cloud or BYOC Premises, then design the number plans on both sides so transfers, consultations and caller identity behave predictably. Genesys Cloud can also pass calls from a PBX trunk out through its own carrier trunks, which can simplify PSTN access for some designs. Our IT Systems, Telecoms & SIP Engineers set that up with SIP access control and toll-fraud safeguards, and test transfers in both directions as part of every wave.

Carrier connectivity is chosen early. Genesys Cloud Voice makes Genesys your carrier and supports porting existing numbers, BYOC Cloud brings your current carrier's SIP trunks to Genesys Cloud, and BYOC Premises keeps media on Edge devices in your own sites. We build a number porting plan with your carrier or Genesys, align each port to a cut-over wave and test every number as soon as it moves, including emergency calling. Recordings held in your current recorder are kept in a searchable archive or moved, as your compliance team decides. Agents usually move from Mitel IP phones to WebRTC and headsets, so our site, network and telephony readiness survey checks bandwidth, firewalls and home-worker connections first.

Discovery goes deep because Mitel configuration is spread across several places. We review the contact centre configuration held in YourSite Explorer, ACD paths and agent skill groups on the PBX, IVR Routing workflows and prompts, the report catalogue, desktop and screen-pop integrations, and any links to workforce scheduling or outbound. Workshops with supervisors, planners and team leaders then uncover the behaviour nobody wrote down. Each item goes into a migration inventory with an owner, a priority and a target approach, and from there into the Requirements Traceability Matrix. Journey by journey, we agree where to keep parity and where to transform, and record every decision in the design decision log before the High-Level Design is written.

We then muster the team from our own bench to fit your estate: an Enterprise Solution Architect who has worked with Mitel and other telephony platforms for decades, an IT Systems, Telecoms & SIP Engineer for trunks, number plans and PBX coexistence, Senior Developers for Architect flows and data actions, a Business Analyst for reports and processes, and testers for SIT and UAT. Every delivery team member holds, or is completing, Genesys Cloud certification. QVCCS takes collective responsibility for the outcome, backed by the whole practice through design authority and peer review. We build to the Low-Level Design under our engineering standards, use CX as Code for repeatable configuration, and trace every system integration test to the Mitel behaviour it replaces.

Cut-over runs in waves by site, team or number range, never as one weekend gamble. Each wave has entry and exit criteria, a rehearsed runbook, test calls straight after the change and a rollback plan that can point numbers back at their Mitel ACD paths if something goes wrong. Because the PBX trunks are already proven, transfers between moved and unmoved teams keep working while the waves progress. Our remote go-live command centre and virtual floor-walking support people through their first shifts, and role-based training helps agents used to Ignite or Contact Center Client, and supervisors used to Mitel real-time monitors, find their way around Genesys Cloud before customers are waiting.

After the last wave, hypercare continues until the operation is stable. MiContact Center Business servers, IVR Routing ports and contact centre licences can then be retired on your terms, while the Mitel PBX carries on serving the rest of the organisation through the trunks we built. Support follows your Genesys Cloud CX consumption model: SLA-based support, up to 24x7x365 where you contract it with QVCCS, or alongside your provider's support as the specialist change and escalation layer. From there, attention turns to the roadmap: digital channels, predictive routing, virtual agents and agent assist, each delivered with the same discovery, design and testing discipline that carried the migration.