As you know, the much-anticipated release of SharePoint 2016 created lively conversations across international organizations. Possibly one of the more interesting questions was whether organizations running SharePoint 2013 or SharePoint 2010 need to migrate to SharePoint 2016 at all. Answering that question is something only the organization asking it can really do – by learning as much as possible on the subject. But if you are using and creating a lot of data and products on SharePoint 2010 and considering a direct migration from SharePoint 2010 to SharePoint 2016, this article is for you.
I’ll present an example of how migration from SharePoint 2010 to SharePoint 2016 works, using Bamboo’s Data-Viewer web part.
How does it work?
Step 1: First of all, back up the database in the SQL server on SharePoint 2010 includes the HW37 Data-Viewer Web Part. We will retrieve the *.bak file (Ex: HW37.bak).
Step 2: Copy and paste the *.bak file to SharePoint 2016 server (EX: C:\ HW37.bak).
Step 3: In the SP2016 server, go to the Central Administrator page, select the Application Management hyperlink on the left pane, select the Web Application tab, and select New.
Step 4: Go to Application Management again and select Manage content databases. Next, select the web application you are using and click on the Database Name hyperlink.
Step 5: Select the Remove Content Database checkbox and Click Ok. You will see the database removed from the list.
Step 7: Run the SharePoint 2016 Management Shell as Administrator.
Run stsadm command line as below:
stsadm.exe -o addcontentdb -url <URL> -databasename WSS_Content_port
Wait for the operation to successfully complete.
Next: Refresh the Content Databases site. You will see the database is updated on the site.
Step 8: Go to the SP2016 site. You will see Data-Viewer showing an error. Don’t worry, that’s because you have not installed SP2016 Data-Viewer onto the SP2016 server yet.
Step 9: Install Data-Viewer and select the web application you’re using. Refresh page. Data-Viewer will now work as expected and all configurations will be kept.