Dispatch by Mio
Published in

Dispatch by Mio

Upgrading to Microsoft Teams, but also have Slack users?

Upgrading to Microsoft Teams, but also have Slack users?

With Microsoft announcing Teams’ feature parity with Skype for Business, the scenario where two collaboration tools become one is finally possible. With Skype for Business users estimated to be around 1.43 billion, there’s potential for a whole lot of Teams migrations. As of March 2018, Microsoft Teams has adoption of 200,000 users.

There are also many companies who use Slack in addition to Skype for Business, given that Teams adoption is still immature.

If this is the case at your company, read below as there are special considerations for those Slack users when the rest of your company is migrating from Skype for Business to Microsoft Teams.

Guidance from Microsoft

Microsoft has set guidelines for when to use Skype for Business and Microsoft Teams. But, with the option to use both, this leaves customers without a clear sense of how to reach the hybrid UC coexistence.

We started with the Skype Operations Framework. Since the introduction of Teams, this has evolved into Practical Guidance for Cloud Voice. These are both robust, tried and tested frameworks that help deploy and adopt Skype for Business and now Microsoft Teams.

Screenshot of Microsoft Teams guidance for Slack users
Practical Guidance for Voice

Options for upgrading to Microsoft Teams

Microsoft has stated their vision for bringing together Intelligent Communications and collaboration is focused on Microsoft Teams. There are two upgrades paths provided by Microsoft, Basic & Pro.

  1. Upgrade Basic is for smaller organizations or those with low Skype for Business adoption. This is designed to upgrade your entire organization to Teams at once.
  2. Upgrade Pro is for organizations with expanded functionality. This is aimed at enterprises who’d benefit from a phased approach.

It’s worth reviewing both paths extensively to determine the best approach for your organization.

Microsoft Teams Pilot

Before you undertake your Microsoft Teams deployment or migration from Skype for Business, it’s always advisable to conduct a pilot. It’s important to note the terminology here. This is not a proof of concept. Businesses often get bogged down with a proof of concept — the concept has been proven, Microsoft Teams is a stable platform transforming business all over the world.

What you are doing here is running a pilot to suit your needs. Your Microsoft Teams pilot needs to be tailored to your businesses unique needs and bespoke requirements.

A select pilot committee is crucial. You need your most vocal users and key stakeholders on-side from day one. Failure to engage and win over the right people could put the entire pilot — and migration — in jeopardy.

Screenshot of the Microsoft Teams enterprise messaging journey
A typical Teams Pilot

What is missing from these plans is a common scenario we run into with our customers that is the elephant in the room: Upgrading to Microsoft Teams when some users also use Slack.

Road from Skype for Business to Microsoft Teams
Skype for Business has a natural path to Teams

Slack vs Microsoft Teams…
Slack and Microsoft Teams?

When you plan for that great day when your Skype for Business to Microsoft Teams migration is complete, do you have a plan for your Slack users?

Your Slack users may have organically introduced Slack as the collaboration tool in your company, with Skype for Business reserved for voice calls. But, with Teams running too, what does this hybrid UC co-existence scenario look like? Is it even possible?

You have two options, and you may not have known the 2nd was even possible!

You may also like: Ultimate Guide to External Federation in Slack

1. Kill Slack and get everyone on Microsoft Teams

An extremely common question is: “How do we move users off Slack when we move to Microsoft Teams”. We often hear this following a merger or acquisition — when the new company is using Slack and the assumption is that everybody has to collaborate in the same app.

Here are two key considerations as you work to get buy-in from your Slack users:

You’ll need to prevent data loss when migrating Slack channels to Microsoft Teams channels:
You will need to re-map channels that exist in both Slack and Microsoft Teams into one Teams channel and migrate all of the existing content over. You will need to tell your team they should prepare to lose data or have a lapse in access to that data for a period of time.

You’ll need to transition your Slack integrations & workflows onto Microsoft Teams:
You’ll need to work out what functionality you will lose, if any, by moving off Slack. Ask your Slack users what integrations they use and workflows they’ve built into Slack that need to be replicated into Microsoft Teams. If the integration is not available for Microsoft Teams yet, you may need to find a workaround solution or a different SaaS provider entirely.

Remember that in general, people will be adverse to losing the app they live in all day, without a good reason. This effort may take many weeks or months of careful planning.

2. Interoperability between Slack + Microsoft Teams

Collaboration apps are extremely personalized and users will have their favorite integrations and bots that they use and rely on, day in day out. In the long term, planning to support two or more messaging environments, like Slack and Microsoft Teams gives your UC strategy more flexibility, as long as everyone can work together across different chat platforms. That’s where M.io can help.

M.io keeps everyone chatting and collaborating in their existing Slack workspaces and their Microsoft Teams environments while federating messaging across all platforms. This truly is the best of both worlds. Everyone gets to collaborate the way they prefer, without the need for a big migration plan.

M.io for Slack + Microsoft Teams Interoperability

With M.io, your Slack users don’t need to change platforms and will still be able to chat with colleagues on Microsoft Teams, and vice versa.

M.io is simple to set up:

  • Connect all the chat apps your teams use by creating your M.io Hub
  • Import all users and channels at once, or select them one by one
  • Team members in your M.io Hub can immediately chat in DMs or groups with members on other platforms
  • File sharing, threaded messages, reactions, and the ability to edit and delete messages are all supported with M.io
  • New conversations will be mirrored in the primary chat platform each employee prefers to use

To find out more about M.io’s Microsoft Teams + Slack interoperability solution and get on the beta list, you can schedule a demo with our team here.

🤖 Thanks for reading! Be sure to👏 this post if you like it, and follow us here on Medium as well as LinkedIn & Twitter.




Microsoft Teams + Slack + Webex Teams News

Recommended from Medium

How to Solve Big Problems and Test New Ideas in Just Six Days.

How to do LinkedIn like a boss

Mentors: Find your match!

New Ways of Caring

Working in a business that no one else is doing

The Resume Conundrum

5 Tips for Your Graphic Design Cover Letter


Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store


Chat better, together. Mio powers cross-platform messaging across Microsoft Teams, Slack, Webex, and Zoom. Learn more at https://m.io

More from Medium

Announcing Onboardly IT — Simple and Secure Way to Manage Access to Company Tools and Applications

Standardisation — A tool not a goal

How do great organizations (especially startups) staff, high-skilled engineers?

Provide your team with unprecedented powers by applying advanced feature toggling approaches.