Migrating Your On-Premise Servers to Azure: What to Expect

For many UK small and medium-sized enterprises, on-premise servers have been the backbone of daily operations for a decade or more. They sit in a back office, a server cupboard, or a small comms room — quietly running file shares, line-of-business applications, email, and Active Directory. They work, mostly. But they are ageing. And the cost of keeping them running — both financially and operationally — is climbing every year.

Microsoft Azure offers a compelling alternative: enterprise-grade infrastructure hosted in UK data centres, with the scalability, security, and resilience that on-premise hardware simply cannot match. But migrating to Azure is not a weekend project. It requires careful planning, the right tools, and a clear understanding of what will change — and what will not.

This guide walks you through the entire migration journey, from assessing your current server estate to post-migration optimisation, with a particular focus on the realities facing UK SMEs in 2026.

Why Businesses Migrate from On-Premise to Azure

The decision to migrate rarely comes from a single event. Instead, it is the accumulation of pain points that tips the scales. Perhaps your main server is five years old and the warranty has expired. Maybe you have been hit by a ransomware scare and realised your backup strategy has gaps. Or your team is increasingly working remotely, and VPN performance to an ageing on-premise server is painfully slow.

Here are the most common drivers we see among the UK businesses we work with:

• Hardware end-of-life: Servers older than five years carry a significantly higher risk of failure. Replacement parts become scarce, and manufacturer support ends. Buying new on-premise hardware is a substantial capital expense — typically £8,000 to £25,000 for a single server, before licensing and installation.
• Security and compliance: On-premise environments require constant patching, firewall management, and monitoring. Many SMEs lack the in-house resource to keep up, leaving them exposed. Azure provides built-in security tooling, automatic patching, and compliance certifications including ISO 27001, Cyber Essentials, and UK GDPR alignment.
• Remote and hybrid working: Cloud infrastructure eliminates the need for site-to-site VPNs and removes the performance bottleneck of routing remote traffic through an office server.
• Scalability: Adding capacity on-premise means buying, racking, and configuring new hardware. In Azure, scaling up is a configuration change that takes minutes.
• Disaster recovery: Replicating a robust DR environment on-premise is prohibitively expensive for most SMEs. Azure Site Recovery provides affordable, automated disaster recovery as a service.
• Predictable costs: Shifting from large capital expenditure cycles to a monthly operational expenditure model makes budgeting far more predictable and cash-flow friendly.

Assessing Your Current Server Estate

Before you can plan a migration, you need a clear picture of what you are working with. Surprisingly, many businesses do not have an accurate, up-to-date inventory of their server environment. Servers accumulate over time, services get installed ad hoc, and documentation — if it ever existed — falls out of date.

A thorough assessment should catalogue the following:

Assessment Area	What to Document	Why It Matters
Physical hardware	Make, model, age, CPU, RAM, storage capacity and utilisation	Determines Azure VM sizing and identifies under-utilised hardware
Operating systems	Windows Server version, patch level, licence type	Licence portability (Azure Hybrid Benefit) can save up to 85% on compute costs
Applications	Every application or service running, dependencies, vendor support status	Some legacy applications may not be cloud-compatible without modification
Data volumes	Total data stored, growth rate, backup frequency and retention	Directly impacts storage costs and migration transfer times
Network configuration	IP addressing, DNS, DHCP, firewall rules, VPN tunnels	Must be replicated or redesigned in Azure Virtual Network
User access	Active Directory structure, group policies, user counts	Determines Azure AD (Entra ID) configuration and licensing
Integrations	Connections to printers, CCTV, telephony, IoT devices	On-premise dependencies that may require hybrid architecture

Microsoft’s Azure Migrate tool can automate much of this discovery. It deploys a lightweight appliance into your on-premise environment that scans your servers, maps dependencies, and generates a readiness report with recommended Azure VM sizes and estimated monthly costs. This is an invaluable starting point and, importantly, it is free to use.

Lift-and-Shift vs. Re-Architecture: Choosing Your Approach

Once you understand what you have, the next decision is how you migrate. The two primary approaches sit at opposite ends of a spectrum, and most real-world migrations land somewhere in between.

For most UK SMEs, we recommend a phased approach: start with a lift-and-shift to get off ageing hardware quickly and reduce immediate risk, then progressively optimise and refactor individual workloads over time. This balances urgency with long-term value and avoids the paralysis that comes with trying to redesign everything at once.

