Migration from Project Server 2007 to Project Server 2013

Recently, for one of our clients, we migrated Project Server 2007 to Project Server 2013. The client had been using Project Server 2007 since past four years, but was looking for an upgrade to experience extensive capabilities and new features of Project Server 2013.

There is no direct method to migrate from Project Server 2007 to Project Server 2013. You have to first migrate to Project Server 2010 and via that you can upgrade to Project Server 2013 through database migration.

Migration prerequisites

• Project Sever 2007, SharePoint 2007 and SQL Server 2005 should be updated to the latest available service packs. If they are not already installed, first install the service packs.
• Install new fresh hardware for Project Server 2010 and Project Server 2013 with latest service packs.

Steps to be performed on Project Server 2007

1. Open SharePoint Central Administration, navigate to Project Server Service application page and find the archive, draft, published, reporting and SharePoint content database for the PWA site to be migrated, and make a note of it.
2. Open SQL Server and take a backup of these five databases – archive, draft, published, reporting and SharePoint content database, and save it in a folder in a hard drive.
3. Copy the saved backup files and save it in 2010 database server.

Steps to be performed on Project Server 2010

1. 1. Restore the five databases in SQL 2008 server.
   2. Mount the SharePoint content database using SharePoint Management Shell script.

Example :

Mount-SPContentDatabase -Name -WebApplication

1. 1. Create the PWA site using SharePoint Management Shell script.

Example :

New-SPProjectWebInstance -Url http://<2007ApplicationServerName>/pwa -AdminAccount “” -PrimaryDbserver “<2007DatabaseServerName>” -PublishedDbname “” -ArchiveDbname “” -DraftDbname “” -ReportingDbserver “<2007DatabaseServerName>” -ReportingDbname “”

1. PWA Site is now created. You can see the home page.
2. Turn off backward compatibility mode in Project Server 2010 from Project Server 2010 home page. Click Server Settings on the Server Settings page, in the Operational Policies section, and click Additional Settings.
3. On the Additional Settings page, in the Project 2007 Compatibility Mode section, clear the Enable Project 2007 Compatibility Mode check box and click OK.
4. Bulk update the project sites so that all issues and risks are created in 2010.
5. Test and verify if all data is correctly migrated. Also, create new projects to check if they are correctly created.
6. Take a backup of the five databases – archive, draft, published, reporting and SharePoint content database for migration to 2013 and save it in a hard disk.

Steps to be performed on Project Server 2013

1. 1. Restore five databases in SQL 2012 server.
   2. Test the content database using SharePoint Management Shell script.

Example:

Test-SPContentDatabase -Name –WebApplication http://<2013ApplicationServerName>/

1. 1. Once successfully run, mount the database using SharePoint Management Shell script.

Example:

Mount-SPContentDatabase –WebApplication http://<2013ApplicationServerName> –NoB2BSiteUpgrade

1. 1. Make your account the secondary owner of the PWA Site using SharePoint Management Shell script.

Example:

Set-SPSite -Identity http://<2013ApplicationServerName>/pwa -SecondaryOwnerAlias “”

1. 1. If you are migrating Project Server 2010 users who were using Windows Classic authentication over to claims-based authentication, you will need to run the following SharePoint Management Shell script. Without running this script, users will not be able to log on to Project Web App after upgrade.

Example:

(Get-SPWebApplication http://<2013ApplicationServerName>).migrateUsers($true)

1. 1. Check your PWA Site collection using SharePoint Management Shell script for problems that can cause upgrade failure.

Example:

Test-SPSite –Identity http://<2013ApplicationServerName>/pwa

1. 1. Upgrade the Project Web App site using below SharePoint Management Shell script.

Example:

Upgrade-SPSite -Identity http://<2013ApplicationServerName>/pwa –VersionUpgrade

1. 1. Consolidate your Project Server 2010 databases to a Project Web App database.

Example:

ConvertTo-SPProjectDatabase -WebApplication http://<2013ApplicationServerName> -dbserver <2013DATABASESERVERNAME> -ArchiveDBName -DraftDBName -PublishedDBName -ReportingDBName -ProjectServiceDBName <2013DatabaseName>

1. 1. Attach the Project Services database to the web application using SharePoint Management Shell script.

Example:

Mount-SPProjectDatabase –Name <2013DatabaseName> –WebApplication http://<2013ApplicationServerName>

1. 1. Check your Project Web App database for problems occurring to cause upgrade to fail using SharePoint Management Shell script.

Example:

Test-SPProjectDatabase –Name <2013DatabaseName>

1. 1. Upgrade the Project Web App database using SharePoint Management Shell script.

Example:

Upgrade-SPProjectDatabase -Name <2013DatabaseName> -WebApplication http://<2013ApplicationServerName>

1. 1. Mount the Project Web App instance using SharePoint Management Shell script.

Example:

Mount-SPProjectWebInstance –DatabaseName <2013DatabaseName> -SiteCollection http://<2013ApplicationServerName>/pwa

1. 1. Check the Project Web App instance for any problem occurring to cause upgrade failure using SharePoint Management Shell script.

Example:

Test-SPProjectWebInstance –Identity http://<2013ApplicationServerName>/pwa

1. 1. Use the below SharePoint Management Shell script to get results of the health check in notepad to get more detailed and helpful information.

Test-SPProjectWebInstance –Identity http://<2013ApplicationServerName>/pwa | Format-Table -Wrap -AutoSize | Out-File -FilePath c:output.txt

1. 1. Upgrade the Project Web App instance using SharePoint Management Shell script.

Example:

Upgrade-SPProjectWebInstance -Identity http://<2013ApplicationServerName>/pwa

1. 1. Enable Project Web App features using SharePoint Management Shell script.

Example:

Enable-SPFeature -Identity pwasite –URL http://<2013ApplicationServerName>/pwa

1. Bulk update all sites to get issues, risks and documents restored.

Check with the previous environment and verify if there is any inconsistency in data.