SQL Server Database Migration to Azure VM — Current Supported SQL Server Version

IT Partner migrates SQL databases from an existing SQL Server to SQL Server running in an Azure virtual machine on the current supported version of SQL Server. The service includes a full database backup to an on-premises location, creation of an Azure VM with the current supported version of SQL Server, connectivity setup, copying files to the VM, deployment finalization, verification, and issue fixing if needed.

This service migrates SQL databases to SQL Server in an Azure VM running the current supported version of SQL Server. SQL Server version targets other than the current supported version of SQL Server should be confirmed separately with IT Partner.

The success criterion is that the SQL databases are available from Azure without data loss. IT Partner verifies the deployment and fixes issues if any are found during the engagement.

The listed service duration is 1 week. The actual schedule depends on environment readiness, database sizes, connectivity, and any issues discovered during verification.

The service is priced at a fixed $450 per project, quoted in writing before work begins — you pay after you approve delivery. Work outside the defined scope — such as other SQL Server version targets, training, or more extensive documentation — is quoted separately.

The engagement starts with a kickoff meeting, followed by a review of SQL Server and Windows Server before deployment. IT Partner then starts and finalizes the deployment, verifies the migration, and fixes issues if any are found.

This service does not include SQL Server version targets other than the current supported version of SQL Server, customer team training, or documentation beyond the project closeout report. More extensive documentation may be available for an additional fee.

Yes — for large data transfers IT Partner will help arrange shipment of hard drives through the Azure Import/Export Service when uploading over the network is prohibitively expensive or not feasible. There is no fixed size threshold; the best transfer method is confirmed with IT Partner during planning based on your data volume and bandwidth.

The customer must provide a dedicated point of contact to work with IT Partner and coordinate outside vendor resources and schedules. The customer is also responsible for configuring networking equipment such as load balancers, routers, firewalls, and switches, and for providing access to physical or virtual servers, systems, services, facilities, and remote access as needed.

Yes. Key prerequisites include an active Azure subscription with permissions for IT Partner to create the target VM and related resources, confirmed SQL Server and Windows Server licensing for the target VM, an agreed VM size, region, and storage layout, administrative access to the source and target environments, sufficient temporary storage for backup files, approved network connectivity, an agreed migration and cutover window, and current backups. The full list is published in the Prerequisites section of this page.

Yes, IT Partner sets up connectivity and connects to SQL Server over the Internet or in the same virtual network. The customer remains responsible for configuring networking equipment such as load balancers, routers, firewalls, and switches.

The implementation plan includes a verification step and fixing issues if any are found during the engagement. Any outstanding issues at closeout are documented in the project closeout report along with final project status and acceptance evidence.