Enterprise Messaging News + Insights by Mio

Handling team chat after a merger or acquisition

Insights August 14, 2018


Handling team chat after a merger or acquisition

The numbers have been crunched. The job titles have been changed. You’ve made an acquisition. Congratulations! Pats on the back for everyone.

But, now questions are being asked:

“We acquired a company that uses Slack. We don’t- what should we do?”
“We’re merging with another company and have two different Slack workspaces- do I have to make a new one?”
“I don’t want to force anyone to change their processes in month one- what should I do?!”

The problem we often hear from IT Managers is “our company uses X, but the new smaller company that’s just been acquired uses Y…and I don’t want to ruffle any feathers.” Typically a startup or smaller company that gets acquired has been using Slack. But, ParentCo uses Cisco Webex Teams or Microsoft Teams.

Upon completion of an acquisition or merger, a quick transition to full team collaboration is crucial. Making the first decision about which messaging tools to use for your new group sets the tone of everything to come.

We’ve put together the below checklist to think through your team’s messaging strategy after a merger or acquisition:

If you want migrate to one chat app…

Not all messaging apps are alike. Will the new app you plan to migrate to support all features needed?

Below are a few things you may run into as you assess potential blockers & changes you will need to make.

  1. What channels and spaces need to be merged?
    You’ll need to map channels like “general” and “product team” to allow for the newer, wider team.
    Which should stay private vs. be publicly available for new team members to join?
  2. Language barriers?
    If you’re a global company, you may find language barriers across platforms become your blockers. Just become one platform supports a language doesn’t mean they all do.
  3. Additional costs incurred?
    Consider licensing tiers and price per user per month.
    Will you have a period of dual running costs? It’s unlikely you will be ready to migrate all at once.
  4. How long will your migration plan take?
    Moving from one platform to another, in any realm, can be a tricky process. It will require meticulous training, alignment from both teams, and on-boarding efforts. Consider this time as part of your total cost of change.
  5. Risk of change?
    On top of the cost of change is the risk of change. How long will it take for your team to get up to speed? Is there risk they could migrate to unapproved chat apps while migration takes place?
  6. Will you need increased Video Conferencing?
    Now that your team has grown, your collaboration needs have increased. Will you need more video conferencing capabilities now that your team is spread across more offices and locations? Does the tool you plan to consolidate into support this? Will you need to add another service, like Cisco Webex Teams, that also includes messaging?
  7. What other file-sharing tools are already used across the entire new team?
    If one company uses Office365 and MicrosoftOne Drive, Microsoft Teams would offer the richest form of collaboration. What happens when the new company uses Google Drive or DropBox? The task of migrating messaging and chat platforms could quickly evolve into a full blown collaboration restructure.
Every migration will have blockers along the way
Every migration will have blockers along the way

Remember to take stock on both sides

It’s tempting to immediately want to consolidate. You may think that an acquisition is perfect timing to introduce a new collaboration or messaging tool. But, take stock for a moment and pause. You have two groups of individuals that use and specialize in what they have been using. You can utilize this period to introduce true subject matter experts on both sides. It’s likely you have internal product evangelists that sing the praises of their preferred tool. Take the time to fully understand why they use and like these tools.

If you want to keep using both apps…

Your alternative option to migrating the new team to a single messaging app is to keep both. While this likely is much less upfront work to manage, it presents longterm implications for the team to consider:

1. Where do all-hands channels exist?
Where will both companies have a single place to chat? For example, where will team-wide HR information be placed? For an urgent matter, will the team know where they should look?

2. Will all employees and/or management be required to use both apps?
Monitoring both apps all the time could mean workflow issues, resulting in friction to getting things done. Also, using two chat apps means additional attention to monitor and double the amount of notifications.

3. Find integrations that work across both chat platforms
If you plan to stick with separate chat apps, there are creative ways to unify collaboration.
Check out our Quick Wins Guide to File Sharing and Quick Wins Guide to Video Conferencing and Virtual Meetings within Slack, Microsoft Teams and Cisco Webex Teams.

One of our favorites is the Webex Meeting Integration that works for Slack & Microsoft Teams users.

Webex Meeting Bot for Microsoft Teams
Webex Meeting Bot for Microsoft Teams

4. Make a long term plan for interoperability

If you plan to have two or more messaging environments, like Slack + Webex Teams or Slack + Microsoft Teams, what you really need is interoperability. Mio keeps everyone chatting and collaborating in their existing Slack workspaces and their Webex Teams or Microsoft Teams environments, while federating messaging across all platforms. This truly is the best of both worlds. Everyone gets to collaborate without the need to make a big migration plan.

Mio is simple to set up:

  • Auth in all chat apps your teams use by creating your Mio Hub
  • Import all users and channels at once, or select them one by one
  • Team members in your Mio 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 Mio
  • New conversations will be mirrored in the primary chat platform each employee prefers to use

Just because you’ve acquired a a company that uses different collaboration and messaging platforms or different chat workspaces doesn’t mean you need to isolate one messaging tool. Nor does it mean you must settle on the friction and communication silos created when using more than once messaging tool in the workplace.

Hopefully, the considerations above have reassured you that it’s not impossible to manage your messaging and chat platforms post-acquisition. It will, absolutely, take some blood, sweat and tears to get there. But, if that’s not for you, Mio can get your newly- expanded team collaborating in no time.

Set up your free Mio account here.

Thanks for reading! Be sure to leave a comment, and follow us on LinkedIn & Twitter to join in the messaging conversation.

  1. […] 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 […]

  2. […] 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 […]

  3. […] move users off Webex Teams when we move to Microsoft Teams”. We often hear this following a merger or acquisition – when the new company is using Webex Teams and the assumption is that everybody has to […]

  4. […] we move users off Slack when we want to fully adopt Webex 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 […]

  5. […] be honest, we’d rather not do it. Sometimes, you have no choice. In the case where your company has merged with another, there’s a decision to be made. Ultimately, you have to do something with one set of […]

Leave a comment

Leave a reply