Cloud migration consulting: a plan per system, then a tested move
Cloud migration consulting for companies that run servers, file shares or line-of-business software in an office, a data centre or a hosting contract they have outgrown. We map what you run, decide for each system whether to move, replace, rebuild or retire it, keep your data in EU regions, and run the cutover with a tested way back. Independent advice, no reseller commissions, and every account in your company's name.
- No minimum contract: book a few hours or a full project
- Scope agreed in writing before work starts
- Independent advice: no reseller commissions
Who our cloud migration consulting is for
Our cloud work is for small and mid-size companies with a server room or a hosting contract nearing renewal, companies whose on-premises software is out of support, teams that moved email to the cloud years ago but still run file and application servers locally, and companies that have already moved some systems and want the rest done properly. The trigger is often concrete: hardware at the end of its life, a security incident, an audit finding, a merger, or a supplier that stops supporting the version you run.
Start with an inventory, not a provider
The most common mistake in a cloud migration is choosing a provider before knowing what will be moved. We start with an inventory: every server, application, database, file share, scheduled job and integration, who uses it, what it depends on, what it costs today and what happens if it stops for an hour. Systems nobody can explain are the most important ones to find. That inventory usually removes a share of the work at once, because some systems turn out to be unused or duplicated. Only then does the choice of platform make sense, and our guide on how to choose a cloud provider gives the criteria.
Seven ways to handle each system
Not every system should be moved the same way. AWS's prescriptive guidance on migration strategies (read 11 November 2026) names seven, known as the 7 Rs, and the vocabulary is useful whichever cloud you choose:
| Strategy | What it means | When it fits |
|---|---|---|
| Retire | Shut it down and archive the data | No business value left, or nobody uses it |
| Retain | Keep it where it is, with a date to revisit | Recently upgraded, special hardware, or not ready |
| Rehost | Move it unchanged, "lift and shift" | Many servers, a deadline, little time to change code |
| Relocate | Move a platform as a whole, such as a virtualisation cluster | Large estates already on a platform the cloud offers |
| Repurchase | Replace it with a SaaS product | Standard needs, such as accounting, CRM or HR |
| Replatform | Move with targeted changes, such as a managed database | Lower running and maintenance effort without a rewrite |
| Refactor | Rebuild it to use cloud-native services | The system holds the business back, and the case is clear |
The same guidance notes that refactoring is the most complex and costly strategy and recommends moving first and modernising afterwards in large migrations. For a smaller company the logic is the same: change one thing at a time, so that when something goes wrong it is clear what caused it.
Your data stays in the EU
For a European company, where data sits and who can reach it is part of the design, not a setting. We choose EU regions for every service that stores or processes personal data, and check the places that are easy to miss: backups, logs, monitoring, email relays and the provider's support access. Where a US provider is used, the GDPR transfer basis is documented. The European Commission adopted its adequacy decision for the EU-US Data Privacy Framework on 10 July 2023, which covers transfers to certified US companies (read 11 November 2026). We record which basis each service relies on, so your data protection officer can answer the question in one document.
When data location alone is not enough and jurisdiction matters too, our sovereign cloud guide explains the options.
Plan the exit before the entry
Switching cloud providers has historically been expensive, mostly because of data egress fees and proprietary services. The EU's Data Act (read 11 November 2026) changes that. It applies from 12 September 2025, requires providers to remove obstacles to switching and to let customers export data in a commonly used, machine-readable format, and allows reduced switching and egress charges only until 12 January 2027, after which switching charges are removed entirely.
The law helps, but design decides how easy a move really is. We describe infrastructure as code, keep data in open formats, prefer services with equivalents at other providers where the trade-off is reasonable, and write the exit route into the migration plan. Your company can then change provider, or bring a system back in-house, without starting from zero. Whether a system belongs in the cloud at all is weighed in our cloud vs on-premise guide.
The EU rules on switching, notice periods and the end of switching charges are explained in our EU Data Act guide. When the move means a new system rather than the same one in a new place, the data itself has to be moved and checked; that is our data migration service.
Cost: an honest estimate per system
Cloud resources are billed for every hour they run, so a server copied unchanged from a basement to the cloud often costs as much or more than before. Real savings come from retiring unused systems, right-sizing what remains, switching off test environments outside working hours, reserving capacity for steady workloads and moving to managed services that replace maintenance work. We estimate the running cost of each system in the target cloud before you decide, compare it with what you pay today, including hardware renewal and the hours your staff spend on maintenance, and set budget alerts from the first day. Our guide to cloud migration cost explains the one-time and running costs in more detail.
File servers, email and line-of-business software
For many smaller companies, the migration is less about servers and more about three familiar things. File shares move to SharePoint, OneDrive or Google Drive, with folder permissions cleaned up on the way, because copying twenty years of inherited access rights into the cloud copies the problem too. Email and calendars are usually in the cloud already; if not, they move first, with the domain and DNS in your company's name. Line-of-business software, such as accounting, ERP or industry-specific systems, is the hardest part: the supplier may offer a cloud version, may support hosting on a cloud server, or may not support either. We check each supplier's position in writing before the plan is final, so a licence or support term does not surprise you in the middle of a cutover.
Security from the first account
- Cloud accounts and the billing relationship in your company's name, never in a supplier's.
- Multi-factor authentication for every administrator, single sign-on where you already have it, and no shared logins.
- Separate environments for production and testing, with least-privilege roles.
- Backups that are tested by restoring them, kept apart from the production account.
- Logging and alerts for sign-ins, permission changes and unusual spending.
How the migration runs
- Inventory and goals. What you run, what it costs, what must not stop, and why you are moving.
- Written migration plan. A strategy per system, target architecture, EU data residency, cost estimate, risks, order of moves and the exit route. You can take this plan to any supplier.
- Landing zone. Accounts, identity, networking, backups and logging set up before the first workload arrives.
- Pilot move. One low-risk system first, to prove the method and the rollback.
- Waves and cutovers. Systems moved in planned groups, each with a rehearsed cutover and a tested way back.
- Decommission and hand over. Old servers switched off, contracts ended, documentation and admin access handed to your team or your IT partner.
Cloud migration or managed IT?
A migration is a project with an end. What runs afterwards needs an owner: patching, backups, monitoring, user changes and cost reviews. Some companies have an IT team that takes it over; others hand it to a partner. If you want us to look after the environment once it is moved, see managed IT services or co-managed IT if you keep your own IT staff. For a broader review of your systems and suppliers before deciding, see IT consulting. Software that is too old to move and too important to retire may need a rebuild: see custom software development. See prices.
Questions we get
Which cloud do you recommend?
The one that fits your systems, skills and contracts. For a company already on Microsoft 365, Azure is often the natural home for servers; for others AWS, Google Cloud or a European provider fits better. We have no reseller agreement with any of them, so the recommendation is not tied to a commission.
Will moving to the cloud save money?
Sometimes, not always. Moving servers unchanged often costs about the same or more, because cloud resources are billed every hour they run. Savings come from retiring what nobody uses, right-sizing what remains and moving to managed services. We estimate running costs per system before you decide, and compare them with what you pay today.
How do you keep our data in the EU?
By choosing EU regions for every service that stores or processes data, checking where backups, logs and support access go, and documenting it for your data protection records. Where a US provider is used, the transfer basis is written down as the GDPR requires.
Can we move without downtime?
For most systems the downtime can be reduced to a short planned window, outside business hours. Data is copied and kept in sync before the switch, the cutover is rehearsed, and a tested way back is ready if something fails.
Do you do the migration or only the plan?
Both. Some clients want a written plan their own IT team or supplier carries out; others want us to run the migration. Either way the plan comes first, and you decide after reading it.
What about leaving a cloud provider later?
The EU Data Act requires cloud providers to remove obstacles to switching and, from 12 January 2027, to stop charging for it. We still plan the exit route at the start: data formats, infrastructure as code and contracts that let you move again.
Get a written quote
Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.