End of life
Exchange 2013, 2016 or 2019 is out of support or the hardware is. Move everyone to Exchange Online in waves and switch the domain once.
Exchange Server to Microsoft 365
Retire the on-premises Exchange server without a hybrid, without PST exports and without PowerShell. MigrateX reads every mailbox and public folder over Exchange Web Services with one service account, and rebuilds them in Microsoft 365 while the server keeps running.
Typical moves.
No hybrid, no ADFS
A small or mid-size company that never set up hybrid and does not want to. One EWS URL, one service account, done.
Public folders that everyone still uses
Decades of shared mail, contacts and calendars in public folders become shared mailboxes with the same structure.
Leaving a hosted Exchange provider
A hosted Exchange 2016/2019 tenant at a provider that exposes EWS: connect with the provider's service account and move to your own Microsoft 365.
In detail.
Mailboxes
Full folder trees with read state, categories and flags; calendars with recurrence; contacts. Original dates kept, delta passes until cutover.
Public folders
Each top-level public folder becomes a shared mailbox; the folders below it keep their path. Mail, contact and calendar folders all move.
Basic or NTLM, impersonation
A service account with the ApplicationImpersonation role reads every mailbox; the password is stored encrypted and used only for EWS calls.
Users & sizes read from the GAL
The address book gives the user list and mailbox sizes for the assessment; no Active Directory access needed.
Forwarding & coexistence
Inbox rules forward new mail to Microsoft 365 per wave, so people can move on different days.
Domain cutover
MX, SPF, Autodiscover and DKIM checked, the domain added to Microsoft 365, a notice ready to send.
Good to know before you plan
- Exchange 2010 and older are not supported: they lack the EWS features MigrateX relies on (SyncFolderItems with change keys, FindPeople).
- Shared mailboxes, distribution groups, mailbox rules and signatures on the server side are listed by name for you to recreate; new mailboxes are created only in the target.
- The EWS endpoint must be reachable from the internet over HTTPS (Outlook Anywhere / Autodiscover already need this). Self-signed certificates can be allowed per connection.
Six steps, one page each.
Connect both tenants, assess, match users, migrate in waves, verify and keep in sync, cut over. Every step lives on its own tab with the numbers that matter and the next action ready.
Read the complete playbookOpen this route with a free assessment.
Connect the source tenant and see users, sizes, shared mailboxes, sites and Teams scored in minutes. Nothing moves until you say so.