How to Migrate to Microsoft 365 Without Losing Email or Downtime

Last updated: September 2026

Written by Graham, Owner, Gray IT · Microsoft Partner

To migrate to Microsoft 365 without losing email or downtime, copy every mailbox to Exchange Online in the background while your current system keeps receiving mail. Verify the data, then switch your MX record last. Lowering DNS TTL beforehand and cutting over at a weekend keeps disruption near zero.

Losing years of email during a move to the cloud is every business owner’s fear. It rarely happens by chance. It happens when the switch is done in the wrong order. Get the sequence right and your team barely notices the change.

This guide sets out the exact process a Microsoft Partner uses. You will learn the migration methods, the step by step cutover, and the mistakes that cause lost mail.

What are the migration methods for Microsoft 365?

Microsoft 365 supports several email migration methods. Cutover moves every mailbox at once and suits businesses under roughly 150 mailboxes. Staged moves mailboxes in batches but only supports old Exchange 2003 and 2007 servers. Hybrid runs both systems together for a gradual switch. IMAP or PST import covers non-Exchange sources like webmail.

Method	Best for	Mailboxes	Coexistence	Typical downtime
Cutover	Small and medium businesses	Up to ~150	None	One weekend
Staged	Legacy Exchange 2003 or 2007	150 to 2,000	Temporary	Phased over weeks
Hybrid	Larger or cautious firms	150 or more	Full	Near zero
IMAP or PST	Non-Exchange sources	Any size	None	One weekend

Cutover migration is the simplest method. Exchange Online, Microsoft’s cloud email service, receives all mailboxes in one batch. Microsoft supports up to 2,000 mailboxes this way but recommends 150 or fewer, per its Exchange migration guidance.

Staged migration now fits very few businesses. It only supports Exchange 2003 and 2007 as the source system. Most firms left those versions behind long ago.

Hybrid migration keeps both systems linked during the move. It gives the smoothest experience for larger teams that need shared calendars across old and new. The trade off is more setup and cost.

IMAP migration is for email that does not live on Exchange, such as legacy webmail. It moves mail only, so contacts, calendars, and rules need a separate step.

Which migration method is right for your business?

For most small and medium businesses, a cutover migration is the right choice. It moves every mailbox in one weekend with the fewest moving parts. Choose hybrid instead if you have more than about 150 mailboxes. Hybrid also suits firms that want both systems running during a phased switch.

Your current server matters as much as your size. Support for Exchange Server 2016 and 2019 ended on 14 October 2025, according to Microsoft’s end of support roadmap. A paid Extended Security Update programme covers eligible servers only until 14 April 2026.

Above roughly 150 mailboxes, cutover risk climbs. The initial copy takes longer and the weekend window gets tighter. That is the point to move up to hybrid or a specialist migration tool.

How do you migrate to Microsoft 365 without losing any email?

You avoid losing email by keeping your existing mail system live throughout the migration. Every mailbox is copied to Exchange Online in the background. Incremental syncs then capture new messages that arrive during the copy. Mail delivery only switches to Microsoft 365 once the data is verified as complete.

During the copy, your old server stays online and keeps receiving mail. Nothing is deleted at the source. New messages are picked up by repeated delta syncs until the moment of cutover.

Verification is the safety net that prevents loss. Before the switch, you compare mailbox item counts on both sides. A pilot group confirms that mail, contacts, and calendars all arrived intact.

Can you migrate to Microsoft 365 with zero downtime?

Downtime is avoided by switching your MX record only at the very end, after mailboxes are confirmed in Microsoft 365. An MX record is the DNS setting that directs incoming mail. Lower its TTL to 300 seconds a day beforehand so the change spreads fast, then cut over at a weekend.

TTL, or Time To Live, tells the internet how long to cache a DNS setting. A high TTL means the internet remembers your old mail route for hours. Lowering it first makes the final switch almost instant.

Schedule the switch for a quiet window, usually a Friday evening. Most users notice nothing beyond re-entering a password on Monday. Their Outlook and phone reconnect to the new mailbox automatically.

What are the steps in a Microsoft 365 migration?

A Microsoft 365 migration follows seven stages. You assess the current setup, buy and assign licences, then prepare the tenant and domain. Next you pre-stage a background copy of every mailbox and run a pilot. Finally you switch the MX record at a weekend, then verify mail flow and support users.

