Forum Discussion
Office 365 Import PST - Folder structure not retained
Hi Adam,
thanks for your reply... why so many PST files? Long story - business decision, I am just an engineer :)
Anyway, why does it create "imported" folder at all? Isn't that the case of using and specifying the following then: If you specify /<foldername>, items in the PST file will be imported to a folder named <foldername>
That's exactly the same then?
Thanks,
G
You can import items to the current folder by choosing this during import, but it will end up as folders in that structure, aka a new inbox folder will be created under your current account! It will not be a separate folder in outlook though! I don't think there is any matching folders feature out of the box afaik
- gjuskromeMar 14, 2019Copper Contributor
Hi Adam,
thank you for this response as well! It makes perfect sense... would you be able to help me with the following question as well, please - it would be great if this is a solution to not use the PST import process...
Environment A
Exchange 2010 mailboxesEnvironment B
Active Directory + Azure AD Connect Sync + Office 365 Tenant (users without mailboxes)Is it safe if I use the Express Migration Scenario (minimal hybrid) from Exchange 2010 to Office 365 Tenant? I would not install or sync with Azure AD as users already exist in the cloud. Would that work? And O365 tenant would remain synced with Environment B.
Thanks,
G
- Mar 14, 2019
- gjuskromeMar 14, 2019Copper Contributor
Yes, that's the source I was getting the info - more specifically express migration?