Successful transition to Microsoft Teams Phone for financial customers<\/h1><\/div>Navigating the pitfalls and problems in a Microsoft Teams Phone migration<\/h4><\/div>![](\"https:\/\/voss-media.imgix.net\/2023\/01\/Tim-Jalland-Colour-White-border.png?auto=compress%2Cformat&fit=scale&h=768&ixlib=php-3.3.1&w=768&wpsize=medium_large\" "\\"Tim-Jalland-Colour-White-border\\"")
<\/span><\/div><\/div><\/div>Author: Tim Jalland
\nSolution Manager, VOSS Solutions<\/h6>\n
Tuesday, July 23, 2024<\/p>\n<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>
For large organizations operating in multiple locations, moving from several older PBX systems to Microsoft Teams Phone needs careful planning and coordination. That was the case with one of our recent projects, working with a multinational banking customer. They operated a multi-cluster Cisco Call Manager solution, and the task was to move this in manageable batches (or groups of sites) to Microsoft over an extended period.<\/h6>\n
They selected VOSS automation to streamline and control the process, based on its ability to address the following critical requirements that were called out in the project definition:<\/p>\n
\n- Dynamic discovery \u2013<\/strong> To extract data from the Cisco PBX quickly and easily, at any point in the migration, and identify user configuration, inventory, usage and possible migration feature gaps that would need to be addressed.<\/li>\n
- Automated migration \u2013<\/strong> To make the process of transferring users from the older PBX to the new Microsoft Teams Phone solution fast, error free, accurate, and without the need to call on Microsoft technical specialists (this was to be run by a deployment team).<\/li>\n
- Managing two systems throughout the migration \u2013<\/strong> From the first site to be migrated, both the Cisco PBX and Microsoft Teams Phone are running live services that change daily, so being able to accurately track items such as number inventory, user services, and performance was critical.
\nSwitching or transferring calls – For a user during a migration batch, from the Cisco PBX to Microsoft Teams Phone, in a transparent and seamless way, without disruption or significant downtime (each user maintained their existing number).<\/li>\n- Reporting \u2013<\/strong> To provide a reporting window into the migration process, to validate each migration batch beforehand, and to track progress throughout the project (each site was represented by a single point of contact).<\/li>\n
- Security \u2013<\/strong> Importantly, to protect and secure access to data during the migration so that sensitive user information (as an example) was not left on spreadsheets, distributed over email, or made available to non-authorized users.<\/li>\n<\/ul>\n<\/div>
Switching between the old and the new<\/h4>\n
The ability to switch calls between the old and new systems attracted significant interest, and we offered several options for discussion, as below.<\/p>\n
\n- Call forwarding \u2013<\/strong> To build a mechanism onto the SBC infrastructure to forward calls initially to the Cisco PBX, and then if the call wasn\u2019t taken up, to re-route the call to Microsoft Teams Phone.<\/li>\n
- Active directory (User) \u2013<\/strong> To steer individual calls either to the Cisco PBX or onto Microsoft Teams Phone based on the location of the user \u2013 the latter being determined by a suitable field in Active Directory, and the field being updated as part of the migration process.<\/li>\n
- Hybrid calling \u2013<\/strong> To provide dial plan integration between the Cisco PBX and Microsoft Teams Phone so that calls were automatically diverted to the correct system based on the call flow configured across the two systems.<\/li>\n<\/ul>\n
After consideration of each option, and based on the ease of implementation, risk, cost, and user experience, the hybrid option was selected. The details of that solution are provided here for reference.<\/p>\n<\/div>
![\"Extending](\"https:\/\/voss-media.imgix.net\/2024\/07\/hybrid-extending-enterprise-voice.png?auto=compress%2Cformat&ixlib=php-3.3.1\" "\\"hybrid-extending")
<\/span><\/div>Hybrid calling with VOSS automation<\/h4>\n
The bank\u2019s Cisco PBX was connected into Microsoft Teams Phone via Direct Routing to offer an integrated solution with a single number inventory. Users could then be freely moved between systems, keeping their number, with the ability to call out to the public telephone network. VOSS automation was used to manage this movement, with the following user service profiles:<\/p>\n
\n- A user with Cisco services (only) – the initial state for a user, pre-migration<\/li>\n
- A user with both Cisco and Microsoft services (both sides ring on a call)<\/li>\n
- A user with Microsoft Teams Phone (only) \u2013 the eventual end migration of a user<\/li>\n<\/ul>\n
Users could simply be selected individually or in bulk, and moved, with the underlying dial plan mechanism and number management being orchestrated and tracked by the VOSS workflow, associated automation, and audit log.<\/p>\n<\/div>
The value<\/h4>\n
The solution offered benefits in terms of:<\/p>\n
\n- A simple and straightforward migration for a user, improving user experience<\/li>\n
- Retention of telephone number and call controls, as they were pre-migration<\/li>\n
- A single portal to manage both systems, pre, during, and post migration<\/li>\n
- A robust and fast migration process, with in built rollback if needed<\/li>\n
- Automated workflows to remove complexity and errors from the process<\/li>\n
- Repeatable operational processes \u2013 for example onboarding \/ offboarding a user<\/li>\n<\/ul>\n<\/div><\/div><\/div>
More information<\/h4>\n
There\u2019s more information on VOSS for migration on our website<\/a>. You can also get in touch with us here<\/a>.<\/p>\n<\/div><\/div><\/div><\/div><\/div>Keep up to date with our latest blogs and subscribe today<\/h4><\/div><\/div><\/div>
Navigating the pitfalls and problems in a Microsoft Teams Phone migration<\/h4><\/div><\/span><\/div><\/div><\/div>Author: Tim Jalland
\nSolution Manager, VOSS Solutions<\/h6>\n
Tuesday, July 23, 2024<\/p>\n<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>
For large organizations operating in multiple locations, moving from several older PBX systems to Microsoft Teams Phone needs careful planning and coordination. That was the case with one of our recent projects, working with a multinational banking customer. They operated a multi-cluster Cisco Call Manager solution, and the task was to move this in manageable batches (or groups of sites) to Microsoft over an extended period.<\/h6>\n
They selected VOSS automation to streamline and control the process, based on its ability to address the following critical requirements that were called out in the project definition:<\/p>\n
\n- Dynamic discovery \u2013<\/strong> To extract data from the Cisco PBX quickly and easily, at any point in the migration, and identify user configuration, inventory, usage and possible migration feature gaps that would need to be addressed.<\/li>\n
- Automated migration \u2013<\/strong> To make the process of transferring users from the older PBX to the new Microsoft Teams Phone solution fast, error free, accurate, and without the need to call on Microsoft technical specialists (this was to be run by a deployment team).<\/li>\n
- Managing two systems throughout the migration \u2013<\/strong> From the first site to be migrated, both the Cisco PBX and Microsoft Teams Phone are running live services that change daily, so being able to accurately track items such as number inventory, user services, and performance was critical.
\nSwitching or transferring calls – For a user during a migration batch, from the Cisco PBX to Microsoft Teams Phone, in a transparent and seamless way, without disruption or significant downtime (each user maintained their existing number).<\/li>\n- Reporting \u2013<\/strong> To provide a reporting window into the migration process, to validate each migration batch beforehand, and to track progress throughout the project (each site was represented by a single point of contact).<\/li>\n
- Security \u2013<\/strong> Importantly, to protect and secure access to data during the migration so that sensitive user information (as an example) was not left on spreadsheets, distributed over email, or made available to non-authorized users.<\/li>\n<\/ul>\n<\/div>
Switching between the old and the new<\/h4>\n
The ability to switch calls between the old and new systems attracted significant interest, and we offered several options for discussion, as below.<\/p>\n
\n- Call forwarding \u2013<\/strong> To build a mechanism onto the SBC infrastructure to forward calls initially to the Cisco PBX, and then if the call wasn\u2019t taken up, to re-route the call to Microsoft Teams Phone.<\/li>\n
- Active directory (User) \u2013<\/strong> To steer individual calls either to the Cisco PBX or onto Microsoft Teams Phone based on the location of the user \u2013 the latter being determined by a suitable field in Active Directory, and the field being updated as part of the migration process.<\/li>\n
- Hybrid calling \u2013<\/strong> To provide dial plan integration between the Cisco PBX and Microsoft Teams Phone so that calls were automatically diverted to the correct system based on the call flow configured across the two systems.<\/li>\n<\/ul>\n
After consideration of each option, and based on the ease of implementation, risk, cost, and user experience, the hybrid option was selected. The details of that solution are provided here for reference.<\/p>\n<\/div>
<\/span><\/div>Hybrid calling with VOSS automation<\/h4>\n
The bank\u2019s Cisco PBX was connected into Microsoft Teams Phone via Direct Routing to offer an integrated solution with a single number inventory. Users could then be freely moved between systems, keeping their number, with the ability to call out to the public telephone network. VOSS automation was used to manage this movement, with the following user service profiles:<\/p>\n
\n- A user with Cisco services (only) – the initial state for a user, pre-migration<\/li>\n
- A user with both Cisco and Microsoft services (both sides ring on a call)<\/li>\n
- A user with Microsoft Teams Phone (only) \u2013 the eventual end migration of a user<\/li>\n<\/ul>\n
Users could simply be selected individually or in bulk, and moved, with the underlying dial plan mechanism and number management being orchestrated and tracked by the VOSS workflow, associated automation, and audit log.<\/p>\n<\/div>
The value<\/h4>\n
The solution offered benefits in terms of:<\/p>\n
\n- A simple and straightforward migration for a user, improving user experience<\/li>\n
- Retention of telephone number and call controls, as they were pre-migration<\/li>\n
- A single portal to manage both systems, pre, during, and post migration<\/li>\n
- A robust and fast migration process, with in built rollback if needed<\/li>\n
- Automated workflows to remove complexity and errors from the process<\/li>\n
- Repeatable operational processes \u2013 for example onboarding \/ offboarding a user<\/li>\n<\/ul>\n<\/div><\/div><\/div>
More information<\/h4>\n
There\u2019s more information on VOSS for migration on our website<\/a>. You can also get in touch with us here<\/a>.<\/p>\n<\/div><\/div><\/div><\/div><\/div>Keep up to date with our latest blogs and subscribe today<\/h4><\/div><\/div><\/div>
<\/span><\/div><\/div><\/div>Author: Tim Jalland
\nSolution Manager, VOSS Solutions<\/h6>\n
Tuesday, July 23, 2024<\/p>\n<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>
For large organizations operating in multiple locations, moving from several older PBX systems to Microsoft Teams Phone needs careful planning and coordination. That was the case with one of our recent projects, working with a multinational banking customer. They operated a multi-cluster Cisco Call Manager solution, and the task was to move this in manageable batches (or groups of sites) to Microsoft over an extended period.<\/h6>\n
They selected VOSS automation to streamline and control the process, based on its ability to address the following critical requirements that were called out in the project definition:<\/p>\n
- \n
- Dynamic discovery \u2013<\/strong> To extract data from the Cisco PBX quickly and easily, at any point in the migration, and identify user configuration, inventory, usage and possible migration feature gaps that would need to be addressed.<\/li>\n
- Automated migration \u2013<\/strong> To make the process of transferring users from the older PBX to the new Microsoft Teams Phone solution fast, error free, accurate, and without the need to call on Microsoft technical specialists (this was to be run by a deployment team).<\/li>\n
- Managing two systems throughout the migration \u2013<\/strong> From the first site to be migrated, both the Cisco PBX and Microsoft Teams Phone are running live services that change daily, so being able to accurately track items such as number inventory, user services, and performance was critical.
\nSwitching or transferring calls – For a user during a migration batch, from the Cisco PBX to Microsoft Teams Phone, in a transparent and seamless way, without disruption or significant downtime (each user maintained their existing number).<\/li>\n- Reporting \u2013<\/strong> To provide a reporting window into the migration process, to validate each migration batch beforehand, and to track progress throughout the project (each site was represented by a single point of contact).<\/li>\n
- Security \u2013<\/strong> Importantly, to protect and secure access to data during the migration so that sensitive user information (as an example) was not left on spreadsheets, distributed over email, or made available to non-authorized users.<\/li>\n<\/ul>\n<\/div>
Switching between the old and the new<\/h4>\n
The ability to switch calls between the old and new systems attracted significant interest, and we offered several options for discussion, as below.<\/p>\n
- \n
- Call forwarding \u2013<\/strong> To build a mechanism onto the SBC infrastructure to forward calls initially to the Cisco PBX, and then if the call wasn\u2019t taken up, to re-route the call to Microsoft Teams Phone.<\/li>\n
- Active directory (User) \u2013<\/strong> To steer individual calls either to the Cisco PBX or onto Microsoft Teams Phone based on the location of the user \u2013 the latter being determined by a suitable field in Active Directory, and the field being updated as part of the migration process.<\/li>\n
- Hybrid calling \u2013<\/strong> To provide dial plan integration between the Cisco PBX and Microsoft Teams Phone so that calls were automatically diverted to the correct system based on the call flow configured across the two systems.<\/li>\n<\/ul>\n
After consideration of each option, and based on the ease of implementation, risk, cost, and user experience, the hybrid option was selected. The details of that solution are provided here for reference.<\/p>\n<\/div>
<\/span><\/div>Hybrid calling with VOSS automation<\/h4>\n
The bank\u2019s Cisco PBX was connected into Microsoft Teams Phone via Direct Routing to offer an integrated solution with a single number inventory. Users could then be freely moved between systems, keeping their number, with the ability to call out to the public telephone network. VOSS automation was used to manage this movement, with the following user service profiles:<\/p>\n
- \n
- A user with Cisco services (only) – the initial state for a user, pre-migration<\/li>\n
- A user with both Cisco and Microsoft services (both sides ring on a call)<\/li>\n
- A user with Microsoft Teams Phone (only) \u2013 the eventual end migration of a user<\/li>\n<\/ul>\n
Users could simply be selected individually or in bulk, and moved, with the underlying dial plan mechanism and number management being orchestrated and tracked by the VOSS workflow, associated automation, and audit log.<\/p>\n<\/div>
The value<\/h4>\n
The solution offered benefits in terms of:<\/p>\n
- \n
- A simple and straightforward migration for a user, improving user experience<\/li>\n
- Retention of telephone number and call controls, as they were pre-migration<\/li>\n
- A single portal to manage both systems, pre, during, and post migration<\/li>\n
- A robust and fast migration process, with in built rollback if needed<\/li>\n
- Automated workflows to remove complexity and errors from the process<\/li>\n
- Repeatable operational processes \u2013 for example onboarding \/ offboarding a user<\/li>\n<\/ul>\n<\/div><\/div><\/div>
More information<\/h4>\n
There\u2019s more information on VOSS for migration on our website<\/a>. You can also get in touch with us here<\/a>.<\/p>\n<\/div><\/div><\/div><\/div><\/div>
Keep up to date with our latest blogs and subscribe today<\/h4><\/div><\/div><\/div>
- Active directory (User) \u2013<\/strong> To steer individual calls either to the Cisco PBX or onto Microsoft Teams Phone based on the location of the user \u2013 the latter being determined by a suitable field in Active Directory, and the field being updated as part of the migration process.<\/li>\n
- Automated migration \u2013<\/strong> To make the process of transferring users from the older PBX to the new Microsoft Teams Phone solution fast, error free, accurate, and without the need to call on Microsoft technical specialists (this was to be run by a deployment team).<\/li>\n