MS Teams Migration Process

• A minimum Microsoft 365 Business Standard license is required to enable Microsoft Teams access and API usage.
• An application must be created in Azure App Registration to allow secure authentication and access to Microsoft Teams data.
• The client must provide the Tenant ID, Client ID, and Client Secret value (the Client Secret Value is visible only once and must be copied immediately).
• A one-time consent from the Admin User is required to authorize tenant-level access for message migration.
• In addition, individual user consent is required to migrate each user’s personal messages and chats and their file.

• A minimum Slack Business plan is required to fetch users.
• The client is only required to grant consent of the admin for users.

General Prerequisites

Admin Access

• Microsoft Teams: Admin access of at least one user with required permissions.
• Slack: Admin access of at least one user with full user and app management rights.

User Consent

Authorization for each user are required to migrate (these will be obtained post-installation of the app on Teams).

• Direct Messages
• Files & Attachments
• Channel Conversations

Once the prerequisites are met, our application will be able to successfully migrate:

• Users
• Chats
• Direct Messages
• Channels
• Files & Attachments

Best For

Free Plan / Pro Plan

Basic workspace migrations where only public channel data is required.

Business+ Plan

Complete workspace migrations where all conversations, channels, and user data need to be transferred.

Import Limitation

Slack does not support migration into an Enterprise Grid organization.

Required Migration Process

If the destination workspace belongs to an Enterprise Grid organization, follow the steps below:

Step 1: Create or Downgrade a Workspace to Business+

Create a new Slack workspace or Downgrade an existing workspace to the Business+ plan.

Step 2: Import Data into the Business+ Workspace

Import the data into the Business+ workspace.

Step 3: Validate Imported Data

Verify that:

• Users are imported correctly.
• Channels are created successfully.
• Messages are available as expected.
• Files and file links are accessible.

Step 4: Upgrade to Enterprise Grid

After successful validation, upgrade the Business+ workspace into the Enterprise Grid organization.

Step 1: Admin Consent

The migration process will begin after obtaining the necessary consent and permissions from the Microsoft Teams administrator.

Step 2: User Discovery

Once consent is provided, we will fetch and analyze all users from the Microsoft Teams environment.

Step 3: User Mapping and Invitations

• We will fetch users from the destination Slack workspace using Slack Admin access.
• If matching users already exist in Slack, they will be mapped automatically on basis of emailId.
• If a Teams user does not exist in Slack, an invitation will be sent to that user.
• The invited user must accept the Slack invitation before migration can proceed for that account.

Step 4: User Migration (Usually will take maximum 2 hours)

After all required invitations have been accepted, user migration and mapping will be completed.

Step 5: Channel Migration

Once user migration is completed, channel migration will begin.

Step 6: Channel Member Migration

After channel migration is completed, channel memberships will be migrated and users will be added to their respective Slack channels.

Step 7: Export Package Generation

After member migration is completed, we will generate and provide a ZIP file containing the migrated message data.

Step 8: Message Import into Slack

The Slack Workspace Owner will need to import the provided ZIP file or zip link into the destination Slack workspace using Slack's Import/Export tool.

This step is required for message migration and historical conversation restoration within Slack.