Migrating from Project Server 03 to 07

[Rob]

I have an enviroment running SQL 2000 with Project Server 2003 and the powers
at be would like to implement Project Server 2007.
My question is this:

We have 25 projects and about 55 resources loaded into 2003.
We do not use timesheets and only have a few high level project type custom
fields being [8] used. Would it not be easier to setup the 2007 instance and
then add the custom fields and then bring in the projects and resources to
the 07 enviroment. I read the migration guide and it seems to be a little
overwhelming for the enviroment we have?



Jennings

 

[Optimum Orgs]

Rob,

Be careful. We just completed the same migration without using the
migration tool, and MOPS 2007 gets VERY confused about the custom outline
codes, duplicating the 2003 AND 2007 codes in the new projects. We finally
got around it by copying the TASKS from the 2003 projects and pasting them
into new 2007 projects (which lost all of the custom fields) - then manaully
copying the custom fields value (by carefully lining up the columns) and
pasting them into the new custom fields. It was tricky and error-prone, and
I'm still not convinced everything is fine.

One thing you should NOT do is open a 2003 project and publish it in 2007.
IT causes all kinds of issues in the 2007 plan.

p.s.
We were pre-SP1 when we did this and I don't know if it's better in SP1.

 

[Rob]

I see well that is good information to have. So copying and pasting might be
the way to go rather then opening and saving as an 07 file? We are planning

Rob,

Be careful. We just completed the same migration without using the
migration tool, and MOPS 2007 gets VERY confused about the custom outline
codes, duplicating the 2003 AND 2007 codes in the new projects. We finally
got around it by copying the TASKS from the 2003 projects and pasting them
into new 2007 projects (which lost all of the custom fields) - then manaully
copying the custom fields value (by carefully lining up the columns) and
pasting them into the new custom fields. It was tricky and error-prone, and
I'm still not convinced everything is fine.

One thing you should NOT do is open a 2003 project and publish it in 2007.
IT causes all kinds of issues in the 2007 plan.

p.s.
We were pre-SP1 when we did this and I don't know if it's better in SP1.

I have an enviroment running SQL 2000 with Project Server 2003 and the powers
at be would like to implement Project Server 2007.
My question is this:

We have 25 projects and about 55 resources loaded into 2003.
We do not use timesheets and only have a few high level project type custom
fields being [8] used. Would it not be easier to setup the 2007 instance and
then add the custom fields and then bring in the projects and resources to
the 07 enviroment. I read the migration guide and it seems to be a little
overwhelming for the enviroment we have?



Jennings

 

[Mike Mahoney]

I see well that is good information to have. So copying and pasting might be
the way to go rather then opening and saving as an 07 file? We are planning

Rob,

Be careful.  We just completed the same migration without using the
migration tool, and MOPS 2007 gets VERY confused about the custom outline
codes, duplicating the 2003 AND 2007 codes in the new projects.  We finally
got around it by copying the TASKS from the 2003 projects and pasting them
into new 2007 projects (which lost all of the custom fields) - then manaully
copying the custom fields value (by carefully lining up the columns) and
pasting them into the new custom fields.  It was tricky and error-prone, and
I'm still not convinced everything is fine.

One thing you should NOT do is open a 2003 project and publish it in 2007.  
IT causes all kinds of issues in the 2007 plan.

p.s.
We were pre-SP1 when we did this and I don't know if it's better in SP1.

I have an enviroment running SQL 2000 with Project Server 2003 and thepowers
at be would like to implement Project Server 2007.
My question is this:
We have 25 projects and about 55 resources loaded into 2003.
We do not use timesheets and only have a few high level project type custom
fields being [8] used. Would it not be easier to setup the 2007 instance and
then add the custom fields and then bring in the projects and resources to
the 07 enviroment. I read the migration guide and it seems to be a little
overwhelming for the enviroment we have?
Jennings- Hide quoted text -

- Show quoted text -

Rob

SP1 improves the issues around moving plans from 1 epm configuration
to another. In your environment an easy approach is to save plans
offline and use import wizard to load into new environment. You will
initially see old configured fields which will not migrate. These
disappear on reopening the enterprise plan. If you use Save As
approach you can display the old enterprise task custom values in a
column and I see no reason why you cannot paste these into the new
enterprise configured field.

regards

Mike

 

[Rob]

