Skip to content
DT Nova

Cloud migration cost: what moving to the cloud really costs

Cloud migration cost has two parts that are easy to mix up: the one-time work of moving systems and data, and the running cost of the cloud services afterwards. The first is set by how many systems move, how each one moves, how much data travels and how much downtime is acceptable. The second is set by how well the new environment is sized and looked after. This guide explains both, the hidden costs, the pricing models for migration work, and how to compare quotes.

It does not quote our own prices. It explains how a migration budget is built, so any quote you receive, from us or from anyone else, makes sense. For how we run migrations, see cloud migration consulting; for keeping data in the EU, see our guide to sovereign cloud.

The short version

  1. Assessment: list every system, decide how each one moves, and estimate its running cost in the cloud.
  2. Migration work: building the target environment, moving systems and data, testing, cut-over and fixing what breaks.
  3. Double running: paying for old and new environments at the same time during the move.
  4. Running costs: cloud services, licences, backups, monitoring and the work of keeping spending under control.

Cloud is now the norm

According to Eurostat, 52.74% of EU enterprises used paid cloud computing services in 2025, mostly for email, office software and file storage, up 7.42 percentage points from 2023 (Statistics Explained, "Cloud computing: statistics on the use by enterprises", data extracted January 2026, read 12 November 2026). The easy services have moved for many companies; the harder and more expensive part is business systems, databases and the integrations between them.

How each system moves sets the cost

ApproachWhat happensCost profile
RehostThe system moves as it is to cloud serversLeast migration work; running costs may stay high if nothing is resized
ReplatformSmall changes, such as a managed database instead of a self-run oneSome extra work; lower running and maintenance effort
RefactorThe system is reworked to use cloud services properlyMost work up front; best fit and often lowest running cost
ReplaceA ready-made cloud service replaces the systemSubscription and data migration instead of a move
Retire or retainThe system is switched off, or stays where it isOften the cheapest decision of all

What drives the one-time cost

  • Number of systems and how tightly they are connected.
  • Data volume and how it is moved: over the network, in stages or with a final synchronisation.
  • Downtime allowed. A weekend cut-over is simpler than a move with no interruption.
  • Security and compliance: identity, encryption, network design, logging and where data may be stored.
  • Licences. Some software is licensed differently in the cloud, which can change both cost and design.
  • Documentation. Undocumented systems need investigation before they can move.
  • People's time. Migration is labour, and labour costs follow location. Eurostat puts average hourly labour costs across the whole economy in 2025 at €34.9 in the EU and €38.2 in the euro area, from €12.0 in Bulgaria to €56.8 in Luxembourg (release of 31 March 2026, read 12 November 2026).

Running costs after the move

Cloud bills follow use. The usual items are compute, storage, databases, data transfer out of the cloud, backups, monitoring and support plans. They stay under control when systems are resized after the move, development environments are switched off when unused, storage is tiered, and someone reviews the bill each month against a budget. Without that review, a migration that was meant to save money can cost more than the servers it replaced.

Hidden costs of cloud migration

  • Double running of old and new environments for weeks or months.
  • Data transfer charges, especially for moving data out again.
  • Systems that do not move well and need refactoring after all.
  • Training for the people who run and use the new environment.
  • Integration fixes when connected systems expect the old addresses or networks. See API integration cost.
  • Data clean-up found during the move. See data migration cost.

The cost of leaving, and EU rules that lower it

Plan the exit when you plan the entry. Under the EU Data Act, contracts for data processing services must set out switching rights in writing, including a maximum notice period of two months and a transitional period of up to 30 calendar days for the switch (Regulation (EU) 2023/2854, Article 25). From 12 January 2027, providers may not charge switching fees for the switching process, and until then may charge only reduced fees no higher than their direct costs (Article 29). Both read on 12 November 2026; see our guide to the EU Data Act.

Pricing models for migration work

ModelHow it worksWho carries the risk
Fixed-price assessmentAn agreed price to list systems, choose approaches and estimate running costsSmall, known commitment for the buyer
Fixed price per system or waveEach system or group priced after assessmentShared; each step is based on evidence
Time and materialsHours billed as workedThe buyer carries overrun risk
Managed service afterwardsA monthly fee to run the new environmentDepends on the written scope; see managed IT services cost

How to compare migration quotes

  • Which systems are in scope, and which approach is proposed for each?
  • Is there an estimate of monthly running costs per system after the move?
  • How is data moved, and how much downtime is planned?
  • Who tests, and what is the rollback plan if a cut-over fails?
  • Are security set-up, backups and monitoring included?
  • How long do old and new environments run in parallel?
  • Are cloud accounts, keys and data in your company's name, in EU regions?
  • What is excluded, in writing?

Ways to spend less without cutting quality

  • Retire first. Every system switched off is a system you do not move.
  • Move in waves. Start simple, learn, then move the harder systems.
  • Resize after moving. Measure real use and shrink what is oversized.
  • Set a budget alert on day one, and review the bill monthly.

Whether a system should move at all is covered in cloud vs on-premise. To compare platforms before the move, read how to choose a cloud provider. All our services are on the services page, and every guide is in the guides library.

Questions people ask

How much does cloud migration cost?

It depends on how many systems move, how each one moves (as it is, with changes, or rebuilt), how much data must be transferred, how much downtime is acceptable and what security and compliance rules apply. Moving file shares and email is a very different project from moving a business system with integrations and a database. Any figure given before the systems are listed and assessed is a guess.

Does moving to the cloud save money?

Sometimes. Savings come from not buying and replacing servers, paying only for what is used and spending less time on hardware. Costs can rise when systems are moved without resizing, when resources are left running, or when data transfer and premium services are not watched. A cost estimate per system, and a review after the move, show which is the case.

What are the hidden costs of cloud migration?

Running old and new environments side by side, data transfer charges, licences that are priced differently in the cloud, retraining staff, refactoring systems that do not run well as they are, and the ongoing work of watching and tuning cloud spending.

Can cloud migration costs be capitalised?

That is an accounting question that depends on your framework and on what is being built or configured. Ask your accountant or auditor before the project, because the treatment of configuration work in cloud services differs from that of software you own.

How long does a cloud migration take?

Moving email and files for a small company can take days. Moving business systems takes longer: each needs an assessment, a test move, a cut-over plan and a check afterwards. Moving in waves, starting with the simplest systems, lowers risk and spreads cost.

Sources

Your cloud migration scope checklist

  • Every system and server today, with its owner and purpose.
  • How systems connect to each other and to outside services.
  • Data volumes and how fast they grow.
  • Downtime each system can accept.
  • Where data may be stored, and any security or sector rules.
  • Licences and how they apply in the cloud.
  • Systems that could be retired or replaced.
  • Who runs the environment after the move.
  • A monthly running-cost budget.
  • Ownership: accounts, keys and data in your company's name.