How to Import PST Files into Office 365

Introduction

Learning how to import PST to Office 365 is one of the most common tasks IT administrators face when migrating from legacy email systems or consolidating old mailbox data into the cloud. PST files, which store emails, contacts, calendar items, and other Outlook data, can accumulate over years of use and represent a significant archive of business communication. Getting that data into Microsoft 365 safely and efficiently requires understanding the available tools and following a clear process. This guide walks you through everything you need to know, from the basics of PST files to a step-by-step walkthrough of the import process.

What PST Files Are and Why They Matter

A PST file, short for Personal Storage Table, is a proprietary Microsoft file format used by Outlook to store copies of messages, calendar events, contacts, tasks, and other mailbox items locally on a user's computer. These files were the backbone of email archiving for decades, especially in environments where Exchange Server storage quotas were tight or where users wanted offline access to old messages. Over time, PST files can grow to several gigabytes, and organizations often end up with dozens or even hundreds of them scattered across workstations, shared drives, and backup tapes.

The problem with PST files in a modern business context is that they are fragile, difficult to manage, and essentially invisible to IT administrators. Because they live on local machines, they cannot be searched, audited, or protected by centralized backup solutions. When a hard drive fails or an employee leaves, that PST file and everything in it can disappear permanently. Moving PST data into Microsoft 365 solves these problems by placing historical email into a managed, searchable, and redundant cloud environment where it is protected by Microsoft's enterprise-grade infrastructure and accessible from any device.

How the Microsoft 365 Import Service Works

Microsoft provides a built-in service called the Office 365 Import Service, accessible through the Microsoft Purview compliance portal. This service supports two primary methods for getting PST files into Exchange Online mailboxes: network upload and drive shipping. Network upload involves uploading PST files directly to a temporary Azure Blob Storage location using a tool called AzCopy, after which an administrator creates an import job that maps each PST file to the appropriate mailbox. Drive shipping is a physical option where you copy PST files onto an encrypted hard drive and mail it to a Microsoft data center, which is better suited for organizations dealing with extremely large datasets or limited internet bandwidth.

Once the PST files are staged in Azure Blob Storage, the import job uses a mapping file in CSV format to tell Microsoft 365 which PST file should go into which mailbox, which folder it should land in, and whether to filter by date range or message type. The import process itself runs in the background and can handle multiple files simultaneously. Administrators can monitor progress from the compliance portal and receive notifications when jobs complete or encounter errors. It is worth noting that this service requires either a Microsoft 365 E3 or E5 license, an Office 365 E1, E3, or E5 license, or the addition of an Exchange Online Archiving add-on license for each affected mailbox.

Step-by-Step Guide

1. Verify Licensing and Permissions: Before starting, confirm that each target mailbox has a license that includes the Office 365 Import Service, such as Exchange Online Plan 2 or an archiving add-on. You also need to be assigned the Mailbox Import Export role in Exchange Online, which is not enabled by default and must be added through the Exchange admin center or PowerShell.
2. Collect and Organize Your PST Files: Gather all PST files from user workstations, shared drives, and any backup locations into a single staging folder on a machine with a reliable internet connection. Rename the files using a consistent naming convention, such as including the user's name or email address, so the mapping process is easier and less error-prone later.
3. Install AzCopy and Obtain the SAS URL: Navigate to the Microsoft Purview compliance portal, go to Data lifecycle management, select Import, and create a new import job to retrieve your Secure Access Signature URL and the AzCopy command-line tool download link. The SAS URL is a time-limited credential that authorizes your machine to upload files directly to Microsoft's Azure Blob Storage container assigned to your tenant.
4. Upload PST Files to Azure Blob Storage: Open a Command Prompt or PowerShell window and run the AzCopy command provided in the portal, pointing it at your local staging folder and the SAS URL. The tool will upload each PST file to the Azure container and display progress in real time, so monitor the output carefully and re-run the command if any files fail to upload successfully.
5. Create the CSV Mapping File: Download the sample CSV mapping file from the Microsoft documentation and populate it with one row per PST file, specifying the target mailbox email address, whether to import into the primary or archive mailbox, the target folder name, and any date filters you want to apply. Double-check every row for typos in email addresses, as errors in the mapping file are the most common cause of failed or misdirected import jobs.
6. Submit the Import Job in the Compliance Portal: Return to the Import section of the Microsoft Purview compliance portal, select your upload session, upload the completed CSV mapping file, and submit the import job for processing. Microsoft will validate the mapping file first and flag any errors before the actual import begins, giving you a chance to correct mistakes without losing your uploaded PST files.
7. Monitor Progress and Verify Completion: Track the status of your import job from the Import page in the compliance portal, where you can see how many items have been imported, how many were skipped due to duplicates, and whether any errors occurred. Once the job shows a status of Completed, log into one of the affected mailboxes in Outlook or Outlook on the Web and verify that the imported folders and messages appear as expected before communicating the change to end users.

