First page of Microsoft's 100,000-partner directory, sorted by responsiveness All 6 Microsoft Solutions Partner designations Microsoft Solutions Partner since 2006 1,100+ organizations under management
Home/Services/SQL Server Database Migration to SQL Server in Azure VM (with Server Upgrade)
Migration

SQL Server Migration to Azure VM — Upgrade & Move Databases

IT Partner migrates SQL databases from your own SQL Server to SQL Server running in an Azure virtual machine and upgrades SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, or SQL Server 2014 to the current supported version of SQL Server. This service requires downtime, and IT Partner will try to minimize it. The project is successful when the SQL databases are available from Azure without data loss.

Timeline 1 weekService owner Mike MackeyMicrosoft Azure

What this engagement is

IT Partner will migrate SQL databases to an Azure VM and upgrade SQL Server as described in the source scope. The source states that SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, or SQL Server 2014 can be upgraded to the current supported version of SQL Server. The work includes preparing the databases, creating a virtual machine with the current supported version of SQL Server, setting up connectivity, copying files to the VM, and configuring the new SQL Server installation. Service details: SKU ITPWW280MIGOT; price $150 per hour; duration 1 week; manager Mike Mackey.

Success criteria

01SQL databases are available from Azure without data loss.

What you receive

SQL databases migrated to Azure VM.
SQL Server upgraded to the current supported version of SQL Server.
New SQL Server installation configured.
Project closeout report indicating the final project status, including evidence of meeting acceptance criteria, any outstanding issues, and the final budget.

How the work unfolds

Kickoff meeting

Kickoff meeting.

Review SQL Server and Windows Server

Review SQL Server and Windows Server.

Start deployment

Start deployment.

Finalize deployment

Finalize deployment.

Verify and fix issues, if any

Verify and fix issues, if any.

Prerequisites

An active Azure subscription with permission to create and configure virtual machines, storage, networking, and related Azure resources.
Administrative access to the source Windows Server and SQL Server environment, including rights to perform backups, run DBCC checks, review SQL Server configuration, and stop or start required services during the maintenance window.
Source SQL Server version must be within the service scope: SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, or SQL Server 2014, with the target as the current supported version of SQL Server confirmed before implementation.
Current inventory of databases to be migrated, including database names, approximate sizes, recovery models, SQL Server instance names, logins, linked servers, SQL Agent jobs, and application dependencies where applicable.
Confirmed maintenance window and business approval for the downtime required to perform final backup, restore, upgrade, validation, and cutover activities.
Sufficient network connectivity between the source environment and Azure, or another approved secure method to transfer backup files to the Azure VM.
Adequate temporary and permanent storage capacity for SQL Server backups, database files, transaction logs, TempDB, and any intermediate migration files.
Required SQL Server installation media, licensing approach, product keys, Azure Marketplace image selection, or other entitlement details must be available or confirmed before deployment.
Application owners or technical contacts must be available to validate application connectivity and functional behavior after the databases are restored in Azure.
A rollback decision point should be agreed before cutover, including who can authorize rollback if validation fails.

Who does what

IT Partner

  • Back up all SQL Server database files from the server to be upgraded so you can restore them, if required
  • Run the appropriate Database Console Commands (DBCC) on databases to be upgraded to ensure that they are in a consistent state
  • Disable all startup stored procedures, as the upgrade process will stop and start services on the SQL Server being upgraded.
  • Perform a full database backup to an on-premises location
  • Create a virtual machine with the current supported version of SQL Server
  • Set up connectivity
  • Connect to SQL Server over the Internet or in the same virtual network
  • Copy file(s) to VM
  • Configure your new SQL Server installation

