Moving to the cloud: a step-by-step migration plan
A cloud migration plan for SMEs in five steps: list your applications, choose a path for each, pick a region and provider, move in waves, control costs.


Your server sits in a cupboard, its warranty ran out years ago, and the person who set it up has moved on. Or your hosting contract is up for renewal and nobody knows what runs where. Moving to the cloud can solve these problems, but only with a cloud migration plan that treats each application on its own merits.
Here is that plan in five steps: take stock, choose a path for each application, pick a region and a provider, move in waves, and control costs and security from day one. We also say when staying where you are is the better answer.
This article offers practical guidance. On where your data may be stored, it is no substitute for advice from your lawyer or your data protection officer.
Before you start: is the cloud the right answer?
The cloud is not automatically cheaper or safer. It changes how you pay (a monthly bill instead of new hardware every few years) and who maintains what: the provider looks after buildings and hardware; you remain responsible for your data, accounts, settings and backups.
Moving is worth it when your hardware is ageing, when staff work from several sites, or when nobody in-house can keep a server up to date. It may not be for a stable application on recent hardware, or for software whose licence forbids it: an off-site backup may be all you need for now.
Step 1: list and assess each application
A migration starts with an inventory, not with a provider. For each application, write down:
- what it does and who uses it, in which departments and countries;
- where it runs today: server, operating system and database versions;
- what it is connected to: accounting, email, payment services, other applications;
- how critical it is: how long the business can work without it, and how much recent data it can afford to lose;
- what data it holds, especially personal or confidential data;
- who supports it: someone in-house, a provider or a vendor.
Connections are where migrations go wrong: an application moved alone may stop talking to one left behind, or slow down. Map these links before deciding anything.
If you have no up-to-date picture of your systems, an IT audit produces exactly this inventory, with the risks and priorities.
Step 2: choose a path for each application
Not every application should move the same way. The usual options, often called the “5 Rs”, are these:
| Path | What it means | When it fits |
|---|---|---|
| Rehost (“lift and shift”) | Move the application as it is to a virtual machine in the cloud | It works well and you must leave the server room quickly |
| Replatform | Move it with a few changes, such as a managed database instead of one you maintain | A sound application, but you want less maintenance |
| Refactor | Rework the code to use cloud services | A core application that has to grow or change often |
| Replace | Switch to a SaaS (software as a service) product | A standard need: email, accounting, file sharing |
| Retire | Switch it off and archive its data | Nobody really uses it any more |
Lift and shift is the fastest route, but it moves your problems along with your servers: a fragile application stays fragile, and can cost more to run in the cloud.
Choosing between refactoring, rebuilding in stages and replacing an ageing application is a decision in itself: we explain it in our article on technical debt and modernisation. It is also the heart of our modernisation work.
Don’t overlook “retire”: each unused application you switch off is one less thing to move, secure and pay for.
Step 3: choose a region and a provider
Where your data will live
The major providers let you choose the region where your data is stored, a choice that matters for the law as much as for speed. The rules on where personal data may be stored and sent differ from country to country: the GDPR in the European Union, the Privacy Act in Australia, Law 09-08 in Morocco, and the personal data protection laws of the United Arab Emirates and Saudi Arabia. Some sectors, such as health, finance and the public sector, add their own requirements.
These are general points, as of October 2026: check with a lawyer which rules apply in every country where you have customers or staff. The principles in our article on AI and the GDPR also apply to the data you move.
How to compare providers
Large providers such as Microsoft Azure and Amazon Web Services (AWS) offer similar building blocks; regional hosts suit data that must stay in one country. Compare them on criteria rather than on prices, which change often:
- regions available where your data must stay;
- the managed services you will actually use (databases, backups, user accounts);
- support in your language and time zone;
- how the bill is calculated, and the tools to cap it;
- how easily you could leave: data export, standard formats, as little lock-in as possible.
For a single web application, shared hosting, a VPS or a managed platform may be enough: our comparison of where to host a web app helps you choose.
Open every account in the company’s name, with at least two administrators.
Step 4: migrate in waves
Moving everything in one weekend is the riskiest plan. Group the applications into waves:
- A pilot: a useful but non-critical application, to test the network, accounts and backups.
- Simple applications: those with few connections, often rehosted or replaced.
- Connected groups: applications that talk to each other, moved together so that they stay close.
- Critical applications last, once the team has practised.
For each wave, prepare:
- a test copy in the cloud, checked by its daily users;
- a switch-over date outside busy periods, announced in advance;
- a way back: the old system kept ready until the new one has proved itself;
- a check after the move: data complete, connections working, response times acceptable.
Automating the set-up pays off from the second wave: environments described in scripts can be rebuilt identically. At Orange Business Services, in a project led by our founder, Banque Populaire workstations were set up in one click instead of half a day or more. The same principle applies to servers in the cloud, and to the updates that follow the move: with continuous integration and delivery (CI/CD), each change is tested and deployed the same way every time.
Moving the data
Plan a first full copy, then a final synchronisation on the switch-over day, and compare counts and totals before and after. Clean up first: there is no point paying to store files nobody needs.
Step 5: plan costs and security from day one
Costs
A cloud bill has many small lines: computing, storage, data leaving the cloud, backups, licences. To avoid surprises:
- set a monthly budget and alerts on each account from the first day;
- label every resource with its application and its owner, to see who spends what;
- resize machines after a month of real use;
- compare the total with your real former costs: hardware, electricity, maintenance and staff time.
To see where the money goes once you are running, and keep the monthly bill in check, read our guide to cloud costs.
Security
In the cloud, one wrong setting can expose data publicly. The essentials:
- two-step login on every administrator account, and as few administrators as possible;
- encryption of stored and transmitted data, usually available as standard;
- backups kept separately, and a restore that has actually been tested, as part of a backup and disaster recovery plan;
- a review of access rights after each wave.
A checklist for your cloud migration plan
- Every application is listed with its users, connections, criticality and data.
- Each application has a path: rehost, replatform, refactor, replace or retire.
- The data-location rules have been checked for every country concerned.
- The provider and region are chosen on criteria; accounts are in the company’s name.
- The waves start with a pilot, and each has a test, a date, a way back and a check.
- Budgets, alerts and labels are in place before the first resource is created.
- Two-step login, encryption, backups and logs are switched on.
- The old servers are switched off and wiped only after the new system has proved itself.
Frequently asked questions
How long does a cloud migration take?
It depends on the number of applications, their connections and the volume of data, so we don’t give a figure without knowing your systems. The inventory in step 1 is what makes a realistic schedule possible: each wave can then be estimated on its own.
Is lift and shift a good cloud migration strategy?
It is a good first step when time is short, for example when a server is failing or a hosting contract is ending. It is rarely a good final state: the application keeps its weaknesses and makes little use of what the cloud does well. Plan a second phase for the applications that matter most.
Can we move our servers to the cloud and keep some on-site?
Yes. This is called a hybrid set-up. It is common during a migration and sometimes permanent: for a machine on a production line, software whose licence rules out the cloud, or data that must stay on your premises. The link between the two sides must be secure and fast enough.
In short
A cloud migration plan starts with an inventory, not with a provider. Each application gets its own path, from lift and shift to retirement, and the region is chosen with the data rules of every country concerned in mind. Waves, a pilot and a way back keep the risk under control; budgets and security set from day one protect the bill and the data.
Is your server room ageing, or is a hosting contract about to end? Book a free 30-minute discovery call: we look together at which applications to move first, and how. If it is useful, an audit of your systems, on the basis of a quote, then leads to a detailed migration plan.
Related servicesModernisationSaaS products
Let’s talk about it on a 30-minute discovery call, free and with no obligation.
Get our next articles in your feed: follow AnazTech on LinkedIn.Follow on LinkedIn






