Azure Data Migration — Tenant-to-Tenant Resource Transfer

Azure Data Migration (SKU ITPWW440MIGOT) is an IT Partner service for moving data and listed Azure resources from one Azure tenant to another. It is typically used for tenant-to-tenant migration during mergers, acquisitions, or moves to a different geographic region.

The service page states that IT Partner can transfer virtual machines, databases, applications, and websites according to an approved migration plan. Each resource is assessed individually because Azure resources can have different workflow roles, downtime requirements, load, size, transfer features, and configuration needs.

The service content says the service allows migration of Entra ID data and includes consultation on technical issues related to Entra ID. However, the same source also lists migration of other Azure data, such as Entra ID, as not included and available as an additional service, so the exact Entra ID migration scope should be confirmed with IT Partner before purchase.

Deliverables include a migration plan with a resource list, transfer features, and planned time costs; migration of data and resources according to that plan; consultation on Entra ID technical issues; and a project closeout report. The closeout report indicates final project status, acceptance criteria matching, outstanding issues, and final budget.

The source page lists the service duration as 20 days. The actual migration plan may vary depending on the client’s needs and the complexity of the Azure resources being moved.

The listed price for Azure Data Migration is $175 per hour. Because the engagement includes analysis and a migration plan with planned time costs, the final budget should be confirmed based on the approved scope and any additional services required.

You need administrative access to the source Azure tenant and administrative access to the destination tenant. The destination tenant should also have licenses similar to the source tenant, or you should be ready to purchase the required licenses.

The engagement starts with a kickoff meeting and client-provided access to the source tenant. IT Partner then analyzes source tenant data, prepares and coordinates the migration plan, performs the migration according to the approved plan, and verifies the result while fixing identified issues.

IT Partner analyzes each resource’s role in the workflow, downtime requirements, load, size, transfer features, and configuration needs before migration. Based on that analysis, IT Partner prepares a migration plan intended to minimize negative effects on employees and other services, but the service content does not guarantee zero downtime.

Downtime requirements are assessed as part of the source tenant and resource analysis. The service aims to plan the migration to minimize negative impact, but exact downtime depends on the resources, dependencies, size, load, and configuration needs and should be confirmed in the migration plan.

The migration plan includes a list of resources, transfer features, and planned time costs for the transfer. It is prepared after IT Partner analyzes the source tenant and is coordinated with the client before data migration begins.

IT Partner is responsible for analyzing the source tenant and hosted resources, preparing the migration plan, transferring data and resources according to that plan, and consulting on Entra ID technical issues. IT Partner also provides the project closeout report at the end of the engagement.

The client must coordinate internal resources and staff schedules, provide a dedicated point of contact, coordinate outside vendors if needed, and provide administrative access to the source and destination tenants. The client also provides required access data, approves and helps refine the migration plan, handles workstation setup or third-party/specific software configuration if necessary, and reviews deliverables in a timely manner.

The service excludes resource sharing setup between the source and destination tenants, workstation setup, and more extensive documentation beyond the project closeout report unless purchased separately. The source also lists migration of other data from Azure, such as Entra ID, as an additional cost item, so that scope should be clarified with IT Partner.

Third-party application configuration is listed as a client responsibility if necessary. The service notes that external applications using Azure resources but not hosted in Azure will need to be reconfigured to use the new data, so those dependencies should be identified during planning.

Workstation setup is not included in the standard Azure Data Migration service. If workstation setup is required, it is identified as a client responsibility unless separately arranged with IT Partner.

The stated success criteria are that the migration plan is provided and confirmed by the client, and that data and resources are migrated according to the migration plan. Final status, acceptance criteria matching, outstanding issues, and final budget are documented in the project closeout report.

After the migration work, IT Partner performs verification and fixes identified issues within the engagement process. The service concludes with a project closeout report showing final project status, acceptance criteria matching, outstanding issues, and the final budget.

Yes, the plan may vary depending on client needs and the findings from the source tenant analysis. The client is responsible for approving the migration plan and participating in improvements if the initial version does not suit the client.

The source page lists Roman Sotnik as the manager for Azure Data Migration. Prospective buyers should confirm current scheduling, scope, and availability with IT Partner before starting the engagement.