Moving to Microsoft 365 without the horror stories

Everyone knows someone with a Microsoft 365 migration horror story: the morning email stopped working, the week half the archive went missing, the month the new mailboxes turned out to have no security on them at all. None of that is inherent to the move. It's what happens when the move is treated as a switch to flip rather than a project to run.

Done properly, a migration is a non-event — people log in one morning and everything's simply there, faster. Here's the checklist we work through to make it boring, in the best way.

Before you touch anything

• Inventory what you actually have. Every mailbox, shared mailbox, distribution list, and how much data each holds. Surprises here become surprises mid-cutover.
• Right-size the licences. Not everyone needs the top tier. Map people to plans deliberately instead of buying one size for all.
• Plan the DNS change, don't improvise it. Email routing lives in DNS (the MX record), and this is where downtime is won or lost. It gets changed once, at a planned moment — not poked at hopefully while mail is flowing.

During the move

• Migrate data first, cut over second. Copy mail into the new mailboxes before redirecting delivery, so nothing is caught in the gap. Done right, there's no window where messages vanish.
• Pick a low-traffic cutover. A weekend or evening switch gives DNS time to propagate before Monday.
• Keep the old system reachable during transition. A safety net costs little and saves the horror story.

The step that's usually skipped: security

This is where "it works!" quietly becomes "we're exposed." A fresh Microsoft 365 tenant is not secure by default in the way it should be. Before you call it done:

• Turn on multi-factor authentication for everyone. Email is the number-one target; MFA is the single biggest thing stopping a leaked password becoming a breach.
• Review the default sharing and access settings rather than trusting them.
• Set up a sensible backup. Microsoft keeps the service running; recovering your data after an accidental deletion or a compromised account is your responsibility, not theirs.

And the part nobody plans for: people

The technical migration can be flawless and the project can still "fail" if everyone's confused on Monday. A short heads-up, a one-page "here's how you sign in and where your mail is," and someone reachable for the first day turns anxiety into a shrug.

None of this is exotic. It's just method — and method is the whole difference between a horror story and a non-event.

Alpha Web plans and runs Microsoft 365, Google Workspace and Zoho migrations as part of our managed IT services, security switched on from day one. Thinking about the move? Talk to us before you change a single DNS record.