Office 365 Import PST - Folder structure not retained

%3CLINGO-SUB%20id%3D%22lingo-sub-369288%22%20slang%3D%22en-US%22%3EOffice%20365%20Import%20PST%20-%20Folder%20structure%20not%20retained%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369288%22%20slang%3D%22en-US%22%3E%3CP%3EOn%20the%20last%20import%20of%20hundreds%20of%20PST%20files%2C%20I%20have%20found%20out%20that%20the%20folder%20structure%20was%20not%20retained.%20Can%20anyone%20confirm%20whether%20the%20following%20is%20working%20as%20expected%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3E%3CEM%3EIf%20you%20specify%26nbsp%3B%2F%2C%20items%20in%20the%20PST%20file%20will%20be%20imported%20directly%20in%20to%20the%20user's%20Inbox%20folder.%26nbsp%3B%3C%2FEM%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EDoes%20it%20mean%20that%20whatever%20is%20in%20PST%20folder%20will%20be%20reflected%20to%20the%20imported%20mailbox%3F%20E.g.%2C%20content%20from%20inbox...%20will%20go%20to%20inbox...%20if%20there%20are%20folders%20and%20subfolders%20in%20the%20inbox%20folder%20of%20PST%20file...%20same%20structure%20will%20be%20created%20in%20the%20mailbox%20in%20the%20cloud.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EWIth%20the%20last%20import%20we%20did%2C%20I%20found%20out%20that%20despite%20using%20the%20%2F%2C%20import%20process%20created%20%22Imported%20XXX%22%20folder%20under%20inbox%20and%20inside%20the%20whole%20folder%20structure%20and%20content%20from%20PST%20file.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThanks%2C%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-369288%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMigration%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369486%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20Import%20PST%20-%20Folder%20structure%20not%20retained%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369486%22%20slang%3D%22en-US%22%3E%3CP%3Eyup%2C%20this%20was%20clarified%20%3A)do%20you%20have%20any%20input%20regarding%20migration%20process%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369481%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20Import%20PST%20-%20Folder%20structure%20not%20retained%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369481%22%20slang%3D%22en-US%22%3E%3CP%3EAfaik%20there%20isn't%20an%20option%20to%20preserve%20the%20folder%20structure%20as%20in%20your%20example.%20Your%20options%20are%20to%20import%20under%20Inbox%20(which%20is%20what%20%22%2F%22%20does)%20or%20under%20a%20custom%20folder%2C%20as%20detailed%20here%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fsecuritycompliance%2Fuse-network-upload-to-import-pst-files%23step-4-create-the-pst-import-mapping-file%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fsecuritycompliance%2Fuse-network-upload-to-import-pst-files%23step-4-create-the-pst-import-mapping-file%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369480%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20Import%20PST%20-%20Folder%20structure%20not%20retained%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369480%22%20slang%3D%22en-US%22%3E%3CP%3E1.%20yeah%2C%20to%20keep%20it%20simple%2C%20you%20can't%20sync%20from%20two%20ADconnect%26nbsp%3B%20to%20one%20tenant%20basically!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2.%20I%20guess%20it%20would%20work...I've%20not%20digged%20deep%20into%20the%20entire%20process%20but%20I%20guess%20then%20you%20would%20need%20to%20match%20users%2C%20etc%20etc%20since%20these%20office%20365%20users%20are%20synced%20from%20your%20other%20AD%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369475%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20Import%20PST%20-%20Folder%20structure%20not%20retained%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369475%22%20slang%3D%22en-US%22%3E%3CP%3EYes%2C%20I%20completely%20agree%20with%20-%20just%20looking%20for%20possible%20solutions%20for%20business.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20reason%20why%20I%20started%20thinking%20about%20the%20express%20(minimal%20hybrid)%20migration%20is%20that%20users%20can%20already%20be%20in%20O365%20tenant.%20However%2C%20before%20you%20initiate%20migration%20you%20must%20disable%20the%20sync%20-%20right%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%2C%20if%20I%20choose%20not%20to%20sync%20at%20all%20(and%20users%20are%20already%20in%20the%20cloud)%20wouldn't%20then%20this%20go%20through%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369468%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20Import%20PST%20-%20Folder%20structure%20not%20retained%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369468%22%20slang%3D%22en-US%22%3E%3CP%3Eoh%20sorry%20missed%20that%20point!%20No%20this%20is%20correct!%20It%20will%20fail..%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20just%20feel%20like%20this%20is%20a%20hassle%20due%20to%20you%20already%20set%20up%20your%20ad%20and%20tenant%20with%20sync!%20You%20need%20to%20break%20this%20to%20start%20syncing%20with%20you%20exchange%20environment%20etc..then%20go%20back!%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20would%20suggest%20using%20a%20third%20party%20migration%20tool!%20most%20of%20these%20are%20quite%20affordable%20and%20makes%20this%20easy%20as%20pie!%20you%20choose%20to%20match%20your%20users%20mailboxes%20with%20the%20users%20in%20office%20365%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F58%22%20target%3D%22_blank%22%3E%40Vasil%20Michev%3C%2FA%3E%26nbsp%3B%20Any%20suggestions%3F%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369461%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20Import%20PST%20-%20Folder%20structure%20not%20retained%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369461%22%20slang%3D%22en-US%22%3E%3CP%3EIndeed...%20but%20the%20cutover%20migration%20requirement%20is%20that%20users%20do%20NOT%20exist%20in%20O365%20as%20the%20cutover%20will%20create%20them...%20isn't%20that%20the%20case%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhy%20would%20you%20not%20use%20the%20express%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369459%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20Import%20PST%20-%20Folder%20structure%20not%20retained%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369459%22%20slang%3D%22en-US%22%3E%3CP%3EI%20would%20say%20cutover%20migration!%20Since%20your%20tenant%20is%20already%20sync%20with%20another%20AD%20etc..%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369453%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20Import%20PST%20-%20Folder%20structure%20not%20retained%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369453%22%20slang%3D%22en-US%22%3E%3CP%3EYes%2C%20that's%20the%20source%20I%20was%20getting%20the%20info%20-%20more%20specifically%20express%20migration%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369448%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20Import%20PST%20-%20Folder%20structure%20not%20retained%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369448%22%20slang%3D%22en-US%22%3E%3CP%3EPlease%20read%20here%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CFONT%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fmailbox-migration%2Fmailbox-migration%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fmailbox-migration%2Fmailbox-migration%3C%2FA%3E%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369442%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20Import%20PST%20-%20Folder%20structure%20not%20retained%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369442%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Adam%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethank%20you%20for%20this%20response%20as%20well!%20It%20makes%20perfect%20sense...%20would%20you%20be%20able%20to%20help%20me%20with%20the%20following%20question%20as%20well%2C%20please%20-%20it%20would%20be%20great%20if%20this%20is%20a%20solution%20to%20not%20use%20the%20PST%20import%20process...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EEnvironment%20A%3C%2FSTRONG%3E%3CBR%20%2F%3EExchange%202010%20mailboxes%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EEnvironment%20B%3C%2FSTRONG%3E%3CBR%20%2F%3EActive%20Directory%20%2B%20Azure%20AD%20Connect%20Sync%20%2B%20Office%20365%20Tenant%20(users%20without%20mailboxes)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20it%20safe%20if%20I%20use%20the%20Express%20Migration%20Scenario%20(minimal%20hybrid)%20from%20Exchange%202010%20to%20Office%20365%20Tenant%3F%20I%20would%20not%20install%20or%20sync%20with%20Azure%20AD%20as%20users%20already%20exist%20in%20the%20cloud.%20Would%20that%20work%3F%20And%20O365%20tenant%20would%20remain%20synced%20with%20Environment%20B.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%26nbsp%3B%3C%2FP%3E%3CP%3EG%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369316%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20Import%20PST%20-%20Folder%20structure%20not%20retained%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369316%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20can%20import%20items%20to%20the%20current%20folder%20by%20choosing%20this%20during%20import%2C%20but%20it%20will%20end%20up%20as%20folders%20in%20that%20structure%2C%20aka%20a%20new%20inbox%20folder%20will%20be%20created%20under%20your%20current%20account!%20It%20will%20not%20be%20a%20separate%20folder%20in%20outlook%20though!%20I%20don't%20think%20there%20is%20any%20matching%20folders%20feature%20out%20of%20the%20box%20afaik%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369298%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20Import%20PST%20-%20Folder%20structure%20not%20retained%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369298%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20aware%20of%20this%2C%20yes.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EReally%2C%20just%20needed%20confirmation%20whether%20it's%20possible%20to%20retain%20exactly%20the%20same%20folder%20structure%20without%20any%20%22imported%22%20folder%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EG%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369295%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20Import%20PST%20-%20Folder%20structure%20not%20retained%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369295%22%20slang%3D%22en-US%22%3E%3CP%3EPlease%20see%20this%20as%20well%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CFONT%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fsecuritycompliance%2Fimporting-pst-files-to-office-365%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fsecuritycompliance%2Fimporting-pst-files-to-office-365%3C%2FA%3E%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369292%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20Import%20PST%20-%20Folder%20structure%20not%20retained%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369292%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Adam%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethanks%20for%20your%20reply...%20why%20so%20many%20PST%20files%3F%20Long%20story%20-%20business%20decision%2C%20I%20am%20just%20an%20engineer%20%3A)%3C%2Fimg%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyway%2C%20why%20does%20it%20create%20%22imported%22%20folder%20at%20all%3F%20Isn't%20that%20the%20case%20of%20using%20and%20specifying%20the%20following%20then%3A%26nbsp%3B%3CEM%3E%3CSTRONG%3EIf%20you%20specify%26nbsp%3B%2F%3CFOLDERNAME%3E%2C%20items%20in%20the%20PST%20file%20will%20be%20imported%20to%20a%20folder%20named%26nbsp%3B%3CFOLDERNAME%3E%3C%2FFOLDERNAME%3E%3C%2FFOLDERNAME%3E%3C%2FSTRONG%3E%3C%2FEM%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThat's%20exactly%20the%20same%20then%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CBR%20%2F%3EThanks%2C%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EG%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369291%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20Import%20PST%20-%20Folder%20structure%20not%20retained%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369291%22%20slang%3D%22en-US%22%3EIt%20will%20be%20added%20as%20a%20separate%20folder%2C%20but%20with%20the%20folder%20structure%20retained%20within!%3CBR%20%2F%3EWhy%20are%20you%20working%20with%20hundreds%20of%20pst%20files%3F%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

