Office 365 Import Failed- Multiple Tricks to Fix Most Common Errors

Depending upon the ever-changing demands of the users, import PST to Office 365 is the most common task carried out by the users. And, completing the entire process without any error or failure happens in rare cases. There are the number of silly mistakes that users do during the import process. This will later result in Office 365 import PST failed error, which makes users search for some troubleshooting ways for the same.

Common Queries Asked by Users:

Now, to understand the problems or errors faced during PST import process, consider some of the queries asked by the users:

A few hours ago, we were importing PST files to Office 365 with the help of AzCopy Tool. And, suddenly, it display the status that Office 365 import failed. The details it displayed is that the process is 70% complete. Now, I am looking for a solution that let me resume the job from where it was left off or I have to restart the job? Some of the sites over the internet suggested me to the delete the entire online archive process and start importing all over again. I do not know why this Office 365 PST import failed as previously I have imported many times without any failure.

When I was uploading multiple PST files in batches, the upload works perfectly during upload process for the first 3 batches. But as I initiated a new job and created a new sas-url to replace the URLs in the copy job, it displayed 403 error message:

I am confused now and do not know how to proceed further. Can anyone suggest me some other simple way to import multiple PST files to Office 365?”

I was trying to import 5 PST files to Outlook 365 via a web-based import application. I have recently uploaded the files with the help of Microsoft Azure Storage tools. After that, created a ‘PSTImportMappingFile.csv’ file that helps Office 365 in determining which PST belongs to which mailbox. However, most of the mailboxes work fine but some of them return the following error:

“Please create Primary and Archive Mailbox for and create a new job”

So, I created a new job but the things are still the same. Does anyone know what is exactly happening?”
How to Troubleshoot Office 365 Import Failed Error?

This section of the blog will let users know the most common scenarios with a short explanation and some hints for troubleshooting:

How to Troubleshoot Office 365 Import Failed Error?

This section of the blog will let users know the most common scenarios with a short explanation and some hints for troubleshooting:

Problem #1: Import Process Failed at 0%

Error Message:
“import failing to initiate”
or
“The operation couldn’t be performed because ‘archive1@contoso.com’ matches multiple entries.”

Solution: In the CSV mapping file for the target mailboxes, a user should use the unique identifiers like ExchangeGUIDs rather than using the primary SMTP address of the users.

Explanation: The main reason behind this import data to Office 365 error is the soft deletion of mailboxes or mail users. They will combat the targeted user’s active mailboxes when they resolve the primary SMTP address.

Problem #2: If a user has created a job with the deleted job name, it displays an error.

Error Message: “Job with the same name already exists”.

Solution: Always use unique names for the jobs to import PST file.

Explanation: The job names must be unique always, in order to avoid any such restriction in the future.

Problem #3: There is a difference in the data that supposed to be imported and the data that is imported actually.

Error Message: Not Applicable

Solution: Simply execute the following command:
Get-MailboxImportRequestStatistics -identity “Name of Import\GUID |fl

After that, you need to have a look at the following parameters:

• EstimatedTransferSize: 1.211 GB (1,300,827,963 bytes)
• BytesTransferred: 64.36 MB (67,487,118 bytes

Explanation: After looking at the figures given above, it is clear that some of the items are already there in the targeted mailbox at the time of import. Hence, in order to avoid duplicates, some items were left.

Problem #4: CSV mapping files are not validated during the import process.

Error Message: “The specified file could not be found. Please ensure that the path to the file is correct.”

Solution: A user simply to re-check the file path in the CSV mapping file.

Explanation: The possible reason behind this is the difference in the cases of file paths.

For example, the path in the mapping file “/test1/OutlookPST/IMPORT/batchA” and the file stored at the Azure Storage account is at: “/test1/OutlookPST/Import/Batcha”. To overcome such issue, a user is suggested use “/test/OutlookPST/Import/Batcha” in the CSV mapping file.

Problem #5: Office 365 Service is not available

Error Message: Error 403 Forbidden

Solution: Double-check the source and destination path

Explanation: This problem mainly arises when the source and destination are not proper. Moreover, the proper and right way of using Azcopy Tool is with the help of below-mentioned command:
AzCopy.exe /Source: /Dest: /V:

All above-discussed tricks are the possible troubleshooting ways to over Office 365 import failed issue. However, if a user is unable to solve the issue by any of the above means, then it suggested switching to some third-party tool.

Import PST to Office 365 Purchase Now

In order to choose the best software for the import process, a user can try Office 365 Import software recommended by:

Paolo Valsecchi, the Vmware Certified Professional-DCV, vExpert

Apart from this, it all depends on the choice of the user for which he or she wants to go. But, if they are confused and unable to make choice between the manual tricks and professional, it is recommended to go for the tool to remove the Office 365 Import Failed error. It is one of the efficient application that requires minimum effort and guarantees complete data migration also.

Frequesntly Asked Question & Answers