Introduction
Welcome to the How Our Migration Works section of our documentation. This page is designed to provide you with a clear understanding about our migration process. Whether you’re transitioning from Slack to Teams, or moving Teams tenant, our service ensures secure and efficient transfer of all your data. We understand that every piece of information, be it a casual chat, a shared file, or a meticulously planned project, carries immense value and importance to your business continuity. Below chapters are about to explain that process and responsibilities of each side to carry out successful migration.
Migration overview
We offer two distinct types of migration services:
Given that both Slack and Microsoft Teams are cloud-based applications, our migration process leverages Slack OAuth2 and M365 OAuth2 app infrastructure to ensure a seamless transition. That approach ensures that we have access only to data and actions which are necessary to perform migration process. A crucial part of the migration process involves collaboration with our clients who establish the necessary connections and provide essential information about the target organization of data and decision on user mappings. Lastly, we offer optional validation and integrity checks to ensure data accuracy and completeness post-migration. This customized approach allows us to deliver a migration process that matches the unique business needs of our clients and secures your data’s safety and integrity throughout the migration process.
High level Migration steps
- Create connections to Source and Target applications
- Create user mappings
- Describe new structure at target tenant
- Migration is pending (Usually migration process is taking from few hours to several business days depending on size of your data.)
- Verification
- Removing connections