SharePoint 2007 Upgrade Considerations


Upgrading from SharePoint 2007 to 2013

Abstract

SharePoint 2007 mainstream support ended on 10/9/2012; it is currently under extended Support through 10/10/2017. Depending on the service pack version, the service pack support ended on 1/8/2013. So businesses that are still running on SharePoint 2007 will soon have to migrate to latest version of SharePoint or look at other solutions.

SharePoint 2010 was a complete redesign/re-platform from SharePoint 2007 and then SharePoint 2013 added several new features, enhancements and upgrades SharePoint 2010. Listed below are some of the differences between SharePoint 2007 and SharePoint 2013 (Most of the features are available in SharePoint 2010).

This post has two goals – (i) provide an overview of the most relevant features, compare and contrast SharePoint 2013 and (ii) highlight the upgrade options, upgrade paths and features for going from SharePoint 2007 to SharePoint 2013.

Introduction

Microsoft SharePoint 2013 is the business collaboration platform for the enterprise and the Internet. SharePoint 2013 can be deployed onsite (also called on-premises) or as a hosted service, such as SharePoint Online. It can also be deployed to physical machines or virtualized to support cost reduction.

Highlights of some of the features

Content Deployment Enhancements

SharePoint 2013 supports automatic Content deployment jobs to help Content Authors deploy changes to content without the help of technical resources. No packaging and deployment or custom scripts are needed. Preset timer jobs deploy content from a staging/authoring site to production site at predefined time intervals.

Multi-lingual Support

Multilingual capabilities in SharePoint 2013 offer rich support for multilingual sites.

SharePoint supports Variations. Variation feature automates the creation, management, synchronization and translation of sites, lists and pages, which eliminates having to manually create a list and all associated objects and pages for each instance of a needed variation. 


Usage and Analytics enhancement

Usage and Analytics information is available at a web site level and provides information related to the number of hits, unique users etc. Popularity trend and most popular items report are some of the features available out of the box. Also supported is integration with 3rd party products like Google Analytics for Web Analytics.

PowerShell Integration

PowerShell is task automation and scripting language from Microsoft. SharePoint has rich support for PowerShell helps in automation and maintenance of SharePoint environment. Several new commands were added for App management, Health Monitoring, Licensing, Machine Translation, and Search, Backup and Recovery and a lot of other features.

Several different platforms support PowerShell including Server products like SharePoint, SQL Server and Exchange. Cloud vendors like Amazon Web Service and Microsoft Azure also support PowerShell.

Security

SharePoint 2013 introduces several new and improved security features, from a new security model in the form of Claims-based Authentication, to a new Single-Sign-On service application called Secure Store, right through to changes in the way SharePoint manages and controls the credentials for its own service accounts. The new Secure Store Service is an authorization service that replaces Single Sign-On (SSO) in SharePoint Server 2007. Secure Store securely holds users’ usernames and passwords for applications outside of SharePoint that SharePoint can integrate with. The Secure Store enables SharePoint 2013 to connect to external data sources through BCS with an individual’s credentials, and is programmatically accessible for developers to leverage in solutions built on top of SharePoint.

Diagnostics

The Unified Logging Service (ULS) in SharePoint 2013 offers a robust logging and tracing system and is used for diagnosing and tracing events and issues within SharePoint and has been improved in several areas, including new manageability controls, log file readability improvements, and the ability to work with ULS logs through Windows PowerShell scripting.

Performance Controls

SharePoint 2013 offers several new performance features designed to protect the server from unexpected peaks in demand, and also to prevent, or control, certain user operations that can place a significant load on the server while it processes them. The two primary performance control features are resource throttling for web requests and large list management for lists containing thousands to millions of items.

Through Resource Throttling settings, SharePoint 2013 provides a way for administrators to determine the level at which the server will enter throttling mode. By default, server CPU usage, available memory, the number of requests in queue, and request wait time are monitored. After three unsuccessful checks, the server enters a throttling period and will remain in this state until a successful check is reported. Requests that were generated prior to the server’s entering throttling mode will be completed; this helps prevent users from losing any current work when the server begins to throttle new requests.

Mobility support and editing capability with Full-Fidelity viewing

SharePoint 2013 has robust mobile support and compatibility which include optimized mobile browser experience, Push notifications, geo-location, Business Intelligence content and office web apps.


