Migrate SharePoint 2010 classic-mode web applications to SharePoint 2013 classic-mode web applications

In my last org task - Upgrade of SharePoint Server to SharePoint 2013 from SharePoint 2007 version, I found that  SharePoint 2013 default authentication method for web application is Claim based authentication and Windows Classic authentication method is deprecated in SharePoint 2013 release.

In SharePoint 2013, complete the following procedure to create a classic-mode web application, then migrate an existing SharePoint 2010 classic-mode Web application to SharePoint 2013 and at last convert an existing SharePoint 2010 classic-mode web application to a SharePoint 2013 web application that uses claims-based authentication.

First we will create a web application using PowerShell command because we cannot create web application having classic based authentication using central administration.

New-SPWebApplication -name "MySiteClassicAuthApp" -Port 100 

-ApplicationPool "MySiteClassicAuthAppPool"

-ApplicationPoolAccount(Get-SPManagedAccount "Domain\account")

Attach an existing content database of SharePoint 2010 version to our new 2013 web application, which we have already added in SQL Server before that we have to Test Content Database using “Test contentDB” powershell command for successful mount of content database.

     Mount-SPContentDatabase "<ContentDb>" -DatabaseServer "<DbServer>" 

       -WebApplication http://SiteName

 

Now detach a content database which was created while creating site.

Dismount-SPContentDatabase "<ContentdBName>"

Convert your SharePoint 2013 classic-mode web application to claims-based authentication - 

  Convert-SPWebApplication -Identity <yourWebAppUrl> 

         -To Claims

         -RetainPermissions [ -Force]

Retain permission property used to retain exiting permissions.

Note:

• If you not used -AuthenticationMethod parameter while creating New classic based auth web application then also by default classic based auth web app will be created.
• Account which your using have sufficient permission to perform activity in SQL and SharePoint.
• Convert-SPWebApplication converts the web application to claims-based authentication. You have to verify that the users can access the web application after you have converted it.
• You must use the content database GUID in this command instead of using the content database name, in case of multiple content databases that have the same name.
• To retrieve the GUID of the content database, run the Get-SPContentDatabase PowerShell cmdlet with no arguments.
• The Dismount-SPContentDatabase  detaches the content database from the web application, but it does not delete the content database from SQL Server. After detached, you cannot delete it by using Windows PowerShell 3.0. You can only remove it by using SQL Server tools. If you want to delete the content database from SQL Server while you detach it, use the Remove-SPContentDatabase instead.

Reference: http://technet.microsoft.com