Microsoft 365 Group Mailbox Tenant-to-Tenant Migration
This service migrates Microsoft 365 Groups with mailboxes from one Microsoft 365 tenant to another. It is for organizations that need to move collaborative group workspaces and their associated mailbox data during scenarios such as company mergers, acquisitions, or tenant consolidations.
What this engagement is
Microsoft 365 Groups provide shared collaboration resources such as a collective Outlook inbox, shared calendar, and document library, with permissions assigned automatically when members are added. This service covers the tenant-to-tenant migration of Microsoft 365 Groups with mailboxes, moving the collaborative workspace and associated mailbox from a source Microsoft 365 tenant to a target Microsoft 365 tenant. Service details: SKU ITPWW560MIGOT; price $35 per mailbox; duration 5 days; manager Roman Sotnik.
Success criteria
What you receive
How the work unfolds
Kickoff meeting.
Pre-migration source system health check.
Creating Microsoft 365 Groups.
Groups Mailboxes migration start.
Verification of groups migration.
Changing MX record to new Microsoft 365 tenant.
Final group migration.
Post-migration tasks.
Prerequisites
Who does what
IT Partner
- Plan and prepare for the migration by assessing the environment and setting up the target tenant.
- Configure the source and target environments for migration, including setting up the necessary permissions and creating a migration batch.
- Detailed Inventory. Create a detailed inventory of all the Microsoft 365 groups that includes their names, sizes, permissions, and any specific configurations.
- Monitor the progress of the migration.
- Verify that all data has been successfully migrated and perform any necessary post-migration tasks.
- Minimize user intervention during the migration process.
Your team
- Provide a dedicated point of contact responsible for working with IT Partner.
- Coordinate any outside vendor resources and schedules.
Frequently asked questions
What does the Microsoft 365 Group with Mailbox Tenant-to-Tenant Migration service do?
This service migrates Microsoft 365 Groups with mailboxes from one Microsoft 365 tenant to another. It is designed for organizations moving collaborative group workspaces and associated mailbox data during mergers, acquisitions, or tenant consolidations.
What is included in this Microsoft 365 Groups migration service?
The service includes migration planning, environment assessment, target tenant preparation, source and target configuration, permissions setup, migration batch creation, migration monitoring, verification, and post-migration tasks. IT Partner also creates the Microsoft 365 Groups in the target tenant, starts the group mailbox migration, changes the MX record to the new Microsoft 365 tenant, and completes the final group migration.
What Microsoft 365 Group data is migrated as part of the service?
The stated success criteria are to migrate mailbox data and configurations accurately and without loss, including emails, folders, rules, and permissions. IT Partner also prepares a detailed inventory of Microsoft 365 Groups, including names, sizes, permissions, and specific configurations.
Does this service migrate the full Microsoft 365 Group workspace, including document libraries?
The source description describes Microsoft 365 Groups as collaborative workspaces with resources such as a shared inbox, shared calendar, and document library, and it also emphasizes the associated mailbox and mailbox data. The exact handling of document libraries and any other group-connected resources should be confirmed with IT Partner during scoping.
How long does the Microsoft 365 Group mailbox migration service take?
The listed duration for this service is 5 days. The actual schedule should be confirmed with IT Partner because timing can depend on the number and size of groups, tenant readiness, DNS coordination, and dependencies on the broader tenant-to-tenant mailbox migration project.
How is this service priced?
The listed price is $35 per mailbox for SKU ITPWW560MIGOT. Prospective buyers should confirm the final count of group mailboxes and any project-specific assumptions with IT Partner before purchase.
What are the prerequisites for this service?
The stated prerequisite is a tenant-to-tenant mailbox migration project from IT Partner. This means the Microsoft 365 Group mailbox migration is intended to be performed as part of, or alongside, an IT Partner tenant-to-tenant mailbox migration engagement.
What happens during the migration engagement?
The engagement follows milestones that include a kickoff meeting, pre-migration source system health check, creation of Microsoft 365 Groups, start of group mailbox migration, verification of group migration, MX record change to the new Microsoft 365 tenant, final group migration, and post-migration tasks. This sequence is designed to prepare both tenants, migrate the group mailboxes, validate the result, and complete cutover activities.
Will users need to perform manual steps during the migration?
The service is designed to minimize user intervention during the migration process. IT Partner handles planning, configuration, migration monitoring, verification, and post-migration tasks, while the client provides coordination and a dedicated point of contact.
How does IT Partner reduce business disruption during the migration?
One of the success criteria is that the migration causes as little disruption as possible. IT Partner supports this by planning the migration, preparing the target tenant, monitoring progress, verifying migrated data, and coordinating the final migration and MX record change.
Is there expected downtime during the Microsoft 365 Group mailbox migration?
The service states that the migration process is intended to cause as little disruption as possible, but it does not provide a specific downtime window or guarantee zero downtime. Any expected business impact should be confirmed with IT Partner based on the migration schedule, mail flow cutover, and tenant-specific conditions.
How is mail flow handled during cutover?
The service includes changing the MX record to the new Microsoft 365 tenant as part of the migration plan. Because MX changes affect where new inbound email is delivered, the exact timing and coordination of mail flow cutover should be planned with IT Partner and the client’s DNS or domain administrators.
Who is responsible for preparing the source and target Microsoft 365 tenants?
IT Partner is responsible for assessing the environment, setting up the target tenant, configuring the source and target environments, setting necessary permissions, and creating the migration batch. The client is responsible for providing a dedicated point of contact and coordinating any outside vendor resources and schedules.
What information does IT Partner collect before migrating the groups?
IT Partner creates a detailed inventory of the Microsoft 365 Groups to be migrated. The inventory includes group names, sizes, permissions, and any specific configurations, which helps plan and validate the migration.
How does IT Partner verify that the migration completed successfully?
The service includes verification that all data has been successfully migrated and completion of necessary post-migration tasks. The success criteria specify that mailbox data and configurations, including emails, folders, rules, and permissions, should be migrated accurately and without loss.
What are the client’s responsibilities during the service?
The client must provide a dedicated point of contact to work with IT Partner throughout the engagement. The client is also responsible for coordinating outside vendor resources and schedules, such as DNS hosting providers or other parties needed for cutover activities.
What happens after the group mailbox migration is completed?
After migration, IT Partner verifies the group migration and performs necessary post-migration tasks. The engagement also includes final group migration activities after the MX record change to the new Microsoft 365 tenant.
Are any items explicitly excluded from this service?
The provided source service description does not list specific out-of-scope or additional-cost items. Customers should confirm with IT Partner whether connected workloads, special requirements, or related migration activities are included before starting.
Who manages this service at IT Partner?
The service page lists Roman Sotnik as the manager for the Microsoft 365 Group with Mailbox Tenant-to-Tenant Migration service. Customers should use the normal IT Partner engagement process to confirm scheduling, scope, and project details.