SharePoint Migration -III

with Vishal Gupta

SharePoint Conference

Key Business Reason to Migrate

Unleashing SharePoint Potential

Migration Approaches

Migration Cycle

Migration Problems

Single Shot Migration

01

02

03

04

05

External Tools07

References08

1.Storage Infrastructure improvements

2.Increase End User Productivity

3.Strong and Effective Enterprise Search

4.Improved BI for Decision Makers

5.Web Content Management

6.Governance Automation

7.Easy moving from SharePoint 2013 to Office 365

3: Key Business Drivers to Upgrade

MOSS 2007

SharePoint 2010

SharePoint 2013

• No direct migration approaches to migrate MOSS 2007 to SharePoint 2013• divided it into two phase approach• first phase the MOSS 2007 code & content will be migrated to SharePoint

2010 second phase the migrated SharePoint 2010 code & content will again be migrated to SharePoint 2013.

3: Migration Approaches

In-place Database attach1. An in-place upgrade takes place on the same

hardware as your previous version installation. When you run an in-place upgrade, the process upgrades the complete installation in a fixed order. This entire migration can be executed offline in a single and combined process.

A database attach upgrade enables us to move to new hardware or a new farm. During a database attach upgrade, we detach (backup) all the content databases from an existing farm and then attach the databases to a new server farm installation. When you attach the databases to the new server farm, the upgrade process runs and upgrades the data in place.

2. Environment will be down for an undefined amount of time.

Does not require your source environment be down during upgrade.

3. As this process creates a lot of SQL transactions and other system logs on the system disk, it creates a disk overhead on multiple drives. Also this upgrade process isn’t recommended for large content database i.e. more than 50 GB.

This process doesn’t create any large amount of system or SQL logs on disks.

4. The upgrade proceeds continuously. You cannot pause the upgrade process in between.

Can be done one content db at a time instead of upgrading all the content db in a single transaction.

5. No rollback As source environment will be untouched no need of rollback.

6. Less control over upgrade process, can’t predicate most activities time involved in overall process.

More flexible than in-place, exact time can be determine for each activities involved in overall process.

3: Available Upgrade Approaches

1.Plan

2.Prepare

3.Test4.Implement

5.Validate

3: Migration Cycle

Plan Prepare Test Implement Validate

Determine strategy Document environment

Build test farms Build/upgrade farms

Troubleshooting

Create a plan for current customization

Manage customizations

Use real data Deploy customizations

Upgrade event failures

Plan for site collectionPlan upgrade strategy

Evaluate techniques

Minimize downtime

UI/UX issues

Plan for performanceMake items upgradable

Find issues early Monitor progress Data issues

Create a communication planClean up an environment

3: Migration Cycle

Content DatabasesService Applications Farm/Web ApplicationFarm Settings List down all the

customizations Plan Upgrade

Performance

3: Plan Checklist

Ensure that the environment is fully functioning before you begin to upgrade.

Perform a trial upgrade on a test farm first.

Plan for capacity.

Back up your databases.

Optimize your environment before upgrade..

3: Plan – Best Practices

In-place Or database attach

database attach

OOTB Migration Approach Recommended /Available in 2013

Create the SharePoint 2010 farm

• Installs SharePoint 2010 to a new farm

Web Application Creation & Code Deployment

• Creates a new web application• Installs all server-side code customizations

Upgrade MOSS 2007 databases

• Sets the MOSS 2007 Site Collection to read-only so that users can continue to access the old site while upgrade is in progress on the new farm

• Back up the content databases from the SQL Server instance on the MOSS 2007 Web Application

• Restores a copy of the databases to the SQL Server instance on the SharePoint 2010 Web Application 

• Attaches the content databases to the new farm and upgrades the content databases for this web application

3: Prepare – Moss 2007 to SharePoint 2010

Know what is in your environment. Do a full survey first.Make your test environment as similar as possible to your real environment.Use real data.

Run multiple tests.

Do not ignore errors or warnings.

Test the upgraded environment, not just the upgrade process.

3: Testing – Best Practices

3: Implement – SharePoint 2013 Upgrade Process

PREPARE

• GATHER INFORMATION AND CLEAN UP 2010 FARM

• PREPARE 2013 FARM

UPGRADE DATABASES

• COPY DATABASE• UPGRADE SERVICE APPLICATION DATABASES• CREATE WEB APPLICATIONS AND APPLY

CUSTOMIZATIONS• UPGRADE CONTENT DATABASES

UPGRADE SITES

• RUN SITE COLLECTION HEALTH CHECKS• RUN SITE COLLECTION HEALTH CHECKS• CREATE AN UPGRADE EVALUATION SITE

COLLECTION• UPGRADE A SITE COLLECTION

Create the SharePoint 2013 farm

• Installs SharePoint 2013 to a new farm

Web Application Creation & Code Deployment

• Creates a new web application• Installs all server-side code

customizations

Copy & Upgrade SharePoint 2010 databases

• Sets the SharePoint 2010 Site Collection to read-only so that users can continue to access the old farm while upgrade is in progress on the new farm

• Back up the content databases from the SQL Server instance on the SharePoint 2010 Web Application

• Restores a copy of the databases to the SQL Server instance on the SharePoint 2013 Web Application 

