GETTING STARTED
Mapping current services to Teams and improving UX Once the data is extracted, the next step is mapping the existing services into Microsoft Teams while improving the overall user experience. However, this transition isn’t always straightforward. Voice features from legacy systems don’t always map "one-to-one" with Teams. At this stage, any glitches can lead to a series of post-migration problems, piling up on the service desk and causing user adoption issues. The challenge is ensuring that users can enjoy a smooth transition without experiencing issues such as call quality drops, missing features, or difficulty adjusting to the new system. Addressing these challenges early can prevent delays and enhance the overall success of the migration.
Feature migration Often the feature description and configuration is different, and each feature will need mapping and converting to the equivalent on Microsoft Teams. For example - a Cisco Hunt Group or Skype for Business Response Group will need converting into a Microsoft Teams Call Queue or Auto Attendant. Feature dependancies More complex features are linked, and users with these features (for example a manager and their assistant) need careful consideration in the mapping process and scheduling for the move to Microsoft Teams. Microsoft PowerShell provides some tools for the above, but it is a command line language for skilled operators only, and does not lend itself to predictable and accurate migration projects.
Feature design
Other features will need redesigning to offer a similar if not identical behavior - for example users with multiple contact numbers or users on shared extensions or lines.
Top tip
Find a mechanism to program and automate the process - to reduce the workload, errors, and time to migration with a view to keeping the user experience robust during and after the process.
Powered by FlippingBook