Email Migration to Microsoft 365

Email migration to Microsoft 365 means moving your company mailboxes — messages, contacts and calendars — from an existing system, whether an on-premise Exchange server, an IMAP/POP provider or another tenant, into Exchange Online. The goal is to transfer every piece of data with no loss and minimal downtime, reconfiguring the domain, DNS records and each user's mail client along the way.

It sounds straightforward. In practice, across more than 25 years as a B2B System Integrator, at TN Solutions we regularly see improvised migrations end in lost emails, days of stalled mail, or teams unable to work. The difference between a clean migration and a disaster almost always comes down to preparation. Here is how to do it properly.

What Migrating Email to Microsoft 365 Really Involves

Migrating email to Microsoft 365 means bringing the full contents of each mailbox — not just the messages, but folders, rules, contacts, appointments and distribution lists — into Exchange Online, the cloud mail service bundled with Microsoft 365 Business and Enterprise licences.

The process touches three distinct layers, and underestimating any one of them is the most common source of trouble:

• The data: the actual transfer of mailbox contents.
• The domain and DNS: changing the MX, SPF, DKIM and DMARC records that redirect the mail flow towards Microsoft.
• The clients: reconfiguring Outlook, smartphones and any application that reads mail on each workstation.

A successful migration coordinates these three planes so that, the moment mail changes course, every mailbox is already populated and every client is ready to connect.

Migration Methods: Which One to Choose

Microsoft offers several strategies. The choice is not a matter of preference: it depends on the source system, the number of mailboxes and the time available.

Cutover Migration

The most direct method: all mailboxes are moved from an on-premise Exchange server to Exchange Online in a single operation. It suits environments up to a few dozen users (Microsoft cites a practical ceiling of roughly 150 to 2,000 mailboxes, but under 150 it remains the sensible option). Simple and fast, though it involves a clean switchover moment — which is why it should be scheduled outside working hours.

Staged Migration

Designed for larger organisations still running Exchange 2003/2007, it moves mailboxes in batches over days or weeks. This spreads the load and softens the impact, but calls for a more involved setup and a temporary coexistence between the two systems.

IMAP Migration

This is the route when mail sits on a generic provider — hosting, a Linux server running Dovecot or Courier — rather than on Exchange. It transfers the contents of mailboxes only, via the IMAP protocol. Note carefully: it does not migrate contacts, calendars or tasks, which must be handled separately. It is robust and well proven for moving away from third-party providers.

Hybrid Migration

For companies with on-premise Exchange that want lasting coexistence between the local and cloud environments. It is the most complex scenario, with identity synchronisation via Entra Connect, and it makes sense in structured settings or during extended transitions.

For most of the SMEs we support, the choice falls to cutover (for those coming from a small Exchange) or IMAP (for those leaving a hosting service or a traditional mail provider).

The Phases of a Well-Run Migration

An orderly project cuts the risk to almost nothing. This is the method we apply.

1. Assessment and Inventory

Before touching anything: how many mailboxes, what size, where they live, which aliases and distribution lists exist, and which devices use them. We check the state of the domain, ownership of the DNS, and any connected services — centralised signatures, business applications that send email, multifunction printers that dispatch scans over SMTP.

2. Tenant Preparation

The Microsoft 365 tenant is configured: domain verification, user creation, licence assignment, security policy setup. This is the right moment to switch on multi-factor authentication (MFA) and to start thinking about data protection from day one — because, worth remembering, Microsoft guarantees service availability but not a backup of your content.

3. Data Migration

The transfer starts using the chosen method. In most cases the initial synchronisation happens while the old mail is still live: users keep working and the data is copied in the background. This reduces perceived downtime to zero.

4. Switching the MX Records

This is the decisive step. Once the mailboxes are populated, the MX records (along with SPF, DKIM and DMARC) are changed to redirect the mail flow to Exchange Online. DNS propagation takes time — from a few minutes up to 24 to 48 hours — during which well-configured systems keep catching incoming mail without dropping it.

5. Client Reconfiguration and Final Sync

Outlook and mobile devices are reconfigured, a delta synchronisation captures any messages that arrived during the transition, and a final check confirms nothing has been left behind.

6. Verification and Post-Migration Support

Send-and-receive tests, checks on calendars and contacts, verification of signatures and rules. The days right after the switch are when user requests surface: a professional migration includes dedicated support through this window.

The Mistakes That Cost You Email (and How to Avoid Them)

Migrations that go wrong almost always repeat the same errors:

• Changing the MX records before migrating the data: mail lands in an empty mailbox while the user hunts for their history elsewhere. DNS must be touched last.
• Ignoring TTL and DNS propagation: without lowering the TTL in advance, the MX switch drags on for hours longer than expected.
• Forgetting SPF, DKIM and DMARC: with no alignment, outbound mail ends up in recipients' spam folders.
• Overlooking services that send email: business apps, CRMs, printers and alarm systems that relied on the old SMTP server stop delivering.
• Skipping a pre-migration backup: a copy of the data before you start is the safety net that lets you roll back without damage.

We always press this last point: planning an Office 365 backup from the outset is not an extra, it is an integral part of a migration done sensibly.

How Long It Takes and What It Costs

There is no single answer, but there are orders of magnitude. Timing depends on the data volume (a 2 GB mailbox and a 50 GB one do not copy in the same time) and the number of users. The background copy can run from a few hours to several days for large volumes but — and this is the point — it happens while people work. Real downtime, the kind users actually feel, is typically confined to the MX switch window, often scheduled over a weekend.

The cost scales with the number of mailboxes, the complexity of the scenario (a simple cutover versus a structured hybrid) and the connected services to reconfigure. Be wary of flat-rate quotes offered without an assessment: a serious project always begins with an inventory.

The TN Solutions Approach

At TN Solutions we handle Microsoft 365 email migration as part of our business cloud services, not as an isolated task. We operate under a management system certified to ISO 9001 for process quality and ISO 27001 for information security, with documented procedures covering access management and data protection throughout the transfer.

The method is concrete: preliminary assessment, tenant preparation, background migration that never stops the work, an MX switch scheduled out of hours, client reconfiguration and support through the critical days. With more than 25 years of experience as a B2B System Integrator, a Google rating of 4.7 across 37 reviews and an operations base in Melzo, just outside Milan, we stay close to the business, with the responsiveness of a local partner.

If your goal is to modernise the whole infrastructure, email is often the first step on a wider journey to the cloud: we are happy to talk it through when you get in touch.

Related Service: Licensing and Backup After Migration

Once the migration is done, two things are worth planning right away: ongoing management of Microsoft 365 for business (licensing, security, support) and turning on Office 365 cloud backup, since Microsoft does not cover accidental loss on the new mailboxes.