Cloud and Webmail Migration Requires MS Exchange Expertise

Cloud migrations fail in a very ordinary way. The export finishes, the screen looks clean, and then something small goes missing. A folder tree shifts. A contact list vanishes. A few sent messages stay behind like they were never invited.

That is why I care less about the word finished and more about the word intact. A mailbox move only counts when the message bodies, folder names, and contacts still line up after the trip. Outlook has a few sharp edges here, and most of them come from how the account type works.

The first thing to know is simple. Outlook does not treat every mail account the same way. Some accounts let a user view and change server details inside Outlook. Others do not. IMAP and POP accounts usually expose those settings. Exchange, Microsoft 365, and Outlook.com do not use the same path, because the server side is controlled centrally.

That difference trips people up. They expect one account screen to behave like another. It often does not. In Exchange, the server administrator handles the core settings, so Outlook hides the kind of manual server controls that POP and IMAP users may see.

If the account is one of the editable types, the path is plain enough. Open the File tab in Outlook. Choose the account from the top drop-down if it is not already selected. Then open Account Settings and pick Server Settings. The account dialog opens, and the incoming settings appear first.

That is where the ordinary fixes live. Mail server name, port, password, and encryption all sit on that screen for incoming mail. After that, switch to Outgoing Mail. There you will see the SMTP side, along with the server timeout delay and the setting that asks for SMTP authentication. When the values match the provider, Outlook usually stops complaining in its quiet, offended way.

Password changes are less dramatic than many users fear. If the password was changed on the provider’s website, Outlook normally asks for the new one the next time it tries to send or receive. That prompt is the update. No separate hunt is needed.

The deeper confusion starts with Outlook data files. These are not mail accounts. They are local storage files that Outlook creates to hold folders such as Inbox, Outbox, and Sent Items. A POP account uses a .pst file, which lives on the computer. A non-POP account, including IMAP and Exchange, uses an .ost file as a local mirror of online content.

That file type matters when an account is removed. Removing the account from Outlook does not erase the account itself. It only stops Outlook from talking to it. The data file remains, and old messages can still sit in the Folder pane like a box left in the hallway.

If the goal is to remove the account cleanly from Outlook, the process starts in Account Settings on the Email tab. Select the account, remove it, and confirm. Then move to the Data Files tab. If the data file for that account still appears, remove that too. For IMAP and POP accounts, there is also a shorter path through the Folder list by right-clicking the account and choosing the remove option.

That still does not delete the file from the computer. It only removes Outlook’s link to it. The file remains on the hard drive in the default Outlook data file location. Anyone who knows how to add it back can still open it and read whatever it contains. Mail files are patient that way.

To delete the data file for real, Outlook can show the file location. Open Account Settings, go to Data Files, select the file, and choose Open File Location. File Explorer opens to the folder that holds the Outlook data files. From there, delete the unwanted .pst or .ost file directly.

A small example makes the point clear. Suppose a POP mailbox is moved to a new computer. The old inbox may not appear there unless the .pst file is copied and imported. If that file is only removed from Outlook and never deleted from disk, it can still be recovered later and brought back into the Folder pane. The data was not gone. It was only out of sight.

Moving the file to another computer is where the import and export steps matter. POP3 accounts depend on the .pst file if the old mail folders are to survive on the new machine. Exchange and IMAP usually keep the online mailbox in sync, so the local file plays a different role there.

The export side starts in Backstage view from the File tab. Open the Import and Export wizard. Choose to export to a file, then pick Outlook Data File (.pst). Select the folder to export, either a single folder or the top-level mailbox view. Then choose where to save the file and how duplicates should be handled. A password can be added, or skipped.

The import side on the new computer follows the same wizard. Choose to import from another program or file. Select Outlook Data File (.pst), browse to the exported file, and choose how duplicate items should be handled. Then pick the folder to import from and the destination in Outlook. When the import completes, the folders and messages appear in the new mailbox structure.

That is the part many people miss. A migration is not judged by the export dialog. It is judged by the mailbox that opens afterward. If the folders are there, the contacts are there, and the message history still makes sense, the move has held together.

I write it this way because the fix is usually simple once the file type is known. The hard part is not Outlook being mysterious. The hard part is noticing whether the account is editable, whether the file is local, and whether the old data still exists somewhere on disk.

The Migration Brief keeps that promise in plain terms: one practical fix, one file format explained, and one safer way to move your mail.