Windows Server Migration to Azure — Physical Server to Cloud Move
This service migrates a physical Windows Server workload to Microsoft Azure using Azure Migrate: IT Partner assesses the existing server, prepares the migration infrastructure, replicates the server to Azure in the background, completes the final server move, and validates the migrated workload. The service is $850, runs 5 days, and is managed by Mike Mackey.
What this engagement is
IT Partner migrates a physical Windows Server workload to Microsoft Azure. The service starts with an assessment of the existing physical server environment, including the current setup, dependencies, and potential challenges. Based on that assessment, IT Partner develops a migration plan and uses Azure Migrate — Microsoft's supported path for physical server discovery, assessment, and migration — to assess and migrate the physical server: the server is replicated to Azure so that data, applications, and settings are preserved, migration runs in the background while the source stays in service, and a coordinated final move brings the workload up as an Azure virtual machine. After migration, IT Partner tests the server in Azure, including network connectivity, application behavior, and data integrity, and provides stabilization assistance for migration-related issues through project closeout. Moving from physical hardware to Azure lets the workload use Azure capabilities such as scaling resources up or down, pay-as-you-go pricing, platform security and compliance features, and built-in redundancy and backup options for high availability and disaster recovery.
Success criteria
What you receive
How the work unfolds
Confirm scope, stakeholders, the server and applications in scope, target Azure subscription and network, cutover window expectations, and required access.
Agree the workload boundary: the server, its applications, dependencies, and any components that will not move.
Deploy the Azure Migrate assessment tooling, discover the physical server, and gather utilization statistics to inform sizing.
Deliver the assessment findings with recommended Azure VM sizing and estimated Azure costs for client approval.
Install the required migration agent on the source physical server and prepare the replication infrastructure.
Enable replication and let the server synchronize to Azure while the source remains in service, monitoring replication health.
Complete final synchronization in the agreed window and bring the workload up as an Azure virtual machine.
Validate boot, access, connectivity, applications, and data; fix migration-related issues within scope; and deliver the closeout report.
Prerequisites
Who does what
IT Partner
- Create and prepare the Azure Migrate project and replication infrastructure required to replicate the physical server to Azure
- Prepare the assessment and migration tooling in the source environment
- Provide assessment report and Azure estimates
- Enable replication for the server, selecting the source environment, the target environment (such as the target subscription, storage, and destination virtual network), and installing the required migration agent on the source server
- Run the final server move and post-migration verification
Your team
- Provide a dedicated point of contact responsible for working with IT Partner and coordinate any outside vendor resources and schedules
- Configure all networking equipment, such as load balancers, routers, firewalls, and switches
- Provide access to physical and virtual servers and/or systems and services, as needed; provide remote and/or physical access to facility and systems required to complete the work
- Provide a supported Windows Server machine for the migration appliance or agent components, as confirmed during planning
- Perform changes to internal and external DNS, as required
What's not included
Limitations & technical notes
Frequently asked questions
What does the Windows Server Migration to Azure from a Physical Server service include?
IT Partner assesses the physical Windows Server, prepares the Azure Migrate project and replication infrastructure, provides an assessment report with Azure estimates, installs the migration agent, replicates the server to Azure in the background, performs the final server move, validates the migrated workload, and delivers a migration acceptance checklist and project closeout report.
What is the price and duration of this migration service?
The service is $850 and runs 5 days, quoted fixed-price in writing before work begins. Azure consumption charges and Microsoft licensing costs are billed by Microsoft separately.
Does IT Partner use Azure Migrate for the physical server migration?
Yes — this service works entirely in Azure Migrate, Microsoft's supported path for physical server discovery, assessment, and migration. The classic Azure Migrate experience is retired and no longer available.
Will there be downtime during the physical server migration to Azure?
Replication runs in the background while the source server stays in service, so business impact is concentrated in the final cutover window rather than the whole migration. The exact window depends on the server, data size, change rate, network throughput, and validation time, and is agreed during planning.
What prerequisites must be in place before the migration starts?
Access to the physical server with credentials, an Azure subscription with the required resources, network connectivity between the server and Azure, a supported Windows Server machine to host the migration appliance or agent components, target network and sizing decisions, and the required Azure permissions. IT Partner confirms the current appliance requirements against Microsoft documentation during planning.
What is the client responsible for during the migration?
Providing a dedicated point of contact, coordinating outside vendors, providing access to required systems and facilities, supplying the machine for the migration appliance or agent components, configuring networking equipment such as load balancers, routers, firewalls, and switches, and making required internal and external DNS changes.
Is network configuration included in this service?
No. Network configuration is outside the scope of this project and is an additional cost item. The client configures networking equipment and performs DNS changes; IT Partner advises on what the migrated VM needs.
How does IT Partner validate that the migrated server works in Azure?
IT Partner confirms the Azure VM boots and shows a healthy state, validates administrative access, tests network connectivity, application behavior, and data integrity, and supports application-owner smoke tests. Results are summarized in the migration acceptance checklist and closeout report.
Can the original physical server be decommissioned after migration?
Yes — once the workload has replicated successfully and passed validation in Azure, the physical server can be decommissioned. IT Partner recommends coordinating decommissioning with your operational, backup, and compliance owners; a detailed decommissioning procedure is not part of this scope.
Can the migrated Azure VM still reach on-premises resources?
That depends on your Azure network design — whether a site-to-site VPN or ExpressRoute exists and whether the VM was migrated into the virtual network associated with it. Because network configuration is outside this scope, connectivity requirements should be confirmed before migration.
Does this service include application modernization or ongoing support?
No. The service migrates the workload as-is, preserving data, applications, and settings. Application modernization, code changes, and OS remediation are excluded, and post-cutover support is limited to stabilization assistance for migration-related issues through project closeout; managed services require a separate agreement.
What deliverables and documentation do we receive?
An assessment report with Azure estimates, the migrated and validated Azure virtual machine, a migration acceptance checklist, and a project closeout report with final status, acceptance evidence, outstanding issues if any, and the final budget. More extensive documentation is available for an additional fee.