Chatee ahora con Soporte
Chat con el soporte

Metalogix Essentials for Office 365 2.5 - SharePoint Online to SharePoint Online Migration

SharePoint Online to SharePoint Online

Supported Structures for Migration

The following are supported structure for SPO to SPO migration.

Site Collection Templates:

·Team Site (classic experience) STS#0

·Team Site (no Office 365 Group) STS#3

List\Library Templates:

·Libraries (1. Document, Wiki, Assets, Pictures, Forms)

·Lists (Custom list, Calendar, Announcements, Tasks, Links, Contacts, Surveys)

Lists - Supported are outlined in Green, unsupported are outlined in Red:

spo to spo 1

Site Collection Administrators: (Default Logic, without checkbox)

Existing: Add all administrators from source to target. AdminPool: If migration admin(s) missed on source and target they must be added to source and target. After migration this migration administrator(s) must be removed (CSOM or azure sync). Original Admins on target should not be touched.

Creating: Source site collection primary admin must be used to create target site collection and all admins must be migrated to target. AdminPool: If migration admin(s) missed on source and target they must be added to source and target. After migration these migration admins must be removed (CSOM or azure sync)

Site Columns: (Default Logic, without checkbox)

Existing/Creating: New Columns must be copied to target with Column Groups. Already existing must not be removed and updated (do not change columns settings)

Site content types: (Default Logic, without checkbox)

Existing/Creating: New Content Types must be copied to target with Content Type Groups. Already existing must not be removed but can be updated with new columns.

List Columns: (Default Logic, without checkbox)

Existing/Creating: New Columns must be copied to target with Column Groups. Already existing must not be removed and updated (do not change columns settings)

List content types: (Default Logic, without checkbox)

Existing/Creating: New Content Types must be copied to target with Content Type Groups. Already existing must not be removed but can be updated with new columns.

Sub Sites (Add checkbox):

Existing: new sub site is created according to global settings, existing sub site must be updated according to migration settings.

Creating: new sub site is created according to migration settings.

Site Collection SharePoint Groups. (depends on Copy Permissions checkbox)

Existing/Creating: Existing groups on target must be updated with missing users from source SharePoint Groups.  Groups not found on target must be created with all source members. If a group was in the mapping file, it should be created with the same name from the mapping file.

Permissions: (One check box with all permissions: site, list, content, groups, permissions levels):

Existing\Creating: Add only missing nodes. Already existing must not be removed and not be updated (do not change permission level)  

Site Collection Storage Size: (Default Logic, without checkbox)

Existing: Skip message will appear in the event that there is no free space. This error appears for each file if there is insufficient space available.

Creating: Preserved from original source site collection.

Copy List Views:

Existing/Creating: Copy View from source, Existing views must be overwritten

Site Home Page URL:

Existing/Creating: Copy Home Page URL from source

Copy Workflows (One checkbox for all workflows for site and list: Nintex, OOB, SPD (platform 10,13)):

Existing: Add only new workflows. Existing workflows must be skipped.  

Creating: Copy Workflow from source

 

Site Collection Permissions Levels: (depends on Copy Permissions checkbox)

Existing/Creating: Existing Site Collection Permissions Levels must be ignored. New Site Collection Permissions Level must be created like on source.

Site Collection Features and Each Site Features (Default Logic without checkbox):

Existing/Creating:  Get Source Site Collection Activated Features and activate them on target site and site collection.  Already Active site collection features must not be touched.  

Not Supported Structures

The following Structures are not supported in SPO to SPO Migration.

·Preservation Hold Libraries are not supported

·Apply Defer Required Fields are not supported for Hyper mode

·Apply Convert Workflows to 2013 is not supported for Hyper mode
 
 

Supported Content for Migration

The Following content is supported for SPO to SPO Migration.

Files:

·Copy all types of files. Migration inside one platform.

·Copy large files (more 2 GB). The limit is set by SharePoint. Migration inside one platform.

·All metadata

·Versions

Pages:

·Site Modern Pages

·Wiki Pages

·Web Part Pages

·Core Properties

·Versions

OneNote:

·2 GB files

·No matter how and where they are created

·New OneNote and modified

·All metadata

·Versions

Items:

·With attachments and without

·All metadata

·Versions

·Copy ID not supported

Folders:

·Core Properties  

Herramientas de autoservicio
Base de conocimientos
Notificaciones y alertas
Suporte de productos
Descargas de software
Documentación técnica
Foros de usuarios
Tutoriales en video
Aviso de actualizaciones de páginas web (RSS)
Comuníquese con nosotros
Obtenga asistencia con las licencias
Soporte Técnico
Ver todos
Documentos relacionados