Thxs for the response Mike.
I agree install SP1 before uploading any projects to 07.
Doing the Save As I notice that all the Custom Fields from 03 show up with
the values. If I have already put these in the Server 07 will it duplicate or
simply update?

I see well that is good information to have. So copying and pasting might be
the way to go rather then opening and saving as an 07 file? We are planning

Rob,

Be careful. We just completed the same migration without using the
migration tool, and MOPS 2007 gets VERY confused about the custom outline
codes, duplicating the 2003 AND 2007 codes in the new projects. We finally
got around it by copying the TASKS from the 2003 projects and pasting them
into new 2007 projects (which lost all of the custom fields) - then manaully
copying the custom fields value (by carefully lining up the columns) and
pasting them into the new custom fields. It was tricky and error-prone, and
I'm still not convinced everything is fine.

One thing you should NOT do is open a 2003 project and publish it in 2007.
IT causes all kinds of issues in the 2007 plan.

p.s.
We were pre-SP1 when we did this and I don't know if it's better in SP1.

"Rob" wrote:

I have an enviroment running SQL 2000 with Project Server 2003 and the powers
at be would like to implement Project Server 2007.
My question is this:

We have 25 projects and about 55 resources loaded into 2003.
We do not use timesheets and only have a few high level project type custom
fields being [8] used. Would it not be easier to setup the 2007 instance and
then add the custom fields and then bring in the projects and resources to
the 07 enviroment. I read the migration guide and it seems to be a little
overwhelming for the enviroment we have?

Jennings- Hide quoted text -

- Show quoted text -

Rob

SP1 improves the issues around moving plans from 1 epm configuration
to another. In your environment an easy approach is to save plans
offline and use import wizard to load into new environment. You will
initially see old configured fields which will not migrate. These
disappear on reopening the enterprise plan. If you use Save As
approach you can display the old enterprise task custom values in a
column and I see no reason why you cannot paste these into the new
enterprise configured field.

regards

Mike

 

[Mike Mahoney]

Thxs for the response Mike.
I agree install SP1 before uploading any projects to 07.
Doing the Save As I notice that all the Custom Fields from 03 show up with
the values. If I have already put these in the Server 07 will it duplicateor
simply update?

I see well that is good information to have. So copying and pasting might be
the way to go rather then opening and saving as an 07 file? We are planning
on doing the Custom fields separtly, but I see your point. Thxs for the heads
up Optimum
:
Rob,
Be careful.  We just completed the same migration without using the
migration tool, and MOPS 2007 gets VERY confused about the custom outline
codes, duplicating the 2003 AND 2007 codes in the new projects.  We finally
got around it by copying the TASKS from the 2003 projects and pasting them
into new 2007 projects (which lost all of the custom fields) - then manaully
copying the custom fields value (by carefully lining up the columns)and
pasting them into the new custom fields.  It was tricky and error-prone, and
I'm still not convinced everything is fine.
One thing you should NOT do is open a 2003 project and publish it in2007.  
IT causes all kinds of issues in the 2007 plan.
p.s.
We were pre-SP1 when we did this and I don't know if it's better in SP1.
:
I have an enviroment running SQL 2000 with Project Server 2003 andthe powers
at be would like to implement Project Server 2007.
My question is this:
We have 25 projects and about 55 resources loaded into 2003.
We do not use timesheets and only have a few high level project type custom
fields being [8] used. Would it not be easier to setup the 2007 instance and
then add the custom fields and then bring in the projects and resources to
the 07 enviroment. I read the migration guide and it seems to be alittle
overwhelming for the enviroment we have?
Jennings- Hide quoted text -
- Show quoted text -

Rob

SP1 improves the issues around moving plans from 1 epm configuration
to another.  In your environment an easy approach is to save plans
offline and use import wizard to load into new environment.  You will
initially see old configured fields which will not migrate.  These
disappear on reopening the enterprise plan.  If you use Save As
approach you can display the old enterprise task custom values in a
column and I see no reason why you cannot paste these into the new
enterprise configured field.

regards

Mike- Hide quoted text -

- Show quoted text -

Rob

The old values are only visible when transitioning from mpp to
enterprise. When you reopen the enterprise plan you no longer see the
old fields (though it would not suprise me if they are still in the
project plan). Clearly you need to update your current enterprise
fields. Where these are task level values, during the save as process
you can expose the old custom field alongside the new custom field and
copy/paste if definitions are consistent.

Mike