Your team

  • Provide Azure subscription access and required approvals for resource creation, estimated Azure consumption, and network/security configuration changes.
  • Provide administrative credentials or approved delegated access to the source SQL Server, Windows Server, and any required backup or file-transfer locations.
  • Identify the databases, applications, users, and dependencies that are in scope for migration.
  • Provide or confirm SQL Server licensing, Azure Marketplace image selection, or other licensing approach for the target SQL Server VM.
  • Approve the maintenance window and communicate expected downtime to application owners and users.
  • Ensure application owners or business testers are available for post-migration validation.
  • Provide firewall, VPN, DNS, or network-change approvals if required to connect applications or users to the Azure SQL Server VM.
  • Confirm acceptance of the migrated databases after validation, or identify issues for remediation within the agreed engagement scope.

What's not included

More extensive documentation than the project closeout report can be provided for an additional fee.
Application code changes, application remediation, or changes required for application compatibility with the upgraded SQL Server version are not included unless separately scoped.
SQL query tuning, index redesign, performance optimization, capacity modeling, or workload re-architecture beyond standard migration validation is not included unless separately scoped.
High availability, disaster recovery, SQL Server clustering, Always On availability groups, log shipping, replication, or multi-region architecture is not included unless separately scoped.
Ongoing SQL Server administration, monitoring, patching, managed services, backup operations, or Azure cost management after project closeout is not included unless separately contracted.
Complex network architecture such as ExpressRoute, site-to-site VPN deployment, hub-and-spoke redesign, private DNS redesign, or enterprise firewall implementation is not included unless separately scoped.
Migration of non-database application servers, reporting platforms, ETL tools, third-party integrations, or other infrastructure components is not included unless explicitly added to the scope.
Data cleansing, schema redesign, consolidation of databases, modernization to Azure SQL Database or Azure SQL Managed Instance, or conversion from non-SQL Server platforms is not included.
Remediation of existing database corruption, unsupported SQL Server features, missing backups, insufficient storage, or source-environment health issues may require additional work.

Limitations & technical notes

!This service requires some downtime. IT Partner will try to minimize it.
!Stored procedures processed at startup time might interfere with the upgrade process.
!The plan may vary depending on your needs.
!The upgrade target is the current supported version of SQL Server. Implementation details should be confirmed before work begins.
!Migration duration and downtime depend on database size, backup and restore speed, network throughput, source server condition, and the number of databases and dependencies in scope.
!Compatibility issues may appear after upgrading from older SQL Server versions. Application validation by the client or application owner is required to confirm business functionality.
!Azure VM performance depends on selected VM size, disk type, disk layout, storage throughput, network configuration, and SQL Server configuration.
!The service is intended for database migration to SQL Server running in an Azure VM; migration to Azure SQL Database, Azure SQL Managed Instance, or a broader data-platform modernization is a different scope.
!If source databases are very large, have high transaction rates, or require near-zero downtime, additional migration tooling or a separately scoped approach may be required.

Frequently asked questions

What does IT Partner’s SQL Server Database Migration to SQL Server in Azure VM service include?

IT Partner migrates SQL databases from your existing SQL Server to SQL Server running in an Azure virtual machine and upgrades supported source versions to the current supported version of SQL Server. The service includes preparing the databases, creating the Azure VM with the current supported version of SQL Server, setting up connectivity, copying files to the VM, configuring the new SQL Server installation, and verifying the deployment.

Which SQL Server versions can be upgraded as part of this service?

The stated scope covers upgrades from SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, or SQL Server 2014 to the current supported version of SQL Server. Confirm implementation details with IT Partner before purchasing.

What is the success criterion for the migration?

The project is successful when the SQL databases are available from Azure without data loss. IT Partner also provides a project closeout report showing final project status, evidence of meeting acceptance criteria, any outstanding issues, and the final budget.

How long does the SQL Server migration to an Azure VM take?

The listed duration for this service is 1 week. The actual plan may vary depending on your needs, because the engagement includes review, deployment, finalization, and issue verification activities.

How is this SQL Server migration service priced?

This service is priced at $150 per hour. The service details list SKU ITPWW280MIGOT, and the final budget is included in the project closeout report.

Will there be downtime during the SQL Server migration and upgrade?

