SharePoint site template Migration RRS feed

  • Question

  • Hi,

    I'm currently designing a migration strategy for a client. All sites of a web application are based on a custom SPWebTemplate.

    Out partner, redevelop the SPWebTemplate with the same Feature GUID and name for v15: I can create a new site based on the new template with the SharePoint 2013 look.

    When I try to mount SP Content databases on SharePoint target farm (2013), I have error messages because SharePoint can't find the old (v14) template. And, I can't do a visual upgrade on the sharepoint site collection also...

    Futhermore, I can't add the old (V14) wsp because it has the same GUID... Does anybody can help me with the methodology to migrate SharePoint sites based on a custom Web Template please?

    Kind regards



    Wednesday, January 4, 2017 10:35 PM

All replies

  • Basically I'm facing this issue:

    But I don't wan't to do the copy XML files trick

    Wednesday, January 4, 2017 10:41 PM
  • Hi,

    Please check the steps below:

    • Open Visual Studio and create a New Project
    • In the list of available templates select SharePoint 2013 – Import Solution Package. Click OK.
    • Make sure the project name is same as the 2010 WSP file name so it is easy to reference it later during the upgrade
    • In the next section choose one of the WSP files exported from 2010 environment
    • In Solution Explorer, find the Onet.xml file in your project and open it
    • In SharePoint 2013 custom master page references are set to the default master page named seattle.master. If the default master page in SharePoint 2010 is customized, change the reference to that custom page in Onet.xml
    • If you review one of the existing site templates you’ll notice there are certain set of Features included in the template. Optionally you can make sure the following set of Features are included in the WebFeatures section

      Feature Name Feature ID
      AccSvcAddAccessApp d2b9ec23-526b-42c5-87b6-852bd83e0364
      AnnouncementsList 00bfea71-d1ce-42de-9c63-a44004ce0104
      BaseWeb 99fe402e-89a0-45aa-9163-85342e865dc8
      BizAppsListTemplates 065c78be-5231-477e-a972-14177cc5b3c7
      ContactsList 00bfea71-7e6d-4186-9ba8-c047ac750105
      ContactsList 00bfea71-7e6d-4186-9ba8-c047ac750105
      CustomList 00bfea71-de22-43b2-a848-c05709900100
      DataConnectionLibrary 00bfea71-dbd7-4f72-b8cb-da7ac0440130
      DataSourceLibrary 00bfea71-f381-423d-b9d1-da7a54c50110
      DiscussionsList 00bfea71-6a49-43fa-b535-d15c05500108
      DocumentLibrary 00bfea71-e717-4e80-aa17-d0c71b360101
      EventsList 00bfea71-ec85-4903-972d-ebe475780106
      EventsList 00bfea71-ec85-4903-972d-ebe475780106
      ExternalList 00bfea71-9549-43f8-b978-e47e54a10600
      FollowingContent a7a2793e-67cd-4dc1-9fd0-43f61581207a
      GanttTasksList 00bfea71-513d-4ca0-96c2-6a47775c0119
      GettingStarted 4aec7207-0d02-4f4f-aa07-b370199cd0c7
      GridList 00bfea71-3a1d-41d3-a0ee-651d11570120
      HierarchyTasksList f9ce21f8-f437-4f7e-8bc6-946378c850f0
      IPFSWebFeatures f9ce21f8-f437-4f7e-8bc6-946378c850f0
      IssuesList 00bfea71-5932-4f9c-ad71-1557e5751100
      LinksList 00bfea71-5932-4f9c-ad71-1557e5751100
      MBrowserRedirect d95c97f3-e528-4da2-ae9f-32b3535fbb59
      MDSFeature 87294c72-f260-42f3-a41b-981a2ffce37a
      MobilityRedirect f41cc668-37e5-4743-b4a8-74d1db3fd8a4
      MySiteMicroBlog ea23650b-0340-4708-b465-441a41c37af7
      NoCodeWorkflowLibrary 00bfea71-f600-43f6-a895-40c0de7b0117
      PictureLibrary 00bfea71-52d4-45b3-b544-b1c71b620109
      PremiumWeb 0806d127-06e6-447a-980e-2e90b03101b8
      PromotedLinksList 192efa95-e50c-475e-87ab-361cede5dd7f
      ReportListTemplate 2510d73f-7109-4ccc-8a1c-314894deeb3a
      SiteFeed 15a572c6-e545-4d32-897a-bab6f5846e18
      SiteFeedController 5153156a-63af-4fac-b557-91bd8c315432
      SurveysList 00bfea71-eb8a-40b1-80c7-506be7590102
      TaskListNewsFeed ff13819a-a9ac-46fb-8163-9d53357ef98d
      TasksList 00bfea71-a83e-497e-9ba0-7a5c597d0107
      TeamCollab 00bfea71-4ea5-48d4-a4ad-7ea5c011abe5
      WebPageLibrary 00bfea71-c796-4402-9f2f-0eb9a6e71b18
      WikiPageHomePage 00bfea71-d8fe-4fec-8dad-01c19a6e4053
      WorkflowHistoryList 00bfea71-4ea5-48d4-a4ad-305cf7030140
      workflowProcessList 00bfea71-2d77-4a75-9fca-76516689e21a
      WorkflowServiceStore 2c63df2b-ceab-42c6-aeff-b3968162d4b1
      WorkflowTask 57311b7a-9afd-4ff0-866e-9393ad6647b1
      XmlFormLibrary 00bfea71-1e1d-4562-b56a-f05371bb0115
    • Now you are ready to generate the WSP file. After compiling the project file Deploy the solution. Chances are the deployment will fail if you haven’t associated a valid SharePoint farm to the project. You can safely ignore that and go to the bin folder to get your WSP file.
    • Upload and Deploy the WSP file in your SharePoint 2013 test environment and try the upgrade again

    More information is here:

    Migrating Custom Site Definitions & Web Templates during SharePoint 2013 Upgrade

    Best Regards,


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact

    Thursday, January 5, 2017 7:52 AM