PST and OST files store Outlook email data

PST and OST files store Outlook email data. That is the plain answer, and it is the one that matters when the file will not open, the export looks thin, or a mailbox seems to have split itself into pieces for no good reason.

I keep the wording simple on purpose. A PST file is a local Outlook data file. An OST file is a local offline copy of a mailbox that Outlook keeps in sync with a server. Both can hold mail, contacts, calendar items, tasks, notes, and other Outlook data. Microsoft also notes that POP accounts use PST files, while Exchange, IMAP, and Outlook.com accounts use OST files for synchronized mailbox data.

That difference is easy to miss. People often see both file types sitting on the same computer and assume they serve the same job in the same way. They do not. A PST is usually the file you can move, back up, or open as a data store. An OST is tied to a profile and a synced mailbox. It is a working copy, not the master record. That small detail causes a lot of confusion, and Outlook is happy to keep it that way.

What matters most is this: the file type says something about where the data lives and how Outlook uses it. If the mailbox is on a server and Outlook is syncing it, the OST is the local copy. If the data is stored as a personal file, or if Outlook is using a POP account, the PST is the container. The data itself is still Outlook data either way. The file name just tells you how Outlook is holding it.

That is why a simple export can still leave people uneasy. An export that finishes without error is not the same as a clean move. The folders may look right at first glance, but the real test is whether the messages, contacts, and other items made the trip in full. I trust the file list less than the mailbox view, and that is not cynicism. It is experience with how mail tools like to be technically correct and practically annoying at the same time.

The other useful fact is that PST and OST files are not magic buckets. They have limits, and those limits change by Outlook version and setup. Microsoft documents size limits and format details that vary by version and file type, so it is poor practice to treat every PST or OST the same. A file that works in one setup may behave differently in another. Mail systems love fine print. It keeps the rest of us employed.

There is also one honest limit here. A PST or OST file can hold the data, but that does not mean the data is easy to recover if the file is damaged. Corruption, sync problems, and profile issues can blur the line between the local file and the mailbox behind it. Sometimes the file is the problem. Sometimes the profile is. Sometimes Outlook is simply telling a sad little lie about what it thinks it synced. The file type helps, but it does not solve every case.

So the clean mental model is this. PST stores Outlook data in a local file. OST stores a synced local copy of Outlook data from a server account. Both are part of the same Outlook world, but they do different jobs. If the goal is to understand where the mail is and what kind of file is involved, that is enough to start with.

That is the part worth keeping in view. A migration only counts when every message, folder, and contact survives intact. If the file type is wrong for the job, or if the sync state is not what it seems, the move can look fine and still miss the point. That is usually where the simple cause lives.

The Migration Brief stays close to that idea: one practical fix, one file format explained, and one safer way to move your mail.