For many organisations still running email on an ageing on-premise server — or juggling personal email accounts and free mail services — Microsoft 365 is the natural next step. But a migration touches every person in the organisation, so planning matters more than technology. Here is how to approach it.

Step 1: Sort out licensing before anything else

Microsoft 365 is licensed per user, and the plans differ in meaningful ways — mailbox size, desktop applications versus web-only apps, security and compliance features. Before choosing:

  • Count your real users. Distinguish full-time staff who need desktop Office apps from occasional users who may only need webmail and Teams.
  • Match plans to roles. Paying for capabilities some users will never use wastes budget; under-licensing power users creates friction later.
  • Check device realities. Older machines may struggle with the latest desktop applications; web-based apps can be a pragmatic interim step.

Getting licensing right up front avoids mid-project surprises and re-work.

Step 2: Plan the migration in stages

A mailbox migration is more than copying email. Each stage has its own questions:

  1. Inventory what exists. Every mailbox, shared folder, distribution list and domain needs to be accounted for before anything moves.
  2. Clean up first. Old mailboxes for departed staff, duplicate contacts and abandoned folders should be resolved before migration — moving clutter costs time twice.
  3. Choose the migration path. The right approach depends on your current mail platform, data volume and tolerance for downtime. A staged (batch) cutover suits most organisations better than a single big-bang switch.
  4. Pilot with a small group. Migrate a handful of representative users first, confirm everything works, then proceed in waves.
  5. Cut over deliberately. Communicate the switch date clearly, migrate final data, update DNS records, and keep support close at hand during the first days.

Domains, DNS and any other hosted email services also need coordinated attention so that mail flows uninterrupted after the switch.

Step 3: Take adoption seriously

The technical migration can be flawless and the project can still disappoint — if people do not change how they work. Adoption is where the value is:

  • Show the difference, not just the tools. Focus training on what improves: shared calendars instead of phoning reception, co-authoring documents instead of emailing attachments, chat instead of walking between offices.
  • Train in role-sized sessions. A short practical session per team beats one long generic presentation.
  • Provide follow-up support. Questions surface in week two, not day one. Plan for a support channel after go-live.
  • Identify champions. One enthusiastic user per department answers most questions before they reach IT.

The payoff

Done well, a Microsoft 365 migration replaces server maintenance worries with a platform that stays current, works across devices and gives your team modern collaboration tools. The organisations that benefit most are not those with the biggest budgets, but those that planned licensing, staged the migration and invested in their people.