This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 77%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
After migration from 2010 to 2016 some of the content is not displaying in 2016
it is one of the subsite from source and destination
PFA
It appears to be those are web parts but not sure, how should proceed to make same goes in 2016 also. Please help
you can see in the "categoires" screenshot. Buniess intelligence knowledge base is the subsite.
in categoires list you can see all business objects, deliver shopping e.t.c so in 2010 site when we click on these links it is showing data in 2010 but where as in 2016 it is not showing data. Please help. you can find below 2016 screenshots also
@sns How did you do the migration from SharePoint 2010 to SharePoint 2016? Database attach or using a third-party tool?
Except using a third-party tool, there's no way to upgrade from SharePoint Server 2010 to SharePoint Server 2016 directly. If you are using Database attach, you need to upgrade your SharePoint as the order:
So, if you are using the method above, please check if the content could be displaying on SharePoint 2013, and also remember that before you upgrade to SharePoint Server 2013 and SharePoint server 2016, run the test-spcontentdatabase Microsoft PowerShell cmdlet to identify missing files.
There are some articles about upgrading to SharePoint server 2013, help them useful for you:
best-practices-for-upgrading-from-sharepoint-2010-to-sharepoint-2013
troubleshoot-database-upgrade-issues-in-sharepoint-2013
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi Wendy Li,
I used dB upgrade
Yes we followed standard procedure to upgrade from 2010 to 2013 and then to 2016.
Please help.
Did the same content show when you migrated to SharePoint 2013?
Before migrating to SharePoint 2016, when running test-spcontentdatabase, were there warnings or errors displaying?
And is there any solution/feature related to the site on your SharePoint 2010 farm?
Hi Wendy Li,
Usually every site collection I navigate to site settings-->site collection upgrade status in the down.
If I see errors =0 then I conclude no issues. so I have not seen any issues in 2013 nor in 2016 as well.
After user reported I came to know about this particular blog subsite. And I saw the logs file from site collection upgrade status which I attached now.
can you please have a look and suggest what needs to be done. 68624-versionsupgradelogs.txt
blog is the subsite from bikb site collection.
@sns I checked the log file that you uploaded, yes, as you said, no error was found when doing site collection UI upgrade.
Could you open the same blog subsite in SharePoint 2013 and check if it could display correctly? We need to confirm if there was something wrong when migrating from SharePoint 2010 to SharePoint 2013.
I have taken fresh backup of DB from 2010 prod and then mounted to 2013. Verified in 2013 environment. PFA screebshots.
used 2010 to 2013 DB method
2013 to 2016 used sharegate for now due to issue,
I have attached screenshots for blog subsite in 2010 actual prod and also for 2013 blog site and 2016 as well.
if it gets sorted out in 2013 may be we can apply same fix in 2016, as per the fix I will work on DB upgrade method from 2013 to 2016 later.
Please find logs from 2013 environment. Please assist further.
HI Wendy,
Did you have chance to look in to above thread?
@sns Per your image, when you upgraded from SharePoint 2010 to SharePoint 2013, the left navigation didn't show on the blog site, is it right?
Before you mounted to SharePoint 2013, did you run test-spcontentdatabase ? we need to use this cmdlet to test the SharePoint 2010 content database against the SharePoint 2013 Web application to verify all customizations referenced within the content database are also installed in the SharePoint 2013 web application.
If all customizations are installed on SharePoint 2013, it should return like the below(the cmdlet I used when upgrading from SharePoint 2016 to SharePoint 2019, it is similar to the process of the upgrade from SharePoint 2010 to SharePoint 2013):
Hi Wendy,
yes. Left navigation did not show up in 2013?
so now DB is in 2013. so shall I execute test-spcontentdb in 2010 or 2013?
As you have mounted the database in SharePoint 2013, you can dismount the content database firstly in SharePoint 2013, then remove it from SQL Server of SharePoint 2013.
Then restore the original backup file into sql server, execute the cmdlet above in SharePoint 2013 using the newly restored database and the existing web application, check if there are missing features/solutions.
Hi Wendy,