On the last import of hundreds of PST files, I have found out that the folder structure was not retained. Can anyone confirm whether the following is working as expected?

 

If you specify /, items in the PST file will be imported directly in to the user's Inbox folder. 

 

Does it mean that whatever is in PST folder will be reflected to the imported mailbox? E.g., content from inbox... will go to inbox... if there are folders and subfolders in the inbox folder of PST file... same structure will be created in the mailbox in the cloud.

 

WIth the last import we did, I found out that despite using the /, import process created "Imported XXX" folder under inbox and inside the whole folder structure and content from PST file.

 

Thanks,

15 Replies
Highlighted
It will be added as a separate folder, but with the folder structure retained within!
Why are you working with hundreds of pst files?
Highlighted

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

Highlighted

I am aware of this, yes. 

 

Really, just needed confirmation whether it's possible to retain exactly the same folder structure without any "imported" folder?

 

G

Highlighted

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

Highlighted

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 mailboxes

 

Environment 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

Highlighted

Yes, that's the source I was getting the info - more specifically express migration?

Highlighted

I would say cutover migration! Since your tenant is already sync with another AD etc..

Highlighted

Indeed... but the cutover migration requirement is that users do NOT exist in O365 as the cutover will create them... isn't that the case? 

 

Why would you not use the express?

