SharePoint Tip of the Month
SharePoint 2013 Migration Made Easy!
Microsoft released the latest version of SharePoint (SharePoint 2013) last year. You may have seen the new features and capabilities and now you want to migrate your SharePoint environment to the new 2013 platform, but there is just a small problem – you are running SharePoint 2007 and Microsoft does not support direct migration to 2013. Don’t worry; it is easier than you think.
Let’s consider the current situation: You are the SharePoint administrator for a large SharePoint 2007 farm. Your environment has close to 1,000 site collections with more than 10,000+ users. Your CIO would like to see all content migrated to SharePoint 2013. The budget and resources do not allow for a SharePoint 2010 pit stop during the migration; you must go directly from 2007 to 2013.
Let’s add in a little complexity to make this fun, too: Your total content size is nearly 1TB. You have multiple content databases and some are larger than the 200GB recommended size. You want to split up the content database during the migration to keep them smaller and manageable.
What are Your Migration Options?
Option 1 – Database attach
This option upgrades the database schema by attaching a content database from SharePoint 2007 to SharePoint 2010. Then you upgrade again by attaching it to SharePoint 2013. This requires an intermediate environment of SharePoint 2010. Essentially, it involves twice the migration effort and an extra environment to build and support.
Option 2 – Content migration
This option allows for direct migration of content from SharePoint 2007 to SharePoint 2013. It does not involve the upgrade of the database schema. It requires a third-party migration tool and can be run directly on the target SharePoint 2013 environment. In short, the tool scans the current SharePoint 2007 sites and libraries, creates new sites and structures in 2013, and copies content to the new libraries and lists while retaining the metadata, security and other properties.
Migration Tools Available
There are many migration tools available from different well-known vendors in the SharePoint market. Most tools will offer similar features and perform similar functions. There are some features that make certain tools better than others.
One tool that we use and recommend is Content Matrix from Metalogix.
- Go directly from 2007 to 2013
- Migration of workflows (OOB, SPD and Nintex)
- Retains all metadata – also can add metadata fields in the upgrade
- Selection of which sites to upgrade
- Keeps permissions intact
- Batch migration
- Up to 125GB/hour
- Support migration of un-ghosted pages
- Full and Incremental migration
- Choose content database at point of migration per site collection
- Changing of template at point of migration
- Source and Target environment – check the sites and click migrate
- Easy to use UI – migrate site collection, sites, library, or items
Benefits gained by using this tool over the traditional database attach method:
- Skip over SharePoint 2010 version
- No need for intermediate SharePoint 2010 environment
- Old database schema does not need to be upgraded – sites are recreated on new database
- GUI support for splitting content DBs
- Can connect to many different source farms
- Batch migrations – selection of a set of site collections and then schedule the migration
- Fix hard coded links
- Retain original metadata and workflow associations
- Incremental and full migration – full migration first, then a subsequent incremental to migration changes
So if you manage a large outdated SharePoint environment and would like to migrate the content to a new SharePoint platform, you should consider a migration tool for the job. On an on-going basis, the tool can be used to move content from one farm to another on the same version, such as development to testing/staging to production farms. The freshly created sites on the new content database means you can leave the errors and issues behind in your old environment. A well-planned migration using full and incremental copy as well as scripts and scheduling will greatly reduce headaches and costs of the project.
This SharePoint Tip contributed by Khanh Hoang, Abel Solutions Senior SharePoint Consultant.