none
Migrating from EPM 2003 to EPM 2010 RRS feed

  • Question

  • Hi guys, we are planning to upgrade to Microsoft Project server 2010 from Microsoft Project server 2003. We have gone thru the references on how to migrate the data using VME.

    The thing is we do not want to migrate the data in one go. We want the data to be migrated project by project i.e. one project at a time.

    Has any one migrated the data in the manner  explained above.

    We are also looking for any other options apart from above and one go migration process.

    Any Ideas would be helpful....

    Monday, March 21, 2011 8:06 AM

Answers

  • Ok.

    In your case, if feasible to me - i would prefer to upgrade and move only the data from PS 2003 to PS 2007. Because this step during the migration of PS2003 to PS2010 is only to upgrade the data.

    And once the validation of the data is done, i would then move any custom solution to PS2010 direclty and then publish 1 or 2 projects to see if my custom solution is working ok. Later can move 4DB set to PS2010, this would skip one unnecessary step in your case. 

    Also see this article and download the guide to help you better understand the migration to PS2003.

    http://technet.microsoft.com/en-us/library/cc197505%28office.12%29.aspx

    Hope this helps.


    | Khurram Jamshed | Follow my blog about Enterprise Project Management Solution | http://khurramjamshed.blogspot.com |
    Monday, March 21, 2011 10:45 AM

All replies

  • Hi,

    i am quite curious to know why you want to do it one by one? because it would be a long process this way depends upon the number of project you have.

    but in this case, you can save the project in your local machine, and upload them one by one to your PWA 2010 instace through Project Professional - you dont have to worry about the project sites and project custom information in this case though, because when you will do it one by one the system will treat them as a new project and will create a project site.

    Let me know if this helps you.


    | Khurram Jamshed | Follow my blog about Enterprise Project Management Solution | http://khurramjamshed.blogspot.com |
    Monday, March 21, 2011 8:25 AM
  • The reason being we have done some customization over the EPM 2003 to suit our requirements. Hence, we wanted to test with alteast 2 or 3 projects initially, with each users entering the timesheet details on both the EPM's. That will gave us a firm tested solution.
    Monday, March 21, 2011 9:37 AM
  • Ok.

    In your case, if feasible to me - i would prefer to upgrade and move only the data from PS 2003 to PS 2007. Because this step during the migration of PS2003 to PS2010 is only to upgrade the data.

    And once the validation of the data is done, i would then move any custom solution to PS2010 direclty and then publish 1 or 2 projects to see if my custom solution is working ok. Later can move 4DB set to PS2010, this would skip one unnecessary step in your case. 

    Also see this article and download the guide to help you better understand the migration to PS2003.

    http://technet.microsoft.com/en-us/library/cc197505%28office.12%29.aspx

    Hope this helps.


    | Khurram Jamshed | Follow my blog about Enterprise Project Management Solution | http://khurramjamshed.blogspot.com |
    Monday, March 21, 2011 10:45 AM
  • Hi,

    Its an acceptable solution and it was in our mind as well.

    Again, the problem is we have to first test our customization on existing data with one project on EPM 2010.

    Is there any SQL script available that will allow us to migrate data of one project (including the resources, customized fields etc...) from EPM 2007 to EPM 2010.

    Also, can you provide me with some case study who have done the migration of EPM 2003 to EPM 2010.

    Thanks


    Tuesday, March 22, 2011 2:49 AM
  • Hi,

    Ok based on this, let me summarize the steps for you which you can follow to migrate and test your custom solution.

    1. after done with the data migration from PS 2003 to PS 2007, provision the PWA2010  instance using these 4 upgraded dbs. (this will move all your projects/custom fields/resources etc. to PS2010, and wont harm your testing)

    2. move your custom solution to the PS2010

    3. create a test project plan and publish it to the PS 2010 server

    4. validate if the custom solution are working OK

     

    this cannot be achieved using SQL script,

    Hope this helps.


    | Khurram Jamshed | Follow my blog about Enterprise Project Management Solution | http://khurramjamshed.blogspot.com |
    Tuesday, March 22, 2011 5:31 AM