Updated November 13, 2023
Plan and Execute Your Microsoft 365 Tenant-to-Tenant Migration Safely and Seamlessly If your organization operates in a Microsoft 365 tenant and is facing a merger, acquisition, or divestiture, chances are you will need to execute a tenant-to-tenant migration. This type of migration includes combining or separating your email content, Enterprise documents in Sharepoint Online and Teams, user’s personal OneDrive content, domains, and more. This endeavor can seem overwhelming, but with a plan and an experienced technology partner, handling all the workloads involved in the migration can be a smooth and educational process for your organization. This article aims to simplify the challenges and considerations of Microsoft 365 tenant migrations.
Identity Management's Role in a Tenant Migration
Before starting your migration, it is crucial to consider Identity and Security workloads and their respective change management processes as part of the overall migration plan. To achieve migration success, it is strongly encouraged to work with an experienced technology partner who understands the potential hurdles caused by changes in these workloads.
In a cloud environment, the user identity is not only the key to the old and new environments but also the security perimeter of both environments in a migration. Proper Identity management during the transition of a migration ensures your users, content, and organization remain secure on all fronts. Microsoft 365 relies on Entra ID (formerly Azure Active Directory) as the Identity Provider (IDP) for user authentication, authorization, and access control. Properly managing Identity changes from source to target environments ensures that users retain access to their resources, email, and collaborative tools with little to no disruption.
What's Involved in a Microsoft Tenant Migration?
Microsoft 365 covers a broad set of applications and features that users depend on daily to execute their work. Doing the work upfront to plan, understand, and communicate the changes during and after a migration is time well spent. Below is a high-level list of areas to consider and plan for in a Microsoft 365 tenant-to-tenant migration:
Identity and Security (Entra ID)
User objects and potential changes need to be planned and communicated clearly. For example, user logins might change from jsmith@ to john.smith@.
Should users be allowed to access the old environment after migration, and if so, how can that be secured and limited?
Security policies and configurations may need to be updated with the new identities being migrated or removed.
The Initial “net new” user onboarding or offboarding process needs to be well-defined and communicated.
Account for new user experience if their login credentials or process changes on their corporate or BYOD devices.
Account for any external (guest) access scenarios that need to be implemented or removed.
Exchange Online migration requires accounting for all mailbox types, distribution groups, mail-enabled security groups, Office 365 groups, mail routing, and more.
Understand any changes to mail flow that could impact email delivery post-migration.
Ensure the new environment is properly secured for email content and access.
Considerations for calendar migrations, contacts, etc.
Cloud Environment
Plan for merging or separation of cloud infrastructure and applications.
Single Sign-on (SSO) for integrated apps including security and limited or expanded access.
Native app access and proper licensing for new users or removal of licensing for existing users.
Site collection migrations including Teams enable O365 Groups.
Member and guest access and permission propagation post-migration.
Teams and Office 365 group content, group and personal chat and channel moves.
Member and guest access and permission propagation post-migration.
One-to-one chat migration (stored in Exchange Online).
OneDrive For Business
OneDrive content migration
Considerations for Known Folder Move per user per device.
Proper access and permissions or removal of the same
Azure
Azure subscription migration.
Resource moves for Virtual Servers (SQL, App Servers, etc.) and Virtual Networks.
Windows 365 and Azure VM considerations.
To learn other best practices for successful Microsoft 365 migrations and mergers, click here.
Change Management for a Successful Tenant Migration
Change management is the linchpin for a successful Microsoft 365 tenant-to-tenant migration.
This type of project can bring about substantial shifts in the way organizations operate, impacting workflows, collaboration, and access to resources. Effective change management ensures that these transitions are met with smooth and organized planning and communication allowing easier adaptation by the workforce. Working with an experienced technology partner for Change Management through a project promotes clear and proactive transitions to facilitate positive adjustment from the organization. By proactively managing this change, end users are more likely to see better returns and engagement maximizing the investment of time and effort in the migration.
A Tenant Migration with JourneyTEAM
JourneyTEAM is a Microsoft technology partner with a proven track record of helping migrate over 10,000 Microsoft 365 accounts. This covers different-sized organizations and projects with varying levels of complexity.
JourneyTEAM offers support plans that cover all the assistance you may require as you plan and execute your Microsoft 365 tenant-to-tenant migration. We start with a checklist of discovery activities to properly analyze and scope the areas of your tenant migration. From there, we will collaboratively discuss the findings of our analysis to put a proper plan in place that addresses the foundational identity management needs to bring the two tenants together. To speak with a Microsoft 365 Migration specialist, contact us.