First page of Microsoft's 100,000-partner directory, sorted by responsiveness Microsoft Solutions Partner — Security, Modern Work, Infrastructure, App Innovation Microsoft partner since 2006 1,100+ organizations under management
Home/Services/Website or Web App Migration to Azure App Service
Migration

Website or Web App Migration to Azure App Service — Cloud Migration

This service migrates your website or web app from your current web server to Microsoft Azure App Service. IT Partner analyzes the web server installation with Microsoft's current App Service migration and assessment tooling, identifies which sites can move and which components are unsupported on the platform, migrates the applicable sites and databases, and validates that the web app works in Azure correctly and stably. The service is $450 per project, runs 1 day, and is managed by Mike Mackey.

Timeline 1 dayService owner Mike MackeyMicrosoft Azure

What this engagement is

IT Partner helps move your website or web app from your current web server to Azure App Service. Depending on your selected items, the migration may involve Azure App Service capabilities such as automatic scaling up and down to meet demand in busy times and reduce costs during quiet times; automatic site backups to protect changes and data; the high availability and resilience of the Azure PaaS platform; deployment slots for development and staging environments and staged go-lives; load balancing and DDoS protection; and traffic management to direct users to the closest geographic deployment. Because App Service is a managed platform, the assessment matters: OS and runtime support, connection strings and configuration values, custom-domain and TLS certificate cutover, and server-level components that App Service does not host are all reviewed before migration, and anything that cannot move is called out. The result is your website(s) running in the Azure cloud.

Success criteria

01Your web app/website works in Azure correctly and stably.

What you receive

Website(s) moved from the web server to Azure App Service.
Sites and databases migrated from a remote server to Azure, as applicable based on the selected migration items.
Migration summary at the end showing the sites migrated, indicating whether they were migrated successfully, and providing links to the newly created Azure web apps.
Project closeout report indicating the final project status, including evidence of meeting acceptance criteria, outstanding issues, if any, and the final budget.

How the work unfolds

Kickoff meeting

Confirm scope, the sites in scope, stakeholders, access to the source web server and Azure subscription, and the cutover approach.

Elaboration specification

Analyze the web server installation with Microsoft's current App Service migration and assessment tooling, identify migratable sites and unsupported elements, and agree the migration specification.

Start migration

Migrate the applicable sites and databases to Azure App Service according to the agreed specification.

Final deployment

Complete the deployment, configure the web apps, and coordinate the DNS and certificate cutover performed by the client.

Verify and fix issues, if any

Verify the migrated sites work correctly and stably in Azure, fix migration-related issues within scope, and deliver the migration summary and closeout report.

Prerequisites

Access to a Microsoft Azure subscription for the target deployment, with permissions to create and configure required Azure resources such as resource groups, App Service plans, web apps, storage, networking settings, and database resources if applicable.
Administrative access to the source web server environment, including required access to website files, web server configuration, application settings, certificates, scheduled tasks or services that affect the website, and related system information needed for migration assessment.
Access to application and database credentials required for migration, including database server connection details, connection strings, service accounts, and any secrets or configuration values required for the website to run after migration.
Current inventory of the website or web app, including site names, hostnames, bindings, SSL/TLS certificates, runtime versions, framework versions, application dependencies, database dependencies, file storage locations, and any third-party integrations.
Confirmation that the application components are suitable for Azure App Service or that unsupported components have been identified for separate remediation. Examples that may require additional review include custom server-level components, Windows registry dependencies, COM components, custom drivers, non-HTTP services, local file-system assumptions, and legacy runtimes not supported by Azure App Service.
Approved backup, snapshot, or rollback approach for the source website and any related databases before migration or cutover work begins.
Planned maintenance or cutover window agreed with the client, with business/application owners available to perform functional validation after deployment.
DNS ownership and access available to the client for required internal and external DNS changes, including the ability to adjust DNS TTL values in advance where appropriate.
Required network and firewall access available between the source environment, migration tooling or workstation, database endpoints if applicable, and Microsoft Azure endpoints.
SSL/TLS certificate files, private keys, passwords, and domain validation access available if custom domains and HTTPS bindings are to be configured in Azure App Service.
For database migration in scope, the target database service, sizing approach, access permissions, and acceptable migration method are confirmed before execution.

