1. How the SharePoint Online
Migration API Works
Manoj Mittal
Technical Architect
MCP, MCTS, OCP, MCSA
Blog :- http://manojmittalblogs.blogspot.in/
2. Agenda
Manual Approach
Tool Based
How SPO Migration API Works (Online & OneDrive)
How to analyze the estimation based on content type
Impact of Document Versions & Multiple Domains
4. MOSS
2007
SP2010 SP2013 SP2016
Attach Detach the Content Database
Note:-
1. 50-60 GB Content takes 4-5 Hours
1.1 Backup the Database
1.2 Copy
1.3 Site Upgrade
1.4 User Upgrade
1.5 Mount the Database at next environment.
2. Server & Software Licensee cost for each environment.
5. Tool Based
Moss2007
SP2016 /
Online
Note:-
1. Cost associated with Tool
2. Continuous running Jobs
3. Support Incremental Migration
4. Pre & Post Migration Check Reports
5. Analyze Matrix Report
Direct Migration, Without going through incremental versions i.e.
Sp2010, Sp2013
7. Manual Approach
SharePoint
2013
SharePoint
Online
Using .STP Files (List & Libraries) –
Schema & Content
Content Migration using Excel Export &
Copy -Paste
Content Migration using MS-Access
Moss2007 &
SP2010
.STP Files doesn’t
Supported
Note- .STP doesn’t work with Publishing Site and Publishing
features and We used for Custom List & Library
19. 19
19
Limitations
Description ( SharePoint Online ) Recommendation
Package size 2-4 GB
File size 2 GB
Target size Target site should remain non-accessible to users until migration is
complete
SharePoint Online limits SharePoint Online and OneDrive for Business: software boundaries and
limits SharePoint Online: software boundaries and limits
Resource (Azure) Default/Limit
TB per storage account 500 TB
Max size of single blob container, table, or queue 500 TB
Max number of blob containers, blobs, file shares, tables,
queues, entities, or messages per storage account
Only limit is the 500 TB storage account
capacity
Target throughput for single blob Up to 60 MB per second, or up to 500
requests per second