Metalogix Essentials for Office 365 2.7 - Release Notes

Metalogix® Essentials for Office 365 2.7

Release Notes

September 2020

These release notes provide information about the Metalogix® Essentials for Office 365 release.

·New Features

·Resolved Issues

·Known Issues

·Version History

·System Requirements

·Product License Keys

·Third Party Contributions

New features

2.7

Pre-Migration Report

New pre-migration report for SharePoint 2013 and 2016, which allows users to scan farms and generate a high-level report for review before starting a migration.

Profile Manager Redesign

Redesigned the Profile Manager's look and feel, providing users easier and more organized access from a centralized location for migration settings.

Additional support for SharePoint Online to SharePoint Online in Hyper Mode

Added support for migration using Export API, Copy workflows and forms, Copy regional settings, themes and templates, Copy checked in/out files.

Multi-language Migration Support

Ability to migrate content in various languages. We now support migration from English to other languages and vice versa, migration in non-English to non-English languages (tested Spanish, Italian, Korean, French, Portuguese, etc.)

Custom metadata columns in Fileshare migration to SharePoint Online

Newaddition to Fileshare to SPO migration which allows users to add custom metadata to a csv, which can then be uploaded as part of a migration. The additional column specified for the items will be added as a text column in SPO and the content will be uploaded.

Office 365 Groups Backup

Ability to create Office 365 groups backup using hyper mode.

Office 365 Groups Auto Provisioning

Ability to automatically provision groups as part of the migration process. ​

Convert 2010 to 2013 workflow style in SPO

Automatic conversion of 2010 workflow style to 2013 both from Navigator and hyper migration path.​

Migrate to Microsoft Teams channel from CSV

Added support for migration to Microsoft Teams channel by specifying the channel name in the csv file.

Validation for CSV for all migration​​​

Ability to validate CSV files for any incorrect values, after the user has uploaded the CSV, to avoid error after starting the migration.

Change to AES 256 algorithm for FIPS compliance

Updated the algorithm for encryption to AES 256 bit, due to this, after the upgrade the existing jobs must be re-created, and passwords should be updated for backup projects, and will need to re-enter proxy settings.

Create STS#3 for team site(no group) migration ​

Created the ability to provision modern templates during migration. As per Microsoft guidelines the functionality does not differ between a classic and modern template. It is also easier & faster to create STS#3 then STS#0 templates.​​​​

Discovery of various template types

Automatic discovery of all template types. For limitation in migration please see Template Limitation Scenario Guide.

Use of Microsoft Export API(AMR) for tenant migrations ​​​

Added support for Export API

Resolved issues

The following is a list of issues addressed in this release.

2.7

Known Issues

The following is a list of issues, including those issues attributed to third-party products, known to exist at the time of release.

·Nintex Forms/Workflow app should be installed before a list/library migration.

·Copy Nintex Forms is supported only as part of “Copy Site as Existing Site” because Nintex Forms app should be installed before site migration. Installation of O365 App at "Copy Site as new Site" or "Promote to New Site collection" is not supported as Microsoft does not allow automatic app installation in the tenant during site creation.

·out of place restore from Backups works inside one tenant only.

·Delete action does not remove snapshot from a hyper backup project stored on Amazon Storage with Custom Endpoint.

·Nintex Form migration is not available as part of Hyper Migration.

·Claims Connection goes to loop in some environments and the connection cannot be finished as a result.

·Modern page migration is part of groups to groups migration. For more limitations please refer to backlog Item #422888

·Migrating Chinese to Chinese tenancy:  

oAzure turbo does not work, as Microsoft does not support Azure containers in the Chinese tenant. As a result, Hyper mode migrations and backups work without Azure turbo.

oEnterprise file systems like Box, Dropbox and Google drives do not work in China.

GCC High Tenant migration:

oOnly works using OAuth connections

oBackup does not work

oOld type Script creation is not working, as there is no support for the OAuth connection type

Proxy Setting:

oBox, Dropbox and Google Drive do not support the use of PAC proxy

oConnection to AWS with PAC is not supported

·Provisioning of personal OneDrive's does not work when using the OAuth connection type.

·Migrating one large file of more than 10 GB results in the tool failing to read all the versions and failing to migrate using Azure.

Google Shared Drives:

oIndividual file/folder share permissions are not preserved upon migration.

oGoogle Shared Drives membership can be copied to Office 365 only when OAuth is enabled.

Language Migration

·Same Language Migration (ex: Italian to Italian)

oDuring new site collection creation we cannot create a new site in the default language present on the source tenant. The new site will always be created in English if the site is not found during migration.

·Claims is not supported for farm connections when performing a high level report.

·SharePoint Online to SharePoint Online Migration

o​​Custom doc template setting is not preserved as it does not work with tokens​

oNo admin pooling when connected via claims.​

oMaster page gallery is not supported.

·Migration of various template type limitation is mentioned in a Scenario Guide Article. ​