Share and Enjoy !

Introduction to Slack to Teams Migrations

This Ultimate Guide provides high-level information you need for when you are researching how to successfully accomplish a Slack to Microsoft Teams (Teams) Migration.

It draws on over ten years of experience from ThreeWill with migrating customers from other platforms to Microsoft 365. This guide gives insights for organizations wanting to prepare for an upcoming migration.


The audience for this Guide is anyone wanting to learn more about successfully migrating their Intranet from Slack to Teams.

Backstory and Introduction

Here’s the backstory on how ThreeWill got involved in doing Slack to Teams migrations. The backstory will help you understand how we arrived at a place where we’re helping clients make the move successfully.

  • Since ThreeWill started in 2001, we have built over a dozen connectors for SharePoint/Microsoft 365 for leading software firms including Atlassian, Jive, and Salesforce.
  • Given this experience, we started getting contacted by companies to migrate them from other platforms to Microsoft 365.
  • As of 2019, we’ve helped hundreds of companies make the move for hundreds of thousands of users.
  • Based on the type of migration, we’ve used both tools from other companies along with our own utilities and processes to help migrate customers migrate to Microsoft 365 successfully.

Define Vision and Business Case

Before we create the business case, you’ll want to make sure you understand the vision, or the “why,” for moving from Slack to Teams.

Based on our conversations with clients, here are some common business cases where companies make a move:

  1. Strategically align with Microsoft as the core collaboration platform
  2. Unify the collaboration experience for the organization by having one place to go to work together
  3. Consolidate resources and focus on building maturity on one key platform
  4. Stop paying double for collaboration because you have both Slack and Teams

From our experience, most clients say it’s a combination of these reasons (but, almost everyone includes #4).

One of the main reasons why we’ve been helping many clients make a move from Slack to Teams is there is a clear business case with hard costs and soft benefits.

The obvious hard cost is the annual subscription costs for Slack when there is broad overlap with Microsoft’s offerings. Microsoft has announced over 100 million active Microsoft 365 users (announced by Satya Nadella on April 27th, 2017) so many organizations are already using Microsoft for collaboration. Many of the business cases that we have worked on with clients have justified migrating from the hard costs alone, often seeing an ROI within months.

With regards to soft benefits, here’s our initial list of top 5 benefits

Speed of Innovation

For many years, smaller companies like Slack ran rings around Microsoft because of the three-year update cycle for products. Three years is an eternity when it comes to collaboration, especially social. With the acquisition of Yammer and probably even more important the adoption of continuous delivery, Microsoft has little to no innovation gap compared to its smaller competitors.

Clear Roadmap

The sales tactic of, “It’s coming in an upcoming version (and it doesn’t come for years),” is no longer being employed. Kudos to the Microsoft 365 team for putting out a clear roadmap – we appreciate this level of transparency from a software company. Also, Microsoft has leveraged the community to provide input on the priority of features through UserVoice forums (Microsoft 365 / SharePoint / Yammer / Teams / Planner).

Office Anywhere

Microsoft has been putting out solid versions of Office on iOS and Android. They are embracing other platforms, and this strategy is succeeding. Employees can BYOD and Microsoft is enabling their productivity – regardless of their choice of device.

CEO Clarity

Here’s a quote from Satya Nadella (TechCrunch Nov 2014 article) –

I just think about three things. There are a few other efforts we do, and I’ve been very clear about those efforts and why they exist and why we are proud of them. But, there are three products in all of this. There is Windows, there is Microsoft 365, and there is Azure. That’s it. Everything else to me is, of course, you can call them features, you can call them parts of that, and even there there’s complexity. Do we need to tame it make sure that we’re not inundated by lots and lots of things? But, from a business model, from what moves the needle for both usage and our revenue, those are the three big things that we are very, very focused on.

Unified Stack

With Microsoft 365, you get social features (like Slack, Jive), document sharing features (like Dropbox, Box), and IM on top of all the other commodity services you get like SharePoint and Exchange.

With all these services in one platform (Microsoft 365), you start seeing some interesting possibilities which leverage all the signals that are tracked in the Office Graph. Apps like Delve and Teams start to show you the power of bringing all your collaboration to one platform (Microsoft 365).

Educate Yourself on FAQs

Well educated clients are our best clients. We’ve compiled a list of frequently asked questions that we have heard when talking to companies about make the move.

Why work with ThreeWill to move from Slack to SharePoint/Microsoft 365?

Some of the reasons you should work with our team on this initiative are:

1. ThreeWill has successfully migrated other customers off of other platforms to Microsoft 365 in a timely manner and can provide references
2. We have an extensive background on the SharePoint / Microsoft 365 APIs from our experience with building commercial connectors and applications
3. To make the whole process go smoothly, we have built migration utilities to manage key information
4. Doing these types of migrations is a one-time project and therefore you should focus your internal teams on other initiatives where they can apply their experience multiple times
5. Using lower cost outsourcing teams that will be doing this for the first time adds risk to meeting deadlines


We need to get off Slack by a certain date, how early should we begin this process?

It is ideal to reach out to us to schedule the workshop 4-6 months before your expiration date. We may not need all that time, but we have a backlog of migrations and will need to get the workshop scheduled 1-2 months in advance.


What are the three phases of these projects?

First, the Slack Migration Workshop. Next, the Implementation (including POC, Pilot and Production migrations). Third, the Sustainment (Post migration support/additional needs like Branding)


What is the purpose of the Slack Migration Workshop?

The purpose of this Slack Migration Workshop is to allow you and ThreeWill to review the business and technical requirements for your Slack migration, explore the migration approaches and options and establish a budget to implement your migration.

The workshop will cover a detailed review of the migration process.  From this review, we identify key decisions that you will need to make related to the migration. We will a) review the current state of both Slack, Microsoft 365 / SharePoint / Teams, and any applicable legacy environments, b) review the requirements and drivers for Slack migration and c) determine the requirements and desired state of Microsoft 365 / SharePoint 2013/16 once the migration is completed. Lastly, this workshop will feed into setting a high-level roadmap, with the supporting approach, estimate, and initial project plan for the migration.

