Sencom – Cross Tenant Teams Migration Case Study

Sencom needed to handle customer merger and migrate Microsoft Teams workspaces to a new Office 365 tenant.

Sencom started to investigate possible ways to execute migration and quickly found out that Cloudiway was the only company providing tools to get the migration done as per the customer expectations.

“We used Cloudiway Teams migration tool for this project and worked well – all customer’s Teams were successfully migrated to the new tenant. We bumped into minor glitches during migration, but Cloudiway support guided us through quickly!”

In the exploration of Sencom’s specific migration requirements, a comprehensive breakdown reveals a multifaceted landscape of elements that demanded meticulous attention and strategic handling:

1. Channels: Sencom’s intricate Teams architecture included a myriad of channels, each serving as a distinct conduit for communication and collaboration. The migration strategy needed to seamlessly transfer not only the content within these channels but also retain their structural integrity to ensure a smooth transition without disruptions to ongoing projects or discussions.

2. Conversations: The wealth of conversational data embedded within Teams represented a vital aspect of Sencom’s knowledge repository. The migration process had to encompass the transfer of threaded conversations, preserving contextual information and ensuring that historical dialogues were seamlessly transitioned to the new environment.

3. Files and Attachments: The repository of files and attachments housed within Teams held invaluable data integral to Sencom’s operations. The migration plan required a robust mechanism to transfer these files while preserving their metadata, versioning, and relationships with associated conversations and channels.

4. Notes: Beyond standard communications, the migration had to account for the migration of notes – a feature integral to capturing and organizing free-form information within Teams. Preserving these notes in their original structure and format was imperative to maintaining the continuity of Sencom’s collaborative knowledge base.

5. Associated Mailbox and SharePoint Site: The interconnected nature of Teams with associated mailboxes and SharePoint sites added layers of complexity to the migration process. Ensuring a seamless integration between Teams and these associated platforms was pivotal to maintaining holistic data integrity and accessibility.

6. Permissions: Sencom’s Teams ecosystem was structured with granular permissions, defining access levels for various team members. The migration strategy had to meticulously replicate these permissions to ensure that data access remained secure and aligned with Sencom’s established governance protocols.

7. Membership Roles: The diverse membership roles within Teams, each with its set of privileges and responsibilities, required a nuanced approach during migration. Preserving these roles and aligning them accurately with the organizational structure was crucial for maintaining collaboration norms.

8. Planners: Sencom’s use of planners within Teams for project management and task organization added another layer of complexity. The migration had to encompass the seamless transfer of planner data, ensuring that project timelines, tasks, and associated details remained intact.