Cloud or your own server: compare costs, security and exit, then migrate in steps

How to compare the cloud and your own hardware on cost, security, data location and exit, and then move one application at a time.

In this topic: IT and data 18

A new server arrives as one quote with one large number on it. The cloud arrives as a monthly fee that looks modest beside it. Side by side, the cloud seems cheaper, yet over the life of that server it can just as well cost more. Deciding on the cloud or your own server means comparing the same period, the same work and the same risks, and knowing how you would get out again.

For many organisations the choice is due now: Microsoft's extended support for Windows Server 2016 ends in January 2027 (source: Microsoft, June 2024). A business unit may face it for the last application in its own server room, an accountant when a client asks which quote to sign.

In short

Compare a server and the cloud on total cost over the same period, never a purchase price against a monthly fee. In every cloud model your data, accounts and access remain your responsibility. Agree the way out before you sign, keep on your own hardware only what truly needs it, and move one application at a time.

  • Costs
  • Security
  • Data location
  • Exit
01 The options

Cloud or on-premises: the options in plain words

The cloud is not one thing. The options run from hardware you own to software you only sign in to, and most organisations already use several.

Six ways to run your ITFrom most to least that you manage yourself.
OptionWhat it isWhat you still manage
On-premisesYour own server in your own buildingEverything, from hardware and power to security and backup
ColocationYour own server in a provider's data centre, which supplies space, power and coolingThe hardware and everything on it
IaaS (infrastructure as a service)Rented virtual serversVirtual serverA server that runs as software on shared physical hardware, so you rent capacity instead of buying a machine., storage and network, paid by useOperating systems, storage and applications (source: NIST, September 2011)
PaaS (platform as a service)A ready platform, such as a managed databaseYour applications and their settings (source: NIST, September 2011)
SaaS (software as a service)A finished application in the browser, such as online accountingSome user settings, plus your data and users (source: NIST, September 2011; Microsoft, August 2026)
HybridPart on your own hardware, part in the cloud, linked togetherEach part, plus the links

In many organisations email and office software already run as SaaS, so the real decision is about what still lives on the server.

02 Costs

Cloud vs on-premises costs: compare the same period

A server is paid mostly up front, the cloud month by month. Only a comparison over the same period, with every cost on both sides, shows which is cheaper.

Work out the TCOTCO (total cost of ownership)Every cost of an option over the same period: purchase or migration, licences, management, energy, backup, replacement and the cost of leaving. of each option over the years you would use a new server, for example five. Server side: hardware, licences, installation, maintenance, management, backup, energy and the replacement at the end. Cloud side: migration and a period of running both, subscriptions, management, backup of cloud data, a second internet line and the cost of leaving. Count your own staff time on both sides too.

In this fictional example, in thousands of euros (the logic works in any currency), the cloud is cheaper for two years because there is no purchase. From year three the server is cheaper, and after five years the gap is €20,000.

Two assumptions can reverse that. If the move cuts the IT partner's fee from €9,000 to €4,000 a year, the cloud ends €5,000 cheaper. If subscriptions rise 5% a year from year two, the gap grows to about €32,000. And after year five the server needs replacing.

Own server Cloud € thousand, cumulative 240180120600 Year 1Year 2Year 3Year 4Year 5 206 186
Where the lines cross. Cumulative cost in the worked example: the cloud leads for two years, the own server is cheaper from year three.
Worked example: five-year TCOFictional accounting firm with 40 staff, amounts in € thousand.
Cost itemOwn serverCloud
Hardware, storage and licences, one-off52none
Installation or migration and training, one-off926
Extra storage in year four5none
Hardware maintenance, yearly3none
Subscriptions, yearlynone22
IT partner management, yearly159
Backup, yearly43
Energy and space, yearly2none
Second internet line, yearlynone2
Total over five years186206
03 Security and availability

Cloud security: who manages which layer

The cloud is not automatically safer or less safe than your own server. What changes is who does what, layer by layer.

