Book your free demo

Server to cloud migration checklist for small and mid-sized businesses

Moving the office server, ERP or file shares to the cloud goes well when the boring parts are done first: knowing what you have, testing the move, and having a way back. Here is the checklist, from inventory to the first month after.

Updated · 7 min read

The short answer

List every system and what depends on it, choose for each one whether to move it as is, rebuild it or replace it with a SaaS tool, set up security and backups in the cloud first, rehearse the move with a copy, then cut over on a quiet day with a tested rollback plan.

Before the move

  • Inventory: servers, apps, databases, file shares, licences, and who uses each
  • Dependencies: which app talks to which database, printer, scanner or device; what runs on schedules
  • Decide per system: lift and shift, rebuild on managed services, or replace with SaaS
  • Size from real usage (CPU, memory, disk, bandwidth), not from the old hardware
  • Licences: check that Windows, SQL Server and ERP licences can move to the cloud
  • Choose the region and confirm any data location rules
  • Agree downtime windows with the business

Build the landing zone

  • Accounts or subscriptions separated for production and testing
  • Single sign-on and multi-factor authentication for every admin
  • Network: private subnets, VPN or private link to the office, no databases on the public internet
  • Backups and monitoring switched on before any data arrives
  • Budget alerts so a mistake does not become a large bill

The move

  • Rehearse with a copy of production and time each step
  • Test with real users: login, printing, reports, integrations, month-end jobs
  • Freeze changes on the old system before cut-over
  • Transfer the final data, switch DNS and connections, and check from a user’s desk
  • Keep the old server running, read-only, until the rollback window ends

The first month

  • Check backups by restoring one, not by reading the report
  • Right-size machines after two weeks of real usage
  • Review the bill weekly for the first month
  • Turn off and securely wipe the old hardware once you are sure
  • Write down what was done, so the next person can run it

Move to the cloud without the surprises

keyt plans and runs cloud migrations for SMBs in the Gulf and Egypt: the right region, a tested cut-over, and backups you have actually restored.

Questions people ask

Still have a question?

Ask us directly
How long does a small business server migration take?

For a few servers and standard apps, two to six weeks including planning and testing. The cut-over itself is often a weekend.

Should we lift and shift or rebuild?

Lift and shift is fastest and fine for stable apps. Rebuild on managed databases and services when you want lower maintenance or better resilience. Replace with SaaS when a good one exists for the job, such as email or file sharing.

Will the cloud be cheaper than our server?

Not always. It usually costs more per month than hardware you already own, but less than replacing it, and it removes power, cooling and maintenance work. Right-sizing and reserved pricing make the biggest difference.

More guides on this topic

Book your free demo

Send a few details and we will reply within one business day with a time for your demo or call.

What would you like?
What do you need help with? Choose any that apply

What are you trying to fix or build? Include any deadline.

Optional. For example: weekdays after 2 pm your time

We only use these details to reply to you. Privacy policy