Menu Close

How To Import PST to Office 365 Mailbox: A Step-By-Step Guide?

Today I’m going to show you on how to import PST to Office 365 mailbox. Before we begin, make sure you have the necessary permission to access the security and compliance center.

Let’s jump right in.

Step 1:

  • Go to the “Microsoft Purview compliance portal“.
  • In the left pane of the Microsoft Purview compliance Portal, click Data lifecycle management > Microsoft 365.
  • On the Import tab, click + New import job.
  • Type a name for the PST import job, and then click Next. Use lowercase letters, numbers, hyphens, and underscores. You can’t use uppercase letters or include spaces in the name.
  • Select “Upload your data
  • click “Show network upload SAS URL”. After the SAS URL is displayed, click Copy to clipboard and then paste it and save it to a file so you can access it later.
  • click Download Azure AzCopy to download the AzCopy tool to your local computer. This version of AzCopy is just an executable file, so there’s nothing to install.

Note: You can leave the Import data page open (in case you need to copy the SAS URL again) or click Cancel to close it.

Step 2:

Now you’re ready to use the AzCopy tool to upload PST files to Microsoft 365. This tool uploads and stores PST files in a Microsoft-provided Azure Storage location in the Microsoft cloud. As previously explained, the Azure Storage location that you upload your PST files to is located in the same regional Microsoft datacenter where your organization is located. To complete this step, the PST files have to be located in a file share or file server in your organization or in an Azure Storage location managed by your organization. The PST storage location is known as the source location in this procedure. Each time you run the AzCopy tool, you can specify a different source location.

Note: Each PST file that you upload to the Azure Storage location should be no larger than 20 GB. PST files larger than 20 GB may impact the performance of the PST import process that you start in Step 6. Also, each PST file must have a unique name.

  • Open a Command Prompt on your local computer.
  • Go to the directory where you downloaded the azcopy.exe file in Step 1.
  • Run the following command to upload the PST files to Microsoft 365.

azcopy.exe copy “<Source location of PST files>” <SAS URL>”

This is an example for a source directory located on file server or local computer.

azcopy.exe copy <D:\Techieberry\anna.pst <“https://3c3e5952a2764023ad14984.blob.core.windows.net”

Step 3:

After the PST files have been uploaded to the Azure Storage location for your organization, the next step is to create a comma-separated value (CSV) file that specifies which user mailboxes the PST files will be imported to. You’ll submit this CSV file in the next step when you create a PST Import job.

Open a notepad file and lists the parameter and save it as the CSV file.

The first row, or header row, of the CSV file lists the parameters that will be used by the PST Import service to import the PST files to user mailboxes. Each parameter name is separated by a comma. Each row under the header row represents the parameter values for importing a PST file to a specific mailbox. You need a row for each PST file that you want to import to a user mailbox.

Step 4:

The next step is to create the PST Import job in the Import service in Microsoft 365.

  • Go to the “Microsoft Purview compliance portal“.
  • In the left pane of the Microsoft Purview compliance Portal, click Data lifecycle management > Microsoft 365.
  • On the Import tab, click + New import job.
  • Type a name for the PST import job, and then click Next. Use lowercase letters, numbers, hyphens, and underscores. You can’t use uppercase letters or include spaces in the name.
  • On the Do you want to upload or ship data? page, click Upload your data and then click Next.
  • On the Import data page, click the I’m done uploading my files and I have access to the mapping file check boxes, and then click Next.

On the Select the mapping file page, click Select mapping file to submit the CSV mapping file that you created in Step 3.

  • After the name of the CSV file appears under Mapping file name, click Validate to check your CSV file for errors.
  • The CSV file has to be successfully validated to create a PST Import job. The file name is changed to green after it’s successfully validated.
  • If the validation fails, click the View log link. A validation error report is opened, with an error message for each row in the file that failed.
  • Click Submit and then click Done.
  • A status flyout page is displayed, with a status of Analysis in progress and the new import job is displayed in the list on the Import PST files page.
  • Click “Refresh” to update the status information that’s displayed in the Status column. When the analysis is complete and the data is ready to be imported, the status is changed to Analysis completed.
  • You can click the import job to display the status flyout page, which contains more detailed information about the import job such as the status of each PST file listed in the mapping file.

Step 5:

After you create the import job in Step 4, Microsoft 365 analyzes the data in the PST files (in a safe and secure manner) by identifying the age of the items and the different message types included in the PST files. When the analysis is completed and the data is ready to import, you have the option to import all the data contained in the PST files or you can trim the data that’s imported by setting filters that control what data gets imported.

  • On the Import tab in the compliance portal, select the import jobs that you created in Step 4 and then click Import to Microsoft 365.
  • The Filter your data page is displayed. It contains the data insights resulting from the analysis performed on the PST files by Microsoft 365, including information about the age of the data. At this point, you have the option to filter the data that will be imported or import all the data as is.
  • Do one of the following:
    1. To trim the data that you import, click Yes, I want to filter it before importing.For detailed step-by-step instructions about filtering the data in the PST files and then starting the import job, see Filter data when importing PST files to Microsoft 365.Or
    2. To import all data in the PST files, click No, I want to import everything, and click Next.
  • If you chose to import all the data, click Next and submit to start the import job.
  • The status of the import job is display on the Import PST files page. Click Refresh to update the status information that’s displayed in the Status column. Click the import job to display the status flyout page, which displays status information about each PST file being imported.
  • When finished Outlook will show the emails within the mailbox.

Congratulations! you have learnt on how to import pst to office 365 mailbox.

Want to improve your Exchange Online experience for better productivity? Check out the tips and tricks mentioned here.

Now I’d like to hear from you:

Which finding from today’s report did you find most interesting? Or maybe you have a question about something that I covered.

Either way, I’d like to hear from you. So go ahead and leave a comment below.

Related Posts

5 Comments

  1. Vedran Segetalo

    How can we Cancel PST importing job that is stucked in Status = “In progess…” for days ?
    And removing all the import requests that belong to that job – does not help too.

  2. Meenakshi

    Thank you so much for the explanation. Recently, I spent $99 on mails daddy pst to office 365 migration app (https://www.mailsdaddy.com) for doing the same. You are really a time-saver and money-saver for many people like me.

  3. JerryBB

    Thank you Techieberry, very clear and helpful! Do you know what happens with the pst files you uploaded? Will they be deleted after some time? Or do you have to cleanup afterwards?

    • techieberry

      Thank you. I’m so glad I could be of assistance. If there are no import PST jobs in progress, then all PST files are automatically deleted 30 days after the most recent import job was created.

Leave a Reply

Your email address will not be published. Required fields are marked *