Azure migration cost for a small business splits into two numbers that get confused constantly: the one-time project cost of moving, and the monthly run cost of being there. The project cost is driven by how many workloads move, how old and undocumented they are, and how much landing zone work has to happen before the first server leaves the building. The run cost is driven by how big the virtual machines are, how much storage they use, and whether anyone commits to reservations or lets the meter run at list rates. NetSys quotes both numbers per business after an assessment, on a month-to-month agreement, and this guide explains what sits inside each one.
What is the difference between Azure migration project cost and Azure run cost?
| Project cost (one time) | Run cost (monthly) |
|---|---|
| Assessment and dependency mapping | Virtual machine compute hours |
| Landing zone design and build | Managed disks and blob storage |
| Identity integration with Entra ID | Backup storage and retention |
| Data seeding and replication | Outbound bandwidth |
| Cutover weekends and parallel-run validation | Licenses not covered by hybrid benefit |
| Application remediation and testing | Monitoring, security tooling, log storage |
| Decommissioning the old hardware | Management and support |
A provider that quotes only the project number is leaving you to discover the run cost on your first Azure invoice. A provider that quotes only the run cost is hiding the labor. Ask for both, and ask which one the quote assumes you will pay through them and which one you will pay Microsoft directly.
What does an Azure assessment cost, and what does it produce?
Microsoft's Azure Migrate tooling is free to use, so the assessment cost is the engineer time to deploy it, let it collect performance data for a few weeks, and interpret the result. The output is the document everything else depends on: an inventory of servers and applications, which servers talk to which (the dependency map), how much CPU, memory and disk each one uses as opposed to what it was bought with, and a first estimate of the monthly Azure bill for right-sized equivalents.
That last item is where money is saved or lost. A server bought five years ago with headroom for growth is usually running at a fraction of its capacity. Migrating it like for like into a virtual machine of the same size means paying every month for capacity that was already wasted. Right-sizing from the assessment data is the single largest lever on run cost, and it is only possible if the assessment ran long enough to capture a month-end or a busy season.
Why does a landing zone cost money before any server moves?
A landing zone is the Azure environment a workload lands in: the subscription layout, virtual networks and address ranges, the VPN or ExpressRoute link back to the office, identity and role assignments, policies that stop someone spinning up an unprotected public server, backup vaults, logging and cost alerts. Microsoft's Cloud Adoption Framework describes the pattern in detail. Building it is real work, and small businesses sometimes push back on paying for it because nothing visible has moved yet.
Skipping it is how migrations turn into expensive cleanups. Without address planning, the second site cannot connect. Without policy, a test server gets left running with a public IP. Without cost alerts, the first sign of a runaway resource is the invoice. A landing zone for a small business is a modest piece of work, but it belongs in the quote as its own line so you can see it was done.
What drives the monthly Azure bill after the migration?
- Compute size and hours. Virtual machines bill while running. Servers that only need business hours can be scheduled off overnight and on weekends, which is common for development and test systems and rare for production.
- Storage tier and performance. Premium SSD for a database, standard SSD for an application server, cool or archive tiers for old files nobody opens. Putting everything on premium storage because it was easiest is a frequent cause of bills that surprise people.
- Backup retention. Every retained restore point occupies storage. Retention set to forever during setup is a quiet monthly cost that keeps growing.
- Outbound bandwidth. Data leaving Azure for the internet is metered. Large file transfers to remote offices or to another cloud add up.
- Licensing. Windows Server and SQL Server licenses are either included in the hourly rate or brought with you. Microsoft's Azure Hybrid Benefit lets businesses with eligible licenses and Software Assurance apply them in Azure instead of paying for the license again inside the VM price.
- Security and monitoring. Defender for Cloud, log ingestion and retention, and any third-party agents are billed per resource or per gigabyte.
How do reservations and savings plans lower the run cost?
Azure's default is pay-as-you-go: list rate, billed for what runs, cancel any time. For a production server that will run every hour of every day for years, that flexibility is paid for and never used. Microsoft's public pricing pages for reserved virtual machine instances and Azure savings plans describe the alternative: commit to one or three years of a given VM size (a reservation) or a given hourly spend (a savings plan), and the rate drops in exchange for the commitment. Microsoft publishes the discount per size and region, and we will not restate it here because it changes.
The judgment call is when to commit. Reserving before the assessment has confirmed the right size locks in the wrong size. A sensible sequence is to migrate on pay-as-you-go, run for a billing cycle or two, right-size from real data, and then reserve the servers that have proven stable. A provider who reserves everything on day one is optimizing their quote rather than your bill.
How do you compare Azure migration quotes?
- Two numbers, separated. Project cost and estimated monthly run cost, with the assumptions behind the run cost listed: VM sizes, storage tiers, backup retention, reservations or none.
- What happens to the old server. Decommissioning, data destruction and hardware disposal are either in the quote or they are your problem.
- Cutover method. Weekend cutovers with parallel-run validation cost more than a single big-bang switch and fail less often.
- Who owns the subscription. It should be your tenant, in your name, with the provider as a delegated administrator, so leaving them does not mean leaving Azure.
- Ongoing management. Patching, backup verification, cost review and security monitoring after go-live, and whether that is a separate agreement.
Frequently asked questions
How much does it cost to migrate a small business to Azure?
There are two costs: a one-time project fee driven by how many servers and applications move and how much landing zone and remediation work they need, and a monthly Azure bill driven by VM size, storage, backup retention and licensing. NetSys quotes both after an assessment of the current environment rather than from a rate card, because a three-server file-and-print office and a three-server ERP environment with SQL are very different projects with the same server count.
Is Azure cheaper than replacing our on-premises server?
Sometimes, and the assessment is how you find out. Azure removes the hardware purchase, the warranty, the UPS, the server room and the weekend rebuild after a failure, and replaces them with a monthly bill that scales with use. It costs more than an old server that is already paid for and running fine, until that server fails. The fair comparison is the next refresh cycle, all-in, against right-sized Azure with reservations, plus the value of tested recovery.
What happens to our Windows Server and SQL licenses in Azure?
Azure virtual machine prices can include the Windows Server license in the hourly rate. If you already own licenses with active Software Assurance, Microsoft's Azure Hybrid Benefit lets you apply them to Azure VMs and SQL instead, lowering the hourly rate. Licenses without Software Assurance generally cannot be moved, which is a detail to settle during the assessment rather than after the first invoice. Your licensing position belongs on the quote as an explicit assumption.
Who manages Azure after the migration?
Someone has to. Patching, backup verification, cost review, identity and access, and security monitoring do not stop because the server now sits in a Microsoft datacenter. NetSys manages Azure environments as part of a month-to-month managed agreement alongside Microsoft 365 and the rest of the environment, with a dedicated account manager rather than a ticket queue. Ask any provider whether post-migration management is included, priced separately, or offered at all.
Getting a number for your environment
The honest answer to what Azure will cost you starts with an assessment of what you run today and how hard it works. NetSys runs that assessment, designs the landing zone, migrates workloads in validated phases and manages the result month to month. Start on our Azure migration page, or read about the broader cloud services we deliver, including Azure Virtual Desktop for firms that want desktops in the cloud as well.
Sources and further reading
- Azure Migrate documentation, Microsoft's assessment and migration tooling.
- Azure landing zones in the Cloud Adoption Framework.
- Azure Reserved VM Instances and Azure savings plan for compute, Microsoft's public pricing terms.
- Azure Hybrid Benefit.
Turn insight into action.
Take a free cybersecurity or AI readiness assessment, or book a call with a NetSys engineer — no obligation, no runaround.