On-premIaaSPaaSSaaS Data andsettings Accountsand access Devices Applications Networkcontrols Operatingsystem Hardware,data centre YouYouYouYou YouYouYouYou YouYouYou YouYou YouYou YouYou You SharedSharedSharedShared ProviderProviderProviderProviderProviderProvider the provider takes over more
Who manages which layer. Based on Microsoft's model for its own cloud (source: Microsoft, August 2026). The top rows stay yours in every model; ask each provider for its own split in writing.

Microsoft states that in every cloud model four things stay yours: the data, the devices that connect, user accounts and access management, including multi-factor authenticationMulti-factor authentication (MFA)Signing in with a second step besides the password, such as a code or an approval in an app on your phone. (source: Microsoft, August 2026). The UK NCSC's cloud security principles make a practical checklist for questioning a provider (source: UK NCSC, June 2023).

Availability and the internet line

When the internet fails, a server in the office keeps working; in the cloud the office stops, though people at home carry on. Translate the availability in the provider's service level agreement (SLA) into time. A worked example: 99.9 percent over a 30-day month allows about 43 minutes of downtime. If the cloud becomes your only workplace, add a second internet line from another provider or over the mobile network, and check whether the provider's backup matches your needs: see backup and recovery.

04 Data location

Where your data lives: transfer rules and sovereignty

Cloud data still sits on physical servers in a particular country. The laws of that country, and of the provider's home country, can reach it.

The UK NCSC advises knowing where your data is and who can access it, and identifying the legal jurisdictions it could be subject to; a jurisdiction may be able to request your data from the provider (source: UK NCSC, June 2023). That is data sovereignty in practice: which government can, in the end, reach your data. Rules differ by country and sector, but they share one principle: when personal data goes abroad, your responsibility travels with it.

Examples of transfer and sector rulesPrinciples only. Check the rules where you operate and take legal advice for your situation.
WhereRule and what to ask
EU and EEAPersonal data may leave when protection travels with it, for example through an adequacy decision or standard contractual clauses (source: European Commission, November 2026). Ask where data is stored and accessed, and which transfer tool applies.
AustraliaTake reasonable steps so an overseas recipient does not breach the privacy principles; you can stay accountable for its acts (source: OAIC, June 2019). Limit in the contract what the provider may do with the data.
CanadaProcessing abroad is allowed, but you stay accountable, need comparable protection and should be open about it (source: Office of the Privacy Commissioner of Canada, January 2009). Mention it in your privacy notice.
US health sectorA cloud provider that stores protected health information for you needs a business associate agreement, even if it holds only encrypted data without the key (source: US HHS, December 2022). No agreement, no cloud for that data.
EU, non-personal dataProviders are expected to take reasonable measures against unlawful access by non-EU governments to data held in the EU (source: European Commission, December 2025). Ask which measures the provider publishes.

The EU's adequacy list includes, among others, the United Kingdom, Japan, Brazil and US companies in the EU-US Data Privacy Framework (source: European Commission, November 2026). Check your customer contracts too, because a client may require data to stay in one country. For the GDPR side, see data protection in practice.

05 Lock-in and exit

Vendor lock-in, egress fees and your exit plan

The more you build on one provider's own services, the harder it is to leave. That is a reason to arrange the exit before you sign.

Lock-in is partly technical, features and interfaces that differ per provider, and partly commercial: egress feesEgress feeA charge a cloud provider makes for data leaving its network, for example when you move your data to another provider or back to your own server.. The UK Competition and Markets Authority found that egress fees and barriers to interoperability limit customer choice in cloud services (source: UK CMA, March 2026).

In the EU, the Data Act, which has applied since 12 September 2025, sets minimum terms for cloud contracts and requires platform and software providers to offer open interfaces and export data in a commonly used, machine-readable format (source: European Commission, December 2025). Switching charges, including egress charges, disappear from 12 January 2027; until then providers may still charge the costs they incur (source: European Commission, December 2025). For EU financial entities, DORA, the EU regulation on digital operational resilience, adds exit strategies with mandatory transition periods (source: EUR-Lex, December 2022).

  • Data export: which data, in which format, and when you last tested an export.
  • Your own copy: a recent backup outside the provider, under your own accounts.
  • Notice and transition: notice periods, how long the service runs during a switch, when data is deleted.
  • Costs of leaving: egress and other charges, and who pays for the work.
  • Dependencies: integrations, sign-in and provider-specific features to replace.
  • Owner: one person who keeps the plan current at each renewal.
