Collab 365 - Real world scenarios to migrate to SharePoint 2016 or Office 365

WWW.COLLAB365.EVENTS

Real world scenarios to migrate to SharePoint 2016 or Office 365

Hi. I’m Gokan.

Brussels, BELGIUM neoxy.be SharePoint MVP

Community Member @GokanOzcifci http://gokan.ms

Hi. I’m Patrick.

Paris, France http://abalon.fr/ Office 365MVP

Microsoft Regional

Director @patricg

https://yos365.wordpr

ess.com

• Which migration ?

• Project plan

• Demo : Migration to SharePoint 2016– Technical process

• Demo : Migration to Office 365– Inventory

– Migration

• Common errors– Migrating to SharePoint 2016

– Migrating previous versions

Agenda

Which migration ?

One or several SharePoint migrations ?

SP2010

Migration trajectories

SP2016

SP Online

Sequential upgrade

From version to version

With DB upgrade

Direct move to last version

Need third party tool

SP2013MOSS 2007

To the Cloud

Tooling is highly

recommended too

New API for perfor-

mance

Hybrid

Imply permanent link between

platforms, may imply

permanent exchanges

The 3 possible waysSequential version DB upgrade

• Verify disk space

• Verify updates levels, functional change

• This is the only directly supported method

Direct move to last version

• Quicker and less expensive

• Third party tool is mandatory

• Allow a major reorganization of content

To the Cloud

• Beware of functional discrepancy and amount of data transfers

• Third party tool is highly recommended

• Reorganization is almost always necessary

Sequential upgrade

From version to version

With DB upgrade

Direct move to last version

Need third party tool

To the Cloud

Tooling is highly

recommended too

New API for perfor-

mance

Migration Project Plan

Plan

• Evaluate existing system

• Custom Framework

• 3th party tools

• Build the Migration plan

• Solutions?

• Authentication?

• Content

Prepare

• Clean

• By the users

• By IT

• Prepare a SWAP

• Prepare new environments

• Test with a copy of

production data

• Correct errors

Migrate

• Create Web Apps

• Respect renewed Best

Practices

• Content Database

Migration

• with a tool

• PoSH

Validate

• Technical acceptance tests

by IT

• Users acceptance tests

• Validate

• Switch

• AAM

• DNS

• F5

Migrate

VerificationCorrections

How to plan?

Assess current content

• By hands

• With PowerShell scripts

• Tools : Documentation Toolkit For

SharePoint

• With migration tools

Build the migration plan

• Why -, Legal Requirement? New

Features?

• What -, Public Facing, Intranet, Service

Applications?

• When ?

• When and how communicate ?

Clean / Reorganize

• By hand

• Scripts

• Tools

Set up new environments for test and future production

• Design and size new farms

•Physical versus virtual

•Servers by role

• Install custom developments

• Basic testing first

Tests on production data

•Deploy Solutions (We all love Add-ins hé )

•Use a copy of production data => Test and verify databases

•Verify that sites are OK in compatibility mode

•Upgrade sites collections

Correct errors

• Analyze migration logs for site collections

•Visual and functional verification of sites Technical Diagrams SharePoint 2013 Upgrade :

• SharePoint 2013 : How to test upgrade ?

How to prepare?

Migration methods

• Copy Content DB + upgrade site

collections

• Third-party tool

Migration type

• Direct or in several steps

• Several versions Cohabitation

• Compatibility mode SP2010 on SP2013

for example

• Complete or Incremental (Third-party tool)

How to migrate?

Acceptance tests

• IT acceptance tests

• Business Users acceptance tests

Validate

• Business agreement

• GO live

Switch

• Users redirection

• Communicate !

How to validate?

Project Plan

Plan

• Evaluate existing system

• Custom Framework

• 3th party tools

• Build the Migration plan

• Solutions?

• Authentication?

• Content

Prepare

• Clean

• By the users

• By IT

• Prepare a SWAP

• Prepare new environments

• Test with a copy of

production data

• Correct errors

Migrate

• Create Web Apps

• Respect renewed Best

Practices

• Content Database

Migration

• with a tool

• PoSH

Validate

• Technical acceptance tests

by IT

• Users acceptance tests

• Validate

• Switch

• AAM

• DNS

• F5

Migrate

VerificationCorrections

Budget

Business

Requirements

What really

matters?

Focus on goals

In theory migration to SharePoint 2016

IT Preview

The SharePoint Server 2016 IT

Preview is provided for the sole

purpose of evaluating new and

updated features in SharePoint

Server 2016 IT Preview. This

software is provided as-is for use in

a test environment and is not

supported by Microsoft Support.

This preview release does not

provide a migration/upgrade path

to the final release of SharePoint

Server 2016.

• SharePoint Server 2016 IT Preview supports an upgrade from SharePoint 2013 with March 2013 PU, version 15.0.4481.1005 or higher.

• When you upgrade from SharePoint 2013 to SharePoint Server 2016 IT Preview, you must use a database attach upgrade, which means that you upgrade only the contentfor your environment and not the configuration settings.

• SharePoint Server 2016 IT Preview does not support SharePoint 2010 mode (that is, compatibility level 14) site collections.

Upgrade to SharePoint Server 2016 IT Preview

Technet : Upgrade to SharePoint Server 2016 IT Preview

Technical process (SharePoint 2013)

