Here is another migration notes from the field.
The previous one is: SharePoint 2007 to 2010 Upgrade
This time is about SharePoint 2010 to 2013 Upgrade.
As you may know, MS discontinued to support in-place upgrade. That left only one option for migration - creation a new farm and restoring supported databases there.
My intention is not retype\reproduce that has been already said by Microsoft about the SharePoint 2013 Upgrade. You have got all it here: Upgrade and migrate to SharePoint 2013
My goal is to summarize some thoughts that I had during the upgrade.
Before to jump into actual migration, it's very helpful to think about architectural changes that come with SharePoint 2013:
You will definitively need more RAM and drive space
And there is a good probability you will need more server to accommodate some of the functionality such as : Office Web Access, Project Server.
More on : SharePoint 2013: Architectural changes. Pain Points
As any migration, it starts with a simple question:
"What do we need to migrate?"
And these couple of notes are about "cleaning the content before moving":
SharePoint 2010 to 2013 Upgrade: Phase I "Cleaning". Unused web applications
SharePoint 2010: Confirm site use and deletion. How to restore Site Collection ?
SharePoint 2010 to 2013 Upgrade: Phase I "Cleaning". Unused spweb
Another big and important step is to prepare a new farm. I like to pay attention to the service accounts that should be used in order to setup the farm up securely:
SharePoint 2010 to 2013 Upgrade: Service Accounts
And once all set in the new farm and running, it's time for content migration:
Here is a quick guide in case if you have a common error like "Missing feature".
Test-SpContentDB MissingFeature, MissingSetupFile, MissingWebPart, MissingAssembly. And not so Fabulous 40 templates.
Apart from mentioned above posts, I didn't get much trouble with upgrading. It looks pretty much the same as SharePoint 2010 upgrade. In case you have some other issue, I recommend to refer to the SharePoint 2007 to 2010 Upgrade. Even though it's a previous version, you can definitely translate the experience from 2010 to 2013 upgrade process.
The previous one is: SharePoint 2007 to 2010 Upgrade
This time is about SharePoint 2010 to 2013 Upgrade.
As you may know, MS discontinued to support in-place upgrade. That left only one option for migration - creation a new farm and restoring supported databases there.
My intention is not retype\reproduce that has been already said by Microsoft about the SharePoint 2013 Upgrade. You have got all it here: Upgrade and migrate to SharePoint 2013
My goal is to summarize some thoughts that I had during the upgrade.
Before to jump into actual migration, it's very helpful to think about architectural changes that come with SharePoint 2013:
You will definitively need more RAM and drive space
And there is a good probability you will need more server to accommodate some of the functionality such as : Office Web Access, Project Server.
More on : SharePoint 2013: Architectural changes. Pain Points
As any migration, it starts with a simple question:
"What do we need to migrate?"
And these couple of notes are about "cleaning the content before moving":
SharePoint 2010 to 2013 Upgrade: Phase I "Cleaning". Unused web applications
SharePoint 2010: Confirm site use and deletion. How to restore Site Collection ?
SharePoint 2010 to 2013 Upgrade: Phase I "Cleaning". Unused spweb
Another big and important step is to prepare a new farm. I like to pay attention to the service accounts that should be used in order to setup the farm up securely:
SharePoint 2010 to 2013 Upgrade: Service Accounts
And once all set in the new farm and running, it's time for content migration:
Here is a quick guide in case if you have a common error like "Missing feature".
Test-SpContentDB MissingFeature, MissingSetupFile, MissingWebPart, MissingAssembly. And not so Fabulous 40 templates.
Apart from mentioned above posts, I didn't get much trouble with upgrading. It looks pretty much the same as SharePoint 2010 upgrade. In case you have some other issue, I recommend to refer to the SharePoint 2007 to 2010 Upgrade. Even though it's a previous version, you can definitely translate the experience from 2010 to 2013 upgrade process.
Very good and informative, great effort on consolidating the steps ! thumbs up
ReplyDelete