Upgrade project plan of 2003 to 2007

[Edward Wang]

We have an issue in upgrading the project plan of 2003 version to 2007.
In 2003 version, in order to make the whole plan consistent in our whole
company and capture the important data from each of the plan, we have defined
& customized some enterprise field and outline codes.
Similarly, in the upgrade, we also built the similar fields with the same
name ( tasks or project Entity).
But when I upgrade the plan of 2003 to 2007, I found the fields of 2003
could not be mapped to the fields of 2007. Usually there are two same name
fields showed in the plan, and one is empty--2007 field, and another one is
tagged. We have nearly 100 active project plans, which means we have to
manually copy and past the mandatory fields for each of plan.
Is there any automatic solution to address this issue?

 

[Dale Howard [MVP]]

Edward --

There is no automatic mapping of enterprise Project fields from a 2003
project to a 2007 project, as you have discovered. Worse still, when you
import the 2003 project into 2007, it "drags" the original 2003 field with
it and there is no way yet to get rid of it. This is a known and reported
bug in Project Server 2007. So, for those 100 projects, you will still need
to specify a value for each enterprise Project field for every project. On
the other hand, assuming you are using the Import Project Wizard, there is a
page where you can specifically map enterprise Task fields from 2003 to
2007. Hope this helps.

 

[James Fraser]

There is no automatic mapping of enterprise Project fields from a 2003
project to a 2007 project, as you have discovered. Worse still, when you
import the 2003 project into 2007, it "drags" the original 2003 field with
it and there is no way yet to get rid of it. ...

I wanted to add the exception that if the migration tool is used, the
2003 projects can be brought over to 2007 maintaining the enterprise
fields. The migration tool will first migrate the Enterprise Global
Template and then can migrate specified projects. Between the time of
migrating the EGT to completing the migration, changes should not be
made to the 2003 EGT or the 2007 custom fields, so that the
appropriate mappings work for all projects.

I understand this may be too late for Edward's situation, but for
everyone else's future reference.


James Fraser