Presentation on Office365 FastTrack migration service for SharePoint 2013

1. dino@dato-on.com

2. Purpose
Understand

3. People
Migration
Service

4. Onboarding
Assessment
Remediate
Enable
Migrate

5. Customer qualifications
Source Platform
Source Content
Destination Platforms

6. Not to exceed:

7. Legacy sites in SP Online sites out
SharePoint 2013
• Custom site templates, pages, etc.
• Custom sandbox solutions.
• Coded workflows.
• Managed metadata *
• Any other customizations (check
remediation details).
• Site content. *
SharePoint Online
and OneDrive for
Business

8. Kickoff
• Eligibility
• Workshops
Assess
• Discovery
tools and
findings
• Plan and
approach
Remediate
• Customer
drives
• Microsoft
tracks
Enable
• Infrastructure
install and
configure
• Service
enablement
Migrate
• Migrations
rollout
Close
• Transition
• Sign-off
Ye
s
o
Prepare
First pass
migration
UAT Incremental
Final Reporting
& Go live
Migration phase overview
Repeating and overlapping migration waves
Provide site migration
schedule.
Upload content DBs (or
drive ship).
Provide user identity
mapping file before 1st
wave.
Provide site migration
schedule.
Invite specified users
to migrated sites.
UAT content &
function in
preparation for
incremental
migration.
Put source sites in read-
only mode.
Run 2nd pass incremental
migration on content.
Sites launched to end
users.

9. Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Week 7 Week 8 Week 9 Week 10 Week 11 Week 12 Week 13 Week 14 Week 15 Week 16
Week 1 – Kick Off Starts
Onboarding and Preparation
Week 3
Assessment Phase Starts
Typical durationis 2 weeks.
Might extend as well depending on total
data content to crawl and other
customer dependent activities.
RemediationAssessment Enable Pilot Migration
Velocity Migration
Week 16
Velocity Migration Starts
2 Weeks 4 Weeks 2 Weeks 3 Weeks
Customer Env Setup Test Migration
Week 13
Pilot Migration Starts
Week 9
Enable Phase Starts
2 Weeks for migrationenv. setup
2 Weeks for Sample/Test Migrations
Week 5
Remediation Phase Starts
Typical durationis 4 weeks.
Might extend/reduce as well depending on total remediation
activities and other customer dependent activities.
2 Weeks
Kick Off
Cloud Enable
FactorySetup
OptionalRemediation
Time
If on-prem remediation is
done/not needed, enable
phase starts early
2 Weeks

10. Pre-Migration
(T-1 week)
Microsoft activities
• Restore content DBs.
• Provide final list of site
collections.
• Validate target sites.
• Create target site
collections.
• Create job DBs and seeding
of jobs.
• Set up job scheduler.
• Run structure and
permission jobs.
• Enable/Disable workflow.
Customer activities
• Fix and respond to any pre-
validation failures escalated
by the Migration Team.
*Migration
(T-0 week)
Microsoft activities
• Run content jobs.
• Run navigation jobs.
• Run content validation.
• Run navigation corrections.
• Validate UIs.
Customer activities
UAT
(T+1 week)
Microsoft activities
• Support UAT – 4 days.
• Fix and respond to issues
reported by customer.
Customer activities
• Validate the migrated sites.
• Log issues in the tracker site
for Microsoft to review and
fix.
Incremental
(T+1 weekend)
Microsoft activities
• Run incremental jobs.
• Run content validations.
Customer activities
• Lock down source sites
before start of Incrementals.
Upload
(T-2 weeks)
Microsoft activities
Customer activities
• Provide the site mapping of
migration wave.
• Upload the content DBs of
migration wave to Azure.
• Provide User Mapping file, if
required.
Upload
Week 1
Prep/Pre-Migration
Week 2
Migration
Week 3
UAT
Week 4
Incremental Sync
Week 4 Weekend Go Live
* Pilot migration in 200GB waves. Velocity migration in 500GB waves.

11. Enterprise network
SharePoint 2013
Cloud-Hosted SQL VMs Migration infrastructure
and scripts
SharePoint Online and OneDrive for Business
1 2
3
Customer
migration
infrastructure
Storage blob
SharePoint
ContentDBs
Azure Blob
Containers
FastTrack Azure subscription
(dedicated to customer)
Customer’s Office 365 subscription
4
7
6
Migrator VPN
Hosts
(Jump Box)
5
Storage blob
Internet

12. SharePoint platforms
Source site definitions
1
2
Source service applications 3
Target

13. Will Migrate
Sites 1 Lists Items
Title Documents Versions (up to 5) 3
Logo Items Permissions and sharing
Theme (OOB only) Views
Navigation Content types
Content types 2 Managed metadata
columns
Site columns Permissions and sharing
Managed metadata terms (up to
200,000)
Declarative workflows 4
Pages
Web parts (limited)
Permissions and sharing
Quota
Property bag
Declarative workflows

14. Will NOT Migrate
Sites Lists Items
Web templates Workflow running instances or
history
Checked out or locked with no
checked in version
Custom user profile properties or
values
InfoPath forms
SQL Reporting Service Reports
Custom web parts, apps, event
receivers, and 3rd
party components Custom list forms (view/add/edit)
Files in draft version
Items are hidden (name starts
with _ )
Un-ghosted or customized pages IRM settings
Workflow running instances or history Recycle Bin (both stages)
Custom site branding, themes, design
packages, and definitions
Access request list
Site settings List Templates
Search settings Any Hidden list
InfoPath forms 1
Information management policies
Anonymous sites or pages
Usage reporting
1. Remediation requires
manual modification of
.xsn files to use SPO
schema for any InfoPath
associations