Azure Migration Tools You Should Know

Microsoft provides a comprehensive suite of tools purpose-built for migration. Understanding which tool does what will save you considerable time and confusion.

Azure Migrate

Azure Migrate is the central hub for planning and executing your migration. It is not a single tool but a collection of integrated capabilities:

• Discovery and assessment: Scans your on-premise environment, identifies servers, maps application dependencies, and recommends Azure VM sizes with cost estimates.
• Server migration: Handles the actual replication and cutover of Windows and Linux servers to Azure VMs, with minimal downtime.
• Database migration: Assesses SQL Server databases for compatibility and migrates them to Azure SQL Database, Azure SQL Managed Instance, or SQL Server on Azure VMs.
• Web app migration: Evaluates and migrates .NET and Java web applications to Azure App Service.

Azure Site Recovery (ASR)

While primarily a disaster recovery service, Azure Site Recovery is also an exceptionally effective migration tool. It continuously replicates your on-premise servers to Azure, allowing you to perform a final cutover with minimal downtime — often under 15 minutes. For businesses that cannot afford extended periods of downtime, ASR is the preferred migration mechanism.

Azure Database Migration Service

For database-heavy environments, the Azure Database Migration Service provides an online migration path for SQL Server, MySQL, and PostgreSQL databases. Online migration means the source database continues to operate during migration, with changes synchronised continuously until you are ready for the final switchover.

Planning the Migration Timeline

A realistic migration timeline depends on the complexity of your environment, the approach you choose, and how much disruption your business can tolerate. Here is a typical timeline for a UK SME with 2–5 on-premise servers and 20–80 users:

In total, you are looking at 8 to 16 weeks from the first assessment call to a fully operational, optimised Azure environment. The actual cutover — the point where you switch from on-premise to Azure — is usually planned for a Friday evening or weekend to minimise disruption, and typically involves less than an hour of downtime when using Azure Site Recovery.

Data Migration Strategies

Data is the most critical and often most time-consuming element of any migration. The strategy you use depends on the volume of data, available bandwidth, and your tolerance for downtime.

Method	Best For	Transfer Speed	Typical Cost
Online transfer (Azure Migrate / ASR replication)	Under 5TB of data	Depends on upload bandwidth	Free (bandwidth charges only)
Azure Data Box (physical device)	5TB – 80TB	Ship device → 1–2 business days to upload in Azure DC	£400 – £600 per device
Azure Data Box Heavy	80TB – 1PB	Ship device → 1–2 business days	£3,000+ per device
Azure ExpressRoute with Data Transfer	Ongoing large-volume transfers	1Gbps – 100Gbps dedicated link	£200 – £2,000+/month

For most UK SMEs with under 2TB of data, online replication via Azure Site Recovery is the simplest and most cost-effective approach. The initial replication runs in the background over several days without impacting server performance, and subsequent changes are synchronised continuously. This means the final cutover only needs to transfer the changes made since the last sync — usually a matter of minutes.

If you have more substantial data volumes, Azure Data Box is an excellent option. Microsoft ships a rugged storage device to your office, you copy your data onto it locally (much faster than an internet transfer), and ship it back. Your data is uploaded directly in the Azure data centre, bypassing bandwidth limitations entirely.

Network Connectivity: Linking Your Office to Azure

Once your servers are in Azure, your users need a fast, reliable, and secure way to connect to them. The right connectivity option depends on your performance requirements, budget, and security posture.

Site-to-Site VPN

A site-to-site VPN creates an encrypted tunnel between your office firewall and your Azure Virtual Network. It runs over your existing internet connection and is the most common starting point for SMEs. Azure VPN Gateway pricing starts at approximately £25 per month for the Basic SKU, making it very affordable.

However, VPN performance is limited by your internet connection. If your office broadband is 80Mbps, that is your ceiling for Azure connectivity. For most SMEs running standard workloads (file access, email, line-of-business applications), this is perfectly adequate.

Azure ExpressRoute

For businesses with demanding performance requirements — large-scale data transfers, real-time applications, or strict latency requirements — Azure ExpressRoute provides a private, dedicated connection that bypasses the public internet entirely. It offers guaranteed bandwidth (from 50Mbps to 100Gbps), lower latency, and higher reliability.

