Title Layout

Subtitle

The Game Of

SharePoint Migrations

Winter Is Coming

Minnesota Microsoft 365User Group

July 15 2019

Thomas Duff

(and Sandra Mahan)

Thomas Duff

› Twitter: @Duffbert

› One Minute Office Magic (https://OneMinuteOfficeMagic.com)

› Email: duffbert@gmail.com

What this story will cover

› Our current home

› Our plans

› Our alliances

› Our Training

› Our Migration

› Our Pitfalls

› Our New Home

Our Current

Home:

SharePoint

2010

The backstory

› Originally wanted to migrate to SP 2013, but it didn’t make the final budget cuts

› Started turning on Office 365 features in 2017 (Exchange, Office Proplus, other features)

› 2019 was targeted for SPO migration

› Cost of not finishing by winter (12/31/2019)

› 3300 sites and subsites to migrate or delete

Our

Plans

Pre-work

› Divided sites into weekly groups (26 in total)

› Tried to keep similar sites (subsites) in same group to avoid multiple URL changes

› Generated a SPO list with all the SP 2010 sites

› Manually went into each list item and built out a projected name and URL for the new SPO sites

Our Alliances

You can’t fight a battle without allies

› Vendor to help with migration (running the actual migrations of sites from SP 2010 to SPO)

› Sharegate for the migration tool

Our

Training

Making Sure The Business Has Knowledge

› Content Panda

› Brainstorm – QuickHelp On Demand Webinars and Skillpaths

– Instructor Led Training

› Spark Connect

› SparkOne

Our

Migration

SharePoint

Migration Site

Migration cycle

› T-2 – Let business know they have two weeks until migration checkout

› T-1 – Let business know they have one week until migration checkout

› Checkout Week – Business reviews their sites for functionality and content migration

› Go-Live – The new site is live, and the old site is locked down to read-only

Migration schedule

T -2 Week

› Send Email #1 to site owners

› Initial migration will occur on Saturday

T -1 Week

› Send Email #2 to site owners to remind them of the upcoming checkout

› The initial migration occurred on Saturday

› SharePoint team does initial checkout:– Review the home page on the new site– Compare the site contents (item counts)– Review site permissions (inherited from parent

site)– Republish any InfoPath forms if needed– Review and update SharePoint Designer

workflows if needed– Update the migration list status to “Checkout”

Site owner Checkout› Send Email #3 to site owners to begin site checkout

› Site Owner Checkout instructions

Site Lock Down

› Delta Migration - Completed Friday night the end of checkout week

› SharePoint team locks down the SP 2010 site:– Add banner on the home page linking to the SPO site (see below)

– Change site permissions to Read (also limited access)

– Remove site owners from Site Collection Administrators

– Remove the SP 2010 site from search (Site Settings, Search and Offline Availability, Allow this site to appear in search results = No)

– If a site collection, go to Central Admin > Site Collection Quotas and Locks to change it to Read-only (blocks additions, updates and deletions).

This site has moved to SharePoint Online, is in a read-only status, and has been removed from search.

New site: https://contoso.sharepoint.com/sites/SiteName

Please update your bookmarks and any other links accordingly.

Site Go-Live

› Send Email #4 to site owner which includes Email #5 template to send to members/visitors

› Update migration list status to “Migrated”

Our

Pitfalls

The night is dark and full of terrors

› PHI and Active Directory Groups

› People don’t read emails

› Document library files with no initial check-in

› InfoPath in SPO does not support web service calls for profile information

› SharePoint Designer 2013 does not have an option to get user profile information

The night is dark and full of terrors

› Permissions groups are often empty for subsites

› Long hours for our SharePoint team

› Difficulty in making sure we divide and conquer the incoming emails

› SPO doesn’t support incoming emails on lists and libraries

› Certain business areas needed longer ramp-up times than one week

Our

New

Home

We learn to celebrate all good things

› To date, we have deleted/decommissioned approximately 1500 of the 3300 sites we started with

› The business has been cooperative in doing what is necessary to make this migration happen

› We’ve had fewer migration issues than expected

What to do next

› The business likes the new look and feel. Working on additional branding and themes

› Learn PowerApps and Flow to start replacing InfoPath and SharePoint Designer

› Refresh and review business apps to incorporate new designs and functionality

Questions