We have a farm running a Sharepoint 2007 implementantion that is filled with data, including running workflows. We have a new version of the sharepoint 2007 site, deployed in a new server farm, and we have to migrate the data between them.

What options would we have for the migration in scenario 1) they are compatible; and in scenario 2) they are not compatible, meaning there are differences in content types, ...?

Any ideas are highly appreciated. Regards

  • What type of "stuff" are you looking to migrate? Content (documents/list items)? Site collections? Lists?
    – Kit Menke
    Feb 21, 2011 at 14:54
  • Several sites (team sites), under the same site collection, and a list that contains a field referencing those team sites. I see we can export a site using the stsadm command, but I'm a bit unsure to what will happen in terms of dependencies the list has, links to docs that may brake, ...
    – user2414
    Feb 21, 2011 at 16:10

4 Answers 4


I will recommend you read this Technet article on moving content databases from one farm to another.

How tricky it will be depends on several things, for example if your SQL server uses aliases or not.

  • I don't want to move the complete content database, otherwise I'll move more things than I want. I really just want a specific list and a bunch of team sites that are referenced by that list...
    – user2414
    Feb 21, 2011 at 16:12
  • Metalogix got a nice tool for doing scheduled migrations from one web app to another (site migration manager i think its called). Its not free, but not terribly expensive either. This might be something you can use? Feb 21, 2011 at 20:36

Check out Gary Lapointe's custom STSADM commands: http://blog.falchionconsulting.com/index.php/stsadmpowershell-commands/

I had very good luck moving a large list using the gl-export list command.


Backup the entire old moss farm sharepoint site collection and restore the new farm sharepoint site collection. if we do backup and restore site collection, the workflow also moved.

Backup stsadm.exe -o backup -url -filename

Restore: stsadm.exe -o restore -url -filename -overwrite

Thanks Ramu


I'd recommend you look at Chris O'Brien's Content Deployment Wizard

This uses the Content Deployment API so has similar options and benefits/drawbacks to using Content Deployment in CA but allows for far more granular data transfer (down to specific file level).

The one thing you may find is a sticking point though is to my knowledge it won't transfer workflows. However I don't think you will be able to do this without restoring the entire content database.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.