Exchange Server to Microsoft 365: steps and risks

Support for Exchange Server 2016 and 2019 ended in October 2025, so an on-premises mail server is now a security risk. Migrating to Exchange Online is usually done without downtime: mail is synchronised in advance and the switch happens at an agreed time. This guide covers choosing a method, preparing and what to fix afterwards.

Why it no longer makes sense to run Exchange Server

Once support ends, Microsoft ships no more security updates – and a mail server is usually reachable from the internet, making it one of the most attacked systems. You also have to look after the hardware, licences, certificates and backups.

Exchange Online takes over updates, availability and baseline spam and malware protection. What remains for you is configuring security properly and, we recommend, separate backups of your Microsoft 365 data.

Migration methods

MethodHow it worksWhen it fits
Cut-overAll mailboxes move at onceSmaller organisations; Microsoft supports up to 2,000 mailboxes, in practice suited to small environments
HybridServer and cloud run side by side; mailboxes move in batchesLarger or more complex environments that need to move in groups
IMAP / specialist toolsMail (and with tools also calendars and contacts) copied from another systemZimbra, Google Workspace, other mail systems

What to prepare before the migration

Most problems can be avoided with good preparation:

  • Microsoft 365 licences for every user;
  • access to your domain’s DNS (MX, SPF, DKIM, autodiscover records);
  • a list of mailbox and archive (PST) sizes;
  • public folders, shared mailboxes and groups;
  • printers, scanners and applications that send mail through your server;
  • a list of mobile phones and a how-to for your people;
  • a heads-up for staff: when the switch happens and what they’ll need to do.

Migration steps

  1. Inventory

    Mailboxes, public folders, groups, sizes, connected devices and applications.

  2. Preparation

    Microsoft 365 tenant, licences, domain verification, MFA.

  3. Synchronisation

    Mail, calendars and contacts copied in advance – first for a pilot group.

  4. Cut-over

    MX records, Outlook and phone setup, user support in the first days.

What to fix after the migration

The migration doesn’t end at the switch. Afterwards we recommend:

  • SPF, DKIM and DMARC records, so mail avoids spam and nobody can impersonate your domain;
  • multi-factor authentication and conditional access;
  • backups of your Microsoft 365 data;
  • switching off the old server after a short monitoring period;
  • short training for staff on new features (Teams, sharing).

Common risks and how to avoid them

The biggest risks are oversized mail archives, forgotten public folders, wrong DNS records and unprepared users. You avoid them by checking mailbox sizes in advance, running a pilot with a few users and giving staff a short how-to. You can check whether your domain’s SPF, DKIM and DMARC are in order with our free check.

Frequently asked questions

Will we lose e-mail during the move?

No. Mail is synchronised in advance and the final switch (MX records) happens at an agreed time.

Do phones need to be set up again?

Usually yes – we prepare a simple guide and help your people.

How long does a migration take?

It depends on the number of mailboxes, data volume and method. We give you an exact plan after the inventory.

Planning a migration?

CallGet a proposal

Choose which cookies you allow. You can change your choice at any time.

Strictly necessary

Needed for the site to work securely and remember your choices (e.g. cookie settings or text typed into a form). They cannot be switched off and need no consent.

Always on
Cookies (3)
  • ithink-consent · IThink (localStorage)
    Stores your cookie choice and an anonymous consent ID. Expires: 12 months.
  • ithink-form:* · IThink (sessionStorage)
    Keeps the text you type into a form so you don’t lose it while filling in a request. Expires: Until the browser tab is closed or the form is sent.
  • __cf_bm, cf_clearance · Cloudflare
    Protection against bots and attacks (set only when needed). Expires: 30 minutes.

Analytics

Help us understand how visitors use the site (Google Analytics 4) so we can improve it. Data is aggregated and IP addresses are not stored.

Cookies (3)
  • ithink-utm, ithink-landing · IThink (sessionStorage)
    Adds the campaign source and first page visited to your request. Expires: Until the browser tab is closed.
  • _ga · Google Analytics 4
    Distinguishes visitors for visit statistics. Expires: 2 years.
  • _ga_8EFLVCZYDP · Google Analytics 4
    Keeps the state of your visit (session). Expires: 2 years.

Marketing

Let us measure the effectiveness of our Google Ads advertising and show you more relevant ads.

Cookies (2)
  • _gcl_au · Google Ads
    Measures whether an ad led to a visit and a request. Expires: 90 days.
  • IDE, test_cookie · Google (doubleclick.net)
    Ad delivery and measurement on Google networks. Expires: Up to 13 months (test_cookie – 15 minutes).

Cookie policy · Privacy policy

Privacy policy

Loading…