Steps to migrate Project server from 2010 to 2013

In this article, I will explain you step by step to migrate Project server from 2010 to 2013.

Script to Classic to claim conversion, run on 2010 environment: (run line by line)

$WebAppName = “http://ServerName:4545/”

$wa = get-SPWebApplication $WebAppName

$wa.UseClaimsAuthentication = $true

$wa.Update()

 

$account = “new\administrator”

$account = (New-SPClaimsPrincipal -identity $account -identitytype 1).ToEncodedString()

$WebAppName = “http://ServerName:4545/”

$wa = get-SPWebApplication $WebAppName

$zp = $wa.ZonePolicies(“Default”)

$p = $zp.Add($account,”PSPolicy”)

$fc=$wa.PolicyRoles.GetSpecialRole(“FullControl”)

$p.PolicyRoleBindings.Add($fc)

$wa.Update()

$wa.MigrateUsers($true)

$wa.ProvisionGlobally()

 

 

Developer Dashboard for 2013: (Not required for Migration)

$svc = [Microsoft.SharePoint.Administration.SPWebService]::ContentService
$dds = $svc.DeveloperDashboardSettings
$dds.DisplayLevel = “On”
$dds.Update()

[AdSense-A]

1. Take the database backup from existing 2010 environment

 

  • Open SQL server on 2010 SharePoint/Project Server environment.
  • Take the backup of necessary databases by doing the following steps.
    • Right click on Database name, Go to Tasks and then click on Backup.

 

    • Select the backup location then click on Ok.

 

    • Confirmation dialog box will appear that your backup of database completed successfully.

 

    • Do the same for the remaining databases (Project server databases)
  • Once all the databases backup has done, move/copy to the databases backups to new 2013 SharePoint/Project server.

[AdSense-A]

2. Restore the database into the new 2013 environment

 

  • Open SQL server on 2013 SharePoint/Project Server environment.
  • Restore all the databases which are copied from 2010 environment. To do this follow the below steps.
    • Right click on “Databases” then click on “Restore Database”.

 

    • Choose the location of database backup and then click on OK.

 

    • Confirmation dialog box will appear that your database restored successfully.

 

    • Click ok
    • Do the same for the remaining databases to restore in new 2013 environment.

[AdSense-A]

3. Test and Mount the SharePoint Content Database

3.1 Create a new web application in 2013 environment

  • Open central administration in 2013 environment

 

  • Click on Manage web applications

 

  • Click on New in the ribbon

 

  • Change the Port number (Here I am changing to 3434 because I am migrating 3434 web application)

 

  • Fill all other required fields then Click on OK ( I am leaving all remaining as default except the database name WSS_Content_3434_Dummy)

 

  • Wait for 10 min, a new window will appear as your web application has been created.

[AdSense-A]

3.2 Content database test & mount

 

  • Open SharePoint Management Shell/ Windows PowerShell as run as administrator (I am using PowerShell)

[AdSense-A]

  • Run “Add-PSSnapin Microsoft.sharepoint.powershell” command

 

  • To run the test command, enter the following command in the PowerShell prompt and received the following results
    • Test-SPContentDatabase -Name WSS_Content_TataSteel –WebApplication http://servername:3434/

 

  • Here the test command has identified a number of issues in the content database including missing assemblies and in this case that the content database is a Classic mode (the default for 2010) and the target web application is in Claims mode (the new default in 2013) and provides some steps to rectify it.
  • Notice at the top you can also see whether the problem found would block the upgrade or is an error
  • Once you are happy that all the potential upgrade blockers have been addressed then the content database can be mounted for real with the following command
    • Mount-SPContentDatabase WSS_Content_TataSteel –WebApplication http://sp2013:3434/ –NoB2BSiteUpgrade

 

  • We can check whether database is attached or not in Central Administration, go to Manage content Databases in Application Management

 

  • The mount process can take some time to complete depending on the amount of content in the database. Once its completed, all that is required is to make sure your account has access to the PWA site collection you’re upgrading using the following command (Optional)
    • Set-SPSite -Identity “http://servername:3434” -SecondaryOwnerAlias “new\username”
    •    Set-SPSite -Identity “http://sername:3434/pwa” -SecondaryOwnerAlias “new\username”

 

  • In this migration, the test command identified that we were attaching the classic database to a claims-based database, so it is also necessary to migrate the users in the content DB to their claims equivalent. To do so, enter the following PowerShell command
    • (Get-SPWebApplication http://servername:3434).migrateUsers($true)

 

  • By this SharePoint sites are migrated from 2010 to 2013, but interface is 2010 only

 

  • To upgrade this look and feel to 2013, click on Site Actions then click on site settings

 

  • Click on Site collection upgrade in Site Collection Administration

[AdSense-A]

  • Click on “Upgrade the Site Collection”

 

  • Click on “I’m Ready”

 

  • Once upgraded, click on “Let’s see the new site”

 

  • Now your 2010 site is completely migrated to 2013 site

 

  • But your Project Web Application site will give an error message