ANAVEM
Reference
Languagefr
How to Import PST Files into Exchange Online in Microsoft 365

How to Import PST Files into Exchange Online in Microsoft 365

Learn to migrate PST archive files to Exchange Online mailboxes using Microsoft Purview portal, AzCopy uploads, and CSV mapping files for bulk email migration.

Emanuel DE ALMEIDAEmanuel DE ALMEIDA
March 17, 2026 15 min 5
mediummicrosoft-365 9 steps 15 min

Why Import PST Files to Exchange Online?

PST file migration represents one of the most critical phases in any Microsoft 365 deployment. Organizations moving from on-premises Exchange servers or legacy email systems often have years of valuable email data stored in PST archive files. These archives contain essential business communications, compliance records, and historical data that must be preserved during cloud migration.

Microsoft 365's PST import service provides a secure, scalable solution for bulk email migration. Unlike manual import methods that require individual user intervention, the centralized import process allows administrators to migrate multiple PST files simultaneously while maintaining data integrity and security compliance.

What Makes Microsoft Purview the Best Choice for PST Migration?

The Microsoft Purview portal (formerly Security & Compliance Center) offers the only officially supported method for enterprise PST imports. This cloud-based service handles the complex logistics of data transfer, validation, and mailbox integration without requiring expensive third-party migration tools.

The service supports both primary mailbox and archive mailbox imports, giving administrators flexibility in data placement. Advanced features include selective date range imports, detailed completion reporting, and automatic data validation to ensure migration success.

Related: Microsoft 365 Backup: Granular File and Folder Restoration

Related: Microsoft 365 E7 at $99/User/Month: Copilot AI + Agent 365

How Does the Import Process Work?

The PST import workflow consists of three main phases: preparation, upload, and processing. During preparation, administrators create mapping files that define which PST files import into specific mailboxes. The upload phase uses AzCopy to transfer files securely to Microsoft's Azure storage infrastructure. Finally, Microsoft's processing engines analyze and import the data into Exchange Online mailboxes.

This tutorial walks you through each step using current 2026 procedures, including the latest Microsoft Purview interface updates and AzCopy commands. You'll learn to handle common migration challenges, verify import success, and troubleshoot issues that may arise during large-scale PST migrations.

Implementation Guide

Full Procedure

01

Assign Mailbox Import Export Role

Before starting the import process, you need proper permissions. Navigate to the Exchange Admin Center and assign the Mailbox Import Export role to your administrator account.

Open your browser and go to the Exchange Admin Center. In the left navigation, click Roles, then select Admin roles. Find and click on Organization Management.

Click the Permissions tab, then locate and select the Mailbox Import Export role. Click Save to apply the changes.

Warning: Permission changes can take up to 24 hours to propagate, though they typically become effective within 1 hour. Don't proceed until you have the necessary permissions.

Verification: Log out and back into Microsoft 365. You should now see the Import option in the Microsoft Purview portal.

02

Create New Import Job in Microsoft Purview

Access the Microsoft Purview portal to create your PST import job. This generates the Azure storage location where you'll upload your PST files.

Navigate to the Microsoft Purview portal through your Microsoft 365 Admin Center. In the left menu, expand Information governance and click Import.

Click Import PST Files, then click New import job. Give your job a descriptive name like "Q1-2026-PST-Migration" and click Next.

Select Upload your data and click Next. On the next screen, click Show network upload SAS URL.

Copy the generated SAS URL to a text file. This URL contains your storage account name, container name, and shared access signature token. It looks like this:

https://3c3e5952a2764023ad14984755276b0d.blob.core.windows.net/ingestiondata?sv=2015-04-05&sr=c&si=IngestionSasForAzCopy201601121920498117&sig=Vt5S4hVzlzMcBxuRqkQeGjvHPrt%2BHmS7fbZ8NL%2FgQas%3D
Pro tip: Save this URL immediately. You'll need it for the AzCopy upload command, and it expires after a certain period.

Verification: The URL should contain "blob.core.windows.net" and end with a signature parameter. Keep this browser tab open for later steps.

03

Install and Configure AzCopy

AzCopy is the only officially supported tool for uploading PST files to Microsoft 365. Download and install the latest version for reliable file transfers.

Download AzCopy from the official Microsoft website. For Windows, download the executable and extract it to a folder like C:\AzCopy.

Open Command Prompt as Administrator and navigate to your AzCopy folder:

cd C:\AzCopy

Test AzCopy installation by running:

azcopy --version

