locked
Migrating Custom Solutions from SharePoint 2010 to SharePoint 2013 RRS feed

  • Question

  • Hi,

    We are doing a migration from SharePoint 2010 to SharePoint 2013 and we are interested in migrating our custom solutions especially master pages and page layouts.

    We have followed the steps as mentioned in TechNet for the database attach upgrade process. After doing database attach and running visual upgrade our sites work fine only if the custom solutions are deployed to 14 hive. If we have the solution deployed to 15 hive and not in 14 hive we get a File not found error for master pages and page layouts.

    We can see all the files listed in the gallery but trying to open them or trying to download a copy throws File not found. This works fine if we have our custom solution deployed to 14 hive but not when it is in 15 hive.

    Any guess as to how we can update our old master page and page layouts to be read from 15 hive and not from 14 hive.

    We need to keep our customizations in 15 hive so that we can easily add new features post migration and make full use of the new 2013 capabilities post migration.


    Rajesh Kumar "Changing the Face" can change nothing.But "Facing the Change" can change everything.

    Tuesday, April 16, 2013 6:54 AM

Answers

All replies

  • Our process for the SharePoint 2010 to SharePoint 2013 migration went something like this:

    1. Install custom solutions on the new SharePoint 2013 farm using Install-SPSolution PowerShell command and the new CompatibilityLevel switch. We installed to both 14 and 15: http://technet.microsoft.com/en-us/library/ff607534.aspx
    2. Mount the content databases to upgrade them: http://technet.microsoft.com/en-us/library/ff607581.asp
    3. Upgrade the various site collections to version 15 using Upgrade-SPSite: http://technet.microsoft.com/en-us/library/jj219599.aspx

    Note that after step 2 and before step 3, your site collection will be using the files from the 14 hive. After step 3 your files will be using the files from the 15 hive.


    Doug Hemminger http://www.sharepointdoug.com

    • Marked as answer by Qiao Wei Sunday, April 28, 2013 8:28 AM
    Tuesday, April 16, 2013 12:13 PM
  • I am able to upgrade each visual webpart which created in earlier version.but we are interested in migrating our custom solutions especially master pages and page layouts.I also able to upgrade master page successfully with VS2012 but when open site it looks something weird not reflected every thing what we have in earlier version.

    Rajesh Kumar "Changing the Face" can change nothing.But "Facing the Change" can change everything.

    Tuesday, April 16, 2013 12:57 PM
  • Depending on your customizations, there will likely be a lot of changes you will have to make to get the master pages to work how you would like on V15. There were significant changes to the CSS and the html. You should be able to deploy your master pages as is to the V14 hive and not upgrade your sites to keep the look and feel the same as how you had it in SP 2010.

    Doug Hemminger http://www.sharepointdoug.com

    Tuesday, April 16, 2013 1:41 PM
  • Hello Doug,

    Do you have idea about creating a custom master page in SharePoint 2013 using Visual Studio 2012.


    Rajesh Kumar "Changing the Face" can change nothing.But "Facing the Change" can change everything.

    Wednesday, April 17, 2013 5:40 AM
  • Rajesh,

    The approach of building custom master page in SharePoint 2013 using Visual Studio 2012 is similar to SP 2010 using VS 2010.

    http://www.sharepointchick.com/archive/2010/03/26/deploying-a-custom-master-page-in-sharepoint-2010.aspx

    But you can use the new Design manager feature in SP 2013 to build the master pages.

    http://msdn.microsoft.com/en-in/library/jj822363.aspx


    MCTS,MCPD Sharepoint 2010. My Blog- http://www.sharepoint-journey.com
    If a post answers your question, please click "Mark As Answer" on that post and "Vote as Helpful

    • Marked as answer by Qiao Wei Sunday, April 28, 2013 8:28 AM
    Thursday, April 18, 2013 4:53 AM