• Status: Solved
  • Priority: Low
  • Security: Public
  • Views: 66
  • Last Modified:

Can someone assist with migrating from SharePoint 2010 to SharePoint 2016 ?

Hi,

What are some best practice procedures for migrating from SharePoint 2010 to SharePoint 2016 ? Any tips or advise would be very much appreciated. I've found a few  things while researching but would like to know what exactly would be the best, easiest, and fastest methods for doing this migration.
0
Chadd Bush
Asked:
Chadd Bush
  • 2
1 Solution
 
Jamie McAllister MVPSharePoint ConsultantCommented:
I completed a project to migrate 2010 to 2016 recently. I had access to two migration tools; Metalogix Content Matrix and Sharegate.

Both these tools have their own limitations and I wasn't happy with everything. The data throughput for a farm of any size was also slow.

In the end, we had a staging farm built specially in SharePoint 2013 to upgrade the databases. We used a community tool called FeatureAdmin to remove dangling solution dependencies. Then we attached the Content DBs to the 2016 farm. This was fast and gave full fidelity for content, permissions and structure.

There were legacy issues with the original structure plus a content DB of 600Gb which couldn't be ported this way. I used Sharegate to move this content, but had to watch it like a hawk. It wasn't good for porting permissions and some author information was missed etc. But it allowed me to split the large content DB across new site collections in their own DBs.

When you use DB attach that content doesn't benefit from the new Shredded Storage capabilities until it's re-written. The migration tools on that 600Gb meant most of our content became Shredded Storage in SQL.

If using migration tools you need to be very careful of hidden content, i.e. files that have no checked in version. Invisible to the tools. So I had to write powershell to iterate through all libraries to uncover this so I could check it in.

$sList = $sWeb.Lists | ? {$_.Title -eq $SourceLibraryTitle} 

$InvisibleFiles = $sList.CheckedOutFiles

foreach ($InvisibleFile in $InvisibleFiles)
{
	$out = "$($InvisibleFile.CheckedOutBy),$($InvisibleFile.Url)"
	$out | Add-Content $file
}

Open in new window


Another gotcha was that the Content Databases in 2016 were much larger for the same amount of content in 2010. About 90% in fact! Allocate lots of disk!

I'm producing a video pulling these lessons and more together and will post the link when complete.
2
 
Annie RoseTech LeadCommented:
Check this step by step artcile to migrate from SharePoint 2010 to SharePoint 2016:
http://expert-advice.org/sharepoint/upgrade-from-sharepoint-2010-to-sharepoint-2016/
0
 
Sandeep KumarAssociate ConsultantCommented:
Use Kernel Migrator for SharePoint software to migrate from SharePoint 2010 to SharePoint 2016 in simple steps.
Visit https://www.nucleustechnologies.com/sharepoint-migration for software details and process for migrating SharePoint.
0
 
Jamie McAllister MVPSharePoint ConsultantCommented:
Full commentary based on the actual question.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now