Skip to main content

Modern workplace

Mail migration without the week of chaos afterwards

Mailbox, calendar and archive migration between platforms with minimal user disruption.

The problem

Email migration goes wrong in predictable ways: shared mailboxes and delegate permissions that do not survive the move, calendar meetings that lose their organiser, archives that were never in scope but turn out to be business-critical, and a support queue that spikes for a fortnight because nobody told users what would change.

How we approach it

We inventory everything that touches mail before moving any of it — shared mailboxes, delegates, distribution lists, forwarding rules, connected applications and archives — because those are what break, not the mailboxes themselves.

Migration runs in waves with mail flowing correctly throughout, and users get specific instructions for their situation rather than a generic notice.

What you get

  • Full inventory of mailboxes, delegates, shared mailboxes and connected systems
  • Wave-based migration with mail flowing throughout
  • Calendar and delegate permissions preserved
  • Archive and retention requirements addressed explicitly
  • User communication targeted to what each group needs to do
  • Post-migration support during the period problems actually appear

How the engagement runs

The sequence, and why each stage comes where it does.

  1. Inventory

    Every mailbox, shared mailbox, delegate relationship, distribution list, rule and connected application is catalogued.

  2. Domain and routing plan

    DNS, mail routing and coexistence are designed so mail flows correctly at every point of the migration.

  3. Pilot wave

    A small representative group migrates first, including at least one complex delegate arrangement.

  4. Production waves

    Users migrate in agreed groups with confirmation checks after each.

  5. Cutover and cleanup

    Mail routing switches fully, the source platform is decommissioned on an agreed date, and archives are verified.

Technology we work with

Named so you can check the fit against your existing estate.

  • Exchange Online
  • Google Workspace
  • Zoho Mail
  • IMAP migration tooling
  • DNS management

Frequently asked questions

Will users lose email during the migration?
No. Mail is copied rather than moved, and the source remains intact until the agreed decommission date. If something is wrong after cutover, the original mailbox is still there.
What about mailboxes larger than the destination limit?
Oversized mailboxes are identified in the inventory stage. They are usually handled by migrating recent mail to the mailbox and older mail to an online archive, which is what the archive is for.

Talk to us about email migration

Tell us where you are now and what you are trying to reach. We will scope it honestly, including whether this is the engagement you actually need.