How to migrate DocRead from SharePoint 2013 to SharePoint 2016

Note: The information in this post relates to DocRead for on-premises SharePoint only. 

If you are considering migrating your SharePoint 2013 Farm to SharePoint 2016 then please read through this article for steps on how to achieve this. Before proceeding, it’s important that you read ‘migrating between editions‘ to understand how this effects your DocRead and DocSurvey licensing.

Preparing your SharePoint 2013 Farm:

It is important to know that we only support migrations that have followed Microsoft’s recommended approach. Please read through these pages on Technet to understand how to upgrade. Please note: we don’t support migrations that have been completed using custom code, or by using 3rd party migration tools such as those offered by AvePoint and Metalogix.

Before you start the migration:

Before you start the migration you will need to download the latest version of DocRead for both 2013 and 2016. It’s very important that you are migrating from one version of DocRead to another with the same build number. (e.g 'v3.3'). If you aren’t running the latest version of DocRead on SharePoint 2013 you will need to carry out an upgrade which is detailed in section 6 of the System Administrators Guide found in our Documentation Centre. Once you have completed the upgrade – it’s important to test DocRead to ensure that it is still fully operational and working as expected on SharePoint 2013.

Migration Steps (Central Admin):

1. Complete the build and testing of your new SharePoint 2016 Farm.

2. Install but do not configure the latest version of DocRead for SharePoint 2016 onto your new Farm. (you will also need a license key by this stage).

3. Install but do not configure the latest version of the DocRead Scheduler onto your new Farm.

4. Attach and upgrade all of the SharePoint content databases that DocRead was used on previously (please refer to the Technet guide).

5. If you are using SharePoint Global Audiences with DocRead it’s also necessary to migrate your User Profile Service App and Metadata Service App which is detailed here.

6. Once this is complete, please test that your Farm is operational and specifically ensure that the Site Collections, Webs, Libraries / Lists, Groups, Audiences and Documents now exist with the same content as they had for SharePoint 2013.

7. Do a full back-up your SharePoint 2016 Farm.

8. Back-up your 2013 DocRead database and restore it to the SQL Server that you will be using for production and make a note of the Database name and Server Name.

9. Navigate to Central Admin > Collaboris Settings > Database Settings and enter the ‘SQL Server’ and ‘Database Name’ that you noted in the step above. Click ‘Ok’.

10. Navigate to Central Admin > Collaboris Settings > Licensing and enter your license key and click ‘Add’. Click ‘Ok’.

11. Navigate to Central Admin > Collaboris Settings > Global Settings and add all of the Web Applications that contain sites where DocRead is activate. (Please note, even if they appear to look the same, it’s important to remove all and re-add them as the internal ID’s will differ). Click ‘Ok’.

Post Migration Steps (Central Admin):

1. Perform a 'Process Reading Tasks' in each DocRead enabled web and ensure that all the tasks are present as before.

2. Configure the DocRead Scheduler as specified in the Installation Guide.

3. Schedule a regular backup of the DocRead database.