The decision to migrate your business calling infrastructure is a big one, after all, the potential disruptions to internal and external communications could cause frustrations and delays on both sides of the business.
Though horror stories are real and should be learnt from, there is also guidance out there to avoid these gremlins and ensure a smooth migration to Teams. Allow Solution Architect, Callum Hardie from Exactive, to talk you through some of the big questions when migrating to Teams.
How can IT Teams eliminate any bugs before rolling out a Direct Routing solution to the workforce?
The best piece of advice to give here is to make sure you follow a proven framework and methodology. A thing to remember is that this is not just about the technology but around the planning and future use of it, so a Change & Adoption plan that details how you are going to use these technologies is a good idea.
If one of the concerns starting the project is getting the bugs out before it hits the end-users, then one of the key questions you should be ‘how are we going to deploy’? I would always recommend you broaden the scope of your pilot to get as much of a variant of your user base as possible. Each department will use the technology in different ways and you’re more likely to find the bugs this way.
What is a co-existence model and will it work for me?
The most common use of the terminology ‘co-existence’ is when describing what features your users have when making the journey from Skype for Business to Teams and the coexistence between the two platforms. One of the more simplified diagrams I use in helping depict the co-existence between the two is below. Although this only covers Skype for business, Teams can co-exist with your on-premises PBX or analogue devices for example.
[caption id="attachment_35767" align="aligncenter" width="602"]
Co-existence Modes[/caption]
The reasons for co-existence have not changed. The most obvious answer is that sometimes it’s impossible to switch one system off and turn another on without any interruption to the end-user. Some other common examples include:
- Complex Estate (large user base, phased approach)
- Sweat Existing Assets (ISDN Contracts, PBX Maintenance)
- Seamless user experience
- Business process changes
The scenarios above should not prevent an organisation from starting their journey to the cloud if the two systems can co-exist, which has historically been a barrier. With Teams, this barrier no longer exists.
