What a realistic cloud migration looks like for an SME
Lift-and-shift is not a strategy. A deliberate migration right-sizes workloads, fixes identity, and documents what runs where.
The Stark Nexus
04 November 2026 · 1 min read
Cloud migration fails quietly. The servers move, the bill goes up, and nobody can explain what changed. Avoiding that outcome is mostly about sequencing.
Start with identity, not servers
Before a single workload moves, consolidate accounts, enforce multi-factor authentication and define who administers what. Identity is the control plane for everything that follows.
Classify workloads honestly
- Lift and shift: acceptable for short-term stability, rarely optimal long term.
- Replatform: move to managed database and object storage services without rewriting the application.
- Retire: the cheapest migration is deleting a system nobody uses.
Plan for the boring parts
DNS cutovers, TLS certificates, backup verification, monitoring and cost alerts are what make a migration feel calm. Schedule them explicitly rather than discovering them during the cutover window.
Measure after, not just during
Track availability, response times and monthly spend for at least a quarter. A migration that improves resilience but doubles cost without a business reason is not a success.