Tenant to Tenant In-Place Archive Migration — Office 365 Archive Transfer

IT Partner’s Tenant to tenant In-Place Archive Migration service helps move In-Place Archive mailbox data from one Office 365 tenant to another Office 365 tenant. The service is designed to preserve messages, folders, metadata, and folder hierarchy while minimizing user intervention during the migration.

This service migrates mailbox data stored in the Exchange Online In-Place Archive from the source Office 365 tenant to the target Office 365 tenant. The stated migration scope includes archive messages, folders, and metadata, with verification that the migrated data is accessible and usable in the target tenant.

This service is specifically scoped for Tenant to tenant In-Place Archive Migration. If primary mailbox migration, Teams data, OneDrive data, SharePoint data, or other Microsoft 365 workloads are required, those items should be confirmed separately with IT Partner because they are not listed in this service scope.

The actual migration schedule can depend on tenant readiness, licensing, mailbox/archive size, permissions, and completion of prerequisites such as target tenant setup and test migration.

The service includes migration planning and preparation, assessment of the environment, target tenant setup, source and target configuration, permission setup, migration batch creation, migration progress monitoring, migration verification, and necessary post-migration tasks such as DNS updates or client reconfiguration where required. It is designed to minimize user intervention during the migration process.

The engagement follows a structured process: kickoff meeting, user identification and environment mapping, target tenant setup, migration configuration, migration execution and monitoring, migration verification, and follow-up closure. This sequence helps ensure the source and target environments are ready before data is moved.

The target tenant must have a valid Office 365 subscription, the necessary user licenses, sufficient storage space, and properly synchronized user accounts and mailboxes. The source and target environments must be correctly configured with required permissions, relevant custom settings such as retention policies or transport rules should be set up in the target tenant, and a test migration and migration plan should be prepared.

Yes, the service is intended to migrate In-Place Archive data while maintaining metadata and folder hierarchy. IT Partner also verifies the migrated data after the migration to help confirm that messages, folders, and metadata were successfully transferred.

IT Partner reduces risk by planning the migration, preparing and configuring both tenants, setting permissions, creating migration batches, monitoring progress, and verifying the migrated data. The service success criteria state that all In-Place Archive data should be migrated without data loss or corruption and remain accessible in the target tenant.

The service is designed to have minimal impact on users in both the source and target tenants. The stated success criteria include users being able to access their email accounts and In-Place Archive data throughout the migration process, although any specific downtime or access constraints should be addressed in the migration plan.

This service focuses on migrating In-Place Archive data between Office 365 tenants, not on a full mail-flow migration project unless separately scoped. Any required DNS changes, client reconfiguration, or mail-flow considerations should be handled according to the migration plan and confirmed with IT Partner for the specific tenant scenario.

IT Partner is responsible for planning and preparing the migration, assessing the environment, setting up the target tenant, configuring source and target migration settings, granting or setting up required permissions, creating the migration batch, monitoring migration progress, verifying migrated data, and performing necessary post-migration tasks within scope. IT Partner also aims to minimize user intervention during the process.

The client must provide a dedicated point of contact, coordinate outside vendor resources, provide temporary access to the existing environment and IT infrastructure, configure network equipment if required, perform internal and external DNS changes as required, and communicate upcoming changes to users. These responsibilities matter because IT Partner needs timely access, coordination, and tenant/network readiness to complete the migration.

The service includes necessary post-migration tasks such as updating DNS records where required, but the client responsibility section states that the client performs internal and external DNS changes as required. In practice, IT Partner can guide or include DNS-related post-migration work within scope, while the client should be prepared to execute DNS changes in their own environment.

Yes, performing a test migration is listed as a prerequisite for this service. A test migration helps validate tenant configuration, permissions, and the migration process before the full In-Place Archive migration is executed.

After migration execution, IT Partner verifies that the In-Place Archive data has been successfully migrated to the target tenant. The service also includes necessary post-migration tasks, such as DNS updates or client device reconfiguration where required, followed by follow-up and closure conversations.

The service excludes items not specifically listed in the scope. For example, work outside In-Place Archive migration—such as broader Microsoft 365 workload migrations, unrelated tenant remediation, or custom projects—should be confirmed separately with IT Partner.