Thomas.Poett@TEAMS (MVP Teams and Cross-Tenant M&A/D Migration Expert Lead)

  Migration Orchestrator is Microsoft's tenant-to-tenant migration approach for moving personal user workloads between separate Microsoft 365 tenants (for example in mergers, acquisitions, divestitures, or internal reorganizations). It is designed to migrate workloads in an order that accounts for dependencies and aims to minimize end-user disruption. What Orchestrator migrates (and what it does not) Orchestrator supports the migration of personal, user-scoped workloads. In the current preview scope, it includes: ·        Exchange Online mailbox (user-visible content such as email, contacts, calendar, tasks, and notes). ·        OneDrive (personal) content, moved to the target with a redirect left in the source location (no incremental/delta passes). ·        Teams chats and Teams meetings (with dependency on mailbox success for meeting migration). Orchestrator does not migrate sha...

Hi all, this is part 2 of  7 videos we streamed about the cross-tenant migration during Merger and Acquisitions. After watching this series, you are able to manage and setup a cross-tenant migration project. Knowing whats important, where to have more intense focus on and what possible to migrate and what's not. Part 1: General Overview Part 2: Personal Data Migration (Mailbox, OneDrive, ..) Part 3: Collaboration Data Migration (SharePoint, Groups, ..) Part 4: Collaboration Services (Telephony, Teams, ...) Part 5: Legal and Compliance (Migration and what to consider) Part 6: Device Migration (Azure, Intune, SCCM, ...) Part 7: Change & Adoption

 

 In this cross-tenant/ tenant-2-tenant migration book, I guide you through the holistic approach, which in deep exercise of Team Voice. I’m working as an Enterprise Solution Architect for Cross-Tenant migration, leading teams with more than 40 persons involved. Technically there are many more aspects, like 3rd party tools vs. Microsoft own solutions and scripts to be written. This book provides you an inside but not providing scripts and detailed configuration. Scripts and configurations are very much an individual approach for each cross-tenant migration. Two very special chapters will be released in 2023, handling and working with Guest User Access and Change & Adoption approach. Both are not only technically important but require a deeper look into their dependencies. Working on an end-2-end overview, technical considerations and understandable working template, this Migration book, it was work consolidated during the last 1 ½ years. DOWNLOAD HERE:  https://www.slidesha...

  Cross Tenant User Migration Approach and considerations In any Tenant 2 Tenant migration the migration approach you have to consider based on: ·        Migration Tools ·        Communication/ Work clusters ·        User and shared data The combination and dependencies of the above will guide you to the best possible decision, how you migrated a tenant and merge it into the target environment. Migration of data is time consuming. We explained the tenant limitation (throttling) in a chapter above. Nevertheless, pre-loading of data into the target tenant is crucial including the sequence required for planning.   Migration Tools There are multiple vendors on the market providing tools, tool sets. They either run on-premises, in Azure or have developed their own cloud-based solution. Principally you will consider a mix of different tools and vendor. Most companies run a h...

  Example of our user data migration approach: Important is the completion of your data pre-load for OneDrive and Exchange. Remember, that the pre-load should include as much data as possible. Syncing on the cut-over day data > 10 GB or more than 500 files in OneDrive, might end up with an INCOMPLETE set of data in the target. Therefore, you should urge using the OneDrive Cross-tenant OneDrive Migration tool from Microsoft. The user will than see data being migrated (missing data) upon he starts working in the target environment. This will not be happening with the cross-tenant migration tool. The switch to the target tenant will take approx. 15min. Migration of Teams personal Chat messages, we mostly limit to 15 days. The performance is acceptable migrating approx. 400 – 800 users/day. Note: You should have special procedures in place for legal-hold users, white glove and user object facing issues. Prepare source and target tenant and ensure the readiness for Microsoft...