Mike Maadarani is an architect, trainer, and presenter with over 20 years of experience in app development and architecture. He provides consulting services focused on enterprise content management, search, and publishing sites. This document outlines the key steps in a SharePoint migration lifecycle including analyze, plan, execute, assess, and sustain. It discusses analyzing content, systems, and custom code, planning the target structure and remediation needs, executing the migration of services, sites and content, assessing the new environment, and sustaining it over time. People knowledge, realistic timelines, and commitment are identified as keys to a successful migration project.

1. Mike Maadarani
MCM Consulting

2. Welcome & Introduction
Mike Maadarani, Ottawa
• App Dev and Architecture for over 20 years (17 Years Microsoft, 3
Years with the “Other Guys”)
• Business focused on Enterprise Content Management, Search, &
Publishing Sites
• Architect, trainer, and presenter
mike@maadarani.com
www.maadarani.com @mikemaadarani

3. GOLD
Thank You Sponsors!
RAFFLESILVER
PLATINUM

4. Cloud
Process
Agenda
Closing and Q&A
Content & Apps
Overview
Migration Life Cycle
Hybrid

5. History recap

6. 2006

7. 2007 – 2012: Revolutionary Trends

8. SharePoint 2013

9. SharePoint Evolution to 2016

10. Should I upgrade?

11. Overview
What is Migration?
• The movement from one location (Source) to another
location (Target)
What is IT Migration?
• People, Hardware, Software, Systems, Data, Information,
Business Processes, Applications, Services
What is Information Migration?
• The movement of documents, metadata, taxonomy and
structure, security, and business process logic

12. Should I upgrade or migrate?

13. Migration/Upgrade Lifecycle
Analysis Plan Execute Assess Sustain
SOURCE
File Share
Exchange Public
Folders
Lotus Notes
Web Content
SharePoint
Other LOB Systems
TARGET
SharePoint Online
SharePoint On-
Premises

15. Analyze: Decision Points
• Content Analysis
• File Shares
• Exchange Public Folders
• Notes Databases
• Existing SharePoint farms
• Web Content
• Other lines of business applications
• Who is involved?
• Stakeholder(s) (Accountability)
• Business Drivers (Awareness)
• Information Technology (Accessibility)
• Individual(s) (Owner)
• Where is our content?
• Hosted or In House
• Centralized or Decentralized
• Local or Abroad

16. • Content Analysis
• How much content? How large?
• How many layers? (Web Applications, Site Collections, Sites)
• Content Types, Metadata? CTH?
• Security Levels
• Workflows
• Linked Information
• M.U.D.R (Systems and Content)
• Maintain
• Upgrade
• Dispose
• Replace
Analyze: Decision Points

17. • Service Applications Analysis
• Search
• Managed Metadata
• Secure Store (must be done before BCS)
• BCS
• User Profiles
• PerformancePoint
Analyze: Decision Points

18. • Custom Code
• WSP
• Event receivers
• Apps (if 2013 to Online)
• Workflows
• Etc…
• 3rd Party Tools
Analyze: Decision Points

19. • Action Items
• Roles and Responsibility Matrix
• Content Inventory Worksheet
• Security Report
• Decision: Build or Buy migration tools AND services
Analyze: Action Points

20. Step 2
Plan your battle

22. Private Cloud
Full Access
Farm Solutions
Sandbox Solutions
$$
Expensive to run
Expensive to maintain
Traditional
We know what we know
We expect innovation and great new features

23. Azure
VMs for you needs
If you’re used to a virtual environment, you’re ready for Azure
A few quirks
Full Access
Farm Solutions
Sandbox Solutions
$$
Pricier
Not clear on upfront cost

24. SharePoint Online
Limited Access
No Farm Solutions
Limited Sandbox Solutions
More script and CSOM code is being added
$$
Totally based on access
AND “seats”
Usually cheaper that the other options
Features and Support
New Features come online first
Updates are almost every quarter
Good support from MS and the partners

