The calculation almost every company makes before a cloud migration is simple: the hourly price of the virtual machine, multiplied by 730 hours. In the example below, on Azure list prices as of 8 November 2026, the virtual machine comes to €271 a month. The infrastructure bill comes to €375. The difference is not a provider error; it is the disk, the backup, the outbound traffic and the archive, each with its own meter.
Cloud migration costs for SMBs are neither higher nor lower than for the server in the office. They are built differently. With a purchased server you pay for capacity once. In the cloud you pay every month for each decision: which size you pick, how long it stays on, where the data sits and how much of it leaves the network.
What cloud migration costs are made of
The first thing to settle is the model: IaaS (you rent virtual machines, disks, network), PaaS (you use a managed platform without administering the operating system) or SaaS (you use a ready-made application such as Microsoft 365). The model decides not only what you pay but also what stays in your hands. Microsoft publishes the split like this:
| Responsibility | On-premises | IaaS | PaaS | SaaS |
|---|---|---|---|---|
| Data, configurations, identities | You | You | You | You |
| User devices | You | You | You | Shared |
| Applications | You | You | Shared | Shared |
| Network controls | You | You | Shared | Microsoft |
| Operating system | You | You | Microsoft | Microsoft |
| Physical hosts, network and datacenter | You | Microsoft | Microsoft | Microsoft |
Whatever the model, data, accounts, devices and access control stay yours. For the budget this means part of the cost does not disappear with the migration: the time of whoever manages identities, access policies and backup stays on your payroll.
Then come the meters. In a typical IaaS project for a small company, the bill has at least six lines:
- Compute: the virtual machine, per hour, while it is allocated.
- Licences: Windows Server is paid per hour, by core count; Microsoft 365 per user per month.
- Disks: per month, by size, even when the machine is stopped.
- Outbound traffic (egress): per GB, after a free monthly allowance.
- Object storage: per GB per month, plus reads and retrieval, different for each tier.
- Backup: per protected instance, plus the space the copies take.
Worked example: one application server and 30 users
The company in the example is hypothetical: 30 people, one Windows server with the business application and shared files, 2 TB of old documents that must be kept. The assumptions, chosen by us so they are easy to redo: Azure region Germany West Central, list prices in euro excluding VAT, read on 8 November 2026 from the Azure Retail Prices API and the official pricing pages, 730 hours a month, 400 GB of outbound traffic a month and 300 GB taken up by backup copies.
| Component | Meter and list price | Per month |
|---|---|---|
| Virtual machine D4s v5 (4 vCPU), Windows, pay-as-you-go | €0.3717/hour × 730 hours | €271.34 |
| Premium SSD P15 disk (256 GiB) | €37.534/month | €37.53 |
| Azure Backup for the virtual machine | €8.9771/instance (50-500 GB) + 300 GB × €0.0539 (GRS) | €25.15 |
| Outbound traffic, 400 GB | first 100 GB free, then €0.0781/GB | €23.43 |
| 2,000 GB archive in the Cool tier (LRS) | €0.009/GB | €18.00 |
| Infrastructure total | €375.45 | |
| Microsoft 365 Business Standard, 30 users | €20.36/user, annual subscription | €610.80 |
| Monthly total | €986.25 |
Three observations. The virtual machine is 72% of the infrastructure, so the remaining 28% is not a detail. Of the €271.34, €120.60 is the Windows Server licence, at €0.1652 per hour for 4 vCPU. And Microsoft 365 costs more here than the whole Azure infrastructure: if some people only work in the browser and on mobile, Business Basic is €6.07 per user per month, while Business Premium is €27.73, also paid yearly. On the Microsoft page, Standard and Premium are now listed as ‘with Copilot’.
What the virtual machine looks like with a reservation, on the same list prices:
| Option | Calculation | Per month | Versus pay-as-you-go |
|---|---|---|---|
| Pay-as-you-go, Windows | €0.3717 × 730 | €271.34 | baseline |
| 1-year reservation + Windows licence | €1,115.85 / 12 + €120.60 | €213.58 | -21.3% |
| 3-year reservation + Windows licence | €2,143.72 / 36 + €120.60 | €180.14 | -33.6% |
| Infrastructure only, 1-year reservation | €92.99 versus €150.75 | €92.99 | -38.3% |
| Infrastructure only, 3-year reservation | €59.55 versus €150.75 | €59.55 | -60.5% |
The gap between the rows is the lesson: Microsoft states explicitly that reserved instance discounts apply only to infrastructure costs, not to software. On Windows without Azure Hybrid Benefit, the licence is still paid in full, so the discount that matters to you is the one in the first three rows, not the last two.
The cloud has no price, it has meters that you set
This is the reframe that changes how you read any migration quote. The price you compare with the office server does not exist as such. There is a set of meters, and the value of each depends on a decision: machine size, commitment length, storage tier, region, who is allowed to start resources.
In the cloud you do not pay for the server. Every month, you pay for the decisions you made about it.
For an SMB, the practical consequence is that a migration needs a cost owner, just as it needs an administrator. Without one, the meters run on default values, and defaults are designed to work, not to be cheap.
The traps that inflate the bill
- Stopped is not deallocated. A virtual machine shut down from Windows stays allocated on the host and keeps being billed. Compute billing stops only in the ‘Deallocated’ state, and disks and networking are still charged then. A test machine used 10 hours a day, 22 days a month, costs €81.77 in compute if it is deallocated the rest of the time and €271.34 if it is only shut down from the operating system.
- Egress adds up. In Azure, the first 100 GB a month are free, then €0.0781/GB from Europe. At AWS Frankfurt, after 100 GB free per month aggregated globally, $0.09/GB. A branch VPN or a sync with the office is paid every month.
- A reservation is a commitment. It runs for 1 or 3 years, does not reduce the Windows licence and only makes sense after you have sized the machine on real usage data.
- Storage tiers carry penalties. Cool requires a minimum of 30 days, Cold 90, Archive 180; deleting or moving earlier is billed pro rata. Archive is offline, and rehydration can take up to 15 hours.
- Backup is not included by default. Microsoft sells Microsoft 365 Backup as a separate service at $0.15 per protected GiB per month. For virtual machines, Azure Backup is also a separate line on the bill.
| Tier | List price/GB/month | 2,000 GB per month | Minimum retention | Access |
|---|---|---|---|---|
| Hot | €0.0176 | €35.20 | none | milliseconds |
| Cool | €0.009 | €18.00 | 30 days | milliseconds |
| Cold | €0.004 | €8.00 | 90 days | milliseconds |
| Archive | €0.0016 | €3.20 | 180 days | hours, rehydration up to 15 hours |
For the archive in the example, Archive looks more than five times cheaper than Cool. But a full retrieval of the 2,000 GB costs €43 in retrieval alone, plus hours of waiting. Archive suits what must be kept and is not read; documents someone needs twice a year are better off in Cool or Cold. How to test that you can actually restore what you saved is covered under backup and continuity.
Leaving the cloud: what changes in 2027
A cost forgotten on the way in is the cost of getting out. The EU Data Act prohibits, from 12 January 2027, any switching charges, including egress charges for moving to another provider or back on-premises (Art. 29). Until then, charges may only be reduced, at direct cost. The contract must provide for a notice period of no more than two months and a transition of no more than 30 days (Art. 25). Azure already offers free egress to customers who leave, through a credit request. Note: the rule concerns switching providers, not outbound traffic from day-to-day operations.
Data residency and GDPR
The cloud provider is a processor under the GDPR, and Art. 28 requires you to use only processors providing sufficient guarantees, under a contract. Art. 32 requires appropriate security measures, including the ability to restore the availability of data in a timely manner, so a tested backup is also a GDPR obligation, not just good practice. Transfers outside the EU fall under Chapter V (Art. 44 onwards).
For Microsoft services, the EU Data Boundary is the commitment to store and process customer data and personal data in the EU and EFTA, with limited exceptions that Microsoft documents. For Azure, regional services deployed in an EU region are in scope; for Microsoft 365, tenants with a sign-up location in the EU or EFTA, except those with Multi-Geo. Romania is on the list of boundary countries, but not on the list of countries with datacenters used. For transfers to the United States, Decision (EU) 2023/1795 on the Data Privacy Framework was listed as in force on EUR-Lex on the date we checked, for organisations on the DPF List.
In practice: choose an EU region, check the data processing agreement and the list of subprocessors, and record in your register of processing activities where the data sits. If you process sensitive data, the choice of region is a decision to document, not a default setting.
FinOps for an SMB: five habits, not a team
The FinOps Foundation describes three phases that repeat: Inform (see and allocate costs), Optimize (improve rates and usage) and Operate (apply the changes and start the cycle again). A 30-person company does not need a FinOps team, just a few habits:
- 1Tag every resource with owner, project and environment (production, test). Without tags, the bill cannot be read by project.
- 2Create a budget per subscription, with alerts on actual and forecasted cost. The budget only notifies: Microsoft states that resources are not affected and consumption is not stopped. Cost data typically appears within 8-24 hours, and budgets are evaluated every 24 hours.
- 3Size after 30 days of real data, then reserve only what is stable.
- 4Schedule automatic deallocation of test machines outside working hours.
- 5Set a lifecycle policy on object storage, so old files move down to cheaper tiers on their own, keeping minimum retention in mind.
Half an hour a month on the top five lines of the bill is enough to catch unattached disks, forgotten running machines and Microsoft 365 licences assigned to people who have left. More on where money leaks in existing infrastructure is in our article on IT cost optimisation in 2026.
How we work
Before a migration we run the calculation above on your data, not on assumptions: which servers you have, what they consume, how many users need which licence, which data must stay in the EU. The IT Infrastructure Optimisation package in our package list delivers current versus proposed TCO, an inventory of hardware, software and licences, a 12-24 month cost optimisation roadmap and a phased execution plan. Catalogue prices, excluding VAT:
- Micro, up to 10 devices: €1,000, 3 days.
- Small, 10-50 devices: €2,600, 7 days.
- Medium, 50-100 devices: €5,800, 12 days.
- Large, over 100 devices: €11,200, 20+ days.
The migration itself, the architecture and operations are part of our IT infrastructure service.
Conclusion
Cloud migration costs are not compared on the price of a virtual machine but across every meter: compute, licences, disks, egress, storage and backup, plus someone who watches them monthly. If you would like us to run the calculation together for your servers and users, with prices checked on the day, book a 30-minute call.
Sources
- Microsoft, Azure Retail Prices API, Standard_D4s_v5 in Germany West Central, EUR, accessed 8 November 2026; the same API for disk, backup, egress, Blob Storage and the Windows licence.
- Microsoft, Azure Bandwidth pricing, Azure Backup pricing and Managed Disks pricing, accessed 8 November 2026.
- Microsoft, Microsoft 365 Business plans and pricing, Ireland, EUR, accessed 8 November 2026.
- AWS, Price List API, AWSDataTransfer, eu-central-1, published 3 November 2026.
- Microsoft Learn, Reservations software costs for Azure, 17 July 2026.
- Microsoft Learn, States and billing status of Azure Virtual Machines.
- Microsoft Learn, Access tiers for blob data, 2 April 2026.
- Microsoft Learn, Pricing model for Microsoft 365 Backup, 4 November 2026.
- Microsoft Learn, Shared responsibility in the cloud, 24 August 2026.
- Microsoft Learn, What is the EU Data Boundary?, 21 July 2026.
- Microsoft Learn, Create and manage budgets, Microsoft Cost Management.
- Regulation (EU) 2016/679 (GDPR), European Parliament and Council, 27 April 2016: Art. 28, 32 and 44.
- Regulation (EU) 2023/2854 (Data Act), European Parliament and Council, 13 December 2023: Art. 25 and 29.
- Commission Implementing Decision (EU) 2023/1795, 10 July 2023: ‘in force’ status checked on 8 November 2026.
- FinOps Foundation, FinOps Framework Phases.