Use Outlook PST and OST files for Office 365 backup

Use Outlook PST and OST files for Office 365 backup.

That is the plain answer, even if Outlook does not make it feel plain. A PST file is the one that matters for backup work. It is a local Outlook data file that can hold mail, contacts, calendar items, tasks, notes, and journal entries. An OST file is different. It is a synced copy of a mailbox that lives on the device and mirrors the server copy. Microsoft says the OST is a local copy, while the PST can be used to back up or export Outlook data.

That difference does most of the work here. If the goal is Office 365 backup, the PST is the useful file. It can be created by exporting Outlook data, and Microsoft notes that PST files can be used to back up, export, and restore Outlook items. The OST is not the same kind of safety copy. It is built for offline access and sync, not for moving as a permanent archive. Microsoft also says an OST is recreated when the account is set up again, which is a polite way of saying it is not the thing to trust as your only backup.

The part people miss

Office 365 mailboxes are usually already stored on Microsoft’s servers. That sounds safe, and in one narrow sense it is. Microsoft says Microsoft 365, Exchange, and Outlook.com accounts keep the live mailbox on the server, with Outlook holding a synchronized local copy in an OST file. So the server is the source of truth, and the OST is just the local mirror.

That is why backup and sync get mixed up so often. A synced copy feels protected until the local file breaks, the profile changes, or the account is rebuilt. Then the OST often comes back empty or is rebuilt from the server again. Useful? Yes. A backup? Not really.

A PST file is different because it is a portable Outlook data file. Microsoft says it can store Outlook items and can be used to back up or export data from an Outlook account. That makes it the file type that fits the backup job.

What this means in practice

When people ask about Office 365 backup, they usually mean one of two things. They either want a copy they can move to another machine, or they want an archive they can keep apart from the live mailbox. PST fits both jobs better than OST.

This is also where a small warning belongs. A PST backup is not magic. It is only as complete as the export that created it, and large or damaged mailboxes can still cause trouble. Microsoft’s repair guidance even tells users to back up the existing Outlook data file before using repair tools, which is a quiet reminder that files can fail in ways no one enjoys. I take that seriously. A finished export is nice. A complete, readable backup is the part that counts.

The other limit is simple. Outlook file behavior can vary by account type, Outlook version, and setup. Microsoft’s own pages note that requirements and defaults differ across Microsoft 365, Exchange, IMAP, and Outlook.com accounts, and that OST files are tied to sync behavior rather than portable backup. That means the idea stays steady, but the exact path can shift.

The clean rule

Here is the rule that holds up best: use PST for backup and export, and treat OST as a local working copy. That is the line worth remembering when someone says “I have the file already, so I’m safe.” Sometimes the file is just the shadow.

I like that this is a simple answer. Outlook has enough little traps without adding confusion here. If the job is Office 365 backup, the PST is the file that does the real work. The OST helps you work while the mailbox syncs. It does not replace a backup plan, no matter how hard it tries to look helpful.

The real goal is bigger than a file extension. It is keeping every message, folder, contact, and calendar item intact when the mailbox moves or needs to be restored. That is the standard I trust, and it is the standard I use when the export button has done its neat little trick but the job is not really done.

The Migration Brief keeps that same shape in mind: one practical fix, one file format explained, and one safer way to move your mail.