25. Hybrid Solution
Online + On-premises
Online + Azure
Azure + On-Premises

26. Upgrade Scenarios
Gradual
Upgrade
Database
Attach
Upgrade
In-Place
Upgrade

27. • Usually cheaper that the other options
• All Content databases
• All content databases
• Search administration
• BDC
• Managed Metadata
• PerformancePoint
• Secure store
• User Profile databases
Database Upgrade

29. Identify SPO Gaps
Federation
Midsize Business plan or higher for AD integration
Midsize, Enterprise E1 or higher for Yammer
Migration costs
Based on size and number of items
Lots of vendors, some are the same core engine
Farm Features
Farm solutions are not supported in Office 365
Need to know what is in the farm, and where they are being used, to create a remediation plan
3rd party solutions
App Store is rich with many solutions

30. • Most companies have
content that is:
• Out of date
• Duplicated
• Difficult to find
• Would benefit from:
• delete/archive/migrate triage
• reorganization
• tagging with metadata
Real world content

31. Plan: Decision Points
• Where will the content go?
• Web Applications
• Site Collections
• Sites
• Pages
• Libraries
• What will the content do?
• Policy Management
• Business Process
• Search ability
• Metadata
• Communicate and Train!

32. • Why is remediation required?
• What to remediate?
• How to remediate?
Remediation

33. Why remediation is required
Some customizations:
Cannot be migrated as is
Some content:
Cannot be migrated
Should not be migrated

34. Content remediation

35. Customization remediation
Branding
Solutions
Provisioning
Solutions
Content Types and
Site Columns
User Interface
Components
Other Built-in
Functionalities
Integration/
Maintenance
Solutions

36. Use OneDrive For Business
• Migrate your MySite and personal files
Personal Sites must be created first before you migrate
Bulk migration requires an account to be added to the personal sites
Use PowerShell to add a migration account to the admin group for
individual personal sites
Remove when done with migration
Bulk Site creation is available through CSOM API

37. Execute your migration

38. Choosing your migration approach
Self-service migration
• Manual
Tools-based migration
• Manual/auto using
tools
Complex migration
• Includes custom
code
• Involve experts

39. Migrate your Service Applications First
Steps to migration

40. Service Apps
Online
• Search
• Consider Hybrid Search
• MMS
• You want to consider 3rd party tools
• BCS
• You need Hybrid environment
• PerformancePoint
• PowerBI, PowerView
• User Profile  O365 Groups Profiles
• AD Sync
On-premises
• Search
• Consider Hybrid Search
• MMS, Secure Store, BCS,
PerformancePoint, User Profile
• Consider DB Upgrade

41. • The migration to the cloud must be performed
remotely
• User identities are different
Migration considerations

42. • Do you really want to migrate?
• Use OOB if possible
• Rebuild if needed
• Test against trial content
• Finalize and lock down code deployment
Execute: Code Migration

43. • Triage your content
• Assess
• Reconfigure your scripts/strategy
• Try again
• Follow your Plan
• Divide and Conquer
• Delta Migration
Execute: Content Migration

44. NO migration is 100% success
Execute: Content Migration

45. • Assess your content
• Re-run migration for missing content
• How is the current state performing/growing?
• Storage
• Security
• Performance
• Event Log
Assess: Action Points

46. • What is your disaster recovery plan?
• SPO, No action
• On-Premises, Plan and implement a DR site
• Turn off old farm, but do not kill it
• What are our growth metrics?
• How we will manage issue tracking and support?
Sustain: Action Points

47. In Closing

48. • Analyze
• Plan
• Schedule
• Communications
• Hybrid strategy
• Triage the content
• Remediate
• Migrate
• Assess
• Sustain
Recap

49. Keys to success
• People
• Source system knowledge (System X)
• Target system knowledge (SharePoint Online)
• Knowledge
• Development
• Knowledge management
• How to structure the data
• Realistic timelines
• Commitment
• Strong steering committee