Cloud migration sounds like a project for enterprises with data lakes and cost-optimisation VPs. It isn't. Moving a small business onto cloud infrastructure is one of the most boring, well-trodden projects we do — and the boring version is the safe one. This guide walks through the framed version we use for SMBs: what cloud actually buys you, the honest migration decision, a step-by-step move that avoids the classic data-loss traps, and how to keep the bill from running away.

1. What "Cloud" Actually Buys a Small Business

Ignore the marketing. For an SMB the honest cloud benefits are:

  • Scale on demand. Pay for capacity you need this month, not peak capacity forever. A promotion or a viral post spikes traffic for a day; cloud rides it instead of crashing.
  • Resilience. Managed services (databases, load balancers) that self-heal, plus snapshots for instant rollback.
  • Predictable ops overhead. Providers patch the underlying hardware; you patch your app.
  • Global reach. Serve a visitor in another city/region from a nearby edge, not one server in one city.

The honest cost: cloud bills require discipline. The same elasticity that saves you money can silently spend it (idle servers, over-provisioned DBs, forgotten snapshots). "Cloud is cheap" is only true if someone watches the meter.

2. Should You Migrate? The Three-Question Gate

Before touching anything, run this gate. If you can't answer all three plainly, don't migrate yet:

  1. What's the real driver? Growth? Redundancy? Cutting an expensive server? Get the reason on paper — migrations without a driver drift.
  2. Who operates it? Post-migration someone must handle security updates, monitoring and billing reviews. If that person doesn't exist, part of the project is creating the handover.
  3. What's the downtime budget? Can the business survive 4 hours offline? Overnight? A real answer decides the migration strategy (lift-and-shift vs careful cutover).

3. The Migration: Step by Step (No Data Loss Edition)

This is the exact sequence we follow, every time, because each step protects the one before it:

  1. Snapshot and verify. Take a full backup of the current server: database dump + uploaded files. Then actually test restoring it somewhere. A backup you've never restored is a hope, not a backup.
  2. Build the new cloud environment. Spin up the same OS + stack (we do PHP/CodeIgniter 4, MySQL), matching versions exactly.
  3. Import and run side-by-side. Restore the data onto the cloud VM. Point a staging domain at it intermediatescom and run the whole site — every form, every page, every login — while the old server still serves production. This "shadow run" is where you catch 90% of migration bugs.
  4. Cut over DNS. When the new site is green, lower the DNS TTL, point the records at the new host, and watch logs for 24 hours.
  5. Keep the old server for 30 days as insurance, then decommission it — and only after final backup.

4. Avoiding the Five Classic Cloud Money-Leaks

  • Idle instances. Dev/staging VMs people forget to switch off. Tag instances and auto-shutdown non-production on a schedule.
  • Oversized database. A managed DB sized for "future" costs monthly forever. Right-size to actual load; scale up when metrics earn it.
  • Forgotten snapshots & old volumes. Classic silent billing. Review block storage monthly; delete what you don't need (after verification).
  • No budget alerts. Set billing alarms at 80% of expected spend before the surprise invoice.
  • Moving the whole app "because cloud." You don't need every microservice on Kubernetes. A single VM or two with a managed DB is a completely respectable small-biz cloud. Avoid the chase for complexity.

5. When You Should NOT Be on Cloud (Yet)

Saying "no" to cloud is also part of good advice. You probably shouldn't migrate if: your traffic is flat and predictable, your server is already fat and idle, you have no one to operate the environment, or the whole point is just "it sounded modern." In those cases a well-chosen VPS or shared plan (see our hosting guide) delivers the same site for a fraction of the monthly metering. Cloud is a tool, not a trophy.

If you do decide the move is right, or you just want someone to look at a confusing existing bill, our cloud team handles SMB migrations end-to-end — snapshot, shadow run, cutover, and the ongoing hygiene that keeps the invoice sane.