How to Export a Shared Mailbox from an OST File

If the shared mailbox has fully synced in Outlook, the quickest route is Outlook's built-in Import and Export Wizard, which saves it straight to a PST. If the original Outlook profile or Exchange connection is no longer available, whatever was already cached locally still lives inside the user's Offline Storage Table (OST) file, and a dedicated OST recovery tool such as EdbMails OST to PST Converter can scan that preserved file directly, preview shared-mailbox content that is actually present and readable, and export the required data to PST without needing the original Outlook profile.

How shared-mailbox caching works

Shared mailboxes in Microsoft Exchange Server and Microsoft 365 let several people work out of one common inbox without needing individual credentials for it. A user gets into a shared mailbox through their own Outlook profile once they've been granted the appropriate permission, most commonly Full Access - though having that permission on its own doesn't guarantee the mailbox is cached locally or exportable; that also depends on how Outlook is configured and how the mailbox was added to the profile.

According to Microsoft, when a shared mailbox or shared folder is added to a profile running in Cached Exchange Mode, all of the folders in that shared mailbox that you have access to are downloaded to your local cache by default (see Microsoft's guidance on shared mail folders in Cached Exchange Mode). Because that download includes full folder content rather than just headers, caching a large or heavily used shared mailbox can noticeably grow the size of your local OST file, which in turn can affect Outlook's sync speed and general performance.

Whether a given shared mailbox actually shows up in the OST depends on several factors:

• Cached Exchange Mode is turned on for the main mailbox.
• Outlook is set to download shared folders locally (the default setting).
• How the shared mailbox was added to the profile - automapped, as an additional mailbox, or as an additional account each behave differently; see the next section.
• Outlook has actually finished syncing that shared mailbox.

If cached shared folders are turned off for the profile, Outlook pulls that content straight from the Exchange server instead, and none of it ends up in the local OST.

Automapped mailbox, additional mailbox, or additional account

A shared mailbox can be added to an Outlook profile in one of three ways, and which one is used affects where its data actually lives:

• Automapped - Exchange or Microsoft 365 adds the shared mailbox to your profile automatically once an admin grants Full Access. Automapped mailboxes generally follow the same shared-folder OST caching behavior described above.
• Added as an additional mailbox - a user manually opens another mailbox alongside their own within the same profile. This also generally follows the same OST caching behavior.
• Added as an additional account - the shared mailbox is configured as its own separate account inside Outlook, connected and authenticated independently of your primary account. In this configuration, its data is typically kept in its own data file rather than folded into your primary OST.

This distinction matters for recovery: if a shared mailbox was set up as an additional account, the content you're looking for may not be inside the OST you're examining at all - see "What if the shared mailbox isn't in this OST?" below.

What is - and isn't - in the OST

Only shared-mailbox content that has actually finished syncing to the local cache is present in the OST. Anything still mid-sync, or any folder that was excluded from caching in the first place, will not be available for export from that file.

Online Archive mailboxes are a separate case: a dedicated Exchange or Microsoft 365 Online Archive is not cached into the primary OST under the normal Cached Exchange Mode model, so there is nothing to recover from the OST for archive-only content.

It's also common for a scan to turn up no shared-mailbox content at all. That usually comes down to one of a few things:

• Download Shared Folders was disabled for the profile.
• Sync never completed before the profile or connection was lost.
• The mailbox was added as a separate account, so its data sits in its own data file rather than this OST.
• The content simply remained server-side and was never downloaded locally.

A few prerequisites are worth checking before attempting an export:

• The Outlook profile is (or was) configured with Cached Exchange Mode.
• The shared mailbox had already been added to the profile.
• The user had appropriate permissions, such as Full Access, to the shared mailbox.
• Cached shared folders were switched on if offline data is needed.
• There's enough local disk space for the PST that comes out of the export.

If you're not sure the OST is in good condition, that's fine - preserve the source file as-is and scan it with a recovery tool to see what shared-mailbox content is actually readable, rather than assuming it needs to be in perfect shape first.

As a quick reference, here's how the situation usually maps to the best starting point:

• Shared mailbox live and accessible in Outlook - export or migrate directly from the server or Outlook.
• Shared folders cached in the user's OST; server unavailable - OST recovery may help.
• Shared mailbox added as a separate account - locate that account's own cache/data source instead.
• Online Archive only - use the server/archive recovery path, not the OST.
• An offline EDB is available - EDB-based recovery may cover a broader set of mailboxes.

Method 1: Export using Outlook, when the mailbox is fully synced

If the shared mailbox has fully synced and Outlook can see it normally, the built-in Import and Export Wizard can be used.

Here's the process:

1. Open Outlook.
2. Select 'File' > 'Open & Export' > 'Import/Export'.
3. Choose 'Export to a file'.
4. Choose 'Outlook Data File (.pst)'.
5. Select the shared mailbox, or just a particular folder.
6. Enable 'Include subfolders' if required.
7. Choose where the file should be saved.
8. Complete the export.

This method exports the data currently available within Outlook. Items that have not yet synchronised to the OST are not included.

Method 2: Recover Cached Shared-Mailbox Data with EdbMails OST to PST Converter

In some recovery scenarios, the original Outlook profile or Exchange connection may no longer be available, but the OST file still exists. Outlook itself won't open an orphaned OST or export from it without the matching profile attached - this is an Outlook product limitation tied to how it links a profile to its data file, not a security restriction on the file itself. When Outlook's built-in export options aren't available, you need a tool that can read the OST file directly instead.

This is the kind of scenario the EdbMails OST to PST Converter covers: it scans the preserved OST without needing the original profile, identifies whether shared-mailbox folders are actually present, previews readable content, and exports supported data to PST. Preserve and validate representative folders, item counts, attachments and calendar items before relying on the result. A PST export is a portable recovery copy, not a substitute for a formal backup, retention or eDiscovery policy.

If access to the source file is affected by account credentials, Windows encryption, disk encryption, or another protection layer, resolve authorized access to that layer before attempting recovery. See the OST access and protection troubleshooting guide for the relevant distinction.

  To learn the complete procedure, follow the OST to PST conversion guide.

Direct restore alternatives

If the goal is to recreate the shared mailbox on Exchange or Microsoft 365 rather than just producing a PST file, migrating the recovered data directly to the target mailbox can be more efficient than staging it through a PST first. EdbMails supports migrating recovered OST data directly to a live Exchange server or Microsoft 365 tenant as an alternative to PST staging, where that's supported for your scenario.

EdbMails can scan and preview cached shared-mailbox content in an OST without Outlook. Outlook with a configured profile is required when exporting recovered OST data to PST. Direct migration to Exchange or Microsoft 365 does not require Outlook.

Troubleshooting and validation

1. Shared mailbox folders are missing

   Possible causes include:

   • Cached shared folders are disabled.
   • Synchronization is incomplete.
   • Auto-Mapping has not updated.
   • Insufficient mailbox permissions.
   • The mailbox was added as a separate account with its own data file.

   Verify Outlook's caching settings, confirm mailbox permissions, and allow synchronization to complete before exporting.

2. Exported PST is incomplete

   An incomplete PST usually indicates that Outlook had not fully synchronised the shared mailbox before export. Take a look at the sync status in the Outlook status bar and make sure every folder is showing current data first.

3. Export option is unavailable

   If the Outlook profile has been deleted, or the mailbox on Exchange is inaccessible, Outlook can't export from the existing OST on its own. Getting the data back at that point means either restoring the original profile or using a dedicated OST conversion tool.

4. OST corruption

   A damaged OST can stop sync in its tracks or block Outlook from reading cached data altogether. If the Exchange or Microsoft 365 mailbox is still up and running, rebuilding the Outlook profile will usually create a new OST through a new sync. If server access is unavailable, what you can recover depends on the condition of the existing OST.

Before relying on the result, a short validation pass is worth the time:

• Confirm the shared mailbox and its folders actually appear in the preview.
• Check the last-synchronized date and how recent the content is.
• Compare the folder list against what you expected to see.
• Verify the exported item counts against the source.
• Spot-check a few representative attachments and calendar items.

Best practices for exporting a shared mailbox from OST

• Turn on Cached Exchange Mode for users who require offline access.
• Make sure the shared mailbox has fully synced before exporting.
• Double-check permissions before you attempt the export.
• Avoid deleting Outlook profiles until required exports are complete.
• Back up exported PST files regularly if you need to keep them long-term.
• Keep Outlook up to date so it stays compatible with Exchange and Microsoft 365.
• Open the exported PST in Outlook afterwards just to confirm it came out clean.

Whether you can successfully export a shared mailbox from an OST comes down to three things: how Outlook was caching that mailbox's data, whether the OST had finished syncing, and the availability of the associated Outlook profile and Exchange mailbox. When the mailbox has fully synced, Outlook's own Import and Export Wizard handles it without any extra tools. When the profile or mailbox is no longer available, EdbMails provides technical guidance for supported OST export and direct-migration scenarios where Outlook's built-in capabilities no longer apply.

---

Additional resources:

• EdbMails OST to PST Converter
• OST to PST Converter User Manual
• Recover Orphaned OST File
• Export OST to Office 365
• Recover Password Protected OST File
• Repair Corrupt OST File