Export Shared Mailbox from OST
Shared mailboxes in Microsoft Exchange Server and Microsoft 365 let several people work out of one common inbox without needing individual credentials for it. When Outlook is configured in Cached Exchange Mode, though, the data from a shared mailbox can end up stored locally too, inside the user's Offline Storage Table (OST) file. That's what lets people keep working with synced mailbox content even when they're offline.
There are plenty of reasons someone might need to export a shared mailbox out of an OST - maybe it's for a backup, maybe an account is about to change and the data needs preserving first, maybe it's part of a migration, or maybe the server just isn't reachable and the cached copy is all that's left to work with. If Outlook itself can't get to the original profile or export the mailbox through its normal tools, converting the OST becomes the next option. This is where something like EdbMails OST to PST Converter comes in - it can pull mailbox data out of a supported OST file and turn it into a PST. Below, we'll walk through how Outlook actually caches shared mailbox data, the ways you can export it, where the limitations lie, and best practices for maintaining data integrity.
Understand the shared mailbox and OST relationship
A shared mailbox lives on Exchange Server or Microsoft 365, and a user gets into it through their own Outlook profile once they've been given the right permissions, such as Full Access, which are assigned.
When Cached Exchange Mode is switched on, Outlook builds an OST file that mirrors the mailbox data. Depending on Outlook configuration, this cache may also include content from shared mailboxes.
Whether the 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 shared mailbox got added automatically through Auto-Mapping, or was added manually.
- Outlook has actually finished syncing that shared mailbox.
If cached shared folders are turned off, Outlook just pulls everything straight from the Exchange server instead, and none of that shared mailbox content ever makes it into the OST.
What Cached Exchange Mode means for shared mailbox caching
Cached Exchange Mode improves performance by maintaining a local copy of mailbox data so Outlook isn't constantly reaching out to the server, and syncs changes between the Exchange server and the OST.
For a shared mailbox, Outlook downloads only the folders that have been set to cache. If the mailbox is large, that sync can take a while depending on its size, your network, and how sync is configured. And if the sync hasn't finished, anything recently added or changed might not be available for export.
Prerequisites: Export shared mailbox from OST
A few things are worth checking before trying to export a shared mailbox from an OST:
- Outlook profile is configured with Cached Exchange Mode.
- The shared mailbox has already been added to the profile.
- The user has appropriate permissions, such as Full Access, to the shared mailbox.
- Cached shared folders are switched on if you need offline data.
- Outlook has finished syncing with Exchange or Microsoft 365.
- The OST file itself is in good shape and accessible.
- There's enough disk space locally for the PST that comes out of the export.
Verifying these prerequisites helps avoid incomplete exports and synchronisation-related issues.
Methods to export a shared mailbox from OST
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:
- Open Outlook.
- Select ‘File’ > ‘Open & Export’ > ‘Import/Export’.
- Choose ‘Export to a file’.
- Choose ‘Outlook Data File (.pst)’.
- Select the shared mailbox, or just a particular folder.
- Enable ‘Include subfolders’ if required.
- Choose where the file should be saved.
- Complete the export.
This method exports the data currently available within Outlook. Items that have not yet synchronised to the OST are not included.
Export using an existing OST file
In some recovery scenarios, the original Outlook profile or Exchange connection may no longer be available, but the OST file still exists. The problem is that Outlook cannot open an orphaned OST or export from it without the matching profile attached. When Outlook's built-in export options are unavailable, you need something that can read the OST file directly instead. This is the kind of scenario EdbMails covers with its OST to PST conversion approach - it's built for cases where Outlook simply can't do the export itself because the original profile or mailbox is unavailable.
Important considerations
Several technical factors determine whether a shared mailbox can be successfully exported from an OST.
- OST ownership
An OST file belongs to whichever Outlook profile and Windows user account created it. Outlook won't let you open it under a different profile.
- Exchange profile dependency
The file stays linked to the Exchange or Microsoft 365 configuration. Remove that profile, and Outlook loses the ability to reuse the existing OST for an export.
- Offline cache limitations
The OST only holds mailbox content that's actually finished syncing. Anything still in progress, or anything excluded from caching in the first place are unavailable for export.
- Archive mailbox considerations
Online archive mailboxes aren't necessarily stored locally. If the archive folders stay online-only, they never make it into the OST - which means there's nothing to export from it.
- Permissions
You can only export what you actually have permission to access. Insufficient permissions may prevent Outlook from synchronising folders or exporting mailbox content.
- Encryption and mailbox association
OST files do carry their own internal encryption and are associated with a specific mailbox, but they are not protected by a user-defined password. Outlook checks the mailbox configuration before accessing the file.
Troubleshooting Guide to Export Shared Mailbox from OST
- Shared mailbox folders are missing
Possible causes include:
- Cached shared folders are disabled.
- Synchronization is incomplete.
- Auto-Mapping has not updated.
- Insufficient mailbox permissions.
Verify Outlook's caching settings, confirm mailbox permissions, and allow synchronization to complete before exporting.
- 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.
- 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 - it's simply too dependent on that original profile. Getting the data back at that point means either restoring the original profile or using a dedicated OST conversion tool.
- 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.
Export Shared Mailbox from OST by EdbMails
When Outlook can't export a shared mailbox - whether because the profile's gone, the mailbox is unreachable, or the OST is orphaned - EdbMails OST to PST Converter provides an alternative method to recover and export the cached mailbox data. It reads supported OST files directly, without needing the original profile, and converts the mailbox into a PST while keeping the full structure intact: emails, contacts, calendar items, tasks, notes, attachments, and the folder hierarchy all stay as they were. The resulting PST opens straight in Outlook, whether you need it for a backup, legal discovery, restoring a mailbox, or moving it to a different Exchange or Microsoft 365 environment.
To learn the complete procedure, follow the Steps to Export Shared Mailbox from OST guide.
Best Practices to Export 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
Following these practices helps maintain data consistency and reduces the likelihood of incomplete mailbox exports.
Conclusion
Whether you can successfully export a shared mailbox from an OST really 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. But if the profile or mailbox is no longer available, Outlook can't work with an orphaned OST on its own because of its dependency on the original Exchange configuration. In these situations, EdbMails provides technical guidance for supported OST export scenarios where Outlook's built-in capabilities are no longer applicable. Understanding how caching, permissions, sync status, and OST limitations all interact is really the key to getting a clean, complete export.