Support for editing depends on the kind of device. Viewing is supported across the 3 major mobile Platforms.

 

Integrating External Data and SharePoint

If you are integrating external data with SharePoint, SharePoint now has built-in platform capabilities such as Business Connectivity Services or the new REST Data Access services to allow two way integrations. Business Connectivity Services, RESTful web services and Client Object Model are the new features.

Business Connectivity Services (BCS) is a new feature of the SharePoint 2013 platform, building on the Business Data Catalog (BDC) functionality of Microsoft Office SharePoint Server 2007.

SharePoint 2013 now has built in RESTful web services support which are intended for use by remote components that need basic capabilities for list and library data. REST Services can be simply accessed using HTTP requests, utilizing standard HTTP verbs such as GET, PUT, DELETE and POST to perform CRUD operations against the service.

Also new to SharePoint 2013 are the various flavors of client object models allowing developers to write and execute code from client machines utilizing the three new client object model flavors. These new Object Models are frequently used to integrate SharePoint 2013 and other systems from a usability perspective. Users can access both SharePoint and other informational assets from a single interface that does not necessarily have to be the SharePoint interface (think custom built Web Applications for example). This new model offers advantages like simplifying Deployment hassles, Language flexibility (.NET based languages, Silverlight and ECMA Script languages like JavaScript are supported), Using this Client object model helps reduce network traffic using Query Optimizations and needs less round trips.

Search Enhancements and upgrades:

The new search in SharePoint 2013 includes several enhancements that include

  1. Improvements in Search UI: Document content preview, complete overhaul of Search UI.
  2. Additions of search filtering option.
  3. Relevance Improvements: New ranking models for people search, intranet and internet sites and result sources.
  4. Changes to crawling: Option for continuous crawl, option to remove items from search index, Search health reports, Overhaul of search architecture.

Business Intelligence and Reporting Additions

SharePoint supports a robust Business Intelligence Center, Dashboard designer, KPIs, Excel Services, and Power View (helps visualize and interface with modeled data by using enabling interactive visualization, animations and smart querying). PowerPivot (it is a feature of Excel that allows you to create an analytic data model and helps analysis of data), PerformancePoint Services, Reporting Services (SSRS) and Visio Services. These features can be used to create Dashboards that can host excel worksheets, graphs and reports.


Upgrading SharePoint 2007 to SharePoint 2013

Upgrade from SharePoint 2007 to SharePoint 2013 can be done via regular upgrade (Microsoft recommends to upgrade to SharePoint 2010 first and then to SharePoint 2013) or using are 3rd party tools like Metalogix, Sharegate , MetaVis and Avepoint.

Upgrading from SharePoint 2007 to SharePoint 2013 needs to be done with an intermediate step, You have to upgrade to SharePoint 2010 first using database attach to upgrade from Office SharePoint Server 2007 to SharePoint Server 2010, and then from SharePoint Server 2010 to SharePoint Server 2013. The process includes backing up your content databases from 2007, set up a small, temporary farm with SharePoint 2010 (you can even use virtual servers if you don’t have space, and a trial version), and attach and upgrade them to 2010 there. Then, set up your destination 2013 farm, back up the 2010 databases, and attach and upgrade them to SharePoint 2013.

This upgrade path also applies to upgrading from Windows SharePoint Services 3.0 to SharePoint Foundation 2010 – you must upgrade to SharePoint Foundation 2010 before you go to SharePoint Foundation 2013.

To upgrade from SharePoint 2010 Products to SharePoint 2013, you use the database-attach method to upgrade. In the database-attach method, you first create and configure a SharePoint 2013 farm. Then you copy the content and service application databases from the SharePoint 2010 Products farm, and then attach and upgrade the databases. This upgrades the data to the new version. Site owners can then upgrade individual site collections.

Step 1: Upgrade from SharePoint 2007 to SharePoint 2010

Before you run any process to upgrade from Microsoft Office SharePoint Server 2007 to Microsoft SharePoint Server 2010, you have to determine which upgrade approach to take. Use the information in this article to help compare the pros and cons for each approach and to review information about special cases that might influence your approach.

Choose an upgrade approach

