Azure Data Migration — Tenant-to-Tenant Resource Transfer
Azure Data Migration moves data and agreed Azure resources — virtual machines, databases, applications, and websites — from one Azure tenant to another, typically after a merger or acquisition or for a move to a different geographic region. IT Partner analyzes each resource's role, downtime requirements, load, size, and configuration needs, prepares a migration plan for your approval, and transfers the resources according to that plan. The service is billed at $175 per hour, typically runs 20 days, and is managed by Roman Sotnik.
What this engagement is
This service supports migration from one Azure tenant to another. IT Partner transfers agreed resources such as virtual machines, databases, applications, and websites. There is no single mechanism for this in Azure: depending on the resource, the right method may be moving a subscription between directories, redeploying the resource in the destination tenant, or copying the data with Microsoft-supported transfer tooling — which is why the analysis comes first. Before migration, IT Partner analyzes the source tenant and hosted resources, including each resource's role in the workflow, downtime requirements, load, size, transfer characteristics, and configuration needs. Based on that analysis and your needs, IT Partner prepares a migration plan intended to minimize negative effects on employees and other services, then transfers data and resources according to the approved plan. Migration of Microsoft Entra ID directory data (users, groups, and identity objects) is a separate IT Partner service; this engagement includes consultation on Entra ID technical issues that affect the resource move.
Success criteria
What you receive
How the work unfolds
Confirm scope, stakeholders, the source and destination tenants, business drivers, downtime expectations, and the schedule.
The client grants administrative access to the source tenant and the resources in scope so analysis can begin.
Analyze each hosted resource: its role in the workflow, downtime requirements, load, size, transfer characteristics, and configuration needs in the destination tenant.
Prepare the migration plan with the resource list, transfer approach per resource, and planned time costs, and coordinate it with the client until approved.
Transfer data and resources to the destination tenant according to the approved plan, coordinating cutover windows where downtime is required.
Verify migrated resources in the destination tenant, fix migration-related issues, and document results in the closeout report.
Prerequisites
Who does what
IT Partner
- Data analysis of the source tenant and the resources hosted in it
- Preparation of a migration plan, including a list of resources, transfer features, and planned time costs for the transfer
- Transfer of data and resources according to the prepared plan
- Consultation on technical issues related to the work of Entra ID
Your team
- Coordinate Client resources and staff schedules
- Provide a dedicated point of contact responsible for working with IT Partner
- Coordinate any outside vendor resources and schedules
- Provide administrative access to source and destination tenants
- Provide the necessary data to access transferred resources
- Approve the provided migration plan and participate in its improvement, in case the initial version does not suit the client
- Workstation setup, if necessary
- Configure third-party applications, if necessary
- Configure specific or self-made software, if necessary
- Review and approve engagement deliverables in a timely manner
What's not included
Limitations & technical notes
Frequently asked questions
What is Azure Data Migration by IT Partner?
It is a service for moving data and agreed 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.
How is Azure Data Migration priced, and how long does it take?
The service is billed at $175 per hour, with the total effort scoped through the migration plan and its planned time costs, and typically runs 20 days. The rate and scope are confirmed in writing before work begins.
Which Azure resources can IT Partner transfer with this service?
Virtual machines, databases, applications, and websites, according to the approved migration plan. Each resource is assessed individually, because Azure resources differ in workflow role, downtime requirements, load, size, transfer method, and configuration needs in the destination tenant.
How does a tenant-to-tenant Azure migration actually work?
There is no single switch. Depending on the resource, the right method may be moving a subscription between directories, redeploying the resource in the destination tenant, or copying the data with Microsoft-supported transfer tooling. IT Partner's analysis determines the method per resource, and the migration plan documents it before anything moves.
Is Entra ID migration included in this Azure Data Migration service?
Directory data migration — users, groups, and identity objects — is not included; it is available as a separate IT Partner service (Entra ID tenant-to-tenant migration). What this engagement does include is consultation on Entra ID technical issues that affect the resource move, such as identity-dependent settings that must be re-created in the destination tenant.
What are the prerequisites for starting the migration?
Administrative access to the source Azure tenant and administrative access to the destination tenant, with licenses similar to the source tenant in place or ready to be purchased.
What is included in the migration plan?
A list of the resources in scope, the transfer approach and characteristics for each, and planned time costs for the transfer. The plan is prepared after IT Partner analyzes the source tenant and is coordinated with you until you approve it — data migration begins only after that approval.
Will there be downtime during the tenant-to-tenant migration?
Downtime requirements are assessed per resource during analysis, and the plan is built to minimize negative effects on employees and other services. Some resource types require a cutover window; the plan states where, and the windows are agreed with you in advance. The service does not promise zero downtime.
What responsibilities does the client have during the migration?
Coordinating internal staff and any outside vendors, providing a dedicated point of contact, granting administrative access to both tenants, providing access data for transferred resources, approving the migration plan, handling workstation setup and third-party or custom software configuration where needed, and reviewing deliverables in a timely manner.
Are third-party applications reconfigured as part of the migration?
Third-party application configuration is a client responsibility where necessary. External applications that use your Azure resources but are not hosted in Azure will need to be reconfigured to point at the migrated resources, so those dependencies are identified during planning.
How is migration success measured?
Two criteria: the migration plan is provided and confirmed by the client, and data and resources are migrated according to that plan. Final status, acceptance criteria matching, outstanding issues, and the final budget are documented in the project closeout report.
What happens after the migration is completed?
IT Partner verifies the migrated resources in the destination tenant, fixes migration-related issues identified during verification, and delivers the project closeout report. Follow-on work — such as directory data migration or resource sharing between tenants — can be scoped separately.