Get a Free Quote
Article

Email Migration: An Enterprise Email Migration Plan and Checklist

Email migration is the process of moving mailboxes, calendars, contacts, archives and related data from one email platform to another, for example from Exchange Server, Google Workspace, Lotus Notes or another Microsoft 365 tenant to Exchange Online. A successful enterprise email migration follows a plan: assess what you have, design identity and coexistence, pilot, migrate in phases, and support users through cutover.

This article lays out a practical email migration plan and checklist for IT leaders. RockTeam delivers these projects through our email migration services.

Common Email Migration Scenarios

FromToGuide
On premises Exchange ServerExchange OnlineExchange to Office 365 migration
Any platformMicrosoft 365Office 365 migration guide and checklist
Lotus Notes / HCL DominoMicrosoft 365Lotus Notes to Office 365 migration
One Microsoft 365 tenantAnother tenantTenant to tenant migration, common after mergers and acquisitions
Google WorkspaceMicrosoft 365Google Workspace to Microsoft 365 migration
Legacy archives and PST filesMicrosoft 365Email archive and PST migration

Email Migration Plan: Seven Phases

  1. Define goals and scope. Decide what moves (mail, calendars, archives, public folders, applications) and what will be retired, and set success measures.
  2. Assess the source. Inventory users, mailbox sizes, shared mailboxes, archives, PST files, mail-enabled applications and compliance requirements.
  3. Design identity and coexistence. Plan directory synchronization, authentication, mail routing and free/busy so users on both systems can work together.
  4. Choose methods and tools. Match native Microsoft methods or third-party tools to each source and size.
  5. Pilot. Migrate a representative group, measure throughput and refine communications.
  6. Migrate in phases. Pre-stage older mail, then move recent mail at each wave’s cutover. Group teams and executive and assistant pairs together.
  7. Cut over and stabilize. Switch DNS, reconfigure devices and applications, run a support surge and decommission old systems after retention needs are met.

Why a Phased Email Migration Works Best

For most enterprises a phased approach lowers risk: each wave proves the process before the next, support teams are not overwhelmed, and problems affect a small group rather than everyone. Coexistence is what makes phasing possible, and keeping the source environment healthy until the last wave matters; server managed services can keep source servers patched and stable during a long transition.

ApproachBest forTrade-off
Single cutoverSmall organizations with simple needsFast, but no coexistence and a bigger change day
Phased wavesMid-size and large enterprisesLonger program, much lower risk
Hybrid long termOrganizations keeping some workloads on the source platformOngoing coexistence to operate

Email Migration Checklist

  • Inventory of users, mailboxes, sizes, shared mailboxes, archives and PST files
  • List of applications, devices and scanners that send mail
  • Retention, journaling and legal hold requirements documented
  • Directory cleaned up and synchronization designed
  • Authentication, MFA and security baseline defined
  • Coexistence design for mail routing and free/busy
  • DNS change plan for MX, Autodiscover, SPF, DKIM and DMARC
  • Pilot group selected and success criteria agreed
  • Wave plan and user communications prepared
  • Support surge and rollback plans ready for each wave

Governance and Security

Email holds an organization’s records and much of its sensitive data, so security and compliance belong in the plan from the start: enforce MFA, configure retention and data loss prevention, and review admin access. Executive sponsorship and, where appropriate, a vCISO help keep security decisions moving.

Avoiding the usual pitfalls is covered in avoiding enterprise email migration failure.

Need an email migration plan?

RockTeam’s migration architects assess your environment, design coexistence and deliver phased email migrations to Microsoft 365 and other platforms. Start with a no cost assessment.

See Email Migration Services

Related Articles

Email Migration FAQs

Moving mailboxes, calendars, contacts, archives and related data from one email platform to another, such as from Exchange Server, Google Workspace or Lotus Notes to Microsoft 365.

Define scope, assess the source, design identity and coexistence, choose methods and tools, pilot, migrate in phases and cut over with a support surge.

Small organizations can use a single cutover. Larger organizations usually migrate in phases with coexistence, which lowers risk and keeps support manageable.

A temporary setup that routes mail, shares calendar free/busy and synchronizes directories between the old and new systems, so users can work normally while migration continues.

Archives and PST files, shared and resource mailboxes, public folders, and applications or devices that send mail through the old system.