Restore Managed Navigation Enabled site Collection in a new SharePoint farm


  • Hi 

    Currently i have a Managed Navigation Enable site Collection.i need to move that site collection to a new SharePoint Farm.

    After i restore using site collection backup .site is restored . but Top Navigation it's gives an Error. Term Store not found.Under site navigation also i cant find any Term set.How can i get my top navigation back using my previous Term set. i already tried by restoring previous farm Managed meta data Database to New Farm but it not worked . your help deeply appreciate.


    Thursday, August 29, 2013 1:32 AM

All replies

  • I found that the following PowerShell fixed the navigation but the navigation itself is still missing from the Term Store UI:

    function UpdateNavigation($url,$termStoreName,$termGroupName,$termSetName)


        $web= Get-SPWeb $url

        $site = $web.Site

        $navSettings = New-Object Microsoft.SharePoint.Publishing.Navigation.WebNavigationSettings($web)

        $taxSession = Get-SPTaxonomySession -Site $site

        $termStore = $taxSession.TermStores[$termStoreName]

        $termGroup = $termStore.Groups[$termGroupName]

        $termSet = $termGroup.TermSets[$termSetName]

        $navSettings.GlobalNavigation.Source = 2

        $navSettings.GlobalNavigation.TermStoreId = $termStore.Id

        $navSettings.GlobalNavigation.TermSetId = $termSet.Id


        Write-Host "Navigation updated successfully for site $url"


    $siteUrl = http://ABC

    $termStoreName = "Managed Metadata Service"

    $navTermSetGroupName = "Site Collection - ABC"

    $navTermSetName = "Site Navigation"

    UpdateNavigation $siteUrl $termStoreName $navTermSetGroupName $navTermSetName

    • Proposed as answer by Badajoz95 Thursday, October 17, 2013 1:31 AM
    Wednesday, October 16, 2013 9:54 PM
  • i think you need to mover the MMS before the Restoring the Site collection.

    also check this one to solve the issue.

    Thanks -WS SharePoint administrator, MCITP(SharePoint 2010, 2013) Blog: *Please remember to mark your question as "answered"/"Vote helpful" if this solves/helps your problem.*

    Wednesday, October 16, 2013 10:14 PM
  • I believe that the term store for the Site Collection is in the Site Collection backup so you don't need to copy the whole taxonomy.

    If you do want to move the whole taxonomy then I have had success with SPMetadataWebServicePartitionData which is clunky / tricky to configure but works once you have the permissions and network shares sorted out. This is really helpful. Remember to change owner accounts after moving cross domains.

    Thursday, October 17, 2013 1:30 AM
  • Term sets are managed in Central admin and I believe part of the config database. Whereas site collection managed navigation just keep the reference (probably term set id/guid) of the term sets to be used for navigation. So when you have restored the site collection backup into new farm, the managed navigation is still looking for terms set by id in the config database, but you have not restored the term set in the target farm. So you need to restore the term sets from source farm to the target farm. Once tool you can try to export/import terms set is available at I'm not sure if the tool keeps the terms set id or not. If it keeps the terms set id then after importing term set, the navigation will work fine as the site collection navigation will find the terms set by the reference id. However, if the terms sets are stored with new id, then you need configure the navigation again in the target farm.

    Sohel Rana

    Thursday, October 17, 2013 2:35 AM
  • After restoring Metadata to new environment:

    1. Found table ECMPermission refer to old site collection id, You need to change to new site collection id
      You can get site if run command:
      $site = Get-SPSite url 
    2. After change site id resetiis  
    3. Change attach navigation to another option.
    4. Reassociate again navigation with term store.

    Tarek Yehia

    Thursday, October 17, 2013 5:14 AM
  • Whilst hacking the ECMPermission table in the MetaData database is something that would invalidate one's warranty, it helped me fix the issue in a test environment.
    Wednesday, November 13, 2013 10:54 PM
  • Surely someone at MS can provide a supported and straightforward solution to moving a site collection and its navigation term set to another farm.

    Attaching a copy of the source Metada database would probably work but would also overwrite any global term sets created in Central Administration.

    If at first you don't succeed, ask an MVP.

    Friday, May 02, 2014 5:18 AM