Thank you for joining us at the AVASOFT + Microsoft Tech Summit 2024! Thank you for joining us at the AVASOFT + Microsoft Tech Summit 2024! Thank you for joining us at the AVASOFT + Microsoft Tech Summit 2024!
Join us at the AVASOFT + Microsoft Tech Summit 2024 on Sep 12 | Microsoft Technology Center | Malvern, PA

Migrate Slack channels, direct chats, multiparty chats to MS Teams Channels and chats seamlessly

Want to know how we planned and migrated the chats and channel from Slack to MS Teams for our client? Read on to know more!
Reading time: 2 min(s)
How AVASOFT boosted the client's Snowflake change management by 60% using GitLab CI:CD?

The client wanted to migrate the Slack channels, Direct chats and multi-party chats to MS Teams channels, Teams 1:1 and 1: many chats. But they did not have any chats initiated in MS Teams and wanted us to do it. See how we resolved it! 

Know our customer

Our client, Fathym has been handling cloud-native application orchestration and infrastructure management that focuses on building apps. Their framework radically reduces the time and work involved in managing legacy applications, adopting new application delivery strategies, and bringing infrastructure and DevOps best practices for their customers. They have a robust, feature-rich API that offers a powerful suite of weather forecasting and low code data visualization tools.  

The client wanted to migrate the Slack channels, Direct chats and multi-party chats to MS Teams channels, Teams 1:1 and 1: many chats.

Business challenges 

  • The client wanted to migrate Slack Channels to MS Teams Channels. They wanted us to create the channels accordingly in MS Teams.  
  • They also wanted to migrate Slack Direct Chats into MS Teams 1:1 Chats  
  • Migrating Slack Multi-Party Chats into MS Team 1: Many Chats was a huge challenge  
  • The client did not have any chats initiated in MS Teams and wanted us to do it.  
  • They also needed suggestions on filtering the user list, and the required MM and DM for migration as they did not have any idea on which conversations needed migration.  

How AVASOFT helped?

  • We exported the Slack and Office365 users list from the tool to complete the additional User Verification process (whom the users need to migrate their direct & group chat). 
  • Once all the additional users got verified, we then started the inventory to identify each user direct and group chats. 
  • We mapped the Slack user with the Office365 user to display and maintain the migrated content.  
  • Then we started the initial migration on multiple VM’s as they all had different requirements like Channels migration, Group chat migration, and direct chat migration respectively. 
  • Our team planned and migrated each user Direct and Multi-party chat migration based on Inventory message volume. 
  • We took over the full control of the migration service and handed over the migrated MS Teams to the client to go live. 
  • Our team also ensured the client overcomes the Slack and MS throttles limitations to proceed with the inventory and migration. 
  • We recommended the filtering of users and chats after the inventory assessment and it helped the client in retaining the important chats and leaving behind the unimportant ones.  

Business gains 

  • Since full control for migration was handled by us; the client was relieved from any issues during migration.  
  • The client was able to get a similar UI in Teams with hardly any workflow disruptions. This made the communication more effective.  

Share this Article