Moving your PST files to Office 365 offers several advantages like enhanced accessibility to Outlook items, cloud storage, and seamless integration with other Microsoft tools Word, Excel, and PowerPoint.
Before migrating PST files, ensure you take a backup of the PST file and check if your Office 365 plan supports importing PST files.
You will have to migrate all your Outlook data to Office 365 properly to enjoy these benefits, Read the upcoming section for methods to migrate Outlook .pst to Office 365 without any hiccups.
Can you still use PST files with Office 365?
Yes, but with real limits that most guides skip over. Classic Outlook (the desktop application, version 2016 through Microsoft 365 Apps) still opens, reads, and imports PST files exactly as it always did. Nothing about an Office 365 subscription removes that capability.
The complication is on the cloud side. Your Exchange Online mailbox does not store PST files natively. When you migrate PST to Office 365, the contents of the file (emails, calendar items, contacts) are uploaded into your mailbox as ordinary mail data. The PST itself does not travel to the cloud; it becomes unnecessary once the import completes.
A Personal Storage Table file is a local format, designed for on-disk storage before cloud mailboxes existed. Office 365 has no way to mount or browse one from a browser or the Outlook mobile app. If a colleague sends you a PST expecting you to open it in Outlook on the web, you cannot. You need the desktop client. That distinction matters when you are planning which users still need classic Outlook installed after a migration.
New Outlook is the exception worth calling out separately. It reads PST files in a limited way but cannot import them. That is covered in the section on new Outlook above. For everyone on classic Outlook, the format remains fully supported through at least 2026 under the current Microsoft 365 Apps support lifecycle.
What Is the Fastest Way to Migrate PST to Office 365?
To migrate PST to Office 365, sign into the Microsoft 365 compliance portal, create a Network Upload import job, upload your PST files to Azure Blob Storage using AzCopy, map the files to the target mailboxes via a CSV mapping file, and then start the import job. For smaller mailboxes, Outlook’s built-in Import/Export wizard is the quickest option without any admin tools.
What are the prerequisites before you migrate PST to Office 365?
The Network Upload method (AzCopy to Azure Blob Storage) requires a specific admin role: Mailbox Import Export in Exchange Online. It is not assigned to Global Admins by default. Skipping this check is the most common reason the import job creation step fails with a permissions error in the Microsoft Purview compliance portal.
You also need to verify your Office 365 plan. PST import through the compliance portal is available on Exchange Online Plan 2, Microsoft 365 Business Premium, and Office 365 E3 and above. Exchange Online Plan 1 does not include it. If your portal does not show the Import option under Data lifecycle management, the plan is the first thing to check.
For the file itself: individual PST files can be up to 20 GB for Network Upload without hitting timeout problems in practice, though Microsoft does not publish a hard cap for that method. Drive Shipping imposes no per-file size limit, which is why large migrations (several hundred gigabytes or more) typically go that route. PST files larger than 4 GB stored on a FAT32-formatted drive will silently fail to copy because FAT32 cannot hold a single file that size. Use NTFS or exFAT for the shipping drive.
Before you start any method, back up the source PST. The Import/Export wizard in classic Outlook occasionally corrupts the source file if Outlook crashes mid-import, especially on files that already have minor inconsistencies. A copy takes two minutes and avoids a recovery problem later.
Methods to Migrate PST to Office 365 Account [4 Methods]
Method 1: Outlook’s Import/Export Feature
Method 2: Use the Azure AzCopy tool
Method 3: Outlook Migration Tool
Method 4: Import Service (Drive Shipping)
Method 1: Outlook’s Import/Export Feature
- Open Outlook, Go to File > Open & Export > Import/Export.

- Select Import from another program or file and click Next.

- Choose Outlook Data File (.pst) and click Next.

- Browse to your PST file and click Open.

- Select the desired options and click Finish.
- Now download and install the Outlook Migration Assistant, launch the tool, and follow the on-screen instructions to migrate the PST files.
Caution
Though Outlook Migration Assistant is designed to minimize data loss, there’s always a risk, especially with large or corrupted PST files, and custom migrations will require a bit of technical knowledge.
Method 2: Outlook Migration Tool
If you feel the above solutions aren’t right for you, you can opt for a Rikvr Transfer for Outlook tool that automates and simplifies the process of transferring PST files to Office 365 with just a few clicks. Since the tool is fully automated, there’s minimal risk of data loss or corruption.
Step 1: Close Outlook and related applications, open Rikvr Transfer For Outlook, and click on the Transfer option

