M2UC Migrations from Avaya to Microsoft Teams
Tom Turrington, Migration Team Lead, VOSS
Following my previous post about VOSS' ability to successfully migrate from Avaya to Cisco UCM, it seemed relevant to write about another of our migration projects which again involves moving from Avaya - this time to Microsoft Teams.
If you want to see how it’s done, watch this video.
In fact, this migration actually involves migrating to both Cisco UCM and Microsoft Teams in parallel, but as I have previously written about migrating to CUCM, the focus of this blog post will be on the move to Microsoft Teams.
Our migration solution - M2UC - has been utilised and has proven its flexibility and capability to handle different data sources and manipulate them in readiness for provisioning into the chosen target system. As with all migrations, our standard DETVL (Discover, Extract, Transform, Validate & Load) process is used.
Once a discovery process has taken place and the required conversion rules have been designed, the following ETVL steps are rotated as many times as necessary - i.e. for as many batches as required. Data is imported into M2UC and at the push of a button it is transformed according to rules previously recorded. The data is then validated and provisioned into the target platform. This is done consistently and in a repeatable manner, at high speed with very high levels of accuracy.
The data never leaves the M2UC platform until provisioning; there are no spreadsheets to deal with and provisioning status is tracked. If errors are encountered during provisioning, these are also logged with information pertaining to each record stored alongside the provisioned data. Any such records can then be filtered, the rules can be adjusted to deal with the errant data as required and re-provisioned.
VOSS M2UC not only provisions singularly to MS Teams or to Cisco UCM, but it can also create hybrid users - those with users that have both Cisco UCM and MS Teams accounts.
M2UC can be used by a single individual or by many teams. Using M2UC workflows, the migration process can be automated further to reduce human intervention and streamline the migration activities. This lowers the required skill level of the operators and reduces the potential risk of human error to an even greater extent. For more information on workflows see this blog post.
No matter which sources or target data that M2UC is utilised for, all of the same powerful features are available. Users can be assigned their own individual projects or can collaborate with others; any input data can be mapped to any target endpoint fields; rules can be used across different datasets (and transferred to other M2UC platforms); validation is possible prior to provisioning and all actions are logged allowing for progress tracking, examination of issues encountered, and full accountability.
We recently hosted a webinar on "How to Migrate and Seamlessly Operate Avaya with Microsoft" - you can catch it, here.
For more information about M2UC, or to discuss your UC migration project - whether involving Avaya, Cisco, Microsoft, or another UC platform, please contact us.