Highlighted

oh sorry missed that point! No this is correct! It will fail..

 

I just feel like this is a hassle due to you already set up your ad and tenant with sync! You need to break this to start syncing with you exchange environment etc..then go back! 

 

I would suggest using a third party migration tool! most of these are quite affordable and makes this easy as pie! you choose to match your users mailboxes with the users in office 365

 

@Vasil Michev  Any suggestions??

Highlighted

Yes, I completely agree with - just looking for possible solutions for business.

 

The reason why I started thinking about the express (minimal hybrid) migration is that users can already be in O365 tenant. However, before you initiate migration you must disable the sync - right?

 

So, if I choose not to sync at all (and users are already in the cloud) wouldn't then this go through?

Highlighted

1. yeah, to keep it simple, you can't sync from two ADconnect  to one tenant basically!

 

2. I guess it would work...I've not digged deep into the entire process but I guess then you would need to match users, etc etc since these office 365 users are synced from your other AD

Highlighted

Afaik there isn't an option to preserve the folder structure as in your example. Your options are to import under Inbox (which is what "/" does) or under a custom folder, as detailed here: https://docs.microsoft.com/en-us/office365/securitycompliance/use-network-upload-to-import-pst-files...

Highlighted

yup, this was clarified :) do you have any input regarding migration process?