Migrating from SharePoint 2010 Classic Mode Authentication to SharePoing 2013 Claims Based Authentication

Ok so I haven't posted in a while, mainly because I've been so busy trying to plan SharePoint 2013!!! It's taken a few attempts, but finally, I've got a procedure that works when you're trying to battle between moving from Classic SharePoint 2010 Authentication to the lovely 2013 Claims. If you have InfoPath forms, prepare for a massive headache!!! But because I get all my wisdom from Googling, I will share my procedure which is tried and tested. It's still new and I haven't completed into a live launch yet but it's a lot simpler than the move from 2007 to 2010, that's for sure.

The first thing that you need to do is to create a Claims Based Web Application in your 2010 farm if you do not have one already. You will also need to define this new Web Application in your DNS Settings for your network.

STEP 1: Backup your Site

1.       Connect to a server on your farm

2.       Open SharePoint Management Shell

3.       In the window, type in the following command:
Backup-SPSite [SiteURL] -Path [PathtoFolder]

STEP 2: Restore your Site to the Claims Based Web Application

4.       Once above is complete, restore the site to your Claims Based Web Application which should be blank

Restore-SPSite  [WebAppURL] –Path [PathtoFolder] -Force

5.       The force switch means that it will overwrite any site collection that might be location on your current claims web app. If you are prompted, press y to continue

STEP 3: Migrate Users to Claims Based Authentication

6.       Once complete, you need to migrate the users from classic based authentication to claims based authentication. Run the below commands as spfarm to enable this:

$wa = Get-SPWebApplication [WebAppURL] 

$wa.MigrateUsers($true)

$wa.ProvisionGlobally

7.       You can check to ensure that this ran properly by viewing the site permissions in your WebApp. The users should have some funny characters before their names.

STEP 4: Backup your Content Database

8.       On your SharePoint 2010 Farm SQL Server, open SQL Management Studio

9.       Right Click on the content database associated with your WebApp and choose TasksàBackup

10.   Backup the database to a specific location

STEP 5: Restore Content Database to SQL 2012 on the SharePoint 2013 Farm

11.   Remote connect to your SharePoint 2013 SQL Farm Server.

12.   Open SQL Management Studio, connecting to your SharePoint instance

13.   Copy the content database from your old SQL Server to this one. You might need to share this on the old server first.

14.   Back in SQL Management Studio on SQL 2012, right click on “Databases” on the SharePoint SQL Instance

15.   Choose “Restore Database”

16.   Browse to the database that you just copied to restore it giving it whatever name you wish

STEP 6: Mount the Database to SharePoint 2013 Claims Web Application

17.   Connect to another server on your 2013 farm

18.   Open SharePoint Management Shell

19.   At the command window, type the following to Mount the database to 2013

Mount-SPContentDatabase “[ContentDBName]” –DatabaseServer “[DBServerName]” –WebApplication [WebAppURL]

STEP 7: Upgrade the Look and Feel

20.   Once the Content Database is mounted, there will be errors on the command screen. Unless there are critical warnings, this should be ok.

21.   Browse to your Web App where you have restored the data

22.   In the red banner at the top of the screen, click on Start Now to upgrade the look and feel

 

That should be it. In this example, I am migrating to a test web application from there, I am going to migrate into the live locations. There are issues with Infopath which I will document soon.

 

Hope this helps!!! Comment below! :)