ExpressRoute is delivered through Microsoft’s peering partners in the UK (such as BT, Vodafone, and Equinix) and typically costs from £200 per month for a 50Mbps circuit upwards. While this is a significant step up from a VPN, it is essential for businesses running latency-sensitive workloads or transferring large volumes of data regularly.

Point-to-Site VPN

For remote workers who need to connect to Azure resources from home or while travelling, a point-to-site VPN provides individual encrypted connections from their devices directly to Azure. This is often used alongside a site-to-site VPN from the office, giving both on-site and remote staff seamless access.

Cost Modelling and Azure Pricing

Understanding Azure pricing is essential for building a business case and avoiding bill shock after migration. Azure uses a consumption-based model — you pay for what you use — but there are several levers you can pull to reduce costs significantly.

Key Pricing Components

• Compute (VMs): Charged per second based on VM size. A standard D2s v5 VM (2 vCPUs, 8GB RAM) costs approximately £60 per month on pay-as-you-go, or £35 per month with a 1-year reserved instance.
• Storage: Azure Managed Disks pricing depends on the tier (Standard HDD, Standard SSD, Premium SSD). A 256GB Standard SSD costs around £28 per month.
• Networking: Inbound data transfer to Azure is free. Outbound transfer is charged at approximately £0.07 per GB after the first 5GB. For most SMEs, this is a negligible cost.
• Licensing: Windows Server and SQL Server licences are included in VM pricing, or you can bring your own via Azure Hybrid Benefit for substantial savings.
• Backup: Azure Backup pricing is based on the size of the protected instance. A typical 500GB server backup costs around £15 – £25 per month.

UK SME Cost Comparison: On-Premise vs. Azure

Here is a realistic cost comparison for a typical UK SME running two servers (one file and print server, one application server) with 40 users:

Cost Category	On-Premise (Annual)	Azure (Annual)
Hardware (amortised over 5 years)	£6,000 – £10,000	£0
Windows Server licences	£1,800 – £3,500	Included (or £0 with Hybrid Benefit)
Electricity and cooling	£1,500 – £2,500	£0
Backup hardware and software	£1,200 – £2,000	£300 – £600
Compute / VM costs	N/A (hardware cost above)	£2,400 – £4,800
Storage	N/A (hardware cost above)	£600 – £1,200
IT support for server maintenance	£3,000 – £6,000	£1,000 – £2,000
Disaster recovery	£4,000 – £8,000 (if implemented)	£600 – £1,200
Networking (VPN Gateway)	£0 (on-site)	£300 – £1,800
Total Annual Cost	£17,500 – £32,000	£5,200 – £11,600

Even at the upper end of Azure pricing and the lower end of on-premise costs, the cloud option delivers a significant saving. And this comparison does not account for the hidden costs of on-premise — unplanned downtime, the risk of catastrophic hardware failure, or the productivity loss when your sole IT person is unavailable to deal with server issues because they are managing other priorities.

Common Migration Challenges and How to Avoid Them

No migration is without its challenges. Understanding the most common pitfalls — and having a plan to address them — dramatically increases your chances of a smooth transition.

1. Legacy Application Incompatibility

Some older applications were never designed to run in a virtualised or cloud environment. They may depend on specific hardware, use outdated protocols, or require direct access to local devices like serial ports or USB dongles.

How to avoid it: Identify these applications during the assessment phase. Options include running them on a dedicated Azure VM with specific configurations, using Azure App Service for web-based modernisation, or maintaining a minimal on-premise presence for the specific application while migrating everything else.

2. Insufficient Bandwidth

If your office internet connection is slow or unreliable, moving your servers to Azure will make performance worse, not better. Every file open, every application interaction, and every login must traverse that connection.

How to avoid it: Test your connection thoroughly before migration. As a rule of thumb, you need a minimum of 100Mbps symmetrical bandwidth for 20–40 users accessing Azure-hosted resources. If your current connection falls short, upgrade it before the migration — not after.

3. Underestimating DNS and Active Directory Complexity

Active Directory is the nervous system of most Windows-based IT environments. Migrating AD to Azure (whether as Azure AD Domain Services or a traditional domain controller on an Azure VM) requires meticulous planning. DNS resolution, group policies, trust relationships, and service accounts all need to work flawlessly from day one.

How to avoid it: Run a parallel AD environment in Azure for at least two weeks before cutover. Test every group policy, every login path, and every service account. Do not decommission your on-premise domain controllers until you are completely confident the Azure environment is stable.

4. Bill Shock