Who does what

IT Partner

  • Analyzing your web server installation, identifying which sites can be migrated to the App Service, and highlighting any elements that cannot be migrated or are unsupported on the platform
  • Installing and configuring Microsoft's App Service migration tooling
  • Migrating sites and databases from a remote server to Azure

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
  • Perform changes to internal and external DNS, as required

What's not included

Website support
Changes or modification of website/web app functionality
More extensive documentation can be provided for an additional fee.

Limitations & technical notes

!IT Partner's responsibilities will depend on your choice of the listed migration items and may include the stated responsibilities.
!The plan may vary depending on your needs.
!Azure App Service is a managed platform: custom server-level components, non-HTTP services, unsupported runtimes, and local file-system assumptions may not migrate and are identified during the assessment for separate remediation.
!Connection strings, application settings, and configuration values typically need rework for the App Service environment; custom domains and HTTPS require certificate and DNS cutover coordinated with the client, who owns the DNS changes.
!Azure consumption charges for the App Service plan and related resources are billed by Microsoft and are not included in the service price.

Frequently asked questions

What does the Website or Web App Migration to Azure App Service include?

IT Partner analyzes your web server installation, identifies which sites can be migrated to Azure App Service and which elements are unsupported, installs and configures Microsoft's App Service migration tooling, migrates the applicable sites and databases, and verifies the result. You receive a migration summary with links to the new Azure web apps and a project closeout report.

How much does the migration cost, and how long does it take?

The service is $450 per project and runs 1 day, quoted fixed-price in writing before work begins. Azure consumption for the App Service plan itself is billed by Microsoft separately.

Will IT Partner assess whether my current website can run on Azure App Service?

Yes. The analysis identifies which sites can be migrated and highlights elements that cannot move or are unsupported on the platform — for example custom server-level components, non-HTTP services, or legacy runtimes. That assessment happens before migration, so you know the boundary in advance.

Are databases included in the migration?

Databases may be included when applicable, based on the selected migration items — the stated scope covers migrating sites and databases from a remote server to Azure. The database target, method, and sizing are confirmed during planning.

What Azure App Service capabilities can the migrated site use?

Depending on configuration: automatic scaling, automatic site backups, the high availability of the Azure PaaS platform, deployment slots for staging and staged go-lives, load balancing and DDoS protection, and traffic management. These are platform capabilities, not automatic guarantees — the configuration for your site is agreed during the engagement.

Will there be downtime during the website migration?

The migration itself runs alongside your live site; user-facing impact is concentrated at cutover, when DNS is switched to the new Azure web app. Cutover timing, DNS TTL reduction, and certificate binding are planned in advance, and deployment slots can support a staged go-live where configured. The service does not promise zero downtime.

Who handles DNS and certificate changes for the cutover?

The client performs internal and external DNS changes, as stated in the client responsibilities. IT Partner configures the Azure side — including custom domain bindings and certificates where in scope — and coordinates the cutover sequence with your DNS administrator.

Does this service include changes to my website or web app functionality?

No. Changes or modifications to website or web app functionality are not included. The service migrates the site as it is; connection strings and configuration values are adjusted for the App Service environment, but application code is not modified.

Does this service include ongoing website support after migration?

No. Website support is not included. The engagement ends with the verified migration, the migration summary, and the project closeout report; ongoing support or hosting management can be arranged separately.

Can this service migrate multiple websites?

Yes — the scope refers to website(s) moved from the web server to Azure App Service. How many sites can move, and which ones, depends on the selected migration items and the analysis of your web server installation.

What happens if issues are found after the final deployment?

The implementation plan includes a verify-and-fix step: IT Partner verifies the migrated sites and addresses migration-related issues within the engagement scope. Broader website support or functionality changes remain out of scope.

What deliverables are included at the end of the migration?

The migrated website(s) in Azure App Service, applicable migrated databases, a migration summary showing the sites migrated and links to the new Azure web apps, and a project closeout report with final status, acceptance evidence, outstanding issues if any, and the final budget.

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.

Often combined with

$450 per project
1 day
Book a meeting