2

I am currently using a tool to migrate the on-premises content to SharePoint Online which is having ADFS and Dir Sync.

I saw a difference in the migrated and non migrated Office 365 AD accounts which is as explained below:

non-migrated users accounts will be domain\fistname_lastname and corresponding claims user will "i:0#.f|membership|[email protected]" but for migrated office 365 accounts will be "i:0#.f|membership|[email protected]"

I would like to start moving the content before migrating the users and interested to know whether the SharePoint permissions will work normally even post migration of user accounts or not. I am even worried about the user specific fields such as modified by and created by.

Please share your thoughts.

Improve this question

1 Answer 1

Reset to default
1

its depend upon the tools, usually if you migrate the users using the tools and then migrate the content it works like a charm. we did the same thing with sharegate for small set of user and no issue at all.

Update: I used tsunami tool to migrated from non sharepoint to cloud. In that project we migrate content then mapped the user...that help us in preserving the metadata...so as per your situation, I think you will be fine as per my experience...BTW which tool u are using?

Improve this answer
1
  • the scenario that i mentioned was migrate the content first and then do the user move later. i can provide the mapping and update the user with changed upn value but i doubt whether it will work or not. most of our users were still not migrated yet so i would like to know.
    – kesava
    Commented Jul 8, 2015 at 21:50

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.