Often times a primary business driver for migration of the Slack content is license renewal fee avoidance prior to the renewal date. Any migration solution will consider and include the ability to extract and backup Slack content for retrieval before your license expires.


What are the costs of the workshop?

The cost for the two-day workshop is a fixed price of $9,500 USD.
Projects are delivered remotely over conferencing software.  If the client requires the delivery of the workshop to be on-site, we will charge for travel time.


What are the deliverables for the workshop?

1. High-level roadmap with the supporting approach and dates.
2. Product backlog with estimates.
3. The initial project plan for the migration.


Who needs to attend the workshop?

We suggest including:

1. Business Sponsor(s)
2. Slack Admin(s)
3. Microsoft 365 Admin(s)
4. Client Project Manager
5. Other Key Stakeholders that will be impacted by the migration


Is there any obligation to ThreeWill after the workshop?

No, you are free to do the migration with another consulting firm or internally and with another utility. But, you will not be able to use our migration utility if we do not perform the Implementation.


How quickly does a typical migration project last?

A typical migration has a pilot migration and a production migration. Smaller migrations typically take 4-6 weeks.  Larger migrations typically take 2-3 months.


What are typical costs for the implementation phase of the migration?

Typical costs range from about $10,000 USD for smaller migrations to over $200,000 for larger and more complex migrations. We have been focusing on helping customers with larger Slack communities that have a lot of intellectual property stored on Slack.


What process do you use for migrations?

We use SCRUM (read this article – Using SCRUM on Migration Projects) and set our clients up with a Client Extranet Site (on Microsoft 365, of course ;).


Is there anything that you typically do after the implementation phase of the migration?

It’s pretty common for us to help customers soften the edges of SharePoint and make it more familiar to end users. Also, it’s pretty common for us to set up a Sustainment Agreement to support future needs.


Conclusion and Next Steps for your Slack to Teams Migration

Thank you for taking the time to read this guide. You’ve now got a better understanding of the steps required for migrating your Intranet from Slack to Teams. Notice how important the approach is to the migration and how many steps are about reducing risk (for example, doing a pilot first to test out all your processes).

Share and Enjoy !

Related Content: