Import PST File to Exchange Server: Complete 2026 Guide
-
Written By
Aradhya Jain -
Approved By
Shivam Rathore -
Updated on
May 4th, 2026 - Read Time
7 minutes
Before You Migrate Outlook to Exchange Server: 3 Things to Set Up First
Most import errors do not come from the command itself. They come from missing setup steps. Get these three things right before doing anything else.
Step 01: Assign the Mailbox Import Export Role
This is the most skipped step and the reason behind the “user does not have the Mailbox Import Export role” error. By default, this role is not assigned to anyone, not even the admin account.
- Assign it manually by running this in Exchange Management Shell: New-ManagementRoleAssignment -Role “Mailbox Import Export” -User Administrator
- Close the shell completely after running this and reopen it. The role does not activate in the same session — skipping this restart is why most people think the fix did not work.
Step 02: Put PST Files on a UNC Network Share
Exchange cannot read PST files from a local path like C:\PST. It only accepts UNC paths in the format \ServerName\ShareName\file.pst. Place all PST files in a shared network folder, then give the Exchange Trusted Subsystem group Full Control over that folder. Without this, import requests either fail instantly or sit at Queued for hours.
Step 03: Export PST From Outlook First if Needed
If the PST file does not exist yet, open Outlook and go to File → Open and Export → Import/Export → Export to a File → Outlook Data File (.pst). Select the mailbox, choose a save location, and click Finish. Then move the file to the network share from Step 2.
Method 01: How to Import PST File to Exchange Server Using PowerShell
Exchange Management Shell gives you more control over the import process, especially when handling multiple mailboxes at once.
- The core command is straightforward: New-MailboxImportRequest -Mailbox “UserAlias” -FilePath “\Server\Share\User.pst”
- Once the command is running, track its progress with: Get-MailboxImportRequest
- This shows the current status of every import request: whether it is Queued, In Progress, Completed, or Failed.
How to Import 100+ PST Files to Exchange in BulkRunning the import command one mailbox at a time is not realistic for large migrations. The better approach is naming each PST file after its target mailbox alias — john.pst, sarah.pst. Using a PowerShell script to loop through the folder and submit all import requests in one run. It eliminates manual mapping, saves hours of work, and removes the risk of loading a file into the wrong mailbox. |
Method 02: Convert PST to Exchange Server Using EAC
- First, log in to the Exchange Admin Center using your admin credentials.
- Now, go to Recipients → Mailboxes.
- Then, click the three-dot menu (…) and select Import PST.
- Enter the UNC path of the PST file — for example, \ServerName\Share\user.pst
- Select the target mailbox and choose where to import.
Set your notification preference and click Finish.
Limitations of Manual PST Import Methods
- Importing the same PST twice fills the mailbox with duplicate emails.
- Large PST files above 10–15 GB frequently cause incomplete transfers.
- Original folder structure from the PST may not always carry over correctly.
- You cannot check what is inside the PST before importing it.
- Moreover, does not work for Exchange Online or hybrid environments.
- If you need to switch email platforms entirely, you can also convert PST to MBOX for clients like Thunderbird or Apple Mail
Professional Tool to Import PST File to Exchange Server
The DRS Softech PST Import Tool handles bulk PST imports without requiring manual role assignments or UNC path configurations for each file. You select PST files to import, set any filters you need, such as date range, remove duplicates, or more. It preserves the complete folder hierarchy and gives you a migration report when the process is done. It supports Exchange 2010, 2013, 2016, 2019, and also Exchange Online. For organizations moving 50 or more mailboxes, it is significantly less error-prone than running individual PowerShell commands. Additionally, you can import PST to New Outlook and several other formats.
Steps to Import Local Outlook .pst Files into the Exchange Server
- Download and install the DRS Softech PST Converter Tool.
- Choose “Select Files” or “Select Folder” to add your PST files.
- You can preview and select the PST files to convert. Click Next.
- Then, choose IMAP as the Saving Format from the given list.
- Enter your IMAP credentials, such as ID & Password, to Sign In.
- Lastly, apply advanced features as per your needs. Click Convert.
Real-Life Scenario:
A network administrator at a manufacturing company had 75 PST files from employees who had been using Outlook locally for years. After moving to Exchange Server 2019, he tried the PowerShell method first but kept hitting permission errors. He switched to the DRS Softech PST Converter Tool, loaded the entire PST folder, applied a date filter, and ran the migration overnight. Every mailbox came through cleanly with its folder structure fully intact. The process is just as smooth when you import PST to Shared Mailbox in Office 365 — same straightforward approach, different destination
Conclusion
In this technical blog post, we explored several methods to import PST file to Exchange Server. This process is manageable when the pre-steps are handled correctly. Assign the Mailbox Import Export role, set up the UNC share with the right permissions. You can use either the manual methods or a professional tool. The DRS Softech PST Converter Tool when you need a clean, error-free migration without the manual overhead.
Frequently Asked Questions
Organizations migrate to Exchange Server for centralized, secure email management. Since Outlook stores data locally in PST format, importing those files into Exchange gives users access to their full email history, contacts, and calendar items directly from the server.
Use the New-MailboxImportRequest command in Exchange Management Shell with the UNC path of the PST file, or use the Import PST option in Exchange Admin Center. Both methods push the PST data into the server mailbox, making it accessible online through Outlook Web App and any connected client.
Yes, when using either the PowerShell method or the DRS Softech PST Converter Tool, all mailbox items, including emails, contacts, calendar entries, and tasks, are transferred.
Yes. You can run multiple New-MailboxImportRequest commands targeting the same mailbox — each request needs a unique name. The DRS Softech Tool also supports this and lets you merge multiple PST files into one mailbox in a single operation.
Not for the PowerShell or EAC methods — those work directly within the Exchange environment. The DRS Softech PST Converter Tool also works independently and does not require Outlook to be installed on the machine running the migration.
For IT consultants and service providers managing migrations across multiple client environments, the Technician or Enterprise license is the most suitable option. These licenses allow usage across multiple systems and cover large-scale migrations without per-machine restrictions.
