Anyone who tells you that migrating to SharePoint 2013 is easy, has either not been around the platform very long, or hasn’t been doing it right himself.
Last time, we looked at some of the new features that could potentially sway you to upgrade to SharePoint to 2013. This time, I want to look at the different migration paths we’re presented with. Follow this series with the outline below.
Articles in this Series
1. SharePoint 2013 New Features: Should You Move?
2. Migrate to SharePoint 2013 - Supported Upgrade Paths
3. Designing a SharePoint 2013 Architecture
4. How to Build a SharePoint Migration Plan
5. Building a SharePoint Governance Plan Before Migrating
6. Predicting Post-SharePoint 2013 Migration Issues
Only One Supported Upgrade Path: SharePoint 2010 to 2013
"The database-attach method is the only supported method for upgrading from SharePoint 2010 Products to SharePoint 2013"
That is an extract from the official Microsoft Technet SharePoint Upgrade Process model.
What does it mean? Exactly what you think: if you’re not running SharePoint 2010, there are no supported migration scenarios. I’ll get to that shortly but to tell you the truth, there is no secret to it – you will need third party tools to perform the migration if you are running a SharePoint version older than 2010.
Assuming that you do fall within the “Supported Migration Scenario”, and are running SharePoint 2010, what can you do to upgrade to SharePoint 2013.
I won’t re-write Microsoft’s well explained document, but I’ll give you a rough summary.
Basically the migration is simple enough from a high level:
- Install SharePoint 2013
- Back Up Databases from 2010 - Restore in 2013 and upgrade Databases
- Upgrade Site Collections to new 2013 Interface using PowerShell or through Site Collection Administration
What Happened to In-Place?
I hope this isn’t a question you’re actually asking. Sorry about the boldness, but this is never a good idea.
It’s comparable to taking your Windows XP, upgrading it to Vista, then upgrading it to Windows 7, and so on, but never actually reinstalling from scratch.
But imagine it on a larger scale, with SharePoint it’s a server that the entire organization is using to collaborate. It’s not something you want to upgrade like that.
Therefore, it is no longer supported. The idea is to migrate to a newly installed ready to go SharePoint 2013 rather than staying on the same box and keeping all the “manual patches” that were done over time to the server. Come on… you know what I’m talking about.
Is Visual Upgrade Still Available?
No and yes. Wait what? SharePoint 2013 no longer has the “Visual Upgrade” feature. However, there is something new called “Deferred site collection upgrade”.
When we were on SharePoint 2007, and SharePoint 2010 became available, it came with a “Visual Upgrade”. If you remember, this would allow a Site Administrator to “Preview” his site in SharePoint 2010.
This sounded great, but the fact was that you needed to migrate your SharePoint to 2010 before accessing this feature.
Result: Many things were broken as your site “looked 2007” but really was a SharePoint 2010 site already. The only things that were touched were things like Master Page, CSS and HTML files.
The New “Deferred Site Collection Upgrade”
I’ll be honest with you, I never really used the visual upgrade, except once for a very small business. In organizations, I needed to make sure the upgrade would be successful before I actually migrated. This rendered the Visual Upgrade feature of SharePoint 2010 a bit useless.
This time, my gut feeling says I will definitely be using this new upgrade solution for SharePoint 2013.
SharePoint 2013 actually installs the files for SharePoint 2010 when it is installed.
- Features, site templates, site definitions, and Web Parts
The directories on the file system are duplicated in both the 14 and 15 paths, for example:
- Web Server Extensions/14/TEMPLATE/Features
- Web Server Extensions/15/TEMPLATE/Features
- IIS support directories:
- _Layouts, _Layouts/15
- _ControlTemplates, _ControlTemplates/15
- Solution deployment, which lets legacy solutions work in 2010 mode
(The above information is straight from Microsoft’s Technet Article)
This basically means when you install SharePoint 2013 and migrate your SharePoint 2010 Content Database over, it will actually still be running in SharePoint 2010 mode.
You won’t have to wait to start using SharePoint 2013.
Take your Databases and move them to SharePoint 2013, continue using them as SharePoint 2010 and create new sites in SharePoint 2013.
How do I actually upgrade the sites?
Ok so you moved your sites over to SharePoint 2013 but they are still running in SharePoint 2010 mode, so how do you upgrade them? And is there a way to preview them before we push the button?
Absolutely, and I think Microsoft did a great job this time around for the migration process.
When your SharePoint 2010 is running on SharePoint 2013 you’ll need to start upgrading. The difference this time is that it’s by Site Collections, and not by Site anymore. Much better, because let me tell you, going to individual sites to upgrade will quickly leave you with a bitter taste.
SharePoint offers you 2 upgrade possibilities
- PowerShell command to upgrade all Site Collections to 2013
- Deferred Site Collection Upgrade; Each Site Collection Administrator upgrades when he’s ready.
In "Deferred Site Collection Upgrade", the Site Collection Administrator can request a preview of their site. This is called upgrade evaluation site collection. The site will be placed in queue to be copied by a once-per-day timer job, to a SharePoint 2013 mode Site Collection.
In other words, SharePoint creates a copy of your Site Collection into SharePoint 2013. This will be available for 30 days before another timer job deletes it. Of course the 30 days value can be changed.
Many other options can be configured for throttling and such, to make sure your farm doesn’t go down while previews are created but the information is available on TechNet already. Find resources at the bottom of this article.
The Site Collection Administrator can also choose to upgrade without looking at a preview.
Upgrading from SharePoint 2010 to 2013
Well you have the official word above, when you migrate to SharePoint 2013 from SharePoint 2010 it seems everything was thought of and should be an easy enough upgrade.
Granted it does not allow you to restructure or re-architect your SharePoint while you upgrade, since it’s a Database Attach upgrade.
But, overall, you should have all the tools to migrate to SharePoint 2013.
In my introduction post, I talk about reasons you may have to make the switch. However, looking at the supported scenarios, and how Microsoft handles SharePoint 2010 to 2013 upgrades, I may take a different approach.
It might just be worth it to upgrade SharePoint to 2013 since it can run in SharePoint 2010 mode as well. But this will only work if there is a lot of Education and Training on this subject early on by Microsoft.
Upgrading from SharePoint 2003 or 2007
That’s where it becomes not so easy. We’ve established that from 2010 there are few, if any, issues, but what about the 20-30% of the others who are still on SharePoint 2007?
It simply is not supported.
You don’t have many possible solutions, either you upgrade to SharePoint 2010 and then SharePoint 2013. Or, use SharePoint migration tools that can bypass this limitation for you.
I wish I had better solutions, and I will keep this part of the blog updated as time passes, and new creative ways of migrating immerse in the world of SharePoint. However, for now, there simply isn’t any.
Sources to get you prepared – You Need to Actually Read Them
- TechNet – Upgrade to SharePoint 2013
- TechNet – Plan for Upgrade to SharePoint 2013
- TechNet – Upgrade to SharePoint 2013 Resource Center
- This blog series… I’ll keep this list updated as time passes
Migrating to SharePoint 2013 Isn't Easy
In fact, the same could be said when migrating from any version. Hopefully this presentation will provide you with some help, ideas or just confirm what you're doing.
**NEW** TechNet - Changes from SharePoint 2010 to SharePoint 2013 and reason for change
Meanwhile to hesitate to reach out if you have any questions @bniaulin
NEXT ARTICLE IN THE SERIES
3. Designing a SharePoint 2013 Architecture