Chat now with support
Chat with Support

Metalogix Essentials for Office 365 2.3 - User Guide

Metalogix Essentials for Office 365 User Guide
Administrator Architect Backup
Interface Overview Common Functions
Connecting to SharePoint and OneDrive for Business Connecting to Cloud Storage Global and SharePoint Administrators Hyper Backup Creating a Full Backup Creating an Update Backup Creating an Exchange Online Mailbox Backup Creating an Office 365 Group Backup Creating a OneDrive for Business Backup Backup Resume Backup Search Restore from Backup Scheduling Backup Jobs Retention Policies Import/Export Backup Archives Moving the Backup Location Backup Project Conversion
Drives
Interface Overview Common Functions
Connecting to Drives Copy Google Drive Copy File Share Copy My Sites to OneDrive for Business Copy Tenant Copy Box Copy Dropbox OneDrive Management Progress Tab Hyper Migration Path Length Overflow
File Manager Informant Migrator
Interface Common Functions
Connect to SharePoint and OneDrive for Business Global and SharePoint Administrators Copy Sites Live Compare Copy Lists and Libraries Copy, Move, and Tag SharePoint Content Copy Alerts Pre-Migration Report Azure Turbo Mode In-Place Tagging of SharePoint Items Incremental Copy Nintex Workflow Migration Orphaned Users Copy Preserving Content Authorship and Approve/Reject Statuses Save Site to XML Using Scripts and Integration With Windows Task Scheduler
Profile and Global Variables Public Folders for SharePoint Reporting and Re-Mapping Users and Templates Security Manager Term Store Manager Scripts Wizards Appendix

Incremental Copy

There are multiple scenarios where copying only incremental changes from the source environment to the target are preferable to create a full copy of all content.

Migrator supports incremental copying of content into both libraries and lists but there are several key differences when using the Incremental Copy feature (Advanced Options).
incremental copy

info

NOTE: The use of Incremental Copy has a significant impact on performance and it is recommended that users apply a filter (e.g. modified at, property is greater than migration date) to reduce the duration of this operation.

Libraries implement incremental copies using the file names. When the Incremental Copy option is selected any duplicate items on the target will be replaced with the source item.

Lists (unlike Libraries) implement incremental copies through an internal attribute (item id). This attribute is automatically generated and sequenced by SharePoint and cannot be overwritten. Therefore, a different approach is used to identify new and updated items, but the result is the same as for Libraries. Any duplicate items will be replaced with the source item.

The Incremental copy option has a filter that allows for the determination of the number and age of the changes that will be brought over during the incremental copy. By selecting the number of days, weeks, or months, you can choose to only bring over differences from the last full copy that was made in the determined time.

Delta Migration - If selecting "0" as the value for the incremental filter, the tool will do a content analysis of both source and target and bring over any content that is identified as differential. In the case of this migration, if a file exists on the source that is not on the target, said file will be copied to the target. In the event that the item exists in the target, the tool will check to see if the item on the source is newer than the one on the target (based off of the last modified date). If the item on the source is newer, then the item will be copied from the source to the target.

info

NOTE:

·This operation is extremely time, processor, and memory intensive as it has to scan every item on both your source and target environments. We only recommend using the "0" delta migration in cases where it is absolutely necessary. Otherwise, set a filter which will specify a time period for the comparison.

·Due to their inherit complexity, Wiki Page libraries and Discussion lists will not be processed during incremental or delta migrations.

Nintex Workflow Migration

Nintex Workflows are included when the option to Copy Workflows (Site or List) is enabled within Metalogix Essentials. The Copy Workflows option is available on the Properties page of most wizards.
nintex workflow 1

Or you can select any site or list that has a workflow associated to it, right click and select Object > Show Workflows.  From the Workflows view, you may select one or more workflows and copy/paste them to the destination location.  This process of copying one or more workflows does not include the workflow dependencies, so this method is recommended in situations only when all dependencies already exist in the destination and only the workflow and its components need to be migrated.
nintex workflow 2

Before you begin with an on-premise Nintex Workflow migration, please review the following requirements:

·The Nintex workflow solution must be installed, configured and working on the destination SharePoint environment prior to any migration.  If a Nintex workflow cannot be successfully created manually in the destination, then do not attempt to migrate them until this is resolved.

·If the Nintex workflow is migrated as part of a List Copy, please note that workflow dependencies will not be migrated.  Please make sure all dependencies already exist in the destination prior to the migration or copy of the workflow as part of a Site Copy operation.

·In progress workflow status, workflow history, and metadata are not currently supported.

·Not all Nintex workflow actions are available when migrating to newer versions, so please make sure you check with Nintex first if you believe an action is not supported.

Archive Option