Yes, this service requires some downtime because SQL Server services may be stopped and started during the upgrade and cutover process. IT Partner will try to minimize downtime, but the service content does not state a guaranteed downtime window.

What happens during the engagement?

The engagement follows milestones for kickoff, review of SQL Server and Windows Server, deployment start, deployment finalization, and verification with fixes if needed. In practical terms, IT Partner backs up and checks the databases, creates the Azure VM, sets up connectivity, copies files, configures SQL Server, and verifies that the databases are available from Azure.

What database preparation does IT Partner perform before the upgrade?

IT Partner backs up all SQL Server database files from the server to be upgraded so they can be restored if required. IT Partner also runs the appropriate Database Console Commands, or DBCC, on databases to be upgraded to confirm they are in a consistent state before proceeding.

Does IT Partner create the Azure virtual machine for SQL Server?

Yes, IT Partner creates a virtual machine with the current supported version of SQL Server as part of the stated service scope. IT Partner also configures the new SQL Server installation and sets up connectivity for access to SQL Server.

How does connectivity to the new SQL Server in Azure work?

The service includes setting up connectivity and connecting to SQL Server over the Internet or in the same virtual network. The source does not specify exact network design, firewall, VPN, private connectivity, or access requirements, so those details should be confirmed with IT Partner for your environment.

What responsibilities does IT Partner handle during the migration?

IT Partner handles database backups, DBCC consistency checks, disabling startup stored procedures, performing a full database backup to an on-premises location, creating the Azure VM, setting up connectivity, copying files to the VM, and configuring the new SQL Server installation. IT Partner also verifies the deployment and fixes issues if any are found within the engagement scope.

What responsibilities does the client have?

The service description does not list specific client responsibilities. In practice, details such as required access, Azure subscription availability, maintenance windows, and approvals should be confirmed with IT Partner because they are not specified in the published scope.

Are there prerequisites for this SQL Server migration service?

No formal prerequisites are listed in the service description beyond the supported SQL Server source versions in scope. Requirements such as permissions, Azure subscription readiness, network access, source server health, and maintenance-window planning are not specified, so they should be clarified with IT Partner before the engagement begins.

Why are startup stored procedures disabled during the upgrade?

IT Partner disables startup stored procedures because stored procedures processed at startup time might interfere with the upgrade process. This matters because the upgrade process can stop and start SQL Server services.

Does the service include a full backup before migration?

Yes, the service includes backing up SQL Server database files from the server being upgraded and performing a full database backup to an on-premises location. This is done so the databases can be restored if required and to support a controlled migration process.

Does this service guarantee no data loss?

The acceptance criterion is that SQL databases are available from Azure without data loss. IT Partner’s preparation steps include backups and DBCC consistency checks, but any environment-specific risk, rollback plan, or validation approach should be reviewed with IT Partner before the migration.

What documentation is delivered after the project?

IT Partner provides a project closeout report that states the final project status, evidence of meeting acceptance criteria, any outstanding issues, and the final budget. More extensive documentation than the project closeout report is not included and can be provided for an additional fee.

What is not included in this SQL Server migration service?

More extensive documentation than the project closeout report is not included in the base service and can be provided for an additional fee. The published scope also does not specify items such as application remediation, detailed network architecture, high availability design, performance tuning, or post-migration managed services, so those should be confirmed separately if needed.

Who manages this SQL Server migration service?

The listed manager for this service is Mike Mackey. The service details identify the offering as SKU ITPWW280MIGOT.

Can the migration plan be customized for my environment?

The plan may vary depending on your needs, according to the service notes. However, any changes should stay within the agreed scope, because the stated service is specifically for migrating SQL databases to SQL Server in an Azure VM and upgrading the supported SQL Server versions described in the service.

Didn’t find your question?

Ask it here. A real engineer answers by email within one business day — and if it’s a good one, it becomes part of this page so the next person finds it.

Answered by a person, one time, to your inbox. Nothing you type here is published without a human reviewing and anonymizing it first.

$150 per hour
1 week
Book a meeting