Cloud Migration for SMEs: Lift-and-Shift vs. Replatform vs. Leave It
Decide per workload, not per company. Lift-and-shift gets you off dying hardware fast but keeps every old problem — and unoptimized, it often costs more than the old server. Replatforming to containers plus a managed database is the usual sweet spot. Stable, isolated, near-end-of-life systems are best left alone. Budget €15,000–€60,000 over 2–4 months for a typical SME migration, and never move everything in one weekend.
The trigger is usually a server rack out of warranty, or a hosting contract nobody remembers signing. Then someone says "let's move it all to the cloud" — which is really three different decisions wearing one trench coat.
Lift-and-shift, replatform, or leave it?
| Option | What it means | Best for | The catch |
|---|---|---|---|
| Lift-and-shift | Copy VMs as-is to cloud VMs | Deadline pressure, dying hardware | Keeps old problems; oversized VMs often cost more than the old server |
| Replatform | Containers + managed database | Apps you actively develop | Real engineering work up front |
| Leave it | Keep it where it is | Stable, isolated, near-end-of-life systems | Needs a named owner and an end date |
The part that surprises people: lift-and-shift frequently raises the monthly bill. Cloud pricing rewards elasticity, and a 1:1 copy of an on-prem VM sized for its worst day is the opposite of elastic. Replatforming pays off because managed databases take patching, backups, and failover off your plate, and containers let you rightsize honestly.
What order should you migrate in?
Inventory first: every system, its owner, its data. Then map dependencies — the ERP that quietly reads from the file server is the thing that ruins migrations. Then pick one low-risk workload, migrate it, run old and new in parallel, compare outputs for a week or two, and cut over.
Repeat with the next workload. The classic failure mode is the opposite: migrating everything at once over a weekend. That compresses all your risk into 48 hours with no fallback, and Monday morning becomes an incident review. Sequenced migrations are slower on the calendar and dramatically faster in practice.
The homework: licenses, DSGVO, data location
Before anything moves, three unglamorous checks. Software licenses — some on-prem licenses don't transfer to cloud VMs. Processor agreements — a DSGVO-compliant Auftragsverarbeitungsvertrag with the new provider, before customer data lands there. Data location — if your contracts promise data stays in Germany or the EU, pick regions (or an EU provider) accordingly. All three are cheap to fix before migration and expensive after.
What does an SME cloud migration cost?
From our projects: €15,000–€60,000 over 2–4 months, depending on how many workloads move and how tangled the dependencies are. Lift-and-shift sits at the low end but leaks money monthly; replatforming costs more up front and is usually cheaper by the end of year one. Either way, plan the cost-optimization pass for a few months after cutover — that's when the real usage data exists.
We run SME migrations exactly this way — inventory, sequence, parallel run, cutover — as part of our cloud & DevOps engagements.
Olio on LinkedIn