You should see version information displayed. The current version as of 2026 is AzCopy v10.x.

Create a dedicated folder for your PST files if you haven't already:

mkdir C:\PST_Files

Copy all your PST files to this location. Ensure file names don't contain special characters or spaces.

Warning: Don't use older versions of AzCopy or third-party tools. Microsoft only supports AzCopy for network uploads to ensure data integrity.

Verification: Run dir C:\PST_Files to confirm all your PST files are present and properly named.

04

Upload PST Files Using AzCopy

Now upload your PST files to the Azure storage location using the SAS URL from step 2. This process transfers your files securely to Microsoft's cloud storage.

Open Command Prompt as Administrator and navigate to your AzCopy directory. Run the following command, replacing the placeholder with your actual SAS URL:

azcopy copy "C:\PST_Files\*" "[YOUR_SAS_URL]" --recursive --log-level=INFO

For example:

azcopy copy "C:\PST_Files\*" "https://3c3e5952a2764023ad14984755276b0d.blob.core.windows.net/ingestiondata?sv=2015-04-05&sr=c&si=IngestionSasForAzCopy201601121920498117&sig=Vt5S4hVzlzMcBxuRqkQeGjvHPrt%2BHmS7fbZ8NL%2FgQas%3D" --recursive --log-level=INFO

The upload progress will display in real-time. Large files may take considerable time depending on your internet connection speed.

Pro tip: Use the --log-level=INFO parameter to get detailed upload information. If uploads fail, check the log files in your user profile's .azcopy folder for troubleshooting details.

Monitor the upload carefully. AzCopy will show transfer statistics and any errors encountered during the process.

Verification: When complete, AzCopy displays "Job completed" with transfer statistics. All PST files should show as successfully transferred with zero failed transfers.

05

Create PST Import Mapping CSV File

Create a CSV mapping file that tells Microsoft 365 which PST files to import into which mailboxes. This file controls the entire import process.

Open a text editor like Notepad and create a new file. The CSV must contain specific columns in the exact order shown below:

Mailbox,IsArchive,TargetRootFolder
john.doe@company.com,FALSE,/
jane.smith@company.com,TRUE,/
mike.johnson@company.com,FALSE,ImportedData

Here's what each column means:

  • Mailbox: The primary email address of the target user
  • IsArchive: FALSE for primary mailbox, TRUE for archive mailbox
  • TargetRootFolder: Destination folder (/ for root, or specify folder name)

Save this file as PST-Import-Mapping.csv in an easily accessible location like your Desktop.

Warning: Ensure all email addresses in the Mailbox column correspond to existing Microsoft 365 users. The import will fail for non-existent mailboxes.

For users without archive mailboxes enabled, you must enable them first:

Connect-ExchangeOnline
Enable-Mailbox -Identity "user@company.com" -Archive

Verification: Open your CSV file in Excel or a text editor to confirm proper formatting. Each row should represent one PST file import destination.

06

Upload and Validate Mapping File

Return to the Microsoft Purview portal to upload your CSV mapping file and validate the import configuration before proceeding.

Go back to your browser tab with the import job still open. Click Browse to select your CSV mapping file, then upload PST-Import-Mapping.csv.

The system automatically validates your mapping file. You'll see a green checkmark next to each valid entry, or red error indicators for any issues.

Common validation errors include:

  • Invalid email addresses
  • Non-existent mailboxes
  • Incorrect CSV formatting
  • Missing archive mailboxes when IsArchive=TRUE

If you see errors, download the error report, fix the issues in your CSV file, and re-upload it.

Once validation passes completely, click Next to proceed to the final configuration step.

Pro tip: Test your CSV file with a small subset of users first. Create a pilot import with 2-3 mailboxes to verify your process before running the full migration.

Verification: All rows in your mapping file should display green checkmarks. The validation summary should show "0 errors" before proceeding.

07

Submit Import Job for Processing

Review your import job configuration and submit it to Microsoft for processing. This initiates the actual PST data import into Exchange Online mailboxes.

Review the import job summary showing your uploaded PST files and mapping configuration. Verify all details are correct, including file names and target mailboxes.

Click Submit to queue your import job for Microsoft's processing. The job status changes to "Analysis in progress" as Microsoft examines your PST files.

This analysis phase can take several hours to complete, depending on the number and size of your PST files. You cannot force or accelerate this process.

Monitor the job status by refreshing the Import page in the Purview portal. The status will change from "Analysis in progress" to "Analysis completed" when ready.

