.NET DeveloperYou can count on us to get the job done. As the Army ad says "We get more done before 9am than most people do all day."

New migration features for SharePoint

You keep hearing about all the new SharePoint 2013 features available and are thinking about doing a migration to the latest and greatest.But you have no idea what features are available with the new release to help you transition to this version. I recently covered the planning of a SharePointMigration to 2013 but one thing I want to look at in detail through this article are the specific features available out of the box.


Supported scenarios for migration

Before we look at the features that will help youtransition, you need to know what you are allowed to do. What I mean by that isthat not all migration scenarios are supported, in fact only one is. You canonly migrate from SharePoint 2010 to SharePoint 2013. That means if you are oneof the many who are still using SharePoint 2007 or even 2003 you will have touse Sharegate Sharepoint migration tools or others to help you migrate. On top of that, evenif you are using SharePoint 2010, the only way to upgrade is to take thedatabases, detach and attach them to SharePoint 2013.

The new 2010 compatibility mode

I have to say, this is pretty cool. Microsoft added thepossibility for you to run your SharePoint Site Collection in 2010 or in 2013when you create it. This is not a fake 2010 like we had when upgrading from2007 to 2010. When you install SharePoint 2013 it actually installs most of thefiles from 2010. So when you are running a Site Collection in 2010 mode youreally are using 2010 files. Very Cool!


So you don’t have to wait before choosing to migrate, youcan dive in right away, keep everything running in 2010 mode and only createnew Site Collections in 2013 mode. This will allow you to spread the migrationover a longer period of time.

Deferred Site Collection upgrade

Because of the new 2010 mode mentioned above we can leavethe Site Collections intact and evaluate their upgrade. In SharePoint 2007 wehad the visual upgrade, but that was useless to be honest as SharePoint wasalready upgraded and the damage done, if any. Only the visuals were kept in2007 mode but not the rest.

This time, with the compatibility mode, we can now leave theSite Collection intact after migrating it and “evaluate” whether or not it willwork in 2013. This is done through another feature called the upgrade sitecollection evaluation. In this scenario, the Site Collection is actually copiedover to a new and separate url using SharePoint 2013. The copy is not instant,the Site Collection administrator actually makes a request to have this doneand a timer job is scheduled to do all the copies in the backlog at a specifictime of day, though this can be configured. The new evaluation site collectionwill only stay running for 30 days before being deleted. You can always changethe default from 30 days to something you choose.

Site Collection Health Checks before migrating

Anyone that runs a SharePoint migration wants to make surewhat they are about to do will work. The best thing we can have is somereporting on our older environment before it moves over. Thankfully, in thisrelease of SharePoint we have some new rules called the Health Check rules.

Rule name


Rule ID

Conflicting Content Types

This rule checks for conflicts between existing content types and content types that are created when you upgrade the site to SharePoint 2013. A conflict occurs when both content types have the same name.


Customized Files

This rule checks for any files that were customized (or unghosted) in the site collection or subsites. When run in repair mode, it can reset the page to the default (reghost the file).


Missing Galleries

This rule checks for all default galleries and reports if any are missing from the site collection or subsites.


Missing Parent Content Types

This rule checks for missing parent content types. If a missing parent content type is found, you can either delete the orphaned content type or associate the orphaned content type with a different parent content type.


Missing Site Templates

This rule checks to make sure that the template the site is based on is available and reports if any elements are missing.


Unsupported Language Pack References

This rule checks to make sure that the language packs that are used by the site collection exist and are referenced correctly by the site collection.


Unsupported MUI References

This rule checks to make sure that the multi-user interface elements that are used by the site collection exist and are referenced correctly by the site collection.



These can be run at the Site Collection level or throughPowerShell for the entire farm.

Very useful to run before migrating to get a good sense ofwhat potential issues you may run into during the migration.

No magic for custom code

Of course it goes without saying that if you heavilycustomized your previous version of SharePoint 2010 there is a good chance thatyou will run into issues when migrating. Some may still work but expect tore-do a lot or keep the Site Collection in 2010 mode. Let’s not forget thatthis is only from SharePoint 2010 to SharePoint 2013 and if you are running aprevious version there is no supported method to upgrade other than goingthrough a 2010 migration followed by a 2013 upgrade. Altogether there are greatnew features to help you with the transition to 2013 from 2010 at the SiteCollection level.

Biography – Benjamin Niaulin

Benjamin Niaulin works as a SharePoint Geek at Sharegate, a Montreal-based software development firm specialized in SharePoint migration.Passionate about SharePoint, Benjamin has been helping people around the globe reach their goals by simplifying SharePoint solutions. With his Microsoft Certified Trainer certification and over 5 years of Training and Speaking experience, he has acquired the skills needed to help everyone understand and use SharePoint.‚Äč 



Learn about the patient management system we developed for Dartmouth-Hitchcock Medical Center and other case studies.



See what clients are saying about Keene Systems.              READ MORE

Successful companies choose the best consultants again and again. Keene Systems developed software for some of the world's most prestigious companies.