Migrate a solution Sharepoint 2007 --> 2010 RRS feed

  • Question

  • Hi,

    I am very new to the Sharepoint area. So, please excuse some stupid questions.
    I have a SharePoint 2007 solution with several master pages and a lot of functionality (ascx etc).
    I should migrate this solution from SharePoint 2007 to 2010 but I dont know exactly how to do that. ... and how to start ...
    I found a howto about changing master pages and upload it to a new sharepoint etc. Is it possible to migrate WebParts and other custom code? How can I check this?
    I know it is very difficult to help me because I cant offer a precise case but perhaps you could post some links etc to push me into the right way...

    Friday, April 15, 2011 4:25 PM


All replies

  • Stefan-

    You are right - migrating from SharePoint 2007 to 2010 is a complex endeavor.  Moving content can be easy following the following methodologies:

    • Build the new farm using SharePoint 2010
    • Create the new WEB apps and Site Collections that you need to move
    • Detach the content databases
    • Put the old content DB in "Read Only" mode
    • Backup the content DB's from the old SQL on the new SQL server
    • Using powershell, attach the content DB on the new SharePoint server to the SharePoint farm
    • When the attach and upgrade is complete - take the content DB OUT of read-onl;y  mode

    At this point, you content is moved.  Once the content is moved, you can attempt to view the site.  The site will initially be in "comparability" mode, meaning it will not have the visual update applied. 

    Now you need to move your ASPX pages and code.  Now your work is going to making sure that your ASPX and code to make sure that they work. If not -systematically start fixing these assets and applying them to the farm.  Once you are able to get your 2007 farm working correctly in 2010 then you are ready for a final pass of moving your content.

    Move your content one last time if users have modified it in the 2007 farm over to 2010 and change your DNS records.

    As you have stated and I affirm - There's nothing easy about this.  Keep doing your homework until you are ready to start the work.

    Jeff DeVerter, MCSE



    Jeff DeVerter
    • Proposed as answer by MrMcBobIT Friday, April 15, 2011 6:22 PM
    Friday, April 15, 2011 6:01 PM
  • Jeff,

    I had a brief follow up question to one of your steps.

    "Create the new WEB apps and Site Collections that you need to move"

    When you create a new Web App won't that create a new content DB for that Web App on the new SQL server?  Do you simply detach that, delete, and attach the old 2007 content DB?


    Friday, April 15, 2011 6:22 PM
  • Jeff,

    thanks for describing this way.
    But I dont want to move the complete Server - I want to move one solution.

    This solution is working well and should not be changed. But a "copy" of it should be used on Sharepoint 2010 in a second department. So, can I migrate the original code code itself and deploy this to the Sharepoint 2010?


    Monday, April 18, 2011 11:06 AM
  • Hi, 

    Solution means .wsp solution package ? or any other custom code aspx pages residing in 12 hive folder ?

    1. Backup the Solution from MOSS 2007 site and added in Sharepoint 2010 Solution management

    2. Deploy the solution and activate the feature in 2010 site.

    3. Then test the solution .


    refer ,

    If it is custom code development refer this link for deployment,




    Monday, April 18, 2011 11:49 AM