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


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.
Chadd BushIT Systems AdministratorAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Annie RoseTech LeadCommented:
Check this step by step artcile to migrate from SharePoint 2010 to SharePoint 2016:
Sandeep KumarAssociate ConsultantCommented:
Use Kernel Migrator for SharePoint software to migrate from SharePoint 2010 to SharePoint 2016 in simple steps.
Visit for software details and process for migrating SharePoint.
Jamie McAllister MVPSharePoint ConsultantCommented:
Full commentary based on the actual question.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SharePoint

From novice to tech pro — start learning today.