An email migration to Microsoft 365 done right means zero downtime. Here is the step-by-step order that copies your mail across without losing a message.
You move email to Microsoft 365 without downtime by copying all your existing mail across in the background first, verifying it is complete, and only then changing the DNS setting that redirects incoming mail. Done in that order, nobody loses a message or misses a day. The whole process usually runs over about a week, most of it invisible to you and your clients.
Email migrations have a bad reputation because people do the steps in the wrong order and switch the domain over before the mail has finished copying. Get the sequence right and the changeover is a non-event. Here is how it works.
Why do email migrations cause downtime?
Migrations cause downtime when the domain's mail setting is changed before the mailboxes are ready. Flip that switch too early and new mail arrives at an empty destination while old mail is stranded at the previous provider.
The fix is simply order. You never redirect mail until the new mailboxes exist, the old mail is copied in, and you have checked it landed. The switch itself takes seconds; the preparation is what protects you.
Note: The riskiest moment is the MX switch, yet by the time you reach it the hard work is already done, so treat it as a final check rather than the main event.
What is the right order for a migration?
The safe sequence copies data first and switches delivery last. Follow these steps and the transition is smooth.
- Set up the accounts in Microsoft 365 and add your domain, without changing mail delivery yet.
- Copy existing email across - all mailboxes, calendars and contacts - in the background while the old system keeps running.
- Verify the copy is complete and nothing is missing.
- Switch the DNS record (the MX record) to point mail at Microsoft 365.
- Let it settle for a day, keeping the old mailbox open to catch any stragglers, then decommission it.
Microsoft documents the migration options in detail on learn.microsoft.com. The principle is the same whichever method you use: data first, delivery last.
How long does an email migration take?
A small business migration typically takes about a week end to end, though most of that is the background copy running while you work as normal. The actual switchover, when mail starts flowing to Microsoft 365, takes a few hours to spread fully.
The size of your mailboxes drives the timeline. A team with years of email and huge archives takes longer to copy than a lean setup. Either way, you keep using your email throughout, which is the point.
Tip: Measure the size of your largest mailboxes early, because a few heavy archives, not the number of staff, usually decide how long the copy takes to run.
What should you sort out before you switch?
Before the changeover, get your security and authentication in place so your email lands and stays protected from day one. Doing this upfront avoids the classic post-migration mess where mail suddenly goes to spam.
- Set up SPF, DKIM and DMARC so your mail authenticates - see why business email goes to spam.
- Enforce multi-factor authentication on every account before staff log in - see what is MFA.
- Decide where files will live so people are not left guessing - see OneDrive vs SharePoint vs Teams.
This is exactly what our Microsoft 365 service handles end to end, and it sits within the wider Microsoft 365 small business guide. We do this work on-site across the region, including Microsoft 365 support in Liverpool.
Warning: If you leave the SPF, DKIM and DMARC set-up until after the switch, your first days on the new system can see legitimate mail dropped straight into spam.
The short version
An email migration to Microsoft 365 is only risky when done in the wrong order. Copy your mail across first, verify it, then switch delivery last, and set up your security records before you flip the switch. Do that and your clients never notice a thing.
Frequently asked questions
Will I lose emails when I move to Microsoft 365?
No, not if the migration is done correctly. All existing mail, calendars and contacts are copied across and verified before delivery is switched, so nothing is lost in the move.
Can I keep my email address during migration?
Yes. Because Microsoft 365 runs on your own domain, your address stays exactly the same. Clients keep emailing the address they always have, and it simply lands in the new system.
How much email downtime should I expect?
None, if the sequence is right. You keep using your existing email throughout the copy, and the final switchover is designed so mail keeps flowing to whichever system is ready to receive it.
Do I need to tell my clients about the migration?
No, a properly run migration is invisible to clients because your address and delivery never actually stop. You only need to inform your own staff about the login change on switchover day.
Can I migrate email myself?
You can for a very small setup, but the DNS and authentication steps are easy to get wrong in ways that cause lost mail or spam problems. For anything with staff and archives, it is worth having it done once, properly.
Planning a move to Microsoft 365? Talk to us about a no-downtime migration and we will map it out for you.