How do we move an old on-premises application to Azure?

There are three routes: move it as it stands onto Azure virtual machines, re-platform it onto App Service and Azure SQL, or rebuild the parts that will not fit, and the application's operating system, .NET version, database features, Windows authentication, file shares, scheduled jobs and licences decide which. This page is for an IT manager at a medium or large organisation who has to move an old line-of-business application off an on-premises server with a rehearsed cut-over and a way back.

By Graham Church, founder and managing director. Updated 15 October 2026.

The three routes

Lift and shift to a virtual machine. The application is moved as it stands onto Windows Server virtual machines in Azure, with SQL Server installed on a VM or replaced by Azure SQL Managed Instance. Least change to the application and fastest to do, but the running cost stays closest to a server’s, because you still pay for whole machines whether busy or idle.

Re-platform to App Service and Azure SQL. A web application moves onto Azure App Service, which runs the code without a server for you to patch, and the database onto Azure SQL Database. Cheaper to run and less to look after, but the application has to fit. App Service runs web applications, not desktop programs or Windows services, and Azure SQL Database does not support everything an on-premises SQL Server does.

Rebuild the parts that do not fit. The pieces that cannot move as they are, such as a Windows service that watches a folder or a report that depends on a printer, are rewritten for the cloud, usually as Azure Functions, Logic Apps or storage queues. Done for those parts only, with one of the first two routes for the rest.

Most old line-of-business applications end up on a mix: the web front end on App Service or a VM, the database on a managed SQL service, and one or two awkward parts rebuilt.

What decides the route

The application decides, not preference.

Operating system and .NET version. Azure virtual machines run supported versions of Windows Server, so an application on an older one has to be proven on a current version first, which is often where the work is. App Service runs .NET Framework 4.x and current .NET web applications; anything older, or anything that is not a web application, needs a VM or an upgrade.

SQL Server features. SQL Agent jobs, linked servers, cross-database queries and CLR assemblies are not available in Azure SQL Database. Azure SQL Managed Instance supports most of them at a higher cost; SQL Server on a VM supports all of them.

Windows authentication. An application that identifies users through Active Directory needs either domain-joined VMs with a VPN or ExpressRoute link to your domain, or a change to sign in through Microsoft Entra ID. The second is the better end state and the larger change.

File shares and local folders. Code that reads and writes UNC paths or a folder on the server needs that storage to exist in Azure, usually Azure Files or blob storage, and may need changing to use it.

Scheduled jobs. Windows Task Scheduler and SQL Agent jobs move unchanged to a VM. On App Service they become WebJobs, Functions or Logic Apps.

Printers, scanners and other devices in the building. A server in Azure cannot see them, so either the application prints through a service on site, reached over the VPN, or that part is redesigned.

Licences. Windows Server and SQL Server licences with Software Assurance can be reused in Azure under the Azure Hybrid Benefit, which changes the cost comparison. Third-party components licensed to a machine may need re-licensing, and the vendor may no longer exist.

What to check before anything moves

Every dependency. Integrations with other systems, service accounts, certificates, hard-coded server names and IP addresses, email relays, and the shared folder somebody set up years ago. The ones nobody remembers fail on cut-over day.

Latency. An application that makes hundreds of small database calls per screen will crawl if it and its database end up on opposite sides of the link. Keep them together, and check what on premises it talks to and how often.

Data residency. Azure has UK regions. Confirm with your data protection lead whether contracts or policies restrict where the application’s data is stored, and choose the region before anything is built.

Backup and restore. Prove that the current backups restore, so there is a known-good copy before the move, and decide how backups will work in Azure and who will test the restores.

Measured usage. Processor, memory, disk and database load over a normal month, including month-end. Sizing from measurements rather than the old server’s specification is where most of the saving is.

Cutting over with a way back

Build the Azure environment from scripts so it can be rebuilt exactly, copy a full set of production data to it, and rehearse the whole cut-over with users testing their real tasks until it runs without surprises and you know how long it takes.

For the real move: freeze changes on the old system, take the final copy of the data, point the application’s DNS names at Azure and let users in, keeping the old environment on but untouched for an agreed period. Decide before the day what would make you roll back, who decides, and the point of no return: once users have written data into Azure, a rollback means bringing that data back too.

What it costs

Azure is billed monthly and the bill follows sizing, so the move is a one-off cost and the running cost is a forecast to check against the real bill after a few weeks. A VM costs the same busy or idle; App Service and Azure SQL can be scaled down further. Budget for running both environments during the overlap. Whether the result is cheaper than the current server depends on what that server really costs, including its replacement, support and the licences you can carry across.

Where to start

The inventory above is where any migration starts, and it is the part most often skipped. CodeFirst, a UK software company that moves established business applications to Azure and AWS, records it in a fixed-price code audit and then runs the move as a cloud migration with a rehearsed cut-over. If the application is on .NET Framework, the .NET upgrade assessment shows how far it could go.

Related questions

Should we upgrade the operating system and SQL Server at the same time as moving?

Usually yes, because the new environment is being built anyway and old versions may not be available to install in Azure. Test the application against the new versions as part of the rehearsal rather than on the day. Where the application will not run on a current version, that is the first thing to fix, before the move.

Will the application be slower once it is in Azure?

Not if the application and its database move together and users reach it over a reasonable connection. It will be slower if the application stays chatty with something that remains on premises, such as a file share or another database, because each call now crosses the link. The dependency inventory shows where that would happen.

Can users still sign in with their Windows accounts?

Yes, in one of two ways. Virtual machines in Azure can be joined to your domain over a VPN or ExpressRoute connection, so Windows authentication carries on as before. The longer-term route is to change the application to sign in through Microsoft Entra ID, which removes the dependency on the link to the domain.

How long does the move take?

It depends on how many dependencies the application has and whether it needs changing to run on the target. Most of the elapsed time goes on discovery and rehearsal; the cut-over itself is usually a planned window outside working hours. A rehearsed move tells you the length of that window before you commit to it.

Want the answer for your system?

Tell us what the software does and what you are trying to decide. We will reply with a straight answer and what we would need to know to be more precise.

Tell us about your system 0800 433 7990 Monday to Friday, 9am to 5pm. A first 20-minute call is free, and we reply to every enquiry within one working day. What happens after you get in touch