How to Convert OST to PST: 3 Free Native Methods vs Standalone Converter

Converting an Offline Outlook Data File (.ost) to a Personal Storage Table (.pst) is a standard requirement when migrating mailboxes, archiving older communications, or recovering messages after an account deactivation.

Your available methods depend entirely on one key condition: Can Microsoft Outlook still open and connect to the underlying email account?

• If Outlook opens and connects to your account: Microsoft provides three native, zero-cost mechanisms to export or copy your data into a .pst file without third-party software.
• If your OST file is orphaned or Outlook cannot open it: An .ost file is cryptographically bound to the specific Exchange/M365 profile that created it. Outlook cannot open or import a disconnected .ost file from another profile or deleted account. In that situation, native tools cannot access the data, and an offline converter is required.

Comparison: Native Outlook Methods vs Standalone Converter

Understanding the Difference: Active vs Orphaned OST Files

An Outlook Data File (.ost) is a local offline cache of your mailbox synchronized from Microsoft Exchange, Microsoft 365, or an IMAP server.

Because the .ost file is tightly linked to your account's unique MAPI profile and security identifiers (SIDs) in Active Directory:

• Active OST: The email account exists, credentials authenticate properly, and Outlook opens normally. In this state, Outlook reads the local cache and can readily export items to any standard .pst file.
• Orphaned OST: The Exchange server was decommissioned, the user account was deleted or disabled, or the user profile on Windows was recreated. In this state, Outlook will display error messages such as "The file cannot be opened" or "Your Outlook data file cannot be configured." Outlook will not let you open an orphaned .ost file via File > Open, nor can the built-in wizard read it.

Method 1: Export OST Data Using Outlook's Import/Export Wizard

If your Outlook profile is intact, the built-in Export wizard is the most reliable free way to create a portable PST archive.

Step-by-Step Instructions:

1. Open Microsoft Outlook on your Windows workstation.
2. Navigate to File in the top ribbon, click Open & Export, and select Import/Export.
3. In the Import and Export Wizard dialog, select Export to a file and click Next.
4. Choose Outlook Data File (.pst) and click Next.
5. Select the root folder of your account (e.g., your email address) so all mailbox contents are included.
6. Crucial Step: Ensure the checkbox Include subfolders is checked. If this is left unchecked, Outlook will only export the root container without your actual emails, calendar, or contacts.
7. Click Browse to choose a destination path and filename for your .pst file.
8. Under Options, select how to handle duplicate items (the default Replace duplicates with items exported is generally recommended).
9. Click Finish. You can optionally assign an encryption password to the PST file, or leave the password fields blank and click OK.
10. Outlook will export the selected folders to your destination PST. The progress window will close automatically when the export finishes.

Method Evaluation:

• Pros: 100% free and native; preserves email folder hierarchy, attachments, contacts, and calendar entries.
• Cons: Strictly requires an operable Outlook profile; cannot process orphaned or disconnected .ost files.

Method 2: Manual Folder Copy into a New PST File

For users who want to selectively export specific folders (such as Inbox or Sent Items) without running through the wizard, Outlook allows creating a fresh PST file and copying folders directly.

Step-by-Step Instructions:

1. Open Outlook and navigate to the Home tab.
2. Click New Items > More Items > Outlook Data File. (Alternatively, go to File > Account Settings > Account Settings > Data Files tab and click Add).
3. Specify a file path and name (e.g., Manual_Backup.pst) and click OK.
4. The new empty PST file will appear in Outlook's left-hand navigation pane alongside your primary mailbox.
5. In your active mailbox folder tree, right-click the folder you want to export (e.g., Inbox) and choose Copy Folder.
6. In the Copy Folder dialog, scroll to your newly created PST file, select the destination, and click OK.
7. Outlook will copy all messages and subfolders to the PST file.
8. Once copying is complete, right-click the top-level name of the PST file in the navigation pane and select Close "Manual_Backup" to safely detach the file before moving it to another machine.

Method Evaluation:

• Pros: Completely free; lets you review and select exactly which folders transfer; leaves original messages untouched on the mail server.
• Cons: Must be performed manually folder by folder; requires an active Outlook environment.

Method 3: Export via Outlook AutoArchive (With Important Precautions)

Outlook includes an automated background archiving feature that offloads older messages from the primary mailbox into an archive PST file. While this can be used as a free method to generate a PST, it requires careful understanding of how AutoArchive operates.

Step-by-Step Setup:

1. In Outlook, navigate to File > Options > Advanced.
2. In the AutoArchive section, click the AutoArchive Settings... button.
3. Check the box Run AutoArchive every X days and set the interval (e.g., 1 day).
4. In the Clean out items older than section, specify the age threshold.
5. Under Move old items to, choose your destination path for the archive .pst file.
6. Click OK to apply the global configuration.
7. To trigger archiving immediately on a specific folder, right-click that folder (e.g., Inbox), choose Properties, select the AutoArchive tab, and confirm its individual archive rules.