Typically Nintex Workflows are included when the option to Copy Workflows is enabled within Metalogix Essentials, however there are some rare scenarios when this process fails.  If the workflow fails and the error message indicates that it failed due to exporting the workflow, please follow the steps detailed in the Nintex Workflow Archive Option section.

Nintex Workflow Migration to SharePoint Online

Nintex Workflow migrations to SharePoint Online (Office 365) are more specialized than those being migrated on-premises.  For additional information, please visit the Nintex Workflow Migration to SharePoint Online section.

Nintext Workflow Migration Archive Option

Typically Nintex Workflows are included when the option to Copy Workflows is enabled within Metalogix Essentials, however there are some rare scenarios when this process fails.  If the workflow fails and the error message indicates that it failed due to exporting the workflow, please follow the steps below to migrate this workflow individually.

This process is designed to copy just the workflow and the assumption is that all dependencies are already met in the destination either using the Essentiaals Copy Site/List function or an alternative method.

1.Open the workflow in question through your browser and choose the Export option.  This will create a *.nwf file that should be saved to your local computer.
Nintex-Workflow-Export

2.In Essentials, right click on the source site or list in the Navigator pane that is associated to this workflow and choose Objects > Show Workflows.
nintex workflow 2

3.Once all workflows have been loaded, you should see the Workflow that was exported in step 1.  Right click on this workflow and choose "Set Archive file".  Load the exported workflow (*.nwf) from step 1 and after that, the workflow name should be appended with (Archive).
Nintex-Set-Archive

4.Right click the workflow again and choose Copy.
nintex workflow 3

5.Navigate to the destination site or list in the Navigator pane within Essentials, right click on this object and choose Paste.

6.Modify the options as needed and click Finish to begin.

Nintex Workflow Migration to SharePoint Online

The migration of Nintex workflows to SharePoint Online (Office 365) is a different method than currently employed for on-premises.  The natural differences between on-premises vs online as well as the limited support of actions available from Nintex leads us to taking an alternate approach for these objects.

Requirements and Caveats

Before migration, please note the following list of requirements and caveats:

·The latest version of the Nintex Workflow App must be deployed and licensed in the destination SharePoint Online site before migration.  If you cannot open the Nintex Workflow Designer in your destination SharePoint Online site, create a workflow and successfully publish it, do not attempt to migrate into this location until this is resolved.

·The user authenticating against the destination SharePoint Online location must have Site Collection Administrator permission.

·Workflow status, workflow history and workflow metadata are not currently supported.

·User Defined Actions (UDAs) are not currently supported.

·If the workflow contains an "Action Set", please make sure to enable the destination site feature "Workflows can use app permissions" prior to the migration.

·Not all on-premises workflow actions are supported within the Nintex Workflow App.  Please take a look at the following table for the list of currently supported actions for SharePoint Online.  Please note that while the actions are mapped based on this table, the action label (it's name) will be retained from the source when viewed in Nintex Online Workflow Designer.  Please also review our General Workflow Objects page to learn about supported action parameters and other specific caveats.

·Make sure you setup and load the appropriate user mapping file so that any workflow actions that contain a user account will be mapped to the appropriate user in the destination.

Supported Nintex Workflow Actions in SharePoint Online

The following table lists the on-premises Nintex workflow actions that can be migrated into SharePoint Online.

info

NOTE: Even though an action may be listed as supported, that does not mean that all parameters in the on-premise action have an equivalent in its online counterpart.  Please be sure to review, test, and adjust where necessary all migrated Nintex workflows.  You may use this General Workflow Objects table as a reference to provide some examples of objects that may need adjustment.

On-premises Actions

Online Actions

Assign Flexi Task

Start a task process

Build String

Build String

Calculate Date

Add Time to Date

Change State

Set Next State

Check Out Item

Check Out Item

Convert Value

Convert Value

Create Item

Create List Item

Delete Item

Delete Item

Discard Check Out

Discard Check Out Item

End Workflow

Terminate Current Workflow

Filter

Filter

Log in History List

Log to History List

Loop

Loop with Condition

Math Operation

Do Calculation

Pause For

Pause for Duration

Pause Until

Pause until Date

Query list

Query List

Regular Expression

Regular Expression

Run If

Run If

Run Parallel Actions

Parallel Block

Send Notification

Send an Email

Set a Condition

Conditional Branch

Set Field Value

Set Field in Current Item

Set Variable

Set Workflow Variable

Set Workflow Status

Set Workflow Status

State Machine

State Machine

Switch

Switch

Update Item

Update List Item

Wait for item update

Wait for Field Change in Current Item

info

NOTE: If the workflow contains an Action that is not supported, this unsupported Action will be created as a Comment in the migrated workflow.  The comment will contain the name of this unsupported Action.

Related Documents