Use Outlook to migrate email clients and formats
Use Outlook as the bridge when moving mail between clients and formats.
Use Outlook as the bridge when moving mail between clients and formats. Outlook can gather messages, contacts, calendars, and folders into an Outlook Data File, called a PST file. That file can then be opened or imported on another Outlook setup, including a Microsoft 365 mailbox.
The key point is simple. An export is only a copy. It is not proof that the move worked. The real test comes after import, when folders, messages, contacts, dates, and attachments are checked in the new mailbox.
I start with the source account. In classic Outlook for Windows, the export path is usually File, Open & Export, then Import/Export. The wizard offers Export to a file. The target format is Outlook Data File (.pst).
PST means Personal Storage Table. It is a local Outlook file that can hold email and other Outlook items. It is not the same as an online Microsoft 365 mailbox. The PST sits on a drive. The Microsoft 365 mailbox lives on a server and syncs with Outlook.
That difference matters during a move. Outlook may show the same folders in both places, but they do not behave the same way. A PST is a file. A Microsoft 365 mailbox is an account service. The migration joins those two parts.
During export, the account or folder tree must be chosen with care. The Include subfolders option matters when the mailbox contains nested folders. Without it, the top folder may export while folders below it stay behind. That is a quiet failure, which is the worst kind because it often looks tidy.
The export can include email, contacts, calendar items, and tasks. The exact choices depend on the Outlook version and account type. Microsoft changes Outlook screens over time, so the names and locations of commands may differ between classic Outlook, new Outlook, and Outlook for Mac.
For a Microsoft 365 move, classic Outlook is often the important part of the process. Microsoft’s current instructions identify the desktop version as the path for importing a PST into a mailbox. New Outlook may have different export choices and may not offer the same full import flow.
Once the PST exists, it can be opened first. Opening a file lets Outlook display its folders without placing the items into the mailbox. This is a useful check. It shows whether the file contains the expected folder tree and whether messages open normally.
Importing is a separate action. In classic Outlook, the path is again File, Open & Export, then Import/Export. This time, the choice is Import from another program or file, followed by Outlook Data File (.pst).
The import wizard asks where the items belong. A Microsoft 365 mailbox can be selected as the destination. The current folder can also be used when the PST is being added to a local Outlook store instead.
That choice deserves attention. Importing into the mailbox sends the items toward Microsoft 365. Copying or opening the PST locally leaves them in the file. Both actions can look similar on screen, but they produce different results.
I treat the PST as an intermediate format, not as a magic universal file. Some email clients use formats that Outlook cannot read directly. A conversion tool may be needed before Outlook can open the data. The tool’s supported source and target formats must be checked first. Format names alone do not tell the whole story.
Email data has several layers. A message may include its body, sender, recipients, dates, attachments, flags, and folder position. Contacts and calendars have their own fields. A conversion can preserve some layers while changing others. That is why a file that opens without an error still needs inspection.
The safest review starts with counts and structure. Compare the main folders in the source and destination. Check Inbox, Sent Items, deleted mail, custom folders, and nested folders. Then open messages from different dates. Check attachments, sender names, and dates.
Contacts need their own check. A contact list may import with names but lose a field that matters, such as a second email address or a note. Calendar items also need review. Recurring events, time zones, and meeting details can behave differently across clients.
A small sample can reveal a large problem. Pick old and new mail. Include messages with attachments and messages from custom folders. Review contact fields and calendar entries too. The goal is not to admire the export screen. The goal is to confirm usable data in the destination.
Duplicates are another common result. An import can place a second copy beside an existing message. This may happen when the mailbox already synced some content or when the same PST is imported twice. Duplicate cleanup should wait until the migration is complete and checked. Deleting too early makes the audit harder.
The file itself also has limits. Large PST files can take longer to open, copy, or import. Outlook data files have size limits that vary with the Outlook version and settings. A very large or damaged file may need separate handling. No general export method can promise a clean result for every file.
Corruption changes the question. If Outlook cannot open the PST, the problem is no longer only a client migration. The file may need repair or conversion through a tool made for that condition. A repaired file still needs the same review after import. Repair is not the same as verification.
This is where 2PST tools fit into the process. Their role depends on the product and its supported formats. Some 2PST products are built for conversion, backup, or recovery around Outlook data files. That capability is separate from Outlook’s own export and import commands. The product page and current documentation should decide whether a given source file is supported.
A second copy of the source data should remain available during the move. The original mailbox or source file is the reference point. Work on a copy when possible. Keep the exported PST unchanged until the destination has been checked. A migration plan that destroys its only source is a plan with poor manners.
There is one honest limit here. Outlook does not preserve every feature from every mail client in the same way. Some fields have no direct match. Some messages may use formats or features that change during conversion. Microsoft 365 and Outlook also change over time, so current version rules matter.
The clean path is therefore steady. Use Outlook to create or receive a PST. Open the file and inspect it. Import it into the Microsoft 365 mailbox when that is the target. Then compare the source and destination before calling the move complete.
The export button is the easy part. The useful part is the check afterward. A finished migration has the folders, messages, contacts, and calendar items where they belong, with the important details still present.
That is the kind of work The Migration Brief is meant to support: one practical fix, one file format explained, and one safer way to move your mail.