1. Assess your environment. Inventory mailboxes, data size, the source server, and every device that sends email.
2. Buy and assign licences. Pick the right Microsoft 365 plan for each user before you start.
3. Prepare the tenant. Create and verify your domain, then set up Modern Authentication, a secure sign in method that replaces password only logins.
4. Pre-stage the data. Copy all mailboxes to Exchange Online and keep them syncing in the background.
5. Run a pilot. Move a small test group first and confirm mail, calendars, and contacts work.
6. Cut over. Lower the MX record TTL, then switch mail delivery to Microsoft 365 at a weekend.
7. Verify and support. Check Outlook and mobile for every user, then retire the old server after a settling week.

What do you need before you start?

Before migrating, get three things ready. First, admin access to your domain’s DNS. Second, a Microsoft 365 tenant with enough licences. Third, a full inventory of every mailbox and distribution list. Then clean up old data, document your mail flow, and confirm your server supports the method you chose.

• Admin access to your DNS or domain registrar.
• Enough Microsoft 365 licences for every user.
• A list of all mailboxes, shared mailboxes, and aliases.
• Old or unused data archived to shorten the copy.
• A record of current mail flow rules and connectors.
• A check of printers, scanners, and apps that send email.
• A tested pilot group ready to move first.

Data cleanup is the step firms skip most often. Smaller mailboxes copy faster and cut the weekend window. Archiving old items before you start can save hours of sync time.

How long does a Microsoft 365 migration take?

Most small business migrations take two to four weeks from start to finish. The cutover itself lasts only a weekend. Microsoft’s guidance shows that mailboxes under 10 GB usually copy within about a day. Your timeline depends on mailbox count, total data size, and internet upload speed.

Large archives and slow upload speeds stretch the schedule. Hybrid projects also run longer because both systems need setup. Booking the cutover for a weekend keeps working hours clear.

How much does a Microsoft 365 migration cost?

Two costs make up a Microsoft 365 migration: the ongoing licence subscription and a one off project fee. The subscription is priced per user each month. The project fee depends on mailbox count, data volume, source system, and out of hours work. Ask for a fixed quote before you commit.

Botched DIY attempts carry the biggest hidden cost. Lost mail and days of downtime are far dearer than a planned project. A fixed price migration turns an uncertain risk into a known cost.

What are the most common Microsoft 365 migration mistakes?

The most common Microsoft 365 migration mistakes cause lost mail or downtime. They include switching the MX record before mailboxes finish syncing, and leaving the DNS TTL high. Others are skipping a pilot, running out of licences, and ignoring shared mailboxes, calendars, or public folders. A properly sequenced cutover prevents each one.

• Switching the MX record too early. Fix: confirm mailbox item counts match on both sides first.
• Leaving DNS TTL high. Fix: lower it to 300 seconds a day before cutover.
• Skipping the pilot. Fix: always test with a small group before the full move.
• Running short on licences. Fix: assign a licence to every user in advance.
• Forgetting shared mailboxes and public folders. Fix: inventory them and migrate them too.
• Overlooking printers and scanners. Fix: check each one supports Modern Authentication.
• Declaring victory at cutover. Fix: plan a support window for the first week after.

According to [engineer name], [role] at Gray IT, in [month 2026]: “[Insert a one or two sentence first-hand quote here, for example why the MX record is never switched until item counts match.]”

How does the Basic Authentication retirement affect your migration?

Basic Authentication is an older sign in method that sends passwords in plain text. Microsoft has retired it across most Exchange Online protocols since late 2022. The last piece, SMTP client submission, is disabled by default from the end of December 2026 under Microsoft’s updated retirement timeline. Your printers, scanners, and legacy apps must move to Modern Authentication.

Mailbox migrations themselves are mostly unaffected by this change. The risk sits with devices and scripts that still send mail using a username and password. Those need Modern Authentication or a supported relay before the deadline.

Audit every device and app that sends email early in the project. Multifunction printers and scan to email are the usual culprits. Fixing them before cutover avoids a nasty surprise on Monday morning.

The safe way to move to Microsoft 365

Getting the order right is what makes a move downtime free. Keep the old system live, verify every mailbox, then switch the MX record last. Do that, and your team keeps working while their email quietly moves to the cloud.

Planning a move from ageing on-premises Exchange? Gray IT is a Microsoft Partner and runs downtime free cutovers for businesses across Kent. Book a migration consultation to map your safe cutover weekend.

Still running email on a server that lost support in October 2025? Now is the time to plan the switch.