Technet : Overview of the upgrade process to SharePoint 2013 Technical diagrams for SharePoint 2013 Upgrade :

• SharePoint 2013 Upgrade Process

• SharePoint 2013: How to Test Upgrade

Migration to SharePoint 2016

MIGRATION TO OFFICE 365

THIRD PARTY MIGRATION TOOLS

Third party tools

• AvePoint DocAve Migrator

• SharePoint Discovery Tool

• Metalogix Content Matrix

• Migration Expert

• Metalogix Metavis

• Dell Migration Suite for SharePoint

• Sharegate Migration Tool

• Pre-Migration Check • How to choose ?

• Size of data to migrate

• Metadata management

• Dedicated server install

Steps 2, 3 and 4 are performed by using either

• the SharePoint Online SPO Migration PowerShellcommands or

• a 3rd party migration tool.

It is important to perform Step 1 to know what tool will fit best your need.

Leveraging the new Migration API

SharePoint Online and OneDrive for Business Migration Speed

1

2

3

4

Strengths

• Direct migration 2007 - 2013

• Cloud Migration

• Granular migration

• Content reorganization

• Differential update

• Content filtering

• Tool delegation IT or Business

Weaknesses

• Testing

• Costs (to be checked with your sales rep)

– 25 to 45€ / GB or

– 14 k€ / frontal or

– 5 k€ / 10 users

• Training

Tools strengths and weaknesses

Demo Sharegate

• You don’t know SharePoint

• You thought training was

optional

• Lack of communication

• You thought database attach

would do everything

• Ignored building a new

architecture

• You didn’t inventory your sites

and test them for upgrade

• No planning, no governance,

no information architecture

• No measurable goals were set

• Branding seemed irrelevant to

you

• Ignoring third party tools

To conclude : 10 reasons your migration may fail

10 Reasons your SharePoint Migration Failed

WWW.COLLAB365.EVENTS

Annexes

Toolbox

• PowerShell

Use Windows PowerShell to

administer SharePoint 2013

technet.microsoft.com/fr-

fr/library/ee806878.aspx

• Visio

office.microsoft.com/fr-fr/visio

• SharePoint Designer

office.microsoft.com/fr-fr/visio

• Documentation Toolkit for SharePointwww.spdockit.com

• SharePoint Manager 2007, 2010, 2013

spm.codeplex.com

• SharePoint Feature Administration and Clean Up Tool 2007, 2010, 2013

featureadmin.codeplex.com

foreach ($w in Get-SPWebApplication) {

write-host "WA " $w.url ($w.sites).count

if (($w.sites).count -gt 0) {

foreach ($sc in $w.sites) {

write-host " CS " $sc.url ($sc.AllWebs).count

foreach ($si in $sc.AllWebs) {

write-host " SI " $si.url

}

}

}

}

PowerShell inventoryIn English

Build an inventory before a SharePoint Migration and

put it in Visiohttp://en.share-gate.com/blog/how-to-build-an-inventory-before-sharepoint-migration

In French

[ #SharePoint 2013 ] Inventaire d’une ferme (en 4

parties)http://blogs.developpeur.org/patricg/archive/2014/02/06/sharepoint-2013-inventaire-d-une-ferme-avec-powershell-et-visio-1-3.aspx

Organigram with Visio

Documentation Toolkit for SharePoint

www.spdockit.com

Documentation Toolkit for SharePoint

TECHNICAL PROCESS

SP2010MOSS 2007SP2013 SP2016

SharePoint Manager

spm.codeplex.com

• The only tool tu supress

problematic sites like

• With unknow template

• Unaccessible site

Clean up (1/2) SharePoint Manager 2007, 2010, 2013spm.codeplex.com

SharePoint Feature Administration and Clean Up Tool

featureadmin.codeplex.com

• Feature Admin Tool for 2007, 2010, 2013

Features clean up(2/2)MOSS 2007

SharePoint Feature Administration and Clean Up Tool featureadmin.codeplex.com

PowerShell :Test / Mount-SPContentDatabase

But you can’t mount SP2007 DB to SP2013…

For SP2010 or SP2013 Claims migration

• Wrong DB name

Some of the best errors met (1/3)

Mount is without error

But site counter is 0

http://sharepoint.stackexchange.com/questions/29719/content-database-shows-no-site-collections

First test results with 28 errors

Some of the best errors met (2/3)

Some of the best errors met (3/3)

Blocking errors

• Mount-SPContentDatabase can end with an error

• But site collection de sites is correctly mounted

and accessible

Positive false error…

More errors …(1/6)

In cas of a wrong chaining of operations (for example claims non converted)

• You need to change site collection administrators

More errors …(2/6)

More errors …(3/6)

Error when executing standard approval workflow• In French • In English

More errors …(4/6)

x

Configuration du Workflow

• This error appears when the checkbox

« Update approval status when Workflow is

ended» is checked

• It tries to update approval status when

workflow end

Error when executing standard approval workflow

More errors …(5/6)

• The previous checkbox implies that

workflow impersonate using the login of the

workflow’s author.

• This is a problem because this one is usually

know only in the original farm (not in the

migrated one)

• We have to use SharePoint Designer to save

the workflow and republish it using an

account with enough privileges in the new

farm

Error when executing standard approval workflow

Resolution

More errors …(6/6)

WWW.COLLAB365.EVENTS

Stay tuned for more great sessions …

Thanks !