Client Prerequisites & Consent Overview (Non-Technical)
This document explains what is required from the client to successfully migrate data between Microsoft Teams and Slack, in simple and clear terms.
Without consent, user data cannot be migrated, which may result in missing or incomplete data.
What Is Needed from Microsoft Teams (Microsoft 365)
1.1 Microsoft 365 License
Each user whose data will be migrated must have a Microsoft 365 Business Standard license (or higher).
This allows access to Microsoft Teams messages and files.
1.2 One-Time Setup by IT / Admin
The client’s IT/Admin team must create a secure application in Microsoft Azure.
This allows our migration tool to connect safely to Microsoft Teams.
The admin will share:
- Tenant ID
- Client ID
- Client Secret
(This is a standard and secure Microsoft process.)
1.3 Admin Approval (Mandatory)
A Global Administrator must approve access once for the organization.
This step allows tenant-level access required for migration.
1.4 User Approval (Mandatory)
Every individual user must approve access to their own:
- Chats
- Messages
- Files
- Their data will not be migrated
- Their chats and files will be missing in the final result
What Is Needed from Slack
2.1 Slack Plan Requirement
A minimum Slack Business plan is required to allow message and file migration.
2.2 Workspace Approval
The client must approve a Slack Bot application at the workspace level.
This allows access to channels, messages, and files.
The Slack Bot application must be approved before migration can begin.
2.3 User Approval (Mandatory)
Each Slack user must approve access to their messages and files.
- Their Slack data cannot be migrated for that user.
- Their content will be excluded, like missing chats in groups or channels.
Why User Consent Is Critical
Migration belongs to individual users.
Platforms do not allow access without user approval.
No approval = No Migration
There is no workaround for missing consent.
Consent Flow – Step Summary
Microsoft Teams
Slack
Final Responsibility Summary
The client is responsible for ensuring:
- Required licenses are assigned
- Admin approvals are completed
- All users complete consent.