Improve PST import tool performance
We found that Import jobs of more than one PST to Mailbox mapping either took an extremely long time to import, or got stuck and never completed. The most reliable way to use the tool was to create individual one-to-one mappings, which meant creating hundreds of jobs when one should have been fine. We also found that imports where the total PST size of multiple mailboxes was over 10 Gb were much more likely to fail or take way too long to finish. Given that Mailbox limits are 50GB, this 10GB limit is too small.
Pankaj Tyagi commented
As you know that the Microsoft provides manual processes one is the Network Upload Method and another is the Drive shipping, you can use any one of them for importing the PST file data to Office 365 manually.
But here another method available which is A2Z Migrations for PST to Office 365 Converter. It will also Import the PST file data including the attachments into the o365 Cloud platform. It will export your multiple PST files into the Exchange online parallelly.
This tool has Perfect methods to migrate from Outlook PST to Office 365 . If you are facing issues then go for This amzaing tool.
john wilson commented
I think the manual method could be the better option to import PST to Office 365. But it is a little bit techie and large process. That's why I would suggest you try Shoviv PST to Office 365. https://www.shoviv.com/pst-to-office365.html
steve smith commented
You can do manually importing single pst file to office365. But you can’t import multiple pst files manually. So, to overcome from this problem you have to use tools. In these tools you can perform many functions like import bulk pst files, recover pst files and many more.
I suggest you to use PST Converter. If you are not aware with the working of software, then start with free demo.
Using the IMAP migration tool was a massive waste of time for me. It took so long to not do anything that I ended up just doing it all manually, using all my data and wasting 5 days of time. I schedule the migration over the weekend for obvious reasons but ended up taking the whole week too because your system does not provide an accurate status.
Try third party tool and easily import PST files to Office 365 . Read more : https://importpstfilestooffice365.blogspot.com
Download and try MailsDaddy PST to Office 365 migration tool which is much faster than other tools. Get free trial edition from official website: https://www.mailsdaddy.com/pst-to-office-365-migration-tool/
I have found some other resources which provides the solution to import large PST files into Office 365, you can try this software, it will help you to quickly perform PST file to Office 365 migration.
shiv gupta commented
Ok thank you
John Kerry commented
Try tool from Microsoft Technet site:
It helps you to import all data from .pst files to Office 365 user account
Nevin fradian commented
Import PST to Office 365, a secure and the most advanced third party software, capable to convert multiple user mailboxes from PST to Office 365 in a single attempt. With the help of this third party software, users can also convert OST files to Office 365. For more information about the software, visit- https://www.nucleustechnologies.com/import-pst-to-office-365/#tab7
PST Import Tool fails when file PST file size is too big. Weak performance, hanging issues, take too much time. Instead, I prefer SysTools import PST to Office 365 tool, Software within no time export multiple PST file within Office 365. Try free demo: https://www.systoolsgroup.com/import-to-office-365/
I have nothing but bad things to say about the PST import tool, and O365 in general for that matter. It constantly creates headaches for myself and my team.
It would be invaluable to be able to import/export PST via Powershell, like can be done in Exchange. I was looking at manually migrating the data from 90 mailboxes from five O365 tenancies into one. This is an absolute nightmare as there are NO supported pathways. Add to that, the fact that Outlook locks up during exports and imports, makes it impossible to run in the background. SMH for O365!
Martin Tillbrook commented
I'm also seeing VERY slow performance. I'm trying to import one 20GB PST into a user's archive at the moment. Its been running now for 24hours and is only at 77%.
My initial upload to Microsoft's blob storage took less than an hour - I don't understand why its taking so long to import now from MS's own storage infrastructure?
There are poor performance, my company 3000 user upload the pst to o365 online archive and then I get a complain because the upload pst slow + hang problem.
Mario P. commented
I just assisted my customer to do 3.5 GIGS and it's only 55% done? what is going on?
Also this tool is not new but in the documentation no one took the time to mention that the name of the files is also case sensitive? we found this out at the time to validate after 4hours.
Can you please fix that in the documentation at least?
Gerald Hopf commented
The performance of the PST Import is abysmal. I've used it for importing two PST files into two mailboxes: one 37GB in size and one 95GB in size. The 37GB worked fine but took a long long time. About 40-50 hours to import. This is not acceptable performance in 2017 and seriously derails any efforts to migrate users overnight or over-weekend without downtime in their "work-ability".
It also was slower than Microsofts own FAQ claims ("import speed at least 1GB/hour")
For my 95GB import (into a 100GB account): it silently failed at about the 30GB mark and just stopped importing any more data. There was nothing in the detailed logs that showed why that might have happened and support was unable to help or explain it either.
Please fix the PST import. In the age of SSDs that can transfer 1TB a second, an import speed of less that 1GB an hour is just a slap in the face of customers who want to migrate to your platform.