locked
Migration from SPS2003 to MOSS 2007 RRS feed

  • Question

  • Hi All

    I am sorry if this question may have been answered earlier but I did some research and was not able to find any thing relevant on it here. I am doing a migration project from SharePoint 2003 to 2007. The client has 6-7 site collection and is running a 3 server farm (WFE, Index and Content DB). The content is mostly SPS 2003 OOB, I have not seen any custom code other than a few custom site definitions.

    My question here is which migration approach would be the best in this scenario; In-place, gradual or DB migration (I cant use any 3rd part tools). I have read most sites and blogs and they refere gradual migration. The client has its own UI and the content is mostly pages. 

    I am wondering as to what steps should I sequentially follow for migration be it any migration. Should I need to create a new farm for MOSS 2007 and add 3 farms? What would happen to the UI as ai believe SPS 2003 did not had master pages support. How would I be able to make sure the UI is exactly the same. The custom site definitions for SPS2003, how should I migrate that? Is there going to be any additional step for custom site def migration?

    Please elaborate and share your thoughts and experiences.

    Thanks in advance. 
    Monday, September 14, 2009 7:22 PM

Answers

  • You basically have 3 options for migration:

    1. Install SharePoint 2007 over the top of SharePoint 2003 (in-place)
    2. Install SharePoint 2007 along side SharePoint 2003 and migrate site by site over to 2007 (gradual)
    3. Install SharePoint 2007 on new hardware and migrate the content databases over (database migration)

    "In-place" is probably easiest, but you either have to stay on the existing hardware, or migrate the 2003 environment to new hardware BEFORE you do the upgrade. Same story for "gradual" really. Generally, if someone wants to move to new hardware, I usually recommend the "database migration" approach. The downside of "database migration" is that it will likely change the URLs of your sites automatically. I wrote a tool you can use to map the old URLs to the new URLs, but it will add some work. You can get the tool here: http://rdacollaboration.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=28073

    If your OK sticking with the same hardware, it sounds like you might want to go ahead with the "in-place" upgrade. With only 6-7 site collections, "gradual" will probably be more headache than its worth. However, before you do anything though, run a "pre-scan" against the 2003 enviroment. The logs will tell you if you have any incompatible web parts, customized pages, etc... Here's info on that: http://technet.microsoft.com/en-us/library/cc262231.aspx. Finding issues in the pre-scan is the only reason I usually see to go with "gradual". That would allow you to migrate all the plain sites, while you correct or code for the special case sites and migrate them when you're ready.

    In-place instructions are here: http://technet.microsoft.com/en-us/library/cc288753.aspx. Backup your existing databases before you do anything. The UI peices should upgrade seamlessly if you stuck with out of the box UI in 2003. If the UI was customized heavily in 2003, you might have to reapply those changes once over to 2007. I highly recommend doing a test run of the upgrade on another environment (if possible) to help expose any unforseen issues. Be prepared for some post-deployment-cleanup as well. I've never had a migration that didn't have at least one weird issue afterwards (content locked out, meta-data not mapping up to documents, etc...), but it's usually fairly minor.

    You can always contact an MS Partner if you feel like you're getting in over your head.
    Good luck!


    Jason Barron
    Blog: http://rdacollab.blogspot.com/
    CodePlex: http://rdacollaboration.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=28073
    • Marked as answer by MossNovice Thursday, September 17, 2009 8:20 PM
    Tuesday, September 15, 2009 5:20 AM

All replies

  • You basically have 3 options for migration:

    1. Install SharePoint 2007 over the top of SharePoint 2003 (in-place)
    2. Install SharePoint 2007 along side SharePoint 2003 and migrate site by site over to 2007 (gradual)
    3. Install SharePoint 2007 on new hardware and migrate the content databases over (database migration)

    "In-place" is probably easiest, but you either have to stay on the existing hardware, or migrate the 2003 environment to new hardware BEFORE you do the upgrade. Same story for "gradual" really. Generally, if someone wants to move to new hardware, I usually recommend the "database migration" approach. The downside of "database migration" is that it will likely change the URLs of your sites automatically. I wrote a tool you can use to map the old URLs to the new URLs, but it will add some work. You can get the tool here: http://rdacollaboration.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=28073

    If your OK sticking with the same hardware, it sounds like you might want to go ahead with the "in-place" upgrade. With only 6-7 site collections, "gradual" will probably be more headache than its worth. However, before you do anything though, run a "pre-scan" against the 2003 enviroment. The logs will tell you if you have any incompatible web parts, customized pages, etc... Here's info on that: http://technet.microsoft.com/en-us/library/cc262231.aspx. Finding issues in the pre-scan is the only reason I usually see to go with "gradual". That would allow you to migrate all the plain sites, while you correct or code for the special case sites and migrate them when you're ready.

    In-place instructions are here: http://technet.microsoft.com/en-us/library/cc288753.aspx. Backup your existing databases before you do anything. The UI peices should upgrade seamlessly if you stuck with out of the box UI in 2003. If the UI was customized heavily in 2003, you might have to reapply those changes once over to 2007. I highly recommend doing a test run of the upgrade on another environment (if possible) to help expose any unforseen issues. Be prepared for some post-deployment-cleanup as well. I've never had a migration that didn't have at least one weird issue afterwards (content locked out, meta-data not mapping up to documents, etc...), but it's usually fairly minor.

    You can always contact an MS Partner if you feel like you're getting in over your head.
    Good luck!


    Jason Barron
    Blog: http://rdacollab.blogspot.com/
    CodePlex: http://rdacollaboration.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=28073
    • Marked as answer by MossNovice Thursday, September 17, 2009 8:20 PM
    Tuesday, September 15, 2009 5:20 AM
  • Hi Jason,

    Thanks for your detailed reply. How about custom site definition? Do you think all the sites that were created with custom site definition would need to be recreated with a new custom site definition? What would happen to the pages/data that was created on the new custom site definition? Is that going to be re-created?



    Tuesday, September 15, 2009 2:23 PM
  • If your talking about true site "definitions" (XML files in the 60 hive), then you will need to develop those same definitions in 2007 AND provide an update map that SharePoint will use to convert the old sites (with the old definition) to new sites (with the new definition). For custom "page tempates" in 2003, you'll need additional mapping files to convert those to "page layouts" in 2007. If you do this correctly, the content should come over intact. (Another reason why a test run - or 2 is helpful).

    Information on this process can be found here: http://technet.microsoft.com/en-us/library/cc263404.aspx

    However, if you're talking about upgrading "templates" (.stp files), then those should migrate without any issue. This is because, underneath the scenes, they are based on existing out-of-the-box site definitions - which are already supported in the 2003 to 2007 upgrade.

    Thanks
    Jason Barron
    Blog: http://rdacollab.blogspot.com/
    CodePlex: http://rdacollaboration.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=28073
    • Proposed as answer by AseemN Thursday, September 17, 2009 8:03 PM
    Wednesday, September 16, 2009 2:21 AM
  • Thanks for your answers Jason. Appreciate your help.
    Thursday, September 17, 2009 7:45 PM