Best Practice: Migrating and converting SharePoint 2010 web applications from Classic-Mode to Claims-Based Authentication in SharePoint 2013

For migrating and converting SharePoint 2010 web applications from Classic-Mode to Claims-Based Authentication in SharePoint 2013, the following steps work best for me:

1. Create new classic-mode web application in SharePoint 2013, using PowerShell.

New-SPWebApplication -Name "ClassicWebAppName" -ApplicationPool "ClassicAppPoolName" -AuthenticationMethod "NTLM" -ApplicationPoolAccount (Get-SPManagedAccount "domain\serviceaccount") -Port 80 -URL "http://webapplicationURL" -HostHeader "HostURL" -Path "IISVirtualDirectoryName"

2. Restore and attach the content database from SharePoint 2010 to SharePoint 2013.

Mount-SPContentDatabase "<contentdb>" -DatabaseServer "<dbserver>" -WebApplication http://webapplicationURL

3. Deploy farm solutions as needed on the upgraded web application in SharePoint 2013.

4. Perform an IIS reset on Central Admin server and each WFE server in the SharePoint 2013 farm.

5. Ensure you can access the site collection in default Windows classic mode.

6. If you have a custom security trust config file, manually copy the file from a SharePoint 2010 WFE server to the Central Admin server and each WFE server in the SharePoint 2013 farm. C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG.

7. If you perform step 6 above, you will also need to manually add the open and closing security policy tag to the web.config file on the Central Admin server and each WFE server in the SharePoint 2013 farm, directly under the system.web opening tag.

<system.web> <securitypolicy> </securitypolicy>

8. Convert the web application to Claims-Based Authentication.

Convert-SPWebApplication –Identity http://webapplicationURL –To Claims -RetainPermissions -Force -Verbose

9. Run the usermigration_Claim.ps1 script, provided by Karim.

usermigration_Claim.ps1

10. Perform an IIS reset on Central Admin server and each WFE server in the SharePoint 2013 farm.

11. Ensure users can successfully access sites in the converted web application.