migrate 2003 to 2007

[Ponch]

Hello,

I want to migrate my project server 2003 projects to my new project 2007
server.
Project 2007 is not on te same server as project 2003.
Wich way do i have to follow?

Tx,

 

[Ben Howard]

Hi Ponch,
Use the following guide from Microsoft.

http://technet2.microsoft.com/Offic...7193-4ed3-93bd-6685f0d82db11033.mspx?mfr=true

 

[James Fraser]

Hello,

I want to migrate my project server 2003 projects to my new project 2007
server.
Project 2007 is not on te same server as project 2003.
Wich way do i have to follow?

Tx,

The documentation from Microsoft is a good starting place:
http://technet2.microsoft.com/Offic...3881-47b3-ba5f-29adf893286d1033.mspx?mfr=true

This is not a simple procedure, and you should plan on doing at least
one test migration (preferably a few) before attempting to migrate the
production data. There are many approaches you can take for the timing
of the migration, but generally, a weekend, all-at-once migration will
cause the fewest headaches in the long run. Otherwise, you need to
keep the custom field definitions entirely static on both servers for
the duration of the migration, and also have to coordinate more
tightly with users regarding which projects are on which servers.


James Fraser

 

[Bill Busby]

The migration is actually pretty straightforward but much of what will impact
you is not documented. Mostly because MS can predict every detail of how you
may configure 2003. Some of the lessons we learned are...

1. Do many migrations, always testing the end result to identify weaknesses
and change your migration approach. The devil is in the details and how you
set up 2003 is going to determine which changes you need to make. We wound up
with a 50+ step migration plan to supplement the MS docs.
2. Actual work in 2003 is the only number that matters. AWP goes away in
2007 (but there's still a command 'Sync to Protected Actuals - anyone know
why this is?)
3. The migrated plans can often have hugely different numbers compared to
your 2003 project plans. We migrated 598 project plans and approx 23% of them
had actual work in 2007 that appeared to have no relation to the actual work
values in 2003. We had to do a lot of manual changes to migrated plans to
bring them in sync
4. There is a known bug that you cannot remove enterprise outline codes
from 2003 so they will come over into your 2007 plans, like it or not. If you
do a 'Save and Publish' as part of your migration the fields will be added as
enterprise custom fields in 2007 and the reporting database will inherit
these fields. In our case we were changing our code fields to improve
reporting. If you remove all enterprise fields from 2003 before migrating the
plans it will not create the enterprise custom fields in 2007 and if you do a
'Save' migration (with no publish) your reporting database will only inherit
the custome fields you define in 2007.

Probably not clear on much of the above, we did the migration at least a
dozen times and learned something new everytime.