06 Own hardware

When an on-premises server still makes sense

Some workloads are better off on hardware you control, at least for now.

Speed of response

A production machine, a CAD workstation or large local files can need answers within milliseconds. Then latencyLatencyThe delay between a request and the answer, for example between a machine in the factory and the server that controls it. decides.

Legacy software

An old industry package, heavy custom code or a licence tied to the hardware may not be supported in the cloud. Ask the supplier and decide per application.

Specialised hardware

Measuring instruments, USB licence keys and production scanners must be physically connected, so the system that drives them stays close by.

Steady loads

Paying per use rewards workloads that grow or peak. A server running at the same level for years gains little from that, and the TCO can favour owning it.

Microsoft's migration guidance tells you to retain workloads that cannot move because of regulatory constraints, technical dependencies or business continuity requirements (source: Microsoft, July 2025). Hybrid is then an end point rather than a phase: SaaS for office work, one small local server for what needs it. The price is double management and two backups, so keep the local part small and document the links.

07 Migration

Cloud migration in five steps

Move per application, not in one weekend. Each step ends with a result you can check.

adjust 12345 InventoryClassifyPilotMigrate in wavesDecommission everything on the servera route per applicationone application or teamwith a fallback readyafter a restore test
A migration in five steps. What the pilot teaches goes back into the plan before the waves start.

Start with an inventory of everything on the server: applications, data, users, integrations, licences and contract end dates, each with an owner. Then give every application a route. Microsoft's Cloud Adoption Framework offers, among others, these routes: retire what no longer adds value, rehost with minimal changes, replatform to a modern hosting environment, replace with SaaS, or retain (source: Microsoft, July 2025).

Pilot with one application or team and test the dull things: printing, scanning, integrations, month-end reports. Migrate in waves outside month-end, with a fallback and one named person who decides to use it. Switch the old server off only after a successful restore test, and have its disks wiped or destroyed securely. More choices like this are in IT and data.

Quick scan

Are you ready to choose between cloud and your own server?

Eight statements from this guide. Answer them for your organisation and see what to settle before you sign.

  1. 1We compare the server and the cloud over the same period, with every cost on both sides.
  2. 2For each cloud service we know which layers we still manage ourselves.
  3. 3Every account in our cloud services signs in with a second step, such as a code on a phone.
  4. 4We know in which countries our data is stored and which laws can reach it.
  5. 5Our contracts state how we get our data back, in which format and at what cost.
  6. 6We have tested exporting the data from our most important cloud service.
  7. 7We know which workloads must stay on our own hardware, and why.
  8. 8Every application on the current server has an owner and a chosen route.
Read next

Related guides

Toolkit

Cloud comparison worksheet and migration plan outline

Below you will find a worksheet that scores own server, cloud and hybrid on ten weighted criteria, filled in for an example accounting firm, and a migration plan outline with the deliverable, owner and finish line of each phase.

Questions

Frequently asked questions

Does moving to the cloud always save money?
No. It avoids a large purchase and scales easily, but the fees run for as long as you use the service. Only a TCO over the same period, including migration, management and exit, shows which option is cheaper.
Is our data safer with a large cloud provider?
Not automatically. The provider looks after the data centre and, depending on the model, the platform. Accounts, access, settings and the data itself remain your job.
Do we still need a server if email and files are already online?
Often not, but check what else runs on it: an old application, shared folders, printer settings or the management of user accounts. It can go once each of those has a new home and a restore test has succeeded.
Can we move back to our own server later?
Yes, but it is a migration in its own right. The less you depend on features found at one provider only, and the more often you export your data in a standard format, the easier it is.