Comparing PST Import Methods for Microsoft 365

Best Practices

• Audit PST Files Before Importing: Use a tool like Kernel PST Viewer or Stellar PST Recovery to inspect files for corruption before uploading, since importing a damaged PST can result in incomplete or missing data in the target mailbox.
• Use the Archive Mailbox as the Target: Direct imported historical data to the user's archive mailbox rather than the primary inbox to keep the primary mailbox clean and prevent users from being overwhelmed by thousands of old messages on day one.
• Apply Date Filters Strategically: Use the import mapping file's date range parameters to exclude very old or irrelevant data, which reduces storage consumption and keeps the migration focused on items that have genuine business value.
• Communicate With End Users in Advance: Let affected employees know that historical email will appear in their mailboxes after the import so they are not surprised or confused by unfamiliar folder structures showing up in Outlook.
• Retain PST Files Until the Import Is Verified: Do not delete or move the original PST files until you have confirmed that all data has arrived correctly in Microsoft 365, giving yourself a safety net if the import job encounters errors or maps data to the wrong mailbox.

Frequently Asked Questions

How Long Does a PST Import Into Microsoft 365 Take?

The time required depends on the size of the PST files, your internet connection speed, and the current load on Microsoft's import service. As a rough benchmark, Microsoft processes approximately 24 GB of PST data per day once files are in Azure Blob Storage, though this can vary. Uploading the files to Azure is typically the longest part of the process for organizations with large archives. Planning for at least a few days from start to finish for a multi-user migration is a reasonable expectation.

Is There a Size Limit for PST Files Being Imported?

Microsoft does not publish a hard per-file size limit for the Office 365 Import Service, but individual PST files larger than 20 GB can become unwieldy and are more prone to corruption. It is generally a good idea to split very large PST files into smaller chunks using Outlook's built-in export tool or a third-party utility before uploading. The total amount of data you can import is effectively limited by your mailbox and archive storage quotas. Exchange Online Plan 2 and Microsoft 365 Business Premium include unlimited archive storage through auto-expanding archiving, which accommodates even the largest historical datasets.

Can You Import PST Files Without Admin Access?

The native Microsoft 365 Import Service requires Global Administrator or Compliance Administrator privileges, along with the Mailbox Import Export role assignment in Exchange Online. Individual users cannot run import jobs on their own through this method. However, users can manually import a PST file into their own Outlook desktop client by going to File, Open and Export, and then Import/Export, which does not require admin rights but does require the Outlook application to be installed and the user to have physical access to the PST file. This manual method is practical for one-off situations but does not scale well for organization-wide migrations.

What Happens to Duplicate Emails During the Import?

The Office 365 Import Service has built-in duplicate detection that compares incoming items against messages already present in the target mailbox or folder. If a duplicate is found, the item is skipped rather than imported a second time, which helps keep mailboxes clean and prevents inflated storage usage. After the import job completes, the portal report shows a count of skipped items so administrators can review what was excluded. In most cases, duplicates are a non-issue, but if you are importing the same PST file multiple times during testing, you may see a higher-than-expected skip count.

Do You Need to Keep Outlook Installed to Complete the Import?

No, the network upload method for importing PST files into Microsoft 365 does not require Outlook to be installed on the machine performing the upload. The process relies entirely on AzCopy, the compliance portal, and a CSV mapping file, all of which are independent of the Outlook application. Outlook is only required if you are using the manual drag-and-drop or File Import method to move a PST into a single mailbox. For any bulk or administrative import involving multiple users, the compliance portal workflow is the correct approach and works from any Windows machine with internet access.

If you are ready to move your organization's historical email into the cloud but want expert guidance to avoid costly mistakes, Always Beyond can handle the entire process for you — from auditing your PST files to configuring the import job and verifying the results. Our team works with SMBs every day to make Microsoft 365 migrations smooth, secure, and stress-free. Reach out to contact Always Beyond today.