Download Buy Now

How to Import an OST File into Exchange Server

Exchange Server natively imports PST files through Mailbox Import Requests, not arbitrary OST files.

An orphaned or offline OST therefore has to be read by a recovery/migration tool, or converted to PST first, before its data can reach an Exchange mailbox.

This method imports OST data directly into Exchange without creating a PST file. If you need a standalone PST, for backup, legal hold, or use outside Exchange, use the EdbMails OST to PST Converter instead.

Importing an OST file into an Exchange Server mailbox can be necessary in scenarios such as recovering data from a damaged Outlook profile, restoring mailboxes after unexpected system failures, or transferring user data to a new Exchange setup. If the original Exchange mailbox is still available, Outlook can reconnect to the mailbox and create a new OST cache, so importing the old OST may not be necessary. A specialized OST recovery or migration tool is required when data must be recovered from an orphaned, inaccessible, or damaged OST file and restored to Exchange Server.

The EdbMails OST to Exchange Server migration tool scans the source OST, previews readable folders and items, maps them to target mailboxes, and migrates selected recoverable data without PST staging.

Import OST to Exchange

The workflow lets you select the OST, connect to the destination Exchange Server, map source and target mailboxes, and choose the required folders. Verify the mapping and representative target items after migration.

Why import OST to Exchange Server?

There are various scenarios where you may need to migrate your emails from OST to Exchange Server. Some of the common scenarios are:

Recovering OST Data During an Exchange Server Change: When the original Exchange mailbox is still available, a normal Exchange-to-Exchange migration should move the server-side mailbox directly rather than use the workstation OST file. OST recovery is appropriate when the old OST contains required data that is no longer available in the source mailbox and must be restored to the target Exchange Server.
Switching to a Different Computer: If the Exchange mailbox is still available, configure Outlook with the Exchange account on the new computer and allow Outlook to create a new OST cache from the server. Recover the old OST only when it contains required local data that is missing from the server-side mailbox.
Recovery after System Crash: If the OST file survives a system crash but becomes inaccessible or damaged, it can be scanned to identify recoverable mailbox data before migration to Exchange Server. If the OST file itself was lost during the crash, it must first be restored from an available backup or storage recovery source before any OST recovery or migration can be attempted.
Migrating Recovered OST Data to On-premises Exchange Server: If mailbox data is available only in an old or orphaned OST file, the recoverable items can be migrated to an available mailbox on the target on-premises Exchange Server.

OST Migration vs Native PST Import to Exchange Server

Path	Source format	When to use
Exchange Mailbox Import Request	PST	Microsoft-supported PST import to Exchange Server
EdbMails direct migration	OST	Recover readable data from an offline or orphaned OST and migrate it to Exchange Server

Prerequisites Before You Start

A supported Exchange Server version on the target end.
The target mailbox already created and available on that server.
The connection permissions EdbMails needs for your setup — a full-access account, an individual user login, or a CSV-based batch of credentials, depending on how many mailboxes you're migrating. Full admin/impersonation rights aren't always required; see connecting without impersonation rights for the lower-privilege options.
Sufficient quota on the target mailbox for the data you're migrating.
Network connectivity between the machine running EdbMails and the target Exchange Server.
If the source OST is damaged or you're working a forensic/sensitive case, work from a preserved copy of the file rather than the only copy.

Exchange OST Import Preflight

Confirm the source, target, permissions and migration scope before starting the job.

Area	Preflight question	Validation
Target	Is the correct Exchange mailbox active and available?	Sign in and verify folder access before migration.
Permissions	Does the approved account have the required mailbox access?	Use a limited pilot job before the full scope.
Source	Is the OST a current cache, an orphaned file or a damaged recovery source?	Preserve a copy and preview the required folders.
Scope	Which folders, dates and item types must move?	Record filters and reconcile logs after migration.

Steps to import OST to Exchange with EdbMails
- Step 1: Download and install EdbMails software
  - Download and install the EdbMails application on your computer.
  - Launch the EdbMails software on your system.
  - Enter your registered email address and password, then click ‘Login’. New users can select ‘Start Your Free Trial’ to continue with the trial version.
    Trial note: The trial processes up to 30 items per folder. See the current pricing page for full-license details.
  - Select ‘OST Recovery and Migration’
  - Select ‘OST to an Exchange Server’.
  - You may continue with the default job name or select the ‘New Job’ option to assign a different name
  - Then, click ‘Next’ to continue.
