SharePoint uses three primary methods for categorizing content. The hierarchy of sites, lists and folders (which is similar to how file systems store files in folders), metadata (via content types and fields), and AutoTagging to tag or classify content for find-ability and filtering. The application has been designed to categorize content in bulk by leveraging one or all of these methods.
This section will walk you through the process of intelligently tagging content. Please refer to the section titled, Copy, Move, and Tag SharePoint, for additional information on moving or copying content into specific sites, lists, and folders.
1.Locate a list or library, containing the content you wish to classify, in the Navigator pane. Double-click on the list to load its contents into the Contents pane.
If the site containing your items or documents is not available in the Navigator pane, follow the instructions for Connecting to SharePoint in order to load it.
2.From the list of files located in the Contents pane, select all the files for tagging. Hold down the CTRL key to select multiple individual files or SHFT key to select multiple consecutive items.
3.Right-click on any of the selected files, and select the Tag option from the drop down menu. This will initiate the tagging wizard.
5.Once the tagging selections are made, press the Next button located at the bottom of the window. A summary screen will be generated asking you to confirm the operation. Press Finish to initiate the tagging. The application will complete the tagging process and provide a notification window.
·For the Migrator version of this wizard, users may select the "Create CSV File for Uploading, Tagging and Copying Files", which will create a CSV file that may be edited and used for tagging at a later time (see Copy and Tag SharePoint Items Using CSV).
·For Migrator version of this wizard, in the event any errors are thrown, you may reprocess any failed items after resolving the underlying issues.
·For lists with Content Approval enabled, an Approval Status field will be displayed. This field can be used to bulk approve/reject selected content.
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).
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.
·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 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.
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.
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.
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 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.
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.
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.
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).
4.Right click the workflow again and choose Copy.
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.