Slack to Microsoft Teams Migration Guide

Overview:

1. Slack migration with Cloudiway
2. Security
3. Performance
4. Audience
5. Pre-migration configuration
   1. Before you start
6. Use the Cloudiway platform to migrate Slack
   1. Allocate Slack migration licenses
   2. Create your source connector
   3. Create your target connector
   4. Activate and monitor your migration
7. Troubleshooting

1. Slack to Microsoft Teams migration with Cloudiway

Cloudiway’s Slack migration solution helps businesses perform elaborate technical migrations through a simple SaaS interface. As a result, Slack migrations require no additional software installation or overhead, and migrations can be performed securely and quickly.

2. Security

For more information about security, please refer to this article.

3. Performance

For more information about migration performance, please refer to this article.

4. Audience

This guide is aimed at experienced system administrators who are capable of connecting to remote systems and using a variety of administration tools.

Although we provide support for our own products, we do not provide support for third party products such as PowerShell or server administration of Microsoft products.

If you are concerned you might have any difficulty completing these steps, please consider a solution with our consulting team, contactable via presales@cloudiway.com. This will ensure a fast, costeffective and stress-free implementation.

5. Pre-migration configuration

5.1. Before you start

Before you start, you will need to ensure you have the details outlined in the following table. You will only need the items associated with your chosen target. The sections below the table only need to be followed if they related to your target. We recommend you create accounts especially for migration. After migration, simply delete the accounts.

6. Use the Cloudiway platform to migrate  Slack

6.1. Allocate Slack migration licenses

Please get in touch with Cloudiway (at sales@cloudiway.com) so that your  licenses can be organized and allocated to your Cloudiway account right away. By getting in touch now, the licenses will be available for use well before you need them.

6.2. Create your source connector

To facilitate mail migration, the Cloudiway platform needs to be able to communicate with both your source and target domains. To do this, Cloudiway uses connectors, which are configured on apps.cloudiway.com. You will need to set up a connector for each source tenant you wish to migrate and each target tenant that mail should be migrated to. Follow the steps below to configure a source connector.

1. Navigate to https://api.slack.com/ and login.
2. Click on Your Apps on the upper right of the screen, then click on Create New App.
3. Give an App Name.
   Select a Slack Workspace.
   Click on Create App.
   
4. Click on the newly created application to edit the settings.
5. Click on Add features and functionality.
   
6. Click on Permissions and navigate to Scopes.
   Add the following scopes and click on Save Changes.
   
7. Once done, install the application.
   Click on Install App to Workspace.
   
8. Click on Allow.
   
9. The app is now installed and an Oauth access token is generated.

List of scopes to Add:

• Access user’s public Channnel / Channels:history
• Access information about user’s public channels / channels:read
• Access content in user’s private channels / groups:history
• Access information about user’s private channels / group:read
• Access content in user’s direct messages / im:history
• Access information about user’s direct messages / im:read
• Access user’s group messages / mpim:history
• Access information about user’s group messages / mpim:read
• Access the workspace’s files, comments, and associated information / files:read
• View some URLs in messages / links:read
• Access your workspace’s profile information / users:read
• View email addresses of people on this workspace / users:read.email.

Note the Oauth Access token. This token is needed when creating the Cloudiway slack connector on the Cloudiway platform.

6.3. Create your target connector

For Cloudiway to migrate your email, it needs to be able to communicate with both your source and target domains. To do this, Cloudiway uses connectors, which are configured on apps.cloudiway.com. You will need to set up a connector for each source you wish to migrate from and each target that you wish to migrate to. With your source connecter already set up, a target connector to Microsoft Teams is now required.

1. Click on Targets on the left, then + New on the Action bar at the bottom of the screen.
   
2. Click on Office Groups / Teams Online and type a meaningful name in Connector name.
3. 
4. Click on the Create button.
5. Fill in the fields.
6. 
   
   Server Region: Most of the time, keep the default value “Worldwide” except if you have a China, German or US Governmental tenant.
   Name of the tenant: enter the name of your tenant (ie cloudiwaylab), not cloudiwaylab.com or cloudiwaylab.sharepoint.com. Filling this field automatically fills the URL field.
   Domain Name: Enter the name of your primary domain.
   Migration User: A sharePoint administrator account ( for permissions to run CSOM calls).
   User Password: The password of the migration user. This is stored encrypted in EAS 256.
   Client ID / Client Secret: Graph API client ID and secrets with permissions to access, groups, users and sites.See this article for creating the application : https://kb.cloudiway.com/article/azure-apps-registration/
7. Click on the Save button at the bottom of the screen.

6.4. Activate and monitor your migration

Now that you have performed all the pre-migration steps within your tenants and within Cloudiway, you’re ready to migrate. We recommend you run a test migration on a single user first to check that your configuration produces the outcome you expect.

To start your migration, select the users or batch you wish to migrate and click on Migration on the Action bar, then Start. Your batch will be scheduled and will begin as soon as resources are available. By default, a hundred migrations can be run concurrently per connector.

Don’t forget that Cloudiway migration platform supports delta passes and that migrations are therefore incremental; every time you restart the migration of a Slack, only items that haven’t already been copied to the target will be migrated. The platform therefore does not duplicate items in the target.

7. Troubleshooting

Cloudiway provides an extensive knowledge base with many resources, including common error messages, video guides and downloads.

Please visit the entire knowledge base here (where you can search for keywords or read through topics): https://kb.cloudiway.com/

The knowledge base also contains information on how you can ask for further support, should you require it.