1. Home
  2. Installation & Configuration
  3. Install VisualSP Classic
  4. Guidelines for Migrating Content to SharePoint 2016

Guidelines for Migrating Content to SharePoint 2016

Applies to: VisualSP Classic
Print Friendly, PDF & Email
If you will be migrating or updating your SharePoint 2013 server to a SharePoint 2016 environment, here are some guidelines to follow to make sure VisualSP successfully makes the transition with you. If the current version is no longer needed, it is advised to uninstall it entirely from the farm and delete the VisualSP Farm Hub site first. Then install it fresh into the new SharePoint on­-prem installation. Your existing 2013 license key will not work with the 2016 version of VisualSP. Request a new license key specifically for 2016 by emailing support@visualsp.com. If you have changed or created new help items, and you would like to migrate those to 2016, there will be a couple of extra steps you will need to take prior to migration.
  1. If you are storing your Help item artifacts in your 2013 Site Assets library, you will need to migrate those artifacts to the 2016 Site Assets library.
  2. You will need to export your custom Help items from 2013 and import them into 2016. If your VisualSP version is 5.5.7 and below you will need to export the entire Help item library then use a text editor to delete all of the Help items except for your custom Help items. These would then be imported into your 2016 environment. As an alternative, if you upgrade to our most recent version of VisualSP, you will be able to select your custom Help items in the Help Gallery and export only those. This could be a big time saver if you have a lot of custom Help items. If you would like to upgrade to the newest version, please download the latest release here.
If you haven't made any changes to the content, or would like to start fresh with our SharePoint 2016 Content Packages, you can skip the export and simply follow the guidelines below.

Database detach/attach migration method

  1. Your existing 2013 license key will not work with the 2016 version of VisualSP. Request a new license key specifically for 2016 by emailing support@visualsp.com.
  2. Perform a standard VisualSP deployment to the new farm using one of the methods documented below.
    1. Installer wizard
    2. PowerShell
  3. Create a test web application and site collection and validate that the deployment is complete and successful.
  4. Attach SharePoint Content DB's to the new farm.
  5. Create a new farm hub site, and fill it with the 2016 content from the zip file on our site.
  6. Configure the VisualSP settings in Central Admin to use the new 2016 hub site.
  7. Delete the original Visual SP farm hub site that was migrated from 2013.
 
Updated on April 3, 2020

Related Articles