Azure’s consumption-based pricing is a double-edged sword. If VMs are left running when they should be deallocated, disks are over-provisioned, or resources are deployed in the wrong region, costs can escalate quickly.

How to avoid it: Implement Azure Cost Management from day one. Set up budgets and alerts. Use Azure Advisor recommendations. Right-size VMs after migration based on actual utilisation data. Consider Reserved Instances for always-on workloads and auto-shutdown schedules for development or test environments.

5. Inadequate Testing

Rushing the cutover without thorough testing is the single most common cause of migration failure. Applications that worked fine on-premise may behave differently in Azure due to network latency, DNS resolution changes, or security group configurations.

How to avoid it: Build a comprehensive test plan that covers every application, every user role, and every integration. Perform a full dry run — a simulated cutover where you switch to Azure for a few hours and then fall back — before the real go-live. This identifies issues in a controlled environment rather than during a live migration.

Post-Migration Optimisation

Migration is not the finish line — it is the starting point. Once your servers are running in Azure, there is significant value to be unlocked through ongoing optimisation.

Right-Sizing VMs

During migration, VMs are typically sized to match or exceed the on-premise server specifications. In practice, many servers are over-provisioned. After two to four weeks of operation in Azure, review actual CPU, memory, and disk utilisation using Azure Monitor. If a server consistently uses less than 30% of its allocated resources, resize it to a smaller (and cheaper) VM SKU.

Reserved Instances and Savings Plans

Once you are confident in your Azure resource requirements, commit to 1-year or 3-year Reserved Instances for your always-on VMs. This typically saves 30–60% compared to pay-as-you-go pricing. Azure Savings Plans offer similar discounts with more flexibility across VM families and regions.

Azure Backup and Disaster Recovery

Implement Azure Backup for all VMs and critical data from day one. Configure Azure Site Recovery to replicate your Azure VMs to a secondary region (e.g., from UK South to UK West) for geographic redundancy. This gives you a fully automated disaster recovery capability that would cost tens of thousands to replicate on-premise.

Security Hardening

Enable Microsoft Defender for Cloud to continuously assess your Azure environment against security best practices. Implement Network Security Groups to restrict traffic between subnets. Enable Just-In-Time VM access to eliminate standing RDP/SSH exposure. Review and implement Azure Security Centre recommendations systematically.

Monitoring and Alerting

Deploy Azure Monitor and set up alerts for critical metrics — CPU spikes, disk space thresholds, failed login attempts, and backup failures. Proactive monitoring transforms your IT support model from reactive firefighting to preventive maintenance.

UK Data Residency and Compliance

For UK businesses, particularly those in regulated industries such as legal, financial services, healthcare, and education, data residency is non-negotiable. Your data must reside within the United Kingdom, and you must be able to demonstrate this to auditors and regulators.

Azure’s two UK regions provide exactly this assurance:

Both regions hold the following compliance certifications relevant to UK businesses:

• ISO 27001 & ISO 27018: Information security and protection of personal data in the cloud
• Cyber Essentials Plus: UK Government-backed cybersecurity certification
• UK GDPR: Full compliance with UK data protection regulations
• NHS Data Security and Protection Toolkit: For healthcare organisations
• FCA and PRA compliance: For financial services firms
• G-Cloud: Listed on the UK Government’s Digital Marketplace

When configuring your Azure environment, ensure all resource groups, storage accounts, and VMs are explicitly deployed to the UK South or UK West region. Azure Policy can enforce this at the subscription level, preventing anyone from accidentally deploying resources outside the UK.

Making the Decision: Is Azure Right for Your Business?

Azure is not the right choice for every business in every situation. If you have a brand-new on-premise server with four years of warranty remaining, minimal remote working requirements, and no immediate compliance pressures, there may be little urgency to migrate.

However, if any of the following apply, Azure should be a serious consideration:

• Your servers are more than four years old or approaching end of warranty
• You have experienced hardware failures, data loss scares, or extended downtime
• Your team works remotely or from multiple locations
• You are in a regulated industry and need demonstrable compliance
• You want predictable monthly IT costs instead of large capital outlays
• Your current backup and disaster recovery strategy has gaps
• You are planning to grow and need infrastructure that scales with you

The key is to approach the migration with realistic expectations, proper planning, and — ideally — an experienced partner who has delivered Azure migrations for businesses like yours. A well-executed migration is transformative. A poorly planned one creates problems that take months to resolve.