spo migration - new api

Migration to Cloud – New Approach

Page

PresenterAshish Trivedi (@ashuetawah)Office 365 & SharePoint specialistWith Readify• Ex-MS Technical Consultant• Presenter in Office Dev Camp with Microsoft• Contribution to OfficeDev PnP

Migrating The Collaboration TriangleVery high

High

Medium

Low

Effort:

On-Premise | SPO | Hybrid | Azure

Security and metadata

Folders and files

Workflows

Features

Site structure

Custom UX

CodeRemove or rewrite

Replace

Transform

Rehost

PLA

Migration Process

PreparePlan

MigrateAdopt

Implementation

Goals:

Review applications and content by scale and complexity distributionReview recommended targets supporting the application and content scale and complexity distribution

Review processes and tools to migrate applications and content

Review skills and effort to migrate applications and content

Current State

Future State

Migration Path

Migration Factory

Speed? The Type of content does impact the rate

of ingestion Using Backend Resources Lots of small, scenario specific, tweaking

that can help get the best out of the API Preliminary data suggest 5X the speed of CSOM before throttling.

Source

Package

SharePoint/ODBFinal Destination

Azure Temporary Storage

Process Overview

File Share,SharePoint On-Prem,Potentially any other Data Source.

Create Package for the API to be able to accept it.

Use the Power of ingestion of Azure to bring the content faster in Microsoft network.

Timer Job Based import in a scalable way that will not hurt the service using back end resources.

SPO Management Shell Commands

New-SPOMigrationPackage[/Export-SPWeb]

ConvertTo-SPOMigrationTargetedPackage

Set-SPOMigrationPackageAzureSource

Submit-SPOMigrationJob

New

Convert

Set

Submit

What you need?

•Azure Subscription•Azure storage account•Office 365 with• Existing active directory O365 integration with on-

premises environment•Normal user added to O365

•SharePoint Online Management Shell MSI

Flow

New-SPOMigrationPackage

Flow

Export-SPWeb

Flow

ConvertTo-SPOMigrationTargetedPackage

Flow

Set-SPOMigrationPackageAzureSource

Flow

Submit-SPOMigrationJob

User Mapping

UserMapping.csv

CSOM

public ClientResult<Guid> CreateMigrationJob(Guid gWebId,string azureContainerSourceUri,string azureContainerManifestUri,string azureQueueReportUri

)

Limitations

• Azure• TB per storage account – 500 TB• Max Size of blob (blob/queue)– 500 TB• Target throughput for single blob – up

to 60 MBPS or upto 500 requests per second• Max number of blob container, blobs,

file shares – only limit is 500 TB storage account capacity

• SPO• Package size – 2 -4 GB• File size – 2 GB • Target size – target site should remain

non-accessible to end user till migration is complete.• SPO Limits apply

Demo

Q & A

Thank you