Cloud

Moving to Microsoft 365: a realistic checklist

The pre-migration work that decides whether a cloud move is smooth or miserable, from DNS to mailbox sizes to the pilot group.

15 January 2025 6 min read By the DTMS engineering team
Illustration of servers moving to the cloud, with a ticked migration checklist

Cloud migrations rarely fail because of the technology. They fail because of the things nobody checked first. This is the list we work through before any migration date is agreed.

Before you start

  • Mailbox sizes and item counts — the big ones need a plan.
  • Who has domain control? If the DNS is with a former web designer, sort that first.
  • Every device and where it authenticates from.
  • Line-of-business apps that send email — scanners, CRMs, invoicing. These break most often.
  • Shared mailboxes, distribution lists and calendar delegates.
  • Any device or app still using basic authentication.

During

  • Pilot group of three to five users, including the most demanding one.
  • Migrate out of hours, with the old system kept read-only as a fallback.
  • MFA configured before the first user signs in, not after.
  • Backup running from day one — not "once things settle".

After

  • Two weeks of close support, with a named engineer.
  • Decommission the old server only after a full verification, not on the Monday.
  • Written record of the new setup, so the next person can pick it up.

More on our cloud and backup services.


Written by the engineers at DTMS Tech Solutions. We support businesses and homes across London, Essex and the South East — ask us anything.

Not sure what you need? Ask a real engineer.

Free 20-minute consultation, no jargon and no obligation. We will tell you honestly whether you need us — and if you don't, we will say so.

Book a consultation