Windows Server Migration to Azure — Physical Server to Cloud Move

This service migrates a physical Windows Server workload to Microsoft Azure by assessing the existing server, preparing Azure migration infrastructure, creating and transferring a server image, enabling replication, completing the final server move, and validating the migrated workload in Azure. IT Partner also provides an assessment report with Azure estimates, post-migration verification, issue fixes if any, and a project closeout report.

The listed price for this service is $850, and the listed duration is 5 days. The plan may vary depending on the client’s environment and needs, so any changes to scope, timing, or cost should be confirmed with IT Partner before the engagement begins.

This service is designed for clients who need to move a physical Windows Server workload from on-premises hardware to Microsoft Azure. It is appropriate when the client can provide server access, required credentials, an Azure subscription with required resources, network connectivity between the physical server and Azure, and a Windows Server 2008 R2 or later server for the migration agent.

The engagement begins with a kickoff meeting, definition of what should be migrated, installation of an assessment server, and collection of statistics. IT Partner then provides an assessment report and Azure estimate, installs the migration agent, starts background migration, performs the final server move, and verifies the migrated server while fixing issues if any are found.

Yes, this service uses Azure Migrate to assess and migrate the physical Windows Server workload to Azure. The process includes preparing the assessment and migration server, enabling replication, selecting the source and target environments, and moving the workload into Azure.

The service deliverables include a new recovery vault, prepared infrastructure with protection goals selected for replication to Azure, a prepared Assessment and Migration Server, and replication enabled for the server. Deliverables also include the migration agent installation, background server migration, the final server move, post-migration verification, and a project closeout report.

The client must provide access to the physical server and necessary credentials, an Azure subscription with required resources provisioned, and network connectivity between the physical server and Azure. The client must also provide a Windows Server 2008 R2 or later server to be used as the migration agent.

The client is responsible for providing a dedicated point of contact, coordinating outside vendor resources and schedules, providing access to required systems and facilities, and supplying the Windows Server 2008 R2 or later migration agent server. The client is also responsible for configuring networking equipment such as load balancers, routers, firewalls, and switches, and for making required internal and external DNS changes.

IT Partner is responsible for creating the recovery vault, preparing the Azure replication infrastructure, preparing the Assessment and Migration Server, and providing the assessment report and Azure estimates. IT Partner also enables replication by selecting the source environment, target environment such as the storage account, destination virtual network, and the virtual machine with the mobility service installed.

No, network configuration is outside the scope of this project and is an additional cost item. The client is responsible for configuring networking equipment such as routers, firewalls, switches, and load balancers, as well as making DNS changes required for the migration.

DNS changes are not listed as an IT Partner deliverable for this service. The client is responsible for performing required internal and external DNS changes, including any changes needed to direct users or systems to the migrated Azure virtual machine.

The service includes background migration followed by a final server move, so business impact is typically concentrated around the final cutover rather than the entire replication period. The exact downtime is not specified in the service scope because it depends on the server, data size, application behavior, network connectivity, and cutover approach; clients should confirm the expected downtime with IT Partner during planning.

After migration, IT Partner tests the server in Azure for network connectivity, application performance, and data integrity. The service success criteria include migrated Azure virtual machines running in Azure and post-migration testing that validates those areas.

After the final server move, IT Partner verifies the migrated workload and fixes issues if any are identified within the stated project scope. IT Partner also provides a project closeout report showing final project status, evidence of meeting acceptance criteria, outstanding issues if any, and the final budget.

The service notes that provided virtual machines have replicated successfully, on-premises or virtual servers can then be decommissioned. Decommissioning should be coordinated carefully with the client’s operational, backup, compliance, and application owners because the service scope does not define a detailed decommissioning procedure.

No, this service is focused on migrating a physical Windows Server workload to Azure while preserving data, applications, and settings through imaging, replication, migration, and validation. Application redesign, modernization, or extensive re-architecture is not stated as part of the included scope and should be discussed separately if needed.

The included documentation is the project closeout report, which indicates final project status, evidence of meeting acceptance criteria, outstanding issues if any, and the final budget. More extensive documentation is not included and can be provided for an additional fee.

Connectivity depends on how the Azure environment is set up, including whether there is a site-to-site VPN or Azure ExpressRoute and whether the migrated virtual machine is placed in the virtual network associated with that connection. Because network configuration is outside the standard scope, clients should confirm connectivity requirements and any additional network work with IT Partner before migration.

Moving the physical Windows Server workload to Azure can help the client use Azure capabilities such as scaling resources up or down, pay-as-you-go pricing, security features including advanced threat protection and compliance support, and built-in redundancy and backup options for high availability and disaster recovery. These benefits depend on the Azure configuration and resources selected for the migrated workload.