0

I have a requirement to migrate from Sharepoint 2013 Classic mode authentication to o365 claims based authentication.

But there is a catch. I need to do it one subsite at a time and not the entire application in one go.

Thanks, Sheldon

Improve this question
2
  • how you migrating the content to office 365?
    – Waqas Sarwar MVP ♦
    May 2 '17 at 12:52
  • If you're migrating the content, yeah there is no need to do any classic to claims conversion.
    – Trevor Seward
    May 2 '17 at 15:22
0

There are different methods (MigrateUsersToClaims, deprecated MigrateUsers) which are called by your PowerShell-commands (Convert-SPWebApplication). All of these methods are scoped at a WebApplication Level.

With the given Information my answer is: It is not possible to convert a SiteCollection/SubSite/List/Item. You must do it at the WebApplication level.

Could you please provide more information abount why you need to migrate one subsite at a time? Maybe your doubts are unnecessary or we can provide a workaround for your problem.

Improve this answer
5
  • Thanks for your answer. We are planning to migrate at a Site collection or at site level because the migration process is taking up a lot of time (An average of a few couple of days).
    – Shel
    May 3 '17 at 4:27
  • Entire farm migration that is.
    – Shel
    May 3 '17 at 4:34
  • If you say "migration process" you mean the classic to claims migration? Or the O365 migration? As Waqas and Trevor already mentioned, your migration-plan would be useful. Chances are good that you can skip the entire process of classic-to-claims. The more information you provide, the better we can help.
    – MHeld
    May 3 '17 at 6:16
  • We used the Convert-SPWebApplication command to migrate the classic mode authentication to claims based authentication on the existing SharePoint 2013 on premises itself and then thought of migrating the upgraded farm to o365 directly. But the volume of the farm is around 1 TB and hence the powershell command went on running for 5-6 days and we had to force stop.
    – Shel
    May 3 '17 at 12:08
  • What exactly do you mean with "migrating the upgraded farm to o365 DIRECTLY"? There is no database-attach method like when you migrate from SP2010 or SP2013 to a newer version.
    – MHeld
    May 3 '17 at 18:06

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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