Migrating your SharePoint Environment to SharePoint 2013 just got easier…
When it comes to SharePoint 2007 or 2010, the use of the word ‘upgrade’ or ‘migration’ can be a bit unsettling at times. SharePoint 2013 is no different; however, Microsoft has made a few improvements to the upgrade process to ease some of the pain that comes with upgrading to the latest and greatest.
While SharePoint 2013 still has that new software smell, I’d like to provide you with a brief overview of some of the changes that will be helpful to know when it’s time to move.
First and foremost, there is no direct upgrade path from 2007 to 2013. If you currently have a 2007 WSS/MOSS farm, you must first upgrade to SharePoint 2010 before ultimately moving to SharePoint 2013; however, there are a number of third-party migration tools that can get you directly from 2007 to 2013 with minimal effort. Contact Fpweb.net today to ask how we can do this for you.
Now, one method that many small businesses have been accustomed to using is the in-place upgrade. Unfortunately, this method is no longer supported. This essentially means that SharePoint 2013 cannot be installed over the top of SharePoint 2010. Why is this concerning? Well, if you have the secondary hardware to stand up a new SharePoint 2013 environment, it’s not. But if you’re like many companies trying to cut costs, secondary hardware can be very expensive and thus, not an option.
To the cloud!
This is the perfect time to move your SharePoint environment to a cloud hosting provider (cough…Fpweb.net…cough). With the in-place upgrade method no longer being an option, this means Database-Attach is the only method (aside from the third-party tools mentioned earlier). The Database-Attach method requires the deployment and configuration of a new farm that is completely separate from the current/previous farm. Databases must then be copied over to the new farm, attached and upgraded manually and intermittently.
What databases or service application can be upgraded using the Database-Attach method?
- SharePoint Connectivity Database
- Managed Metadata
- Business Data Connectivity
- Performance Point Service Application
- Secure Store Service Application
- User Profile (Profile, Sync, and Social Databases)
- Search Administration.
SharePoint 2013 Upgrade Improvements
With past SharePoint upgrades, once the database had been attached, the only people who could perform individual site or site collection upgrades were farm administrators. In SharePoint 2013, both farm administrators AND site collection administrators can perform these upgrades, as they see fit.
In SharePoint 2013, you have the ability to take a visual test drive of a Site Collection to evaluate what it will look like before actually performing the visual upgrade. When an evaluation site is created, it is completely separate from the live site, and can be set to expire and deleted automatically. In addition, Site Collection Administrators can use the Health Checker to proactively determine if any issues will arise with the new SharePoint 2013 interface.
A great feature in this release is the ability to have SharePoint 2010 and SharePoint 2013 components run in the same farm (in IT terms, the 14 and 15 hives can live together). This is beneficial if a customer has any specific features, site templates, site definitions or web parts that are not yet compatible with 2013, the farm upgrade can still be completed and these problem children can be dealt with at a later date.
For any SharePoint migration questions or if you’re ready for a custom SharePoint 2013 Cloud, contact Fpweb.net today!