15. Will NOT Migrate
Publishing Sites
Master Pages
Page Layouts
Style libraries/ Java script files
MMS-based navigation
Retention Policies
Item level publishing setting
Field values for site columns
Remediation required by customer
before site goes live:
• Pages not rendering properly
• Pages not migrated due to
custom page layout, content
type
• Pages not migrated due to
custom webparts
• Page Version not correctly
migrated
• Navigation Links

16. Will Migrate
Sites Lists Items
Permissions and sharing Documents Versions (Up to 5) *
Items
Documents and folders
permission and sharing
Will NOT migrate
Sites Lists Items
MySites branding Workflows Checked-out or locked
Custom content types Custom columns
Custom columns Contents other than documents
Feeds, Alerts, Notifications

17. Will migrate
Service Applications Settings Other
Managed Metadata Terms 1
Will NOT migrate
Service Applications Settings Other
Access Services Vanity URLs Full-trust Code
Business Connectivity Services (BDC) Alternate Access Mappings Sandbox Solutions
Excel Services Custom managed paths 3rd
party add-ins or components
Machine Translation Service
Performance Point Service
PowerPivot and PowerBI Service
PowerPoint Conversion Service
Search Services
Secure Store Service
SQL Server Reporting Services
SQL Server Analysis Services
User Profile and Synchronization Services
Word Automation Service
Work Management Service
Visio Graphic Service
1. One-time full migration
only. Up to 20,000 terms.
Incremental Sync ???

18. More details on the Scheduling,
Communications, and Reporting
workshop
Migration Wave
Migrations are scheduled in a multi-pass approach:
Full migration during a week
Incremental migration during a weekend
Estimated migration throughput calculations:
Total Weeks = Total Size of Content / Migration Rate
where Migration Rate ≈ 500GB/wave
Actual migration throughputs are determined during pilot migration
Week 0 Week 1 Week 2 Week 3 Week 4 Week 5 Week 5+
Wave 1 Site Plan Database
Upload
Prep-Week Execute UAT Go Live
Wave 2 Site Plan Database
Upload
Prep-Week Execute UAT Go Live
Wave 3 Site Plan Database
Upload
Prep-Week Execute UAT
Wave 4 Site Plan Database
Upload
Prep-Week Execute

20. Get started quickly with assessment
here

21. What does SharePoint Migration Assessment Tool (SMAT) assess?
SharePoint 2013
Customer
Admin
SMATrunsona
SharePoint Farm
Internet
FastTrack
Engineer
Assessment
Results

22. What do we assess?
SharePoint 2013
Customer
Admin
SMATrunsona
SharePoint Farm
Internet
FastTrack
Engineer
Assessment
Results

28. Decision points to consider

29. • InfoPath forms
• Custom sandboxed solution packages
• Coded workflows
• Custom features
• Third party products
• Broken inheritance
• Custom site templates
• Customized master pages
• Items with many versions
• Large lists or libraries
• Managed metadata *
• Running workflow instances
• Alerts
• URLs & links
• Site collection settings
• Checked out files
• Workflow history
• Web parts
• Pages

30. Consider hybrid
Hybrid Solution Scenarios
Hybrid OneDrive for Business
With hybrid OneDrive for Business, users will be redirected to OneDrive for Business in
Office365 when they click the OneDrive link in SharePoint Server 2013/2016.
Hybrid site features
With hybrid site features, you can integrate parts of your site navigation between SharePoint
Server and Office365 for Enterprises.
Hybrid search
With hybrid search, inbound, outbound, and two-way search can be configured to allow search
results from SharePoint Online and SharePoint Server 2013/2016 on-premises - to be displayed
in either environment.
Hybrid Business Connectivity Services
With hybrid Business Connectivity Services (BCS), you can leverage your existing BCS solutions
to allow connections to your SharePoint Server 2013/2016 data sources from SharePoint Online
(not supported for version 1.0).
Hybrid Duet Enterprise Online
With hybrid Duet Enterprise for Microsoft SharePoint and SAP Server 2.0, users can view and
change information that is stored in an SAP application from within SharePoint sites.
Additional on-premises infrastructure configuration is required for hybrid solutions:
Azure AD
DirSync
S2S ACS trust
Firewall reverse proxy

32. Enable the service for migration
Customer planned activities
• Make sure Office 365 service enablement is completed, for example if Directory Synchronization or ADFS will be required,
assure these configurations are completed and working properly.
• Complete remediation as per the remediation plan and checklist.
• Provide remote access for the migration team.
• Complete pre-requisites for migration tool configurations.
• Plan for “pre” and “post” migration support with content owners and users.
• Finalize the migration schedule for both test and pilot migrations.
FastTrack Team planned activities
• Prepare source environment.
• Prepare Azure migration environment.
• Prepare target environment.
• Perform migration validations.

33. The migration management site is created within the customer’s SharePoint Online tenant. It is used to track, report, and help
coordinate key activities throughout the migration process. The site is implemented as a SharePoint-hosted app (SHA) for
SharePoint Online. The app includes lists and associated workflows.

34. There are three main lists in the migration management site.
1. The Migration Items list is the primary control list used for managing site collections
to be migrated. This list contains all critical information related to a site collection
being moved. This list is managed by the migration team.
2. The Issues list is the location where all issues identified during the content validation
stage of the migration are logged and acted on.
3. The Workflow Tasks list contains the tasks that have been assigned to content
owners or technical owners to validate the site.

35. fasttrack.office.com/driveadoption
Scenarios
Methodology
Communities
Resources