- Step 2: Select the Outlook OST file that you want to import
  - Click ‘Browse for OST file'.
  - Choose the offline OST file stored on your local drive and click ‘Next’ to proceed. Alternatively, you may select an OST file from an accessible network location, provided the EdbMails application has the required permission to read the source OST file.
  - EdbMails scans the selected OST file and displays mailbox data that can be read and recovered from the source. For damaged or partially corrupted OST files, the amount of recoverable data depends on the condition and readability of the file. Scan time can vary based on the OST file size and level of corruption.
  - Once the recovery scan finishes, the recoverable OST data appears within the application, showing the readable folder and subfolder structure detected in the source. Users can navigate through any folder to explore its contents. Selecting items such as Emails, Contacts, Notes, Tasks, or Calendar displays all related entries along with a detailed preview panel on the right. This lets you access OST file contents directly within the application, without requiring Outlook.
- Step 3: Complete the migration
  - Once your OST file is selected, preview and choose the required folders, connect to your target Exchange server, map the source and target mailboxes, and start the migration.
  - EdbMails displays migration progress and a completion summary for the job. Review the logs and representative target items before closing the migration.
  See the full step-by-step OST to Exchange migration guide for detailed screenshots and instructions.

OST-to-Exchange migration controls

Direct Import without Outlook Dependency: EdbMails lets you import OST files directly into an Exchange Server Mailbox without requiring Outlook, the original Outlook profile, or time-consuming manual steps such as Export OST to PST and Import OST to PST. This simplifies recovery from orphaned or inaccessible OST files.
Damaged OST handling: The application displays mailbox data that remains readable in the source. Severe corruption can prevent some folders, items, or properties from being recovered.
Selective and Controlled Data Import: Instead of exporting the entire mailbox, EdbMails allows selective migration of folders or items. This targeted approach can reduce unnecessary data transfer and helps keep the migration scope aligned with the recovery requirement.
Simplified Exchange Migration: Compared to scripting-based native migration methods, EdbMails offers a guided interface with automatic mailbox mapping and optional mailbox creation. Review the generated mapping before migration so that the selected OST source is aligned with the intended Exchange mailbox.
Preserves Readable Mailbox Data: EdbMails migrates recoverable and readable mailbox data while preserving supported email properties such as sender, recipients, timestamps, attachments, and folder hierarchy.
Supports Bulk OST Import: For multi-mailbox projects, use the batch/mapping options supported by the current EdbMails build and verify each source-to-target mapping before migration.
Pause, Resume, and Monitor Migration Progress: The tool supports pause and resume controls where available for the current workflow. After an interruption, verify job status and logs before resuming.
Logs and migration reports: EdbMails generates migration logs and status reports to support operational review. Reports complement, but do not replace, validation of representative target folders and items.

Validate the Target Mailbox

Review the migration summary and job report after completion.
Check folder placement and parent/subfolder structure against the selected source scope.
Open representative messages from different dates and folders.
Check attachments, contacts and calendar items separately when they were included.
Review skipped items, failures and retries in the job log.
Confirm that the target mailbox is accessible in its normal client.
Use a repeat or retry process only when it is supported and appropriate for the current workflow.

Limitations to Keep in Mind

Scanning a damaged OST surfaces whatever is readable — severely damaged files may still have some items that can't be recovered.
Direct OST-to-Exchange migration does not require Outlook; Outlook with a configured profile is only needed if your workflow first exports the OST to PST.
This page doesn't cover how repeat jobs on the same source handle already-migrated items — check current EdbMails documentation if that matters for your workflow.
EdbMails only needs the read/connection permissions described in Prerequisites above — it doesn't require the network-share configuration Exchange's own PST Import Service uses.

Frequently Asked Questions

Can Exchange Server import OST files natively?
No. Exchange Server's native import path is Mailbox Import Requests, which accept PST files, not arbitrary OST files. An orphaned or offline OST needs to be read by a recovery/migration tool, or converted to PST first, before it can reach an Exchange mailbox.
Can I import an OST without converting it to PST first?
Yes. EdbMails migrates recovered OST data directly to Exchange Server without a PST staging step. Converting to PST is only needed if you specifically want a portable file instead.
Do I need Outlook installed?
Not for direct OST-to-Exchange migration. Outlook with a configured profile is only required if your workflow exports the OST to PST instead.
What Exchange permissions are required?
It depends on your setup — a full-access account, an individual user login, or a CSV-based batch of credentials for multiple mailboxes. Full admin/impersonation rights aren't always necessary; see the Prerequisites section above for lower-privilege options.
Can I import selected folders only?
Yes. You can choose specific folders or items rather than migrating the entire mailbox, which keeps the target mailbox size and migration time down.
Can I migrate multiple OST files?
Yes, using CSV-based mailbox mapping to migrate several source OST files to their corresponding target mailboxes in one batch.
What if the source OST is corrupted?
EdbMails scans the file and displays whatever mailbox data can be read and recovered. Severely damaged files may still have some items that aren't recoverable.

Additional resources

In this manual

Introduction Reasons to Import Steps to Import

OST to Exchange migration

Just $129 Onwards

Buy Now

Need help?

24/7 Customer support

Personalized Demo

Book a personalized demo

Still need help?

Email us / Call us