SharePoint migrations rarely turn out as you plan them, are sometimes risky, and too often take longer than planned. Over the last 10 years of migrating from SharePoint 2003, 2007, 2010 to the latest versions of SharePoint/Office 365, we’ve seen a consistent theme: organizations underestimate the complexity and level of effort required for a successful migration.
Whether you are planning to complete your own migration, or engaging a vendor to assist, this tutorial discussed precautions you can take to avoid the slippery slope experienced in SharePoint migrations.
During this tutorial, we:
Evaluate options of moving content from various systems of origin (including previous versions of SharePoint and non-Microsoft CMS)
Go through the assessment steps to understand the full landscape of your existing environment
Review methodologies for moving content from one environment to the next
Review a check list of precautions you should take in migrating to either SharePoint 2013 on-premise or online
Create a migration strategy you can take back to your organization
5. ENOUGH ABOUT US – YOUR TURN
• What are you migrating from – to?
• Where are you in the process?
• What are your biggest concerns?
• What are you looking to get out of this session?
5
9. Failure to Fully Scope
the Effort
1
Failure to Budget for All
Activities
2
No Buy-In from
Stakeholders
3
Content is Not Cleaned
or Enhanced
4
WHY MIGRATIONS FAIL
24. 24
Infrastructure
Environment
• Network Infrastructure
Where are the current and future systems
located?
Do users currently complain about
speed?
• Test Throughput/transfer rates
SpeedTest App
Fiddler
IE 9+
Test upload/ migration to an O365 site
25. 25
Infrastructure
Health
• Run Microsoft Pre-Upgrade Checkers
2007 C:>stsadm -o preupgradecheck
2010 Test-SPContentdatabase, Test-SPSite
• Review of Databases
Dedicated vs. Shared
Number & Size of content databases
Size of My Site database
• Review Web.config for customizations
26. 26
Infrastructure
Central
Administration
• Authentication Methods (in Web App
Settings)
• Farm Structure
Service Configuration per server
• Deployed Features
Farm
Web App Features
What Services Applications Configured
Search Service Application
– Search Schema/ Customized?
– Content Sources (Can see if there is any separation
of site collections)
– Scopes/ Result Sources
Non-Standard Service Applications
(PerformancePoint, etc.)
Taxonomy (MMS)
Expectation for Office Web Apps
27. 27
Functionality
Manual Review
• View Most complicated site (Open in
SharePoint designer if possible)
• Review dates content was last
modified in View All Site Content
• 2007 or 2010 see if usage is turned on
and view latest reports
• Find workflows
• Identify 3rd Party Applications (Teleric,
Bamboo, Newsgator, lightning tools)
28. 28
Functionality
Pass/ Fail Tests
• Create a sub site within each site
collection
• Create a content type
• Create a page in the Pages and Site
Pages libraries
• Upload document
• Create an item
Rule of Thumb: If it has ever broken
before, test it
44. 44
What’s in a Job?
Migrating with Tools
Many migration tools
allow you to run jobs
for flexibility in
migration
• You don’t ever want to run a “full
migration,” i.e. send everything in one
job
• Jobs allow you to re-organize as you
migrate
• Jobs allow you some control in what
successful transfers vs. what fails to
fully transfer
• Your need for granularity in your jobs
will differ
• Different tools allow for different
capabilities around jobs
51. Migration Prep Migration
Test
Migration
Site Build
Out
Inventory
Redesign
Content
Clean
Up
Migrate
Redesign
Cutover Migration
51
Cutover/Training
NOTE: Most of the advice in this presentation is for a Cutover structure
53. Who Needs to be Involved?
Role Responsibilities
Project Sponsor Pays the bills, Defines scope/motivation, Gives a deadline for completion, could be Business or IT,
best if combination of both
Project Manager Coordinator of all the moving parts
IT Infrastructure Manages user authentication, technical infrastructure and architecture for the to-be system, supports
migration through usage of a migration tool
IT Application Development Builds out the to-be structure of the new SharePoint, provides migration of any custom applications,
workflows, system integrations. UI development and SharePoint configuration, manual clean up of
sites
Business Analysts Requirements gathering, inventory/audit capture, content clean up facilitation, SharePoint build out,
manual clean up of sites, can provide testing capability and migration validation
Training Coordinator Provides training and manages communication to end users during migration process
Business Sponsor Top down support for change management in the roll out of a new SharePoint environment
Content Managers Support inventory/audit, feedback and requirements for a new design, responsible for content clean
up in their site areas, user acceptance testing participants, require training prior to release of the site
End Users Receives communication on the roadmap for the migration, participates in training on the new site
53
64. Procedure Title Procedure Description Role(s) Responsible
Document Upload How documents are uploaded
directly to libraries
Trainer
Users
Document
Categorization
How to classify documents with
metadata
Trainer
Users
New site creation How to request new sites are
created
Project Manager
Administrator
Site Owner
Support How to request support. Portal
Project Manager
Administrator
Users
User Training Onboarding Procedure Trainer
Deployment Procedure How to request new features, web
part, applications
Project Manager
IT Dev Team
Policies & Procedures
65. Flexible
65
Original
Corporate
Portal
Departmental
Portal
Department & Team
Sites
Project Team Sites
Personal My Sites
• Controlled
• Tightly Governed
• Push Content
• Ad Hoc
• Loosely governed
• Push/ Pull content
• Permanent
• Dashboards
• Business Intelligence
• Business Process management
• Applications
• Permanent
• Knowledge Management
• Information Sharing
• Short Lived
• Collaboration
• Permanent
• Personal Information
• Public/ Private Viewed
69. 69
“A survey of corporate CIOs and general counsels
found that, typically, 69% of the data most
organizations keep, can – and should – be deleted.”
-Compliance, Governance and Oversight Counsel (CGOC) Summit
76. Restructure Information Architecture
76
Content
Types
Lists and
Libraries
Sites/Navigation
Site Collections/Navigation
Web Applications
Recommended!
Supports growth
and sustainability
Determines how
users navigate
to browse
content
Influences metadata,
templates, and
searching for content
Beware:
Beware of lack of
control of URLs in
O365
84. Additional Resource: White Paper
Leave your business card with Jill and
we’ll email you a complimentary copy of
7 Office 365 Migration Best Practices.
86. Plan to Leverage New Functionality
Your Files to Office 365. Simple. Fast.
Migrate Cloud Files to SharePoint Online & OneDrive for Business
http://www.metalogix.com/Products/Drive2Office365.aspx
87. 4 - Develop an Information Architecture (IA)
Evaluate current business process
Consider existing site structures
Departmental/team reorganization
Publishing requirements
Search/findability
Navigation
Content Growth
“Over half feel they would be 50% more
productive with enhanced workflow, search,
information reporting, and automated
document creation tools” 1
1 – The SharePoint Puzzle – adding the missing pieces, AIIM, 2012
88. Getting Ready to Migrate
Strategy & Inventory
Updated Information
Architecture & New Features
Prepare - Reorganization?
Prepare - Migrate, archive, or
leave behind?
Prepare SharePoint for migration
www.metalogix.com/products/Content-Matrix.aspx & www.metalogix.com/products/ControlPoint.aspx
90. Upgrade v Migration – In Microsoft Terms
UPGRADE: -The Physical
Transformation of a SharePoint
Content Database from one
Schema Version to the Successive
Updated Schema
MIGRATION: -The Physical Movement
of SharePoint Containers, Data and
Associated Attributes from one
SharePoint Farm to a new Farm
independent of SharePoint version
http://www.metalogix.com/Blog/Blog-Article/13-02-11/Yes_You_Can_Move_Straight_From_SharePoint_2007_to_SharePoint_2013.aspx
91. The Database Attach Upgrade
1. Farm Admin creates/configures new 2013 farm (no in-place upgrade for 2013)
2. 2010 DBs placed in read-only mode and copied to 2013 farm via SQL Server
3. Content DBs upgraded (but not site collections – remain in 2010 “mode”)
4. Service Application DBs upgraded
5. Site collections evaluated and upgraded by owners
The Out of the
Box Approach
92. The Database Attach Upgrade – Issues?
1. Farm Admin creates/configures new 2013 farm (no in-place upgrade for 2013)
2. 2010 DBs placed in read-only mode and copied to 2013 farm via SQL Server
3. Content DBs upgraded (but not site collections – remain in 2010 “mode”)
4. Service Application DBs upgraded
5. Site collections evaluated and upgraded by owners
The Out of the
Box Approach
What about SharePoint 2007 or 2003 or Office 365?
“Read Only” is not collaborative. How long can SharePoint be offline?
Lots of accidents waiting to happen? How long before something breaks?
Truly gradual? Change Management? SharePoint Sprawl? Future growth?
93. The OOTB – Where It Can Go Wrong
Potential Content Issues
Document Libraries with greater than 250,000 documents
• May fail therefore move to folders with 2000 documents in each
Remove excess versions of documents to increase speed
• Either Manually or Programmatically
Remove unused templates, features and web parts
• Stsadm commands to identify current use
94. The OOTB – Where It Can Go Wrong
Potential Database Issues
Sites Collections & Databases larger than 100GB will be slow and may fail
•Split Across Multiple Databases
My Sites should be moved to their own Content DB
Remove duplicate or orphaned site collections
•These can cause the DB attach to fail
Site Collection Limit per Content DB has Changed
•2,500 non-personal maximum but up to 10,00 possible in mixed use (personal + non-
personal)
95. The OOTB – Where It Can Go Wrong
General SQL Management & Performance
Issues
Upgrade Multiple Databases in Parallel
• Upgrading in Parallel can be slower than one at a time
Use Throttling
• Limit number of DB upgrades that happen at once
SQL Mirroring should be turned off
SQL Storage can grow up to 50% larger than Source DB size
• Must be recovered post upgrade
97. Advantages of a Migration Tool
Skip SharePoint versions e.g. 2007 straight to
2013
Site collection-specific vs. content DB
Reorganization, splitting sites & lists
taxonomy, permissions, content types
Re-template sites
Implement a customized migration or
upgrade strategy
Support for Workflow
98. Closing thoughts:
• A migration is a great opportunity to reassess your business
requirements and “spring clean”
• The most successful migrations are those that pay close
attention to the end user experience throughout
• Put as much control into the hands of your end users as
possible. After all, they own the content
99. eventmobi.com/sptcboston
Please take a moment to fill out the
class feedback form via the app.
Paper feedback forms are also
available in the back of the room.
Editor's Notes
Adam Edit
Adam Edit
Adam & Jill
Jill & Adam
Migrate from SQL Server in Azure VMs
Migrates 99% of content from Content DBs located
in Azure Virtual Machines
Azure Virtual Machines are physically next door neighbors to
SharePoint Online
Geographical distance is no longer an issue!
The Power of Automation
PowerShell allows consulting companies to automate the migration of thousands of Site Collections, Sites, Lists instead of migrating 1 at a time
Combining PowerShell with massive multi-threading creates a multiplier effect
Create master CSV file with all mailboxes and sizes
For Staged: combine large and small mailboxes
Coach users to reduce mailbox sizes
E3 plan has unlimited storage for users
Archiving leverages 2nd tier storage
Establish settings in Admin Center
Admin Center is similar to Exchange on-prem
Unified messaging
Built in protection
J – REPLACE WITH SCREEN CAPTURES IF INTERESTING
Migration presents an ideal time to assess the current SharePoint’s information architecture and to determine what should change.
IA izncludes the combination of Content, Context, and users. For example, a user opens a main landing page. Does this user see the right content? Is it within the right context? Should this user see this content and in this context? Or should this user be receiving something else in terms of content and experience?
IA considers how information – i.e., content – is design to “flow” to a user but also how a user flows to content.
A good example is Amazon. If navigating to the Amazon