How to migrate DocRead from SharePoint 2010 to SharePoint 2013
If you are considering migrating your SharePoint Farm to SharePoint 2013 (from SharePoint 2010) 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 licensing.
Preparing your SharePoint 2013 Farm :
It is important to know that we only support migrations that have followed Microsoft’s recommended approach.
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.
If you do wish to use one of these approaches then it may still be possible to migrate your DocRead data but it would require one of our DocRead developers to work with you as a chargeable piece of work.
Before you start the migration :
Before you start the migration you will need to download the latest version of DocRead for both 2010 and 2013. It’s very important that you are migrating from the one version of DocRead to another with the same build number. (e.g “v2.5″). If you aren’t running the latest version of DocRead on SharePoint 2010 you will need to carry out an upgrade which is detailed in our Installation Guide. 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 2010.
Migration Steps (Central Admin) :
- Complete the build and testing of your new SharePoint 2013 Farm.
- Install but do not configure the latest version of DocRead for SharePoint 2013 onto your new Farm. (you will also need a license key by this stage).
- Install but do not configure the latest version of the DocRead Scheduler onto your new Farm.
- Attach and upgrade all of the content databases that DocRead was used on previously (please refer to the Technet guide).
- If you are using SharePoint Global Audiences with DocRead it’s also necessary migrate your User Profile Service App and Metadata Service App which is detailed here.
- 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 2010.
Do a full back-up your SharePoint 2013 Farm.
- Back-up your 2010 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.
- 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’
- Navigate to Central Admin > Collaboris Settings > Licensing and enter your license key and click ‘Add’. Click ‘Ok’
- 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 the re-add them as the internal ID’s will differ). Click ‘Ok’.
Disable the following DocRead timer jobs by going to Central Admin > Monitoring > Review Job Definitions :
- DocRead audiences synchronisation job
- DocRead readership processing job
- DocRead SharePoint synchronisation job
- DocRead Worker job
- DocSurvey Stats Job (optional)
- Migration Steps (Site Collection)
- That’s all you need to do in Central Admin for now. The next phase is deactivate and uninstall the old 2010 Features and activate the new 2013 Features.
- You can download the ‘upgrade Powershell script from here.
- Once downloaded, open Powershell script with Notepad and edit the Datasource, Database (DocRead database) and user credential (if required).
Save the updates
- Execute the Powershell script file (click right mouse button and select ‘Run with Powershell’.
- IMPORTANT: The script only reactivates DocRead basic features. If any additional features were activated before you should reactivate them manually.
- Post Migration Steps (Central Admin) :
- Perform an IISReset on all of your machines in the production Farm.
- Restart the SharePoint Timer job on all machines in the production Farm (see step 12 above for a list).
- Perform a “Process Reading Tasks” in each DocRead enabled web and ensure that all the tasks are a present as before.
- Configure the DocRead Scheduler as specified in the Installation Guide.
- Scheduler a regular backup of the DocRead database.