Moving your business email to Microsoft 365 is one of those projects that feels terrifying and turns out to be very doable - provided you plan it rather than wing it. Email is the lifeblood of most firms, so the fear is understandable: lose access for a day and the phones start ringing. The trick is a staged migration where mail keeps flowing throughout and nothing is switched over until it is proven. Here is the path, step by step, so you arrive on the other side with no lost messages and no nasty surprises.
Before you touch anything: take stock
Most migrations that go wrong, go wrong because of what was not checked beforehand. An hour of stock-taking now prevents days of firefighting later. Build a simple inventory of what you are actually moving.
- •Every mailbox and its rough size, plus any shared mailboxes, distribution lists and aliases people rely on.
- •Where mail lives today - an old on-premises Exchange server, a hosting provider's POP/IMAP, or another cloud platform - because that decides the migration method.
- •Who controls your domain name and its DNS settings, since the final switch happens there - and if nobody knows, find out now, not on cutover day.
- •Anything connected to email: shared calendars, the website contact form, the accounting system that sends invoices, scanners or alarms that email alerts.
Pick the right licence and plan the destination
Microsoft 365 is not one product but a family of plans, and picking the wrong one means paying for features you will never use or missing ones you need. Match the plan to how people actually work - some staff may need only email and the web apps, while others need the full desktop Office suite, and you can mix licences across the team.
It is worth understanding what you are buying beyond mailboxes, because security and compliance features differ sharply between tiers. Our guide to Microsoft 365 versus a one-off Office explains the subscription model in plain terms, and the deeper, cost-optimised licensing decision - which matters once you have more than a handful of users - is covered in our Microsoft 365 licensing optimisation guide.
Set up the tenant and prove it before cutover
Your Microsoft 365 'tenant' is your private space in the service, and you set it up fully before moving a single live mailbox. Create the accounts, configure security settings, and - critically - verify your domain inside Microsoft 365 without yet redirecting your live mail to it. This lets you build and test in safety.
This is also the moment to get security right from the start, while it is easy: switch on multi-factor authentication for every account (our MFA rollout guide shows how to do it smoothly), and plan how you will back the data up, because - as many firms learn the hard way - Microsoft 365 does not back itself up. Decide your backup approach now, not after an accidental deletion.
Migrate the mail in a controlled way
With the destination ready, you copy the existing email, calendars and contacts across. For most small and mid-sized firms this is done with a migration tool that connects to the old system and the new tenant and moves everything in the background, while the old mailboxes keep working normally.
The sensible pattern is to run an initial bulk copy of all historic mail well ahead of time, then a final 'top-up' sync of anything that arrived since, immediately before you switch over. A pilot group goes first - move a few willing users, confirm everything looks right on their side, fix any surprises, and only then move everyone. A staged migration like this keeps mail flowing the entire time, which is the whole point. Larger or tenant-to-tenant moves follow the same logic at scale, as our tenant-to-tenant migration playbook details.
Cut over the domain - the one big moment
The actual switch is a single change: you update your domain's mail-routing record (the 'MX record') in DNS to point at Microsoft 365 instead of the old system. From that moment, new email arrives in the new mailboxes. It is anticlimactic when planned well, and tense when not.
Time it for a quiet period - a Friday evening or a weekend - so the changeover settles before the next busy morning. Be aware the change takes a little while to ripple across the internet, so for a short window mail may land in either the old or new system; that is normal, which is why you keep the old mailboxes available a little longer rather than deleting them the instant you cut over. Do the final top-up sync just before flipping the record so nothing from the last hours is missed.
After the switch: tidy up and embed it
Cutover is not the finish line; the days after decide whether people feel the project succeeded. Reconnect everything that touches email - desktop and mobile mail apps, the website form, the accounting and scanning systems - and reconfigure how your applications and devices send mail through the new service.
Then do the closing jobs that are easy to forget: confirm everyone can send and receive, check shared mailboxes and calendars came across, and give staff a short orientation so they get value from the wider toolkit rather than just email. Keep the old system around read-only for a while as a safety net, then decommission it. Finally, confirm your backup is actually running against the new tenant. If a hands-off migration appeals, our team runs these end to end through our email security and productivity services - and a good migration is also the natural moment to refresh ageing business laptops so staff land on hardware that does the new tools justice.