#qSharePointMigration Best Practice: Divide & Conquer

Migrations are hard. SharePoint migrations are no exception. We all wish there was a single “Move All” button to bring over everything to a new version of SharePoint or a new server. Sorry to break it to you, but there is no silver bullet.

 

Moving a company to a new HQ provides a good analogy. Unless you have a tiny office with just a couple of people, you will need to move your people and stuff gradually according to a well thought-out plan. Migrations do disrupt business operations, but we can always minimize the impact by following some simple best practices.

 

The Benefits of Granular, Phased Migrations

 

One of the main benefits of Quest Migration Suite for SharePoint is that it offers significant flexibility in how granular your SharePoint migrations can be. You can move entire site collections, or you can copy just a single document between sites.

 

It is often tempting to do migrations at the highest level possible. With Migration Suite, you can migrate up to the site collection level – but is it a good idea? Well, it depends on how big your site collections are. It’s one thing to copy a few gigabytes, but if your site exceeds 100-200 GBs, you should seriously consider splitting your migration into smaller chunks so that you have more control over the process. If something goes wrong, would you rather be troubleshooting a single list or hundreds of them? Needless to say, large migration jobs can be chaotic to manage and will take much longer to execute and see results. Additionally, site and content owners will need time to verify the migration, so getting them something to test early on while other site collection parts are being migrated is a nice benefit.

 

How to Perform Granular, Phased Migrations with Quest Migration Suite

 

If you have a large site collection, you can go from top to bottom, migrating the root site first, followed by sub-sites. The Copy Sub-Sites option (on by default) in the Site Copy wizard enables you to copy a site without its child sites (“shallow” site copy):

 

You can combine shallow and recursive copy any way you need. (E.g. you need to keep permissions for most of the sites, but some need their permissions reset to inherited. Or you need to move certain sites up in the site tree.)

 

In some cases you can go one step further and migrate sites without any list and library content. The Copy Lists and Libraries option enables you to do this:

 

 

This might be particularly useful when you need to pick and choose which lists and libraries need to be migrated.

 

There are multiple ways to execute your SharePoint migrations more efficiently. You need to think carefully about which migration strategy works best for you. Migration Suite for SharePoint will help you implement it and make your next migration a success.

About the Author
Alex Kirillov
Product Manager with the Microsoft Platform Management group