• Attaches the content databases to the new farm and upgrades the content databases for this web application

3: Implement – SharePoint 2013 Upgrade Process

Review Logs • Upgrade Logs • Application Event Logs

3: Validate

Validate Migrated Environment • Review and Validate Web Applications • Review and Validate Services • Validate External Data Sources • InfoPath

• BCS Connections (External Content Types and External Lists) • Excel Services connections • External targets for Enterprise Search

• Authentication Providers • Customization defects and fixes

• The health checks are run automatically in repair mode when you start to upgrade a site collection.

• Health checks examine a site collection and list potential upgrade issues, such as missing or unsupported elements

Rule name Description

Customized Files This rule checks for any files that were customized in the site collection or sub sites

Missing Galleries This rule checks for all default galleries

Missing Site Templates This rule checks to make sure that the template the site is based on is available and reports if any elements are missing.

Unsupported Language Pack References This rule checks to make sure that the language packs that are used by the site collection exist and are referenced correctly by the site collection.

Unsupported MUI References This rule checks to make sure that the multi-user interface elements that are used by the site collection exist and are referenced correctly by the site collection.

3: Site Collection Health Check

http://technet.microsoft.com/en-us/library/cc303420.aspxhttp://technet.microsoft.com/library/cc263447(office.14).aspxhttp://technet.microsoft.com/en-us/library/cc303420(v=office.15).aspx

3: References

1. SP technology 2013 workflows are built on Windows Workflow Foundation 4 (WWF4). However, SharePoint 2010 workflows continue to Windows Workflow Foundation 3 (WWF3). The workflow migration is not suggested:- There is one more framework available with SP 2013 called as WAW. But AFAIK you can still create SP2010 type workflows using SPD2013. 2.Error during upgrade is missing server-side files, templates, features, or other server-side customizations— either files that were installed with SharePoint 2010 Products or customized files:- When you prepared for upgrade, you should have created an inventory of the server-side customizations. Check this inventory to make sure that all the files that are needed for your customizations are installed in your new environment.

3.More than 5,000 site collections in a database, consider breaking them out into multiple databases. To avoid errors during upgrade or broken sites after upgrade, we recommend that you move some site collections into separate databases. If you have multiple content databases, you can also speed up an upgrade process by upgrading multiple databases in parallel

3: Migration Problems

4. Some sites and site templates are not available in SharePoint 2013 .Sites based on these templates will not work in SharePoint 2013. Remove these types of sites before you upgrade:-You can use the Get-SP Site Windows PowerShell command together with the following options to find these sites:Get-SPSite|Where-Object{$_.RootWeb.Template- eq"PowerPointBroadcast#0“}

5. If you haven’t installed SharePoint 2010 SP1, after you upgrade to SP Server 2013, your out-of-the-box workflow tasks (such as Approval, Collect Feedback) will go into locked status:-Users should install SharePoint 2010 SP1 before upgrade to SharePoint Server 2013.

6. We could create a list item under folder in custom list using Create ListItem action in SharePoint 2010 but in SharePoint 2013 Create List Itemaction doesn’t support creating items in the folder due to platform limitation:- Try calling SharePoint 2010 workflow using Start a list/site workflow action in the SharePoint 2013 workflow.

7.A mismatch in authentication methods can cause problems when you upgrade:-Claims-based authentication is the default authentication method for web applications in SharePoint 2013. If the web application was using classic mode, you can either update it to claims before you upgrade the database, or create the web application in classic mode and then migrate it to claims.

8.You cannot upgrade a database that is set to read-only. Make sure that you set the databases to read-write before you attach and upgrade the databases.

9.You must manually create all trusted data connections for Excel Services after upgrade.

10.How to upgrade environments that include services farms to SP2013. Some services in SharePoint 2010 Products can be shared across multiple farms . A services farm hosts services such as Business Data Connectivity service, Search, and User Profiles that other farms consume. When you upgrade to SharePoint 2013, you first upgrade the services farm, and then upgrade the farms that consume those services.

Key Features:1. Direct Upgrade to SharePoint 20132. Migrate File Shares and more

1. Content Matrix 6.0 connects and moves terabytes of content from file shares, blogs, wikis, Exchange Public Folders, PST files, eRoom and websites.

2. Content Matrix 6.0 moves the content, files, associated metadata and other relevant attributes such as permissions or information structure into SharePoint. Empower Content Owners

Metalogix Content Manager 6.0http://www.metalogix.com/Products/Content-Matrix.aspx

Key Benefits:1. Upgrade with Confidence2. Move to the Cloud: Office 365 and Office 365 Dedicated3. Keep SharePoint Organized4. migration speeds of up to and beyond 125GB per hour5. Move Structure, Workflows and Permissions6. Analyze your existing content

Supported Source Systems1. SharePoint Server 2013 & 20102. SharePoint Foundation 2013 & 20103. Office 3654. Office SharePoint Server 2007 & WSS 3.05. SharePoint Portal Server 2003 & WSS 2.06. File Shares7. Exchange Public Folders & PST files8. Google Blogger, Word press, Movable Type, Telligent 9. Blogs using Metaweblog standard or RSS 10. Atlassian Confluence, Media Wiki11. HTTP or HTTPS accessible websites