⚠️ Critical Precautions & Limitations of AutoArchive:

• Moves, Not Copies: By default, AutoArchive moves messages from your OST/server mailbox to the local PST. This means items are deleted from the server mailbox to free up quota. If your goal was to create a safety copy while keeping server data intact, AutoArchive will alter your server mailbox unless strictly configured.
• Excluded Folder Types: By default, AutoArchive does not process Contacts, Notes, or certain system folders.
• Exchange Admin Overrides: In corporate Microsoft 365 or Exchange environments, administrators frequently disable AutoArchive via Group Policy (GPO) or override it with Exchange Retention Policies / Messaging Records Management (MRM). If retention tags are enforced by your tenant administrator, local AutoArchive settings may have no effect.
• Modified Date Dependency: AutoArchive calculates item age using the Modified Date of an email (when it was last moved, edited, or flagged), not the Received Date. Recent folder reorganizations can prevent older emails from being archived.

Technical Note: Why PowerShell COM Scripts Are Not a Simple One-Liner

Some online guides suggest using PowerShell scripts with the Outlook COM object (New-Object -ComObject Outlook.Application) to convert OST to PST.

It is important to understand what COM scripting actually does:

# This command ONLY mounts an empty PST store into an active Outlook profile:
$Outlook = New-Object -ComObject Outlook.Application
$Namespace = $Outlook.GetNamespace("MAPI")
$Namespace.AddStoreEx("C:\Backups\Export.pst", 1)

Running $Namespace.AddStoreEx() simply attaches an empty PST file to Outlook's active session. It does not copy, export, or convert any emails or folders by itself.

To actually transfer items using PowerShell COM, a script must:

1. Enumerate each folder and item in the source mailbox recursively.
2. Call $Item.Copy().Move($TargetFolder) for every individual message.
3. Handle MAPI security prompt dialogs that block programmatic access to Outlook address books and message bodies.
4. Explicitly release every COM object using [System.Runtime.InteropServices.Marshal]::ReleaseComObject() to avoid process leaks and file locks.

Because COM automation still requires a fully functional, authenticated Outlook client and is significantly slower than Outlook's native GUI wizard, writing custom PowerShell COM loops is rarely practical for standard end-user conversions. For enterprise server-side exports across multiple mailboxes, administrators should use Microsoft 365 Compliance Search / eDiscovery export tools or Exchange Management Shell (New-MailboxExportRequest) rather than client-side COM scripts.

When Native Methods Fail: Standalone Offline OST Conversion

When the Exchange account is permanently deleted, the active directory user is removed, or the .ost database header is damaged, Outlook's native export tools cannot be used.

In these circumstances, a dedicated offline parser like Prism OST to PST Converter provides an alternative extraction path:

• Direct B-Tree Parsing: The engine reads the raw database structures of the .ost container directly from disk without requiring Microsoft Outlook to be installed or configured.
• Processes Orphaned Files: Because it parses the offline file independently, it does not require Exchange server connectivity, Active Directory authentication, or valid MAPI profile registry entries.
• Read-Only Operation: Source .ost containers are opened in strict read-only mode to prevent write locks or accidental corruption during analysis.
• Evaluation Availability: Prism OST to PST Converter is commercial software. A free evaluation version is available that provides full mailbox folder scanning, item-level previews (subject, sender, body, and attachments), and allows converting up to 50 items per folder to verify conversion fidelity before purchasing a license.

Step-by-Step Offline Extraction:

1. Download and launch Prism OST to PST Converter on your Windows workstation.
2. Click Add File and select your orphaned or disconnected .ost file.
3. The software scans the database hierarchy and displays a folder tree alongside email previews.
4. Select PST as your target output format and specify an output folder.
5. Click Convert to parse the offline mailbox and write out standard RFC-compliant PST files.

Frequently Asked Questions

Can I open an orphaned OST file directly in Microsoft Outlook?

No. Microsoft Outlook does not permit opening an .ost file through File > Open > Outlook Data File. Outlook only allows opening .pst files directly. OST files can only be accessed by the specific email profile and server account that initially generated them.

Where is the default OST file location on Windows 10 and 11?

By default, Outlook stores cached .ost files in the following user directory:

%localappdata%\Microsoft\Outlook

(Typically: C:\Users\<Username>\AppData\Local\Microsoft\Outlook)

What is the maximum size limit for Outlook PST and OST files?

In Outlook 2013, 2016, 2019, 2021, and Microsoft 365, Unicode .pst and .ost files have a default administrative limit of 50 GB. While registry entries (MaxLargeFileSize) can theoretically expand this limit, files approaching or exceeding 50 GB experience slower search indexing and elevated risk of structural instability.

Does converting an OST to PST alter the original file?

Native Outlook exports read from the active cache and write new data into the PST without modifying the local OST (with the exception of AutoArchive, which moves messages). Dedicated offline converters such as Prism operate strictly in read-only mode, leaving the source .ost file intact on disk.