Shared Mailbox Tenant-to-Tenant Migration — Microsoft 365 Mailbox Transfer
The Shared Mailbox Tenant-to-Tenant Migration service helps organizations transfer shared mailboxes from one Microsoft 365 tenant to another, typically during mergers, acquisitions, divestitures, consolidation, or separation of Microsoft 365 environments. IT Partner plans, prepares, configures, inventories, monitors, verifies, and performs post-migration tasks for shared mailbox migration, including emails, calendar items, contacts, associated data, related permissions, configurations, and settings. SKU: ITPWW570MIGOT. Price: $35 per mailbox. Duration: 5 days. Manager: Roman Sotnik.
What this engagement is
Shared mailboxes are used when multiple people need access to a common mailbox, such as company information inquiries, customer support, reception desks, or other shared functions. Users with access can send email directly from the shared mailbox or send messages on behalf of the mailbox address. This service supports the migration of shared mailboxes from one Microsoft 365 tenant to another, including the mailbox data and related permissions, configurations, and settings. It is intended for organizations that need to consolidate or separate Microsoft 365 environments as part of mergers, acquisitions, divestitures, or other significant organizational changes. Service details: SKU ITPWW570MIGOT; price $35 per mailbox; duration 5 days; manager Roman Sotnik.
Success criteria
What you receive
How the work unfolds
Confirm the shared mailbox migration scope, source and destination tenant details, mailbox counts, project contacts, access requirements, schedule, communications approach, and validation responsibilities. Review dependencies on the broader tenant-to-tenant mailbox migration project.
Review the source Microsoft 365 tenant readiness, shared mailbox inventory, mailbox sizes, permissions, delegation settings, send-as/send-on-behalf requirements, migration access, and any known Exchange Online issues that could affect migration.
Create or prepare the required shared mailboxes in the target tenant using the agreed naming, alias, and configuration approach. Align target objects with the migration plan and confirm that required permissions can be applied.
Configure the migration batch or migration tooling, start the shared mailbox data synchronization, and monitor initial progress for connectivity, throughput, authentication, and item-level errors.
Validate migrated mailbox content and representative mailbox functionality in the destination tenant, including folders, recent and historical mail, calendar items, contacts, and assigned access permissions where applicable.
Perform the final synchronization or cutover step after the initial migration is complete, confirm any remaining delta items are transferred, and align final timing with the tenant-to-tenant migration schedule.
Complete final validation, review migration results with the client, address migration exceptions within the agreed scope, confirm shared mailbox access from supported clients, and provide status information for project closure.
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 shared mailboxes 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.
- Provide temporary access to the existing environment/IT Infrastructure.
What's not included
Limitations & technical notes
Frequently asked questions
What is the Shared Mailbox Tenant-to-Tenant Migration service?
The Shared Mailbox Tenant-to-Tenant Migration service transfers shared mailboxes from one Microsoft 365 tenant to another. It is typically used during mergers, acquisitions, divestitures, tenant consolidation, or separation of Microsoft 365 environments.
What types of mailbox data are included in the shared mailbox migration?
The service includes migration of shared mailbox data such as email, calendar items, contacts, associated data, related permissions, configurations, and settings. IT Partner also verifies that the mailbox data has been successfully migrated to the destination tenant.
Does this service include migration of user mailboxes?
This service is specifically for shared mailboxes. The stated prerequisite is a tenant-to-tenant mailbox migration project from IT Partner, so user mailbox migration should be discussed as part of that broader project rather than assumed to be included in this shared mailbox SKU.
How much does the Shared Mailbox Tenant-to-Tenant Migration service cost?
The service price is $35 per shared mailbox. The listed SKU is ITPWW570MIGOT, and pricing should be calculated based on the number of shared mailboxes included in the migration scope.
How long does the shared mailbox tenant-to-tenant migration take?
The stated service duration is 5 days. The exact schedule may depend on migration readiness, mailbox inventory, access availability, and coordination with the broader tenant-to-tenant mailbox migration project.
What is included in IT Partner’s shared mailbox migration work?
IT Partner plans and prepares the migration, assesses the environment, configures source and target tenants, creates the migration batch, inventories shared mailboxes, performs a pre-migration health check, creates shared mailboxes, starts and monitors migration, verifies migration results, performs final email migration, and completes post-migration tasks. The service is designed to minimize user intervention during the migration process.
What information is captured in the shared mailbox inventory?
The inventory includes the shared mailbox names, sizes, permissions, and any specific configurations. This inventory helps define what must be migrated and verified in the destination Microsoft 365 tenant.
What are the prerequisites for this service?
The stated prerequisite is a tenant-to-tenant mailbox migration project from IT Partner. This means the shared mailbox migration is intended to be performed as part of an existing or related Microsoft 365 tenant-to-tenant migration engagement.
What does IT Partner need from the client to perform the migration?
The client must provide a dedicated point of contact, coordinate any outside vendor resources and schedules, and provide temporary access to the existing environment and IT infrastructure. These inputs are required so IT Partner can assess, configure, migrate, monitor, and verify the shared mailbox migration.
Who is responsible for configuring the source and destination tenants?
IT Partner is responsible for configuring the source and target environments for migration, including required permissions and migration batch creation. The client is responsible for providing the access and coordination needed for IT Partner to complete that configuration.
What happens during the shared mailbox migration engagement?
The engagement includes a kickoff meeting, pre-migration source system health check, shared mailbox creation, migration start, migration verification, final email migration, and post-migration tasks. These steps are used to prepare the tenants, move mailbox data, confirm migration results, and complete follow-up tasks after migration.
Will users still be able to access shared mailboxes after migration?
A success criterion for the service is that users can access shared mailboxes from desktop PCs, mobile phones, and tablets from any place at any time. IT Partner verifies the migration so the data and settings from the source tenant are transferred to the destination tenant.
Does the service migrate shared mailbox permissions?
Yes, the service scope includes related permissions, configurations, and settings for shared mailboxes. IT Partner also inventories mailbox permissions before migration and verifies that data and settings have been successfully migrated.
Does the service include Send As or Send on Behalf shared mailbox scenarios?
The service overview recognizes that shared mailbox users may send email directly from the shared mailbox or send messages on behalf of the mailbox address. Because the service includes related permissions, configurations, and settings, these scenarios should be reviewed during inventory and validation, but exact handling should be confirmed with IT Partner for the specific tenant configuration.
How does IT Partner reduce business impact during the migration?
IT Partner plans the migration, performs a pre-migration health check, creates migration batches, monitors progress, verifies results, and performs post-migration tasks. The service also states that IT Partner works to minimize user intervention during the migration process.
Is mailbox downtime or mail flow impact specified for this service?
The service description does not specify a guaranteed downtime window or mail flow behavior during cutover. Organizations should confirm expected cutover timing, mail flow handling, and user communication requirements with IT Partner during the kickoff and planning stage.
What verification is performed after migration?
IT Partner performs verification of email migration and verifies that all data has been successfully migrated. The service success criteria include successful transfer of shared mailbox data and settings from the source tenant to the destination tenant.
What post-migration tasks are included?
The service includes post-migration tasks after final email migration and verification. The source material does not list each post-migration task in detail, so any required activities such as cleanup, access review, or user communication should be confirmed with IT Partner for the specific project.
What is not included in this service?
The provided service scope does not identify specific exclusions or additional-cost items. Because the service is narrowly defined around shared mailbox tenant-to-tenant migration, any work outside shared mailbox migration should be confirmed with IT Partner before the project begins.
Who manages this service at IT Partner?
The listed service manager is Roman Sotnik. The service SKU is ITPWW570MIGOT for Shared Mailbox Tenant-to-Tenant Migration.