Migrate email to Microsoft 365 using Exchange Online

Migrate email to Microsoft 365 using Exchange Online. That is the clean answer, but the real work is in matching the path to the mailbox type and making sure the old mail, contacts, and folders all land where they belong.

I keep the same thought in front of me when this job comes up: an export is not the finish line. A migration only feels done when the mailbox opens in Microsoft 365 and the mail still looks like mail. The folders are there. The contacts are there. The dates make sense. The odd little bits that people forget until they are missing are still present.

Exchange Online is the mail service inside Microsoft 365. It is the place where the mailbox ends up. The move into it can happen in a few ways. A mailbox from an on premises Exchange server can move in batches. Mail from another hosted service can come in through an IMAP migration path. A pile of PST files can be imported through Microsoft’s import service. Each path is different because the source is different. That detail matters more than the brand name on the cover.

The plain fact is this. Microsoft 365 does not treat every old mailbox the same way. An Exchange server migration is not the same as a PST import. A Gmail or Yahoo style mailbox is not the same as a local archive file. If the source is wrong, the move gets messy fast. The tool may still finish, which is a nice trick, but a finished job and a safe job are not the same thing.

For Exchange on premises, Microsoft supports mailbox moves and staged or hybrid paths in Exchange Online. Those paths are built for moving user mailboxes over time, not just dumping one file into another place. They are the right shape when the source is an Exchange server and the goal is a Microsoft 365 mailbox that keeps working after the move.

For PST files, Microsoft uses the Microsoft Purview import service. That service supports network upload and drive shipping. In simple terms, you either upload the PST files to Microsoft or copy them to an encrypted drive and send that drive in. Microsoft then imports the data into Exchange Online mailboxes. It also uses a mapping file so the right PST goes to the right mailbox. That is the kind of part people skip once, and then spend the afternoon untangling.

The contacts and calendar items matter too. Exchange migrations can carry more than message text, and Microsoft’s migration paths are set up to move mailbox content, not just the inbox. Still, what survives depends on the source and the path. IMAP moves, for example, are good for mail, but they do not behave like a full Exchange move. That is where the small print lives, and small print is where mailbox surprises hide.

I trust the general shape of the process, but I do not trust the word “complete” on its own. A migration can end with no error and still miss something a person cares about. A nested folder can land in the wrong place. A contact list can come over thinner than expected. A mailbox can open, and yet the archive or calendar may not look the same. That is why I treat verification as part of the migration, not as a bonus step.

There is one honest limit here. Requirements change. Microsoft updates migration methods, admin screens, and service rules over time. A path that fits one source system today may not fit it the same way later. So the safest reading of “migrate email to Microsoft 365 using Exchange Online” is practical, not magical. It means use Exchange Online as the target, then pick the migration method that matches the source mailbox and the kind of data you need to keep.

That is the part people want in one sentence. Move the mail into Exchange Online, but do it through the right route for the source. If the source is Exchange, use the Exchange migration paths. If the source is PST, use the import service. If the source is IMAP, expect mail migration, not a full clone of every mailbox feature. The names are different because the jobs are different.

I like that this answer stays plain. No mystery is needed here. The move is real, the tools are there, and the rules are not hidden. The hard part is not the word “Microsoft 365.” The hard part is making sure the data arrives whole and still usable when it gets there.

That is why I keep the same standard in mind. A migration only counts when every message, folder, and contact survives intact. Anything less is just an export with better marketing. The Migration Brief fits that same idea: one practical fix, one file format explained, and one safer way to move your mail.