# Office 365 migration checklist: from on-premises Exchange and file servers

An Office 365 migration from on-premises Exchange and file servers has eight phases: inventory, identity, choosing the mail migration method, moving mailboxes, moving file shares to SharePoint and OneDrive, DNS cutover, devices, and then backup and decommissioning. The mail method depends on your Exchange version and mailbox count. Microsoft's guidance points small organizations to a cutover migration and larger ones on Exchange 2010 or later to a hybrid deployment.

By Shai Goldenberg. Updated: 2026-11-14.

## Before the checklist: names and support status

Office 365 is now sold as Microsoft 365, and the mail service is Exchange Online. People still search for "Office 365 migration", so this post uses both names for the same destination.

One date frames many of these projects. Microsoft's lifecycle pages list the end of extended support for both Exchange Server 2016 and Exchange Server 2019 as October 14, 2025. The currently supported on-premises version is Exchange Server Subscription Edition. An organization still running 2016 or 2019 for production mail is running without security updates, which is often what starts the migration.

Method limits and version rules below come from Microsoft's documentation on learn.microsoft.com as of November 2026. Check the current pages before you commit to a plan.

## Phase 1: inventory

Nothing is moved in this phase. You count what exists.

- [ ] Exchange version, cumulative update level and number of servers
- [ ] User mailboxes, with sizes and item counts
- [ ] Shared mailboxes, room and equipment mailboxes, distribution groups
- [ ] Public folders, with sizes and owners
- [ ] Archive mailboxes and PST files on desktops and file servers
- [ ] Mail-enabled applications: scanners, ERP, monitoring and line-of-business systems that send through the Exchange server
- [ ] Mail flow: spam filter, journaling, transport rules, connectors to partners
- [ ] File servers: shares, total size, permission model, oldest and largest folders
- [ ] Accepted domains and who controls their DNS
- [ ] Outlook and Windows versions on desktops, and mobile devices that sync mail
- [ ] Legal holds and retention obligations

The applications that relay mail through Exchange are the item most often missed. They keep working during the project and fail on the day the server is switched off.

## Phase 2: identity

Mailboxes belong to accounts, so identity is settled before any data moves.

- [ ] Decide the identity model: cloud-only accounts, or accounts synchronized from on-premises Active Directory to Microsoft Entra ID
- [ ] Clean up Active Directory: duplicate proxy addresses, invalid characters, stale accounts
- [ ] Make sign-in names match email addresses, so users sign in with what they know
- [ ] Choose the sign-in method and plan multi-factor authentication from day one
- [ ] Assign licenses by group, and confirm each plan includes what you intend to use

Microsoft's documentation states that staged and hybrid migrations require directory synchronization. A cutover migration does not, which is one reason it suits small organizations with no plan to keep on-premises account management.

## Phase 3: choose the mail migration method

| Method | What it does | Microsoft's guidance on fit |
|---|---|---|
| Cutover | Moves all mailboxes in one batch, then mail routing switches | Supports up to 2,000 mailboxes. Microsoft says 150 or fewer is more reasonable |
| Express (minimal hybrid) | Uses the hybrid wizard for a quick move without full coexistence | Listed for Exchange 2010, 2013 and 2016 with fewer than 150 mailboxes moving over a few days |
| Staged | Moves mailboxes in batches over time | Exchange 2003 and 2007 only. Not supported for Exchange 2010 or later |
| Hybrid | On-premises Exchange and Exchange Online coexist, mailboxes move gradually | Recommended for Exchange 2010 or later with more than 150 mailboxes |
| IMAP | Copies email only | For non-Exchange systems. No calendar, contacts or tasks |

### What hybrid Exchange gives you, and what it costs

Microsoft's decommissioning article lists the benefits of a hybrid deployment: users see each other's free/busy information across both environments, mailboxes can move in both directions, and users do not need to recreate their Outlook profiles after a move. The same article says hybrid "comes with a hefty price in complexity" and that Microsoft strongly recommends considering cutover or staged migration for organizations with fewer than 2,000 mailboxes.

