Sharepoint Migration from SPS 2003 to MOSS 2007 RRS feed

  • Question

  • Hi

    I need some advice on what options I have on moving site content between two different Sharepoint Environments. Basically Company A has aquired Company B, Company A has a MOSS 2007 environment and Company B has SPS 2003 with nearly 3000 sites. Company B has to shutdown their SPS 2003 environment.

    So I need to move the 3000 sites and content to the MOSS 2007 environment.. What options do I have.. One option I believe is available to me is to create new sites in MOSS and then copy the content manually via Windows Explorer. (But what do I lose by doing this ?)

    I've read about stsadm.exe is this something that can be used between environments ?

    All advice, links Welcome.







    • Moved by Mike Walsh FIN Friday, September 16, 2011 10:42 AM admin q (From:SharePoint - Collaboration (pre-SharePoint 2010))
    Friday, September 16, 2011 10:31 AM

All replies

  • Hi

    Refer the following TechNet white paper explaing on how to upgrade the Upgrading Large Microsoft Office SharePoint Portal Server 2003 Intranet Portals to Microsoft Office SharePoint Server 2007.



    Also refer the following MSDN URL briefing on Upgrading SharePoint Portal Server 2003 Customizations to SharePoint Server 2007






    • Marked as answer by Wayne Fan Saturday, September 24, 2011 6:25 AM
    • Unmarked as answer by Steven AndrewsEditor Thursday, November 10, 2011 12:47 PM
    Saturday, September 17, 2011 6:56 AM
  • Thanks, these doc refer to either an upgrade or migration.. I have two separate environments, so an upgrade or migration is out of the question.

    I need to manually copy contents from SPS 2003 to MOSS.


    Thursday, November 10, 2011 11:02 AM
  • Manually copying them would be daft, not only is is a HUGE man effort (excluding any analysis, testing, communication and so on) you'll also lose any audit trails that you might have a legal obligation to keep.

    Can you give us some more information on the type or volume of content and how it's structured.

    Steven Andrews | SharePoint Professional | http://www.twitter.com/backpackerd00d | https://baron72.wordpress.com/
    Thursday, November 10, 2011 2:03 PM
  • I know this is MAD, but this is the preferred method being discussed by people within... Due to lack of budget.. I don't like this idea one little bit..

    I want to provide a better solution to the business, so any ideas...

    How's about in place upgrade on SPS to MOSS, then backup database and restore to Company A MOSS environment.. Would that work..


    Tuesday, November 22, 2011 2:38 PM
  • Any solution is better than one guy manually copying loads of files.  I've got two thoughts here: -

    1. You say there's no budget, so make the cost of a migration tool less expensive than the alternatives.  The cost of one tool is typically several £k but put that in comparison to the cost of you being taken out of projects, your time if you have to works evenings or weekends to get this done.  Also consider the compliance and auditing that mergers and acquisitions typically have.  Moving documetns manually will typically delete any/all audit trails that your company will have to provide externally.  If any/all of these cost more than one of the migration tools out there, I'd argue that case
    2. IF you can't avoid doing it manually, I'd forget about an inplace upgrade on the 2003 kit as you'll lose it if the upgrade fails.  Have you got access to virtual software? If so, build a virtual 2003 set-up, clone it and then copy your database into this.  Perform the upgrade (lots of literature already exists for this) and then move that into 2007.


    Steven Andrews | SharePoint Professional | http://www.twitter.com/backpackerd00d | https://baron72.wordpress.com/
    Tuesday, November 22, 2011 4:28 PM