Migrate to SharePoint 2013 Stress Free

Post on 16-Nov-2014

843 views 1 download

Tags:

description

Stress Free Migration to SharePoint 2013 using these best practices and processes.

transcript

Migrating to SharePoint 2013

Stress Free

Nick Kellett@nickkelletthttp://www.linkedin.com/in/nicholaskelletthttp://www.stoneshare.com

January 28, 2014

About Me About me:

Chief Technical Officer at StoneShare Inc Software technologist, speaker, instructor, and blogger Advocate of lifelong learning and sharing knowledge Twitter: @NickKellett LinkedIn: www.linkedin.com/in/nicholaskellett

So what’s this session about anyways?

A Little History Migration Options – 2003 or 2007 to 2013 Migration Options – 2010 to 2013 Migration Tools and Utilities Top 5 Migration Tips Recommended Migration Process

Those who cannot clean up the past content are condemned to migrate it

A Little History

2003 to 2007 migration

Options: In Place, Gradual Database Attach Migration Third Party Vendor

Common problems: Customizations and unghosted Pages Architecture changes OOTB migration wasn’t granular enough Third party tools were lacking, or expensive

2007 to 2010 migration

Options: In Place, Database Attach Third Party Vendor

Common problems: Customizations Architecture changes OOTB migration still wasn’t granular enough Branding Changes Massive changes in Hardware requirements

Migration Options from 2003 or 2007

Migration Options – 2003 or 2007 to 2013

Migration Options

2003 to 2013: Third Party Vendor 2003 to 2013

2007 to 2013: 2 step OOTB Migration: 1. Database Attach from 2007 to 20102. Database Attach from 2010 to 2013 Third Party Vendor 2007 to 2013

Migration Options from 2010

Migration Options – 2010 to 2013

Migration Options

Types of Migration: Content / Data Functionality

Content Migration Options Database Attach Third Party Vendor

Functionality Migration Options Database Attach Third Party Vendor Cleanup and Redeployment

Migration Options – Database Attach

Install new 2013 Farm Detach Service Application Databases from

2010 Upgrade Service Application Databases in 2013 Detach all content databases from 2010 Attach content databases to new 2013 farm Upgrade Sites

Run Site Collection Health Checks Upgrade Evaluation Site Choose whether to upgrade the Site

Migration Options – Vendors

Major Vendors are AvePoint and Metalogix ShareGate is a Canadian Company How do they work?

Install agents on source location(s) Install Administrator console(s) Perform the migrations at a very granular level

Most allow discovery process beforehand Most are licensed by volume of content

migrated/managed

Migration Options – Vendor Benefits

Clean up before moving More granular migration options Scheduled migrations Migrate to/from a variety of sources “Wave” Migrations Reusable Migration Tasks Split/merge sites, libraries, and lists Migrate Nintex workflows Use the product afterwards to manage your

SP2013 site

Migration Options – Vendors (cont.)

Migration Options – Vendors (cont.)

Top 5…

Migration Tips

Tip 1 – Spring Cleaning Archive old sites – move to Archive web application (up

to 4 TB) Archive old content – move to Archive doc library, site, or

web application (up to 4 TB) Clean up user permissions Clean up orphan sites

Backup your content databases. For each, run: Stsadm –o enumallwebs–databasename

<ContentDatabaseName> –databaseserver <DatabaseServer> >c:\<ContentDatabaseNameOrphans>.txt

Delete up all sites that have a value InSiteMap=”False”

Common Migration ProblemsPain Recommended solution

Uncontrolled environment Audit and govern

Lack of hardware Virtualize

Customized pages Revert to site definition

Custom site definitions Upgrade, recreate, or replace

Third party applications Upgrade, recreate or replace

Customized web config files Look in web.Config for FBA settings, connection strings, custom safe control entries, and port these over

Custom code Look in GAC and 12 or 14 hive for custom code. Upgrade, recreate, or replace

Language packs Ensure the new farm is running the required language packs

Tip 2 – Governance and Monitoring Plan and Govern Early

Audit your content and functionality Consider restructuring

Governance Strategy and Plan Setup a Governance Committee before migrating Setup Storage Quotas when migrating Monitor and report

Tip 3 – Start Early Provide your business users with a “Cheat Sheet” of

instructions Provide them with a SharePoint list called “Content

Inventory” Get them to identify which sites/content within that they

want to migrate OR get them to cleanup and then do a site-to-site migration

Classify their tasks into categories Meet with them on a weekly basis to help them through

the process

Tip 4 – No Big Bang Migration

Keep the old Farm going!!! Migrate a group at a time Consider the impact of a long cutover on your users and

administrators, and infrastructure Plan carefully What does “Live” mean

Tip 5 – Test, Test, Test Setup test farm Perform mini-migrations Verify third party addons support SP2013 Review upgrade log files (new Upgrade document library

in each site) Review sites in 2010 mode Test upgrade to 2013 mode

A to Z

Recommended Migration Process

Migration Process

Restructure Farm? Pre-Migration Checklist 1…n Test Migrations Production Migration Final steps

Restructuring

This is a good opportunity to restructure your farm

Use mergedb to consolidate site collections into one content database

Use backup / restore to move site collections around

Use Third Party Tools to restructure: Web Application, Site Collections, and Site Layouts Navigation Content

Pre-Migration Checklist

Upgrade SharePoint 2010 to SP2 Run preupgrade checker on 2010 Backup All Content Databases Backup Service Applications (if any) Install All 2013 Prerequisites Install SP2013

1..n Test Migrations

Setup Test environment Create database copy of real content Migrate using the chosen approach Check the Log Files Test Data and Functionality Test Visual Upgrade on site collections Identify and fix problems

Migration Fixes

Turn off features or functionality you don’t need Delete orphans Replace or upgrade third party components Replace or upgrade custom code

Migration Production

Setup production environment Migrate using the chosen approach Test Data Test Functionality Use Visual Upgrade on site collections Switch over requests to new farm (if required)

Project Plan Sample

Migration Resources

Microsoft Upgrade to SharePoint 2013 guidance on Technet: http://

technet.microsoft.com/en-us/sharepoint/fp142375.aspx

Metalogix Content Matrix: http://

www.metalogix.com/Products/Content-Matrix.aspx AvePoint DocAve Migrators and Content

Manager: http://www.avepoint.com/sharepoint-migration-tools

/ ShareGate

http://en.share-gate.com/ SPYam – SharePoint Community on Yammer

In Closing

What, Me Worry?

Q & A Connect with me on Twitter: @nickkellett Connect with me on LinkedIn:

http://www.linkedin.com/in/nicholaskellett