Migrate Projects from one enviornment to another

T

Todd

Hi,

I am in a situation where I need to migrate projects (and their
associated issues/risks/docs) from one existing project server
enviornment to another project server environment.

In the past, I have successfully migrated one environment to another,
essentially to take advantage of a new database (using the following
link, which was very helpful):

http://support.microsoft.com/default.aspx?scid=kb;en-us;905386

But in this case, I need to somehow migrate only the projects and their
associated information, as the destination database already contains
live projects that can't be overwritten. So the option of backing up
and restoring the database is not an option.

Everything is telling me that this can't be done. That I'll need to
import each project individually and then re-create each risk/issue/doc
in the new environment. But I was just wondering if anyone has run
into this before and what they may have done.

Is there an easy way of getting the sharepoint sites over to the new
environment at least?

Any comments would be helpful. Thanks!!
 
C

Charlie Holmes

To move the projects:
Save each as an MPP file, and then import them into the enterprise on
the new server. (Don't just "open" and "save" to the server... this
will create problems with your views.) You'll probably need to
redefine special outline codes or fields if they are different between
the two servers, and you'll need to replace your resources (from the
old environment) with the enterprise resources from the new
environment.

To move the WSS sites:
Use the STSADM tool to back them up from the old server, and then use
it to restore them to the new server. This will only create the sites;
it won't link them to your "Project" projects. To do that, you'll have
to use the PWA admin page to re-link each project to its proper
workspace. There's a great Microsoft resource at the following URL
that should familiarize you with the STSADM tool:
http://www.microsoft.com/technet/prodtechnol/sppt/reskit/c2861881x.mspx

It's theoretically possible to automate this process, but I wouldn't
recommend it unless you have a large enough number of projects that it
would take you more than a few hours to follow the steps above.

Also, this goes without saying, but make backups of everything. I've
followed each process above to move projects around and to move project
workspaces around, but the whole process is fairly error-prone. The
software is robust enough that you won't "crash" your destination
server by performing any of these tasks, but a good rule to follow
would be not to delete anything from the "source" environment until you
are absolutely certain that you have duplicated it perfectly in the
"destination" environment.

Best of Luck,
Charlie Holmes
RGA
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top