There are two basic approaches to upgrade: in-place and database-attach. In addition, there are various techniques you can use to combine aspects of these basic approaches to mitigate downtime or potentially improve performance. The following table compares the in-place and database-attach approaches.

Approach

Description

Pros

Cons

In-place upgrade

You can install SharePoint Server 2010 on the same hardware. You can also upgrade the content and settings in the server farm as part of a single process.

Farm-wide settings are preserved and upgraded. Customizations are available in the environment after the upgrade, although manual steps may be required to upgrade or rework them.

Servers and farms are offline while the upgrade is in progress. The upgrade proceeds continuously. Consequently, you must allocate enough time for all content to be upgraded in sequence.

Database attach upgrade

You can upgrade the content for the environment on a separate farm. The result is that you do not upgrade any of the services or farm settings. You can upgrade the databases in any order and
upgrade several databases at the same time. While each database is being upgraded, the content in that database is not available to users.

You can upgrade multiple content databases at the same time, which results in faster upgrade times overall than an in-place upgrade. You can use a database attach upgrade to combine multiple
farms into one farm.

The server and farm settings are not
upgraded. You must manually transfer settings that you want to preserve from the old farm to the new farm. Any customizations must also be transferred to the new farm manually. Any missing customizations may cause unintended losses of functionality or user experience issues. Copying databases over a network takes time and bandwidth. You must plan for that. You need direct access to the database servers.

The following table lists the downtime mitigation techniques that you can use during upgrade to reduce the amount of time that users cannot access their content or to potentially increase upgrade performance.

Technique Description Pros Cons
Parallel upgrade You can attach and upgrade multiple databases at a time to speed up the upgrade process overall. The maximum number of parallel upgrades depends on your hardware. This technique works for either in-place or database attach upgrades. Faster upgrade times for your overall environment. This is a manual process that requires additional steps and monitoring.
Hybrid approach 1: Database attach with read-only databases Lets you continue to provide read-only access to content during the upgrade process. For this approach, you set the databases to read-only while the upgrade is in progress on another farm. This method reduces perceived downtime for your users. The existing farm can continue to host non-upgraded sites (in read-only mode) while you upgrade the content. As a result, there is minimal downtime for users.You can upgrade multiple content databases at the same time, which results in faster upgrade times overall than an in-place upgrade.You can upgrade hardware in addition to software. The server and farm settings are not upgraded. You must manually transfer settings that you want to preserve from the old farm to the new farm.Any customizations must also be transferred and upgraded manually. Any missing customizations may cause unintended losses of functionality or user experience issues.Copying databases over a network takes time and bandwidth. You must plan for that.You need direct access to the database servers.
Hybrid approach 2: In-place upgrade with detached databases: Lets you take advantage of an in-place upgrade’s ability to upgrade content and settings, while adding the speed of a database attach upgrade. For this approach, you use an in-place upgrade to upgrade the farm and settings, and to detach and upgrade multiple databases in parallel (on the same farm or a separate farm). Farm wide settings can be preserved and upgraded.Customizations are available in the environment after upgrade, although manual steps may be required to upgrade or rework them.You can upgrade multiple content databases at the same time, which results in faster upgrade times overall than an in-place upgrade. Copying databases over a network takes time and bandwidth. You must plan for that.You need direct access to the database servers.

Another option to consider if you are facing an overly long outage window is to use Alternate Access Mapping URL Redirection with a database attach approach, so that you temporarily redirect users to an existing farm while you upgrade the content on a new farm. This is an advanced method and should not be used unless other downtime mitigation techniques are not sufficient.

Preparing for Upgrade 

Steps Notes

Run the pre-upgrade checker and address any issues. Use the report that is generated by the tool to fill out the Upgrade planning worksheet.

Perform this step multiple times as you clean up your environment and test your upgrade process. Running the checker takes only a few minutes, but addressing any issues might take days or weeks..

Clean up your environment
Before you begin the upgrade, make sure that your environment functions in a healthy state and that you clean up any content that you do not have to keep. Remove or repair any orphaned sites or data, address any large lists or large access control lists (ACLs), remove extraneous document versions, and remove any unused templates, features, or Web Parts.

Perform this step once for the whole environment.This process might take days or weeks to complete.

