Practical Step-by-Step Guide to Migrate OST to Office 365 (Exchange Online)

How to migrate OST to Office 365: overview

To migrate OST to Office 365 requires converting or exporting data from an Outlook offline file and then importing that mailbox data into Exchange Online. This guide explains safe, repeatable methods, prerequisites, and an actionable checklist so an administrator or technician can complete the migration with minimal disruption.

Plan and prerequisites to migrate OST to Office 365

Before starting, inventory OST files, confirm Outlook/Exchange versions, and verify Office 365 licensing for the target mailboxes. Important terminology: OST = offline Outlook Data File; PST = Personal Storage Table. OST files are linked to a profile and cannot be imported directly into Exchange Online without conversion.

Pre-migration checklist: OST→365 Migration Checklist

• Confirm user identity mapping (old mailbox → new Office 365 mailbox).
• Back up OST (copy the .ost file) and document sizes and dates.
• Verify Outlook version and connectivity; install any required updates.
• Decide migration method: convert OST to PST, export via Outlook, or rebuild/resync mailbox.
• Set timeline for move, communicate with users, and prepare recovery steps.

Step-by-step methods to migrate OST to Office 365

Two practical methods are most common: convert/export OST content to a PST and import the PST into Office 365, or re-create the mailbox and let Outlook resynchronize from Exchange if the server copy exists. The chosen method depends on access to the original mailbox and the OST state.

Method A — Convert OST to PST and import (most reliable)

1. Open the source Outlook profile and export mailbox data to a PST using Outlook's Export feature or a trusted OST-to-PST converter if the OST is orphaned.
2. Validate the PST: check folder counts and important items (calendar, contacts, attachments).
3. Use the Microsoft 365 Import service or Outlook to upload/import the PST into the target Office 365 mailbox. For the Microsoft 365 Import service, follow the import steps and mapping rules.

Method B — Recreate profile and resync (preferred when server copy exists)

1. Ensure the original mailbox still exists on the Exchange server. Create the target Office 365 mailbox or migrate the mailbox via hybrid/IMAP tools as needed.
2. Set up the user in Office 365 and configure Outlook profile to point to the new mailbox; Outlook will download server data, making OST re-population possible without conversion.

When to use each method

Use conversion when the OST is orphaned or when server-side mailbox is gone (terminated accounts). Use resync when a server copy is present and network time is acceptable.

Practical tips for a smooth OST to Office 365 migration

• Tip 1: Validate message counts after export and again after import—use folder-level checksums or simple counts to ensure completeness.
• Tip 2: Keep a separate export of critical folders (Inbox, Sent, Calendar) before bulk import to simplify recovery if something fails.
• Tip 3: Test the full workflow with one pilot mailbox of similar size and complexity before bulk runs.
• Tip 4: For large PST imports, schedule off hours and monitor throttling limits in Exchange Online.

Common mistakes and trade-offs

Common mistakes

• Attempting to import an OST file directly without conversion—OST is not importable by Exchange Online.
• Failing to verify folder and item counts after import, which can hide missing emails or calendar items.
• Not accounting for duplicate items when merging PST content into an existing mailbox.

Trade-offs

Converting OST to PST then importing is reliable but can be time-consuming and may require third-party tools for orphaned OSTs. Recreating profiles and resyncing is faster when a server copy exists but will not help if the mailbox was deleted or corrupted.

Real-world example

Scenario: A contractor left and the company deleted the Exchange mailbox. The IT team has an OST on a laptop. Using Method A, the OST was converted to a PST, exported via Outlook, then uploaded using the Microsoft 365 Import service to a litigation-hold mailbox. Validation showed 98% of items matched; missing items were recovered from the backup PST copy and reimported.

Core cluster questions

• How can an orphaned OST be converted to a usable PST?
• What is the process to import a PST into Exchange Online?
• When should a mailbox be rebuilt instead of importing data?
• What tools are available for OST-to-PST conversion and validation?
• How to handle calendar and contact data when migrating OST to Office 365?

For official guidance on importing PST files into Office 365 using Microsoft services, see the Microsoft documentation: Import PST files to Office 365.

Troubleshooting checklist

• Check Outlook profile connectivity and update credentials if import stalls.
• Run SCANPST on PSTs created from OST conversions to fix corruption before import.
• Monitor Exchange Online throttling logs and retry imports with exponential backoff.

Next steps and governance

Document the migration steps and retention settings applied post-import. Consider retention policies, litigation hold, and mailbox auditing in Office 365 to meet compliance needs.

FAQ: How to migrate OST to Office 365 without data loss?

Ensure OST is exported to PST, validate item counts and folder structure, then import into the target mailbox using the Microsoft 365 import workflow. Keep backups at every stage.

FAQ: Can Office 365 import an OST file directly?

No. OST files are linked to an Outlook profile and must be converted or exported to PST before importing into Exchange Online.

FAQ: What are safe conversion tools or approaches for orphaned OST files?

Use reliable OST-to-PST conversion utilities or the Outlook export function when the profile can be loaded. After conversion, validate with a copy of the PST and use scan utilities to check integrity.

FAQ: How long does it take to migrate OST to Office 365?

Time varies by mailbox size and method: small mailboxes (under 5 GB) can be done in under an hour; larger or many mailboxes might require scheduled batches and off-hours windows.

FAQ: How to prevent duplicates and missing items during OST to Office 365 migration?

Validate exports before import, import into a clean mailbox or staging mailbox, and use item counts and spot checks for calendar/contacts. If duplicates occur, use mailbox cleanup tools or scripts to deduplicate after import.