In practice, choose hybrid when the migration will take weeks, when groups must keep scheduling meetings with each other throughout, or when some mailboxes must stay on-premises for a period. Where systems stay on both sides for the long term, the design questions go beyond mail and are covered on our [hybrid cloud services](https://goldenroz.com/hybrid-cloud-services/) page.

### Tenant to tenant migration

A merger or divestiture means moving from one Microsoft 365 tenant to another. Microsoft provides native cross-tenant mailbox migration. According to its documentation, the move is started from the target tenant, target users must already exist as mail users with specific attributes, a per-user license is required, and mailboxes on hold are blocked from moving. The hard parts are usually domain names, which can exist in only one tenant at a time, and coexistence while both tenants are in use.

## Phase 4: move the mailboxes

- [ ] Run a pilot with IT staff and a few willing users from different departments
- [ ] Check migration endpoints and network throughput before scheduling batches
- [ ] Lower the DNS TTL on mail records several days before cutover
- [ ] Migrate shared mailboxes with, or just before, the people who use them
- [ ] Recreate permissions and delegations that do not cross between environments
- [ ] Move or retire public folders. Microsoft documents a batch migration path to Exchange Online
- [ ] Decide what happens to PST files: import, archive or delete
- [ ] Tell users what changes and when, in one short message with screenshots

## Phase 5: file shares to SharePoint and OneDrive

Microsoft provides two free tools for this. The SharePoint Migration Tool migrates content from on-premises SharePoint sites and file shares to Microsoft 365, and Migration Manager handles file share migrations at larger scale from the admin center.

The tools are the easy part. The design is where projects go wrong.

- [ ] Map each share to a destination: personal home folders to OneDrive, team shares to SharePoint sites or Teams
- [ ] Do not recreate one giant share as one giant library. Split by team and by who needs access
- [ ] Simplify permissions. Deep folder-level permissions on a file server become hard to manage in SharePoint
- [ ] Scan for long paths, unsupported characters and file types before migrating
- [ ] Find files that cannot move: databases, application data folders, files opened by legacy software over a drive letter
- [ ] Archive or delete what nobody has opened in years, with the data owner's approval
- [ ] Run an incremental pass close to cutover, then make the old share read-only

Some data should stay on a file server: large engineering files, application shares, anything a legacy program expects on a mapped drive. That is a normal outcome.

## Phase 6: DNS cutover

- [ ] Verify each domain in the tenant
- [ ] Point MX to Exchange Online once mailboxes are in place
- [ ] Update Autodiscover, internally and externally. Microsoft's guidance warns that updating only one causes inconsistent client connectivity
- [ ] Publish SPF that includes every legitimate sender, including the applications found in phase 1
- [ ] Enable DKIM signing and publish a DMARC record, starting in monitoring mode
- [ ] Reconfigure scanners and applications to send through a supported relay method

## Phase 7: devices and users

- [ ] Update Office apps to a supported version before the move
- [ ] Reconfigure mail on phones, and remove old profiles
- [ ] Set up the OneDrive sync client and redirect known folders if that is the plan
- [ ] Enforce multi-factor authentication and block legacy sign-in protocols
- [ ] Staff the help desk heavily for the first two days after each batch

## Phase 8: backup, then decommissioning

### Backup and retention

Set retention policies for mail and files to match your obligations. Then answer one question in writing: if a user or an attacker deletes or encrypts data and nobody notices for several months, how do we get it back. If native retention does not answer that, add an independent backup, and test a restore.

### Decommissioning Exchange

This step has a known trap. Microsoft's article on decommissioning explains that when directory synchronization is enabled, most recipient properties cannot be managed from Exchange Online and must be managed on-premises. It describes three scenarios:

1. All mailboxes in the cloud and no directory synchronization needed. Disable synchronization and uninstall Exchange.
2. Directory synchronization stays. Remove most servers. Microsoft documents supported options for the last one, including managing recipients with the Exchange management tools, and a newer path that transfers the source of authority for Exchange attributes to the cloud.
3. On-premises services such as SMTP relay or public folders still depend on Exchange. Microsoft recommends against removing Exchange until those are migrated.

Uninstall Exchange properly. Do not delete the virtual machine. Then retire the file server shares that were migrated, and update the documentation, monitoring and backup jobs that still reference the old servers. The servers that remain need the routine described in our [server maintenance checklist](https://goldenroz.com/blog/server-maintenance-checklist/).

## What to do next

Complete the phase 1 inventory. The mailbox count, Exchange version and list of relaying applications decide the method and most of the effort. Our [Microsoft 365 migration](https://goldenroz.com/microsoft-365-migration/) service runs the project end to end, and [Microsoft 365 consulting](https://goldenroz.com/microsoft-365-consulting/) covers tenant design, licensing choices and security configuration before or after the move. Goldenroz is independent and is not a Microsoft partner. Projects start at $25,000 at a fixed price per phase, and managed IT is a monthly retainer quoted after an assessment.

## Questions buyers ask

### What is the difference between cutover, staged and hybrid migration?

A cutover migration moves all mailboxes in one batch and then switches mail routing. A staged migration moves mailboxes in batches and, per Microsoft's documentation, is not supported for Exchange 2010 or later. A hybrid deployment connects on-premises Exchange with Exchange Online so mailboxes can live in both and move gradually.

### How many mailboxes can a cutover migration handle?

Microsoft's documentation says a cutover migration supports up to 2,000 mailboxes, and adds that it is more reasonable to migrate 150 users or fewer because of the time it takes to create and migrate that many. Above that, Microsoft recommends a hybrid migration for Exchange 2010 and later.

### Can we remove the last Exchange server after moving all mailboxes?

It depends on whether you keep directory synchronization from Active Directory. Microsoft's decommissioning article says that if all users will be managed in Microsoft 365 with no directory synchronization, Exchange can be removed. If you keep synchronization, recipient attributes are still managed on-premises, and Microsoft documents specific supported paths for shutting down or uninstalling the last server.

### What is a tenant to tenant migration?

It moves mailboxes and other user data from one Microsoft 365 tenant to another, usually after a merger, acquisition or divestiture. Microsoft provides native cross-tenant mailbox migration, which is started from the target tenant and requires a per-user license. Mailboxes on hold are not moved.

### Do we still need backup after moving to Microsoft 365?

Microsoft operates the service and its availability, and you remain responsible for your data and how long it is kept. Retention policies and recycle bins cover many cases but are configured by you and are not an independent copy. Decide the recovery requirements first, then decide whether native retention or a separate backup product meets them.

---
Page: https://goldenroz.com/blog/office-365-migration-checklist/
Book a free one-hour call: https://calendly.com/daniarozin/daniel-rozin-consultation-1-hour-clone