Record settings for user profile synchronization
Record the settings used for user profile synchronization in your previous environment in the upgrade worksheet. You will apply them to your new environment when you create and enable the User Profile Synchronization service. Record settings for connections, property mappings, and filters.

Perform this step once for the whole environment.

Record blocked file types
Blocked file types are not preserved during upgrade. Copy the list of blocked file types and save the list in the upgrade worksheet so you can reapply the settings after upgrade.

Perform this step once for the whole environment.

Back up your environment
Back up your entire environment to ensure that you can recover the existing environment in case something goes wrong during the upgrade process.

Perform this step once for the whole environment.
This step can take an hour, several hours, or longer, depending on your data set and your environment.

Perform the Upgrade.

 

Steps Notes

Run the pre-upgrade checker
Run the pre-upgrade checker again to identify any new or remaining issues before you start the upgrade.
.

Running the checker takes only a few minutes, but addressing any issues might take longer.

Install prerequisites on all servers
Before you can upgrade, you must run the prerequisite installer successfully on each Web server that has Office SharePoint Server 2007 installed.

Perform this step on each Web server and application server in your environment.

Detach databases (in-place upgrade with detached databases only)
If you are performing an in-place upgrade with detached databases, detach the databases before you run Setup.

Perform this step for each content database and Shared Services Provider (SSP) database in your environment.

Disconnect users
If you are upgrading a server farm, disconnect all the users from the server farm by stopping the World Wide Web Publishing Service (W3SVC) on all Web servers.

Perform this step on each Web server in your environment.

Run Setup on all servers
Run Setup on all servers to upgrade the software.

Perform this step on each Web server and application server in your environment.
This step might take a few minutes or more than an hour, depending on how many servers are in your environment.

Install language packs
Install any language packs you need before you run the SharePoint Products Configuration Wizard.

Perform this step on each Web server in your environment.
This step should take only a few minutes per Web server.

Configure forms-based authentication for a claims-based Web application (in-place upgrade with detached databases only)
For Web applications that were configured to use forms-based authentication or Web single sign-on (Web SSO) authentication, you must perform additional steps before you attach and upgrade the databases. First, you convert the Office SharePoint Server 2007 Web applications to claims authentication. After you convert the Web applications to claims authentication, you configure your Web application zones for forms-based authentication (or Web SSO authentication, as appropriate). Then, you can migrate users and permissions to SharePoint Server 2010.

Perform this step now if you are following the in-place upgrade with detached databases approach. If you are following a standard in-place upgrade approach, perform this step after upgrade is completed.
Perform this step for any Web applications that used forms-based authentication in Office SharePoint Server 2007.

Attach databases (in-place upgrade with detached databases only)
If you are performing an in-place upgrade with detached databases, attach the databases and then upgrade the data.

Perform this step for each content database and SSP database in your environment.
This step might take an hour, several hours, or days, depending on your data set, whether you are upgrading multiple databases
in parallel, and the hardware on the Web servers, database servers, and storage subsystem.

Monitor upgrade progress.
Use the Upgrade Status page in SharePoint Central Administration to monitor progress as your sites are upgraded.

Perform this step once for the whole environment.
This step might take an hour, several hours, or days, depending on your data set.


Perform Post-Upgrade Steps.

Steps Notes

Configure forms-based authentication for a claims-based Web application.

For Web applications that were configured to use forms-based authentication or Web single sign-on (Web SSO) authentication, you must perform additional steps after upgrading. First, you convert the Office SharePoint Server 2007 Web applications to claims authentication. After you convert the Web applications to claims authentication, you configure your Web application zones for forms-based authentication (or Web SSO authentication, as appropriate). Then, you can migrate users and permissions to SharePoint Server 2010.

Perform this step for any Web applications that used forms-based authentication in Office SharePoint Server 2007.

Configure new and upgraded services after in-place upgrade.

Many new services are available in SharePoint Server 2010. You can enable these new services after you perform an in-place upgrade by using the Farm Configuration Wizard or by configuring them individually.

Perform this step once for your environment.

Upgrade profile properties to taxonomy data and update the photo store for User Profile services.
Data in profile properties in Microsoft Office SharePoint Server 2007 that had multiple values was stored in the SSP database as part of the Profile Services data. For SharePoint Server 2010, this data must be converted to taxonomy data and be stored in the managed metadata database. When you upgrade, any photos that were stored as profile pictures must be updated. If you do not update the photo store data, either no photos will be displayed or some photos might appear distorted. You perform these actions from the command line by using Windows PowerShell cmdlets.

