Table of contents
- What are the prerequisites to migrate data from Slack to Microsoft Teams?
- What kind of permission sets are used during the migration?
- What needs to be done after migration is completed?
- What is the difference between automated and manual Slack Provisioning?
- Do you create users in target Microsoft 365 during migration?
What are the prerequisites to migrate data from Slack to Microsoft Teams?
- Slack Environment: You must have Workspace Admin permissions. This allows necessary access to your Slack workspace data.
- Microsoft 365 Environment: You need to be a Global Administrator. The Global Administrator role is the top-level administrator role within Microsoft 365 and carries with it extensive access to all features, settings, and data.
What kind of permission sets are used during the migration?
For slack following scopes are used: channels:history, channels:read, users:read, users:read.email
What needs to be done after migration is completed?
From our side all migration data is permanently erased from our systems, including:
- References to Source & Target Connections
- List of user mappings
- Client information
It is strongly advised that client delete all existing apps created during connection provisioning. Instructions how to do it can be found there:
What is the difference between automated and manual Slack Provisioning?
Both produce the same result. Although automated provisioning can create you a connection with just few clicks and in fast time, the manual option gives you more control and self-awareness about your slack resources.
Do you create users in target Microsoft 365 during migration?
No, we didn’t. The reason is that creating user usually includes assigning new paid license and password. We do not want to compromise your security, so creating required accounts before migration is client responsibility.