Warning: Don't delete your local PST files until the import completes successfully. Keep them as backup until you verify all data imported correctly.

Once analysis completes, you'll see detailed information about each PST file, including size and estimated import time.

Verification: The job status should show "Analysis completed" with detailed file information displayed. No error messages should appear in the job summary.

08

Start the Import Process

After Microsoft completes the analysis, initiate the actual import of PST data into your Exchange Online mailboxes.

Select your completed import job from the list and click Import to Office 365. This opens the final import configuration dialog.

Choose your import scope:

  • "No, I want to import everything" - Imports all data from PST files
  • "Import only the last two years of messages" - Filters older content

For most migrations, select "No, I want to import everything" to ensure complete data transfer.

Click Next to review the final settings, then click Submit to start the import process.

Click Done to return to the import jobs list. The status changes to "In progress" as Microsoft imports your data.

Pro tip: Large PST files can take 24-48 hours to import completely. Plan your migration timeline accordingly and communicate expected completion dates to users.

The import process includes all mailbox data: emails, calendar items, contacts, tasks, and notes from the PST files.

Verification: Monitor the import progress through the Purview portal. The status should show "In progress" with periodic updates on completion percentage.

09

Verify Import Completion and Data Integrity

Once the import completes, verify that all PST data successfully transferred to the target mailboxes and troubleshoot any issues.

Check the import job status in the Purview portal. A successful import shows "Completed" status with detailed statistics for each PST file.

Download the import completion report by clicking on your completed job and selecting Download report. This CSV file contains detailed results for each imported item.

Log into each target mailbox to verify data presence:

  • Check email counts match expectations
  • Verify calendar appointments imported correctly
  • Confirm contacts are present
  • Test search functionality for imported content

For archive imports (IsArchive=TRUE), access the archive mailbox through Outlook or Outlook Web App to verify content.

If you specified custom target folders, navigate to those locations to confirm proper data placement.

Warning: Some items may fail to import due to corruption or size limits. Review the detailed report to identify any failed items and determine if manual intervention is needed.

Common post-import tasks include:

  • Updating user permissions on imported folders
  • Configuring retention policies for imported data
  • Training users on accessing their imported content

Verification: All users should be able to access their imported PST data through Outlook or Outlook Web App. Search functionality should return results from imported content.

Frequently Asked Questions

How long does it take to import PST files into Exchange Online?+
Import time varies significantly based on PST file size and quantity. Small files (under 1GB) typically import within 2-4 hours, while large files (10GB+) can take 24-48 hours. The initial analysis phase alone can take several hours for large datasets. Microsoft processes imports in batches, so you cannot accelerate the timeline. Plan for 1-3 business days for complete migration of substantial PST collections.
What is the maximum PST file size supported for Exchange Online import?+
Microsoft supports PST files up to 150GB for Exchange Online import through the Purview portal. However, files larger than 20GB may experience longer processing times and higher failure rates. For optimal results, consider splitting very large PST files into smaller segments before import. The service also has a practical limit of 500 PST files per import job for performance reasons.
Can I import PST files directly into user archive mailboxes?+
Yes, you can import PST files directly into archive mailboxes by setting IsArchive=TRUE in your CSV mapping file. However, the target user must have an archive mailbox enabled before import. Use the PowerShell command Enable-Mailbox -Identity 'user@company.com' -Archive to enable archive mailboxes. Archive imports are ideal for older email data that doesn't need to be in the primary mailbox.
What happens if some PST files fail to import completely?+
Partial import failures are common and don't stop the entire job. Microsoft provides detailed completion reports showing which items failed and why. Common failure reasons include corrupted PST files, oversized individual messages, or permission issues. You can retry failed imports by creating a new import job with only the failed PST files. The detailed error logs help identify specific issues for troubleshooting.
Do I need special permissions to import PST files in Microsoft 365?+
Yes, you need the Mailbox Import Export role assigned to your administrator account. This role is not included in standard admin roles and must be explicitly assigned through the Exchange Admin Center. The permission change can take up to 24 hours to propagate, though it typically becomes effective within 1 hour. Without this role, you won't see the Import option in the Microsoft Purview portal.
Emanuel DE ALMEIDA
Written by

Emanuel DE ALMEIDA

Microsoft MCSA-certified Cloud Architect | Fortinet-focused. I modernize cloud, hybrid & on-prem infrastructure for reliability, security, performance and cost control - sharing field-tested ops & troubleshooting.

Discussion

Share your thoughts and insights

You must be logged in to comment.

Loading comments...