Perform this step once for each User Profile service application in your environment.
This step contains a lot of smaller steps. Depending on the complexity of your user profile data and your configuration, this might take an hour or several hours to complete.

Create and configure the Secure Store service application and migrate SSO data to the Secure Store service.
The SSO service that was available in Office SharePoint Server 2007 has been replaced with the Secure Store service in SharePoint Server 2010. There is no direct upgrade path for the data and settings from SSO to the Secure Store service, but you can migrate data from the SSO database to a new Secure Store database. Excel Services Application needs the Secure Store service account to function correctly.

Perform this step for each Secure Store service application that needs data from a previous SSO service.

Upgrade solutions that depend on the Business Data Catalog.
If your Business Data Catalog solution depended on the Web Parts that are provided by Office SharePoint Server 2007 and SharePoint Server 2010 by default (such as the Business Data List Web Part or the Business Data Actions Web Part), you must upgrade your solution to use the upgraded application definitions (called “BDC models”) in the Business Data Connectivity service, because those Web Parts have been upgraded to use the new object model provided by the new service.

Perform this step once for your entire environment.

Verify upgrade and review upgraded sites.
Review sites to be sure that they have been upgraded successfully and are ready for users to view.

Perform this step for every upgraded Web application and site collection in your environment.
This step might take an hour, several hours, or days, depending on your content.
You should also have site owners review their sites and report any issues.

Start a full crawl.
After all content is upgraded and all settings are configured, you can start a full search crawl of your content. This might take several hours or several days to complete, depending on how much content exists in your environment.

Perform this step once for your entire environment.
Performing a full crawl can take several hours or days to complete, depending on the amount of content in your environment.

 

Step 2: Upgrade from SharePoint 2010 to SharePoint 2013

Create the SharePoint 2013 farm

The first stage in the upgrade process creates the new SharePoint 2013 farm:

  1. Administrator installs SharePoint 2013 to a new farm. The administrator configures farm settings and tests the environment.
  2. Administrator sets the SharePoint 2010 Products farm to read-only so that users can continue to access the old farm while upgrade is in progress on the new farm.

Copy the SharePoint 2010 Products databases

The second stage in the upgrade process copies the databases to the new environment. You use SQL Server Management Studio for these tasks.

  1. With the farm and databases in read-only mode, Administrator backs up the content and service application databases from the SQL Server instance on the SharePoint 2010 Products farm.
  2. Administrator restores a copy of the databases to the SQL Server instance on the SharePoint 2013 farm and sets the databases to read-write on the new farm.

Upgrade SharePoint 2010 Products databases and service applications
The third stage in the upgrade process upgrades the databases and service applications.

1. Administrator configures the service applications for the new farm. The following service applications have databases that you can upgrade during this process:

  • SharePoint Server 2010 and SharePoint Foundation 2010
  • Business Data Connectivity service application
  • SharePoint Server 2010 only
  • Managed Metadata service application
  • PerformancePoint Services service application
  • Search service application
  • Secure Store Service application
  • User Profile service application

2. Administrator creates a web application on the SharePoint 2013 farm for each web application on the SharePoint 2010 Products farm.
3. Administrator installs all server-side customizations.
4. Administrator then attaches the content databases to the new farm and upgrades the content databases for those web applications.
5. Administrator confirms that the upgrade is successful.

Upgrade SharePoint 2010 Products site collections

The final stage in the upgrade process is to upgrade the site collections. In SharePoint 2013, site owners are in charge of upgrading their sites. The upgrade process for My Sites is slightly different from for other types of site collections.

Upgrade MySites

Administrator upgrades the My Site host and then individual users can upgrade their My Sites or the farm administrator can upgrade them by using Windows Power Shell. The following illustration shows four stages for the My Site host and My Sites during the upgrade process.

Upgrade other SharePoint 2010 Products site collections

Owners of all other site collections can start to upgrade their sites as soon as they see a notification on their site’s home page that the new version is available. The following illustration shows four stages for a site collection during the upgrade process.

Categories: Cloud

SEARCH ARTICLES