Project Server Data Migration - Cheat Sheet
Data Migration can be a long difficult progress. In Project 2007 we made a lot of investiments to make this process a lot smoother for users.
This post provides a list of quick steps to migrate your Project Server 2003 data into Project Server 2007. I've done it several times and it works well. If there are any failures, the log gives you detailed information for troubleshooting the issue.
This list doesn't provide a detailed documentation of the process or all the detailed steps or how to troubleshoot problems. For that, refer to the Beta 2 documentation.
1) Install Project Server 2007 and provision a Project Web Access site
2) Backup your clean Project databases (all 4 of them). If you run into problems you can restore the databases and start over
3) Get your Project 2003 database ready. Restore an existing Project 2003 database onto the same SQL server as the Project Server 2007. Or create a linked server on the Project Server 2007 SQL Server (SQL Server instance->Security->Linked Servers). Link it to the Project Server 2003 SQL Server. In the security tab choose ‘be made with this security context’ and give a SQL Auth account (Eg. user: sa password:<whatever>)
4) Install Project 2007 Professional and choose the “install migration tool” advanced option in setup
5) Change the default Migration ini file that gets installed with Project Professional (you can find it at Program FilesMicrosoft OfficeOffice12 P12MIGRATION.INI.SAMPLE) Add in the right values for Project Server 2003 databases, Project Server 2003 Linked SQL Server, Project Server 2007 PWA etc. ***Spend some time to make sure all your parameters are valid. There are detailed explanation of each parameter***
6) Run the migration tool from the command line: "<drive>:Program FilesMicrosoft OfficeOFFICE12p12migrationtool.exe" -c "<location>p12migration.ini"
7) Look at the command line/migration log to make sure everything is fine. If not, do corrections and re-run migration tool - it should start from where it stopped last. If there is a irrecoverable problem, make changes in Project Server 2003, restore the clean Project Server 2007 databases and retry migration.
8) If you have any local windows accounts (eg. <MachineBrad Sutton>), make sure you use PWA->edit user functionality to edit those accounts so that they are valid.
9) Go to the migrated PWA site as an admin, edit each migrated security category, go to the “Views – add to category” section and add the ‘My Work’ set of views to the category. If you don’t add these views, migrated users will not be able to see any views when they navigate to the ‘My work’ page.
10) Go to PWA->Server Settings->Operational policies->project workspace provisioning settings and choose ‘Automatically create a project workspace…” option. This is the more common option. If you don’t want workspaces to be created automatically, you need not do this.
Comments
Anonymous
June 15, 2006
That's great!Anonymous
June 15, 2006
I am glad you like it :)Anonymous
June 21, 2006
The comment has been removedAnonymous
June 22, 2006
May I...ummm...disagree? Resource leveling is a great function in Microsoft Office Project if you have learnt how to use it. Better would be critical chain, of course, but I do not expect this seriously.
OliverAnonymous
June 27, 2006
Segnalo un bel post ricco di indicazioni e trucchetti per migrare il DB di Project Server da un ambiente...Anonymous
June 28, 2006
Do you work with SQL 200 or 2005? What ist the best way to migrate Project Server with SQL and 2007?
I have a PS2003 on SQL and would like to migrate the database and the to the Beta2.
thanks SteffenAnonymous
June 29, 2006
I am actually having some problems installing the desktop version, it crashes at about 15% through the installation, does it every time, doesnt give me any idea of what has happened just says send info to MS, which I have done.
Any ideas, anyone else had the same problem?
FraserAnonymous
July 09, 2006
plz reply
immedeatlyAnonymous
July 26, 2006
Accidentaly deleted some resources from the Global Database. How to recover the resources? Using MS Porject 2003 Enterprise version. Thanks!Anonymous
December 07, 2006
What about migration from Project Server 2007 Beta2 TR to RTM version ?Anonymous
January 07, 2007
What about migration of sharepoint workspaces?Anonymous
January 09, 2007
The comment has been removedAnonymous
September 27, 2007
Hi, Is there any procedure/steps when migrating from Project Server 2007 to Project Server 2007.Anonymous
November 27, 2007
The comment has been removedAnonymous
March 18, 2008
I had problem how to migration Ms project 2007 from one database server to other database server. for the first installation, application, database reside on same machine server. how to migration database ms project to other server and aplication still in old server. thanks before RullyAnonymous
March 19, 2008
I have plan to migrate ms project sql server 2007 from one server to other server. please advice and give me scenario case how to do it thanksAnonymous
March 19, 2008
Hi there, Any suggestions for this error message: An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown. Additional exception information: SharePoint Products and Technologies cannot be configured. The current installation mode does not support SKU to SKU upgrades because there exists an older version of Windows SharePoint Services that must be upgraded first. Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException: Exception of type 'Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException' was thrown.Anonymous
June 03, 2008
PingBack from http://caleblocalnews.k2free.com/requiredfieldshavevalidvaluesmsproject2007.htmlAnonymous
June 30, 2008
Well i have trouble migrating PS 2003 to PS 2007 too ;/ When i run the P12 migration tool it tells me that the project has succesfully migrated but... when i open PWA or try to access the project from PP - the project list is empty ;/ Any ideas what might be worng ... ?Anonymous
August 24, 2008
To Bartek: Hi Bartek, make sure you are adding your projects to the save and publish section of the .ini file. It seems that you just saved them.Anonymous
October 15, 2008
The comment has been removedAnonymous
October 24, 2008
The comment has been removedAnonymous
October 31, 2008
hello all, i am getting the following error when trying to attach a SharePoint 2.0 content db to a windows sharepoint services 3.0. do you have an idea about what could be causing it? thx for all your help. have a nice weekend. command:
stsadm.exe -o addcontentdb -url http://usnapvm3devepm1:80 -databasename DevEPM_temp_310 -databaseserver usnapvm3devdb2 errors:
---------- C:PROGRAM FILESCOMMON FILESMICROSOFT SHAREDWEB SERVER EXTENSIONS12LOGSUPGRADE.LOG [SPWebTemplateSequence] [ERROR] [10/31/2008 11:41:57 PM]: Template PWS#0: SPSite Id=abaaba05-0a21-4a37-85a2-ff9fcb8d41af could not be accessed due to exception. Skipping this SPSite for template upgrade. Exception: System.IO.FileNotFoundException: The site with the id abaaba05-0a21-4a37-85a2-ff9fcb8d41af could not be found. [SPWebTemplateSequence] [ERROR] [10/31/2008 11:41:57 PM]: Template PWS#0: SPSite Id=abaaba05-0a21-4a37-85a2-ff9fcb8d41af could not be accessed due to exception. Skipping SPWeb Id=813b3054-9e3f-46be-9c47-333c0e777afc for template upgrade. Exception: System.IO.FileNotFoundException: The site with the id abaaba05-0a21-4a37-85a2-ff9fcb8d41af could not be found. [SPWebTemplateSequence] [ERROR] [10/31/2008 11:41:57 PM]: Template MPS#0: SPSite Id=abaaba05-0a21-4a37-85a2-ff9fcb8d41af could not be accessed due to exception. Skipping SPWeb Id=2b60587a-59a1-4b34-aaa6-12bc0cd7e030 for template upgrade. Exception: System.IO.FileNotFoundException: The site with the id abaaba05-0a21-4a37-85a2-ff9fcb8d41af could not be found. [SPWebTemplateSequence] [ERROR] [10/31/2008 11:41:57 PM]: Template MPS#0: SPSite Id=abaaba05-0a21-4a37-85a2-ff9fcb8d41af could not be accessed due to exception. Skipping SPWeb Id=88bd14cf-8bf1-4e8e-8c47-91af6e16bf45 for template upgrade. Exception: System.IO.FileNotFoundException: The site with the id abaaba05-0a21-4a37-85a2-ff9fcb8d41af could not be found. [SPWebTemplateSequence] [ERROR] [10/31/2008 11:41:57 PM]: Template MPS#0: SPSite Id=abaaba05-0a21-4a37-85a2-ff9fcb8d41af could not be accessed due to exception. Skipping SPWeb Id=8832366c-f5bf-487f-a200-986a100c9bf6 for template upgrade. Exception: System.IO.FileNotFoundException: The site with the id abaaba05-0a21-4a37-85a2-ff9fcb8d41af could not be found. [SPWebTemplateSequence] [ERROR] [10/31/2008 11:41:57 PM]: Template MPS#0: SPSite Id=abaaba05-0a21-4a37-85a2-ff9fcb8d41af could not be accessed due to exception. Skipping SPWeb Id=ac80a789-b21a-4690-b2cc-c2375f87db81 for template upgrade. Exception: System.IO.FileNotFoundException: The site with the id abaaba05-0a21-4a37-85a2-ff9fcb8d41af could not be found. [SPWebTemplateSequence] [ERROR] [10/31/2008 11:41:57 PM]: Template MPS#0: SPSite Id=abaaba05-0a21-4a37-85a2-ff9fcb8d41af could not be accessed due to exception. Skipping SPWeb Id=e9cc310c-792e-4c93-97a7-f1e3384cdeab for template upgrade. Exception: System.IO.FileNotFoundException: The site with the id abaaba05-0a21-4a37-85a2-ff9fcb8d41af could not be found. [SPManager] [INFO] [10/31/2008 11:41:57 PM]: Inplace Upgrade session finishes. root object = SPContentDatabase Name=epm_migration1_il Parent=SPDatabaseServiceInstance Name=INSTANCE1, recursive = True. 7 errors and 0 warnings encountered.
Anonymous
March 15, 2009
hi sir iAM ENGINEER need the programs thanksAnonymous
April 29, 2009
The comment has been removedAnonymous
June 09, 2009
I have migrated from PS 2007 to PS 2007 but facing problem in restoring project workspaces... How to restore... Reply..ASAP..Anonymous
August 13, 2009
The comment has been removedAnonymous
February 19, 2010
The comment has been removedAnonymous
March 21, 2010
i want to know how we can migrate database from sql to oracle.Anonymous
July 12, 2010
Don't get me wrong, but this is the easyest part of the migration... People don't use sharepoint in your company? If I have 3000 projects with project workspaces in sharepoint, evething working fine on Project Server 2003. What should I do with those 3000 project workspaces, with tasks, issues, risks... conected to the project tasks and everything? Do you have some step-by-step for this? Thank's