Step 2: Click on browse to select the Backup of the PST file.

Step 3: Choose all the Outlook settings and click on Next.

Step 4: Once the transfer process is completed, click on Finish. Now access all your Outlook data on Office 365.
Method 3: Import Service (Drive Shipping)
For very large datasets Microsoft offers a Drive shipping service for importing PST files into Office 365. This is particularly useful for large PST files or organizations with limited internet bandwidth. Here is how it works:
- Copy your PST files to an encrypted hard drive
- Follow Microsoft’s guidelines to securely ship the hard drive to their designated location
- Ship the hard drive to Microsoft following their drive shipping guidelines.
- Once Microsoft receives the hard drive, they’ll upload the PST to Azure. You can then create a PST Import job as in the Network Upload method.
Which method should you use? A comparison by use case
The right method depends almost entirely on how much data you have and whether you have admin access to your Office 365 tenant.
| Method | Best for | Requires admin? | Practical data limit |
|---|---|---|---|
| Outlook Import/Export wizard | Single user, under 10 GB | No | No enforced limit, but slow above 10 GB |
| Network Upload via AzCopy | IT admins migrating multiple mailboxes | Yes (Mailbox Import Export role) | No hard cap; practical ceiling around 20 GB per file |
| Drive Shipping | Very large datasets, low bandwidth sites | Yes | None (physical media) |
| Migration tool (third-party) | Bulk migration, multiple users, scheduling | Depends on tool | Tool-dependent |
A single user with one PST under 5 GB should not touch AzCopy. The Outlook wizard gets the job done in under 20 minutes. Conversely, if you are an IT admin trying to migrate all PST files for 50 users at once, the Import/Export wizard is not a realistic option: you would be sitting at 50 desks in sequence. Network Upload with a CSV mapping file handles all 50 mailboxes in one import job.
Drive Shipping is the method most people overlook. If your office has a slow internet connection and you are moving 200 GB of PST data, uploading to Azure Blob Storage will take days and risks timeouts. Shipping an encrypted hard drive is slower on paper but more reliable in practice for anything above roughly 100 GB total.
An Import PST to Office 365 tool (a third-party migration application) makes sense when you need scheduling, filtering by date range, or a detailed audit log of exactly what was imported and what was skipped. The built-in Microsoft methods give you a status report, but the granularity is limited. Whether that matters depends on whether your organization has compliance requirements around the migration itself.
Post-Migration Checks
Once you have successfully migrated your PST file into Office 365 then, be sure to check all the data integrity and other aspects such as:
- Mailbox Settings and Permissions: Check all the rules, auto-replies, retention policies, and user permissions and access rights on Office 365.
- Backup and Recovery: Verify the Office 365 environment backup and recovery procedures.
- Directory and Data Synchronization: Verify both directory and data synchronization is working correctly to keep the information updated.
How to import PST file in Outlook 365 Online
Outlook on the web (Outlook 365 Online) has no built-in option to import a PST file directly from your browser. PST is a local file format and the web client cannot read your file system. The question of how to import PST file in Outlook 365 Online comes up constantly, and the honest answer is that it requires a different tool entirely.
The correct approach is to use the Network Upload method through the Microsoft Purview compliance portal import. You upload the PST to Azure Blob Storage using AzCopy on a local machine, create an import job in the portal, and map the PST to the target mailbox. Once the import job completes, the data appears in that user’s Outlook 365 Online mailbox automatically. There is no step where you do anything inside the web client itself.
If you only need to move a small amount of data and you have access to the classic Outlook desktop client, the faster path is to import the PST there and let the data sync to the cloud. For a single user with a PST under 2 GB, the desktop import followed by sync typically completes in under 30 minutes on a standard broadband connection. The compliance portal method is worth the extra setup time only when you have multiple PST files, large volumes of data, or no access to a desktop Outlook installation.
How do I Import a pst file into Microsoft Outlook 365?
This works in classic Outlook for Microsoft 365, not the new Outlook. Open classic Outlook, go to File > Open & Export > Import/Export. The Import and Export Wizard opens. Select Import from another program or file and click Next.
On the next screen, select Outlook Data File (.pst) and click Next. Browse to the PST file you want to import. Under options, choose Do not import duplicates unless you specifically need to overwrite existing items. Click Next, then select which folders to import and whether to import them into your current active account or a specific folder. Click Finish.
Outlook imports in the background. There is no progress bar for large files, which makes it look like nothing is happening. For a 10 GB PST, expect 20 to 40 minutes depending on drive speed. If Outlook closes or crashes mid-import, the items already written remain in the mailbox and the rest are not imported. You will need to run the import again using the Do not import duplicates option to pick up where it left off without creating copies. If you are asking how to import PST file in Outlook 365 Online (meaning through the web browser at outlook.com or the Microsoft 365 web app), that is not possible directly. The web version of Outlook does not accept PST uploads. You must use the Microsoft Purview compliance portal import process or the classic desktop client for that path.
New Outlook PST file support: what changed and what it means for migration
New Outlook for Windows, the version Microsoft is progressively rolling out as the replacement for classic Outlook, does not support local PST files. At all. There is no Import/Export wizard, no File menu path to open a PST, and no setting to add one as a data file. This is a deliberate architectural decision, not a bug or a missing feature that will appear in a later update.
That makes new Outlook PST file support a real blocker for anyone who still relies on classic Outlook PST files as their primary mailbox store. If your organization is planning a migration to Microsoft 365 and users are still on new Outlook, the only supported path is to import the PST files directly into Exchange Online mailboxes using the Network Upload or Drive Shipping methods described above. You cannot open the PST locally in new Outlook and then move the data from there.
If you need to access an old PST file before completing the full migration, install classic Outlook side-by-side or use the How to import PST file in Outlook 365 Online workflow via the compliance portal to get the data into the mailbox first, then access it through new Outlook from Exchange Online. Classic Outlook remains available through volume-licensed Office 2021 and the Microsoft 365 Apps subscription, so you do have time to complete the migration before support ends.
How do I add a pst file in new Outlook 365?
New Outlook 365 does not support the classic Import/Export wizard, and this trips up a lot of people. You can open a PST for read-only browsing by going to File > Open & Export > Open Outlook Data File, but you cannot import its contents into your cloud mailbox from within the new Outlook interface directly.
The practical workaround is to install or switch back to classic Outlook, run the import there, and then let the changes sync to your Microsoft 365 mailbox. If you are on a managed device where switching Outlook versions is not an option, use the Network Upload method through the Microsoft Purview compliance portal import instead. That path is admin-controlled and works regardless of which Outlook version is installed on any individual machine.
Microsoft has confirmed that full PST import support is not on the current roadmap for new Outlook. New Outlook PST file support remains limited to read access. If your organization is planning to roll out new Outlook broadly, factor in this gap now and document a migration path for users who still have local PST files before the switch happens.
How to transfer Outlook PST files to a new computer?
Copy the PST file itself. That is the whole operation. A PST is a single self-contained file, typically sitting in C:\Users\YourName\Documents\Outlook Files\ or C:\Users\YourName\AppData\Local\Microsoft\Outlook\ depending on your Outlook version and how it was first set up. Copy it to a USB drive, an external disk, or a network share, then paste it anywhere on the new machine.
Once the file is on the new computer, open Outlook, go to File > Open & Export > Open Outlook Data File, and point it at the copied PST. Outlook adds it to the folder pane immediately. You do not need to reinstall anything or re-enter account credentials for this step alone.
A few things catch people out. If the original PST was stored on a network drive and you simply moved the shortcut rather than the file, the new machine will show an error because the path no longer resolves. Check that you copied the actual .pst file and not a shortcut. Files over 50 GB also take noticeably long to copy over USB 2.0; a direct Ethernet transfer or USB 3.0 drive is worth the extra minute to set up.
If your goal is not just to access the old mail locally but to get it into your cloud mailbox on the new machine, the answer is in the Import/Export method above. Open the copied PST via Open Outlook Data File first so Outlook can see it, then run the import from File > Open & Export > Import/Export and select that file as the source. If you are unsure how to get Outlook to recognise the file before you start, the question How do I open up a PST file in Outlook? walks through that step in detail.
Conclusion
I recommend planning and preparing your Outlook migration with all the necessary tools and taking a backup of your PST files before proceeding. This will help you avoid migration issues like import job failures and upload problems.
I hope this article has helped you learn various ways to move PST files to Office 365 seamlessly. Choose the solution that works best for you.


