Dispatch by Mio
Published in

Dispatch by Mio

Migrating from Jabber to Cisco Webex Teams, but have Slack Users?

Migrating from Jabber to Cisco Webex Teams roadmap
Migrating from Jabber to Webex Teams, but have Slack users?

Cisco recently announced businesses can now connect Cisco Jabber to the Webex cloud. This new hybrid solution for communication is excellent for companies making a gradual migration to Webex Teams. This all seems great, until you realise you have users that have both Slack and Jabber.

Organizations using Jabber will have the opportunity to enable Team Messaging modes. This upgrade will bring core features of Webex Teams into Jabber. On-premises and cloud users should benefit from a more consistent experience.

If you’re keeping your infrastructure on-premises for now, the new integration means you can still access the features of the Webex cloud. Cisco intends this integration to be a bridge for people moving from Jabber to Webex.

Why migrate Jabber to Webex Teams?

The hybrid setup is useful for today’s enterprises. It ensures that you can federate your Jabber client with Webex Teams. That means that users in both platforms can connect without switching apps.

Essentially, Cisco is offering an alternative approach to the rip and replace migration method. Rather than telling team members they can no longer use a specific app and removing it from the workforce; you can transition them slowly.

To set up interoperability:

  • Add your organisation to the Cisco Platform Identity service. Check in the Cisco Control Hub to see if your business has already been added.
  • Set up SSO for Cisco Platform Identity if you use single-sign-on for Webex Teams
  • Go to the Control Hub and click on Services then choose Message > Messenger
  • Scroll down to Options and click on Cisco Webex Teams / Jabber Interop then hit save

While this solution supports your Jabber and Cisco Webex users, it doesn’t help team members using other apps. What do you do if you have employees on Slack too? There’s no button for Jabber and Slack or Webex and Slack interoperability.

Cisco Jabber and Cisco Webex Teams logos
Cisco Jabber and Cisco Webex Teams

Migrating Slack to Cisco Webex Teams

Unlike a migration from Jabber to Cisco Webex Teams, moving from Slack to Webex Teams is much harder. You’ll need to move all of the data in your Slack workspaces into Cisco. This means:

  • Visiting Your Profile > Admin > Workplace Settings.
  • Clicking on Import/Export Data and download all of your information.
  • Sending your content directly to Webex Teams if it’s smaller than 2GB. If you have more than 2GB of data, you’ll need a third-party service like Dropbox.

If the files you move from Slack to Cisco Webex Teams are too large, you may end up losing critical data packets. You’ll also have the challenge of encouraging adoption to face with a migration from Slack to Webex Teams. Your Slack users can easily continue to use their favorite app behind your back if they’re not happy on Cisco. That’s where problems like shadow IT and workplace silos begin to emerge.

Shadow messaging in enterprise chat caused by multiple chat apps
Shadow messaging is the latest form of shadow IT

Why choose integration over migration when dealing with Jabber and Slack?

Humans are creatures of habit.

We decide which tools we like to use and stick by them. By integrating Jabber and Webex Teams, Cisco is creating a familiar environment that your staff members may feel more comfortable adopting. However, this doesn’t solve the problems of migrating users from other tools to Webex Teams.

Even if you managed to transition all of your employees successfully, you might find that you need to compromise on tools and plugins. Not all collaboration apps feature the same integrations. This means that your workflow suffers while your employees adapt to the alternatives.The good news is that there is a better way.

Rather than forcing users to choose from Slack and Cisco Webex Teams, Mio can help.

How Mio syncs Slack, Cisco Webex Teams, and Microsoft Teams
Mio powers seamless communications between Microsoft Teams, Slack and Cisco Webex Teams

Mio for Slack and Cisco Webex Teams

It’s becoming easier for companies to connect teams on dispersed apps from the same vendor. However, the challenge comes in syncing staff members, regardless of what app they use.

The good news is that there are innovators out there working to solve this integration issue. Mio integrates your messaging platforms. With Mio, you can avoid vendor lock-in and give your teams the freedom to use the apps they prefer.

Whether you’re messaging on Slack or Cisco Webex Teams, your employees will be able to see and connect with each other seamlessly. You can even send a file to a user on Slack through Cisco Webex, and vice versa.

Are you ready to discover what you can accomplish with Mio? Learn more with this video!

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

--

--

--

Microsoft Teams + Slack + Webex Teams News

Recommended from Medium

New Relic Dashboard & Integrations

Using AWS Database Migration Service to replicate Data from MYSQL to REDSHIFT

Build Your Text Editor With Rust! Part 5

The Best Software development methodologies, Part 1

Using SSM Parameter Store

🥳 The Dapp List Curation dashboard (curation.thedapplist.com)

This is what happened to open source in 2018 (and beyond)

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
Mio

Mio

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

More from Medium

What is a discovery stack? Daily routine with Captain Matt.

What is a discovery stack? Daily routine with Captain Matt.

Digital Pond: EP#3 Sam Booth — Building a Business for the Digital Era

Data Migration Tool: Migration M1 to Latest Version

Data Migration Tool: Migration M1 to Latest Version

How to Change Applications Passwords Using Applications Schema Password Change Utility (FNDCPASS)