6.1 - Execution Steps

6.1.1 - Discover Items 6.1.2 - Pre-migration Checks
6.1.3 - Processing 6.1.4 - Synchronization
6.1.5 - Reset Items 6.1.6 - Erase
6.1.7 - History  


6.1.1 - Discover Items


The Execution view is divided into 2 sections

Migration Tasks – where all the user created migration tasks are visible with the
number of items to be processed in each task. The count will be 0 prior to discovery
but will show the total items discovered post discovery.

Task details – This section shows the details of the selected migration task. This
section is split into four distinct areas
a. Execution - This Execution screen parted into:
i. Discovery - to discover what is on the source system. This is the first
step in migration. Once the item discovery is complete, the items can
be verified by clicking on “Items Explorer” button.
ii. Pre-Migration Check - to check erroneous items/contents from
iii. Process - to process the items and load them onto the target system.
This step can be executed only after the Discovery has been run at
least once and at least one item has been discovered.
iv. Post Process – to perform post-processing actions on items to be
migrated. This will be mainly used to process shortcut links or resolve
links based on items migrated in Process stage.
v. Reset – to reset the items uploaded to target system, so that they can
be reprocessed.
vi. Erase – To delete the items migration-staging database. Ideally, it
should be done after Reset if items are processed. After Erase user
has to redo Discovery of the items in order to migrate them.
b. Items List
c. Items Explorer
d. Show Graph


Discovery and Analysis

Discover Items

Select a migration task from the ‘Migration Tasks’ panel on the left. Click the “Discover” button in the ‘Discovery’ area and the select "New Discovery" from the dialog box.



Migration Accelerator will start discovering items from the source system and record their status in the staging database repository.



Note: Any modification done to the source items after Discovery has completed will not be reflected in the application until a new Discovery has been run. See the Synchronisation section for information about delta discoveries.


6.1.2 - Pre-migration Checks

The pre-migration check feature identifies any potential issues with the discovered items that might affect your migration. You can start the pre-migration check by selecting the "Check" button from the Content Analytics section of the Execution tab.

This will then present you with a screen to configure the check parameters, this allows you to modify the rules if you have any custom requirements.



Once you're happy with the settings you can click the "Run" button to begin the Pre-Migration Check.



This feature performs the following checks against SharePoint/SharePoint Online Site
Collection configuration based on the rule:
1. Blocked Characters in Filenames – Illegal characters in the source file/folder names.
2. Disallowed Extensions – An extension that is prohibited in the target system.
3. Max File Size – The file size exceeds the limit supported by SharePoint/SharePoint
4. Max characters in filename – The item name’s length exceeds the
SharePoint/SharePoint Online limits.
5. Max characters in folder name - The length of a folder name exceeds the
SharePoint/SharePoint Online limits.
6. Max URL length for items – The URL/Path length of a parent container exceeds the
SharePoint/SharePoint Online limits.
7. Max URL length for containers – The length of the item’s URL/Path exceeds the
SharePoint/SharePoint Online limits.
8. Maximum items in folder – The folder contains more items than is permitted within
SharePoint/SharePoint Online.
9. Maximum major versions per document – The major versions of the document.
10. Maximum minor versions per major version – The minor versions per major version.
11. Temp file extensions – These are the temporary files of the source.
12. Items with no name - Checks whether the Item Name is blank.
13. Items with same name as another item in a folder- Checks whether the Item Name
is duplicate.
14. Items with name mismatch across version - The Item Name differs over versions of
a document.
15. Items with differing extensions across versions – The file extensions/formats vary
over the course of a document’s versions.
16. Content referenced by multiple folders The Item is filed/present in multiple folder
17. Items with empty (zero byte) content - The Item has an empty file binary, meaning
that no content exists.
18. Items that have been deleted or marked for deletion – The Item is marked as
deleted in the source system.
19. Items with content type mismatch across versions – The content type varies of a
document’s versions.

20. Unsupported version labels – The version of the documents which are not
21. Empty Folders – Checks folders which are empty.


The results of the check can be seen in the Power BI report.

6.1.3 - Processing

After successful discovery of all items present in the source system, click the "Process" button in the ‘Processing area’ in order to start the content migration. This will launch the processing parameters popup window in which you can configure the processing parameters.

The available parameters cover:

  1. Process to stage –The migration goes through below processing stages, so one has to select appropriate target processing stage from below list:
    1. Capture Metadata – This stage captures metadata of all the items from source system.
    2. Classify – This stage performs content classification of all items based on content type mapping defined in migration task settings. This stage may retrieve content if required in order to perform content classification.
    3. Filter – This stage applies item filter rule in order to skip certain items in migration.
    4. Extract – This stage performs an extract operation on source metadata if any.
    5. Transform – This stage mainly transforms source metadata to target metadata by executing different metadata mapping rules. This stage may retrieve content if required in order to perform transformation.
    6. Load – This stage retrieves content if not obtained in earlier stages and performs upload of content and metadata on target system.\
Note:To process internal links within document it is mandatory to do transformation first then load. Maximum file size for the document should be less than 2 GB.
  1. Type of items to process
    Here you can find the Process Errors flag which tells the application to reprocess any items that had failed previously.
  2. Throttling parameters
    This section allows you to throttle the application either performance or item wise.
    1. Maximum number of items to process – Allows you to select the maximum number of items that will be processed in the processing run.
    2. Maximum number of threads – Allows you to select the maximum number of threads to use during migration, in simple terms this is the number of concurrent item loads that can occur at a time. Increasing the thread count corresponds with an increase in through-put but can lead to a higher load on the migration and target systems.

Once all processing parameters have been selected click the “OK” button to start the migration or click the “Cancel” button to cancel the processing.

Upon clicking the “OK” button the application will start processing each item based on the mapping rules that you have defined. The progress of the migration will be displayed in the processing dialog screen as shown below.

The "Successful items" count shows the number of items that have successfully processed up to the target stage in the current processing run.

The "Errors" count shows the number of items that have failed in the current processing run.

If you have enabled package processing you will see the number of items successfully packaged on the left hand side, once these items have loaded onto the target and been verified the success count will go up appropriately.



6.1.4 - Synchronization

Proventeq Migration Accelerator supports one-way synchronization from Documentum to Office365 /SharePoint.

If source contents are changed after particular task discovered and/or processed, then user needs to re-discover the same task to synchronize the updated items on the source system. Then user need to do pre-migration checks followed by processing and post processing on newly added or modified items.

In Synchronization or Delta Processing, using packaging, Original document which is modified will be deleted from target in the first processing attempt and then in subsequent processing attempt, they will be migrated.


6.1.5 - Reset Items

The ‘Reset’ functionality is available to remove any items loaded on to the target system by the application.

From the ‘Processing’ area in the ‘Execution’ tab, click the ‘Reset’ button. This will pop up a “Configure Processing parameters” screen where user can select the number of items to reset and the number of threads to execute this action. Click the “Ok” button to initiate the Reset action.




On completion of this process all relevant items will be deleted from the target system

Reset Items – Progress dialog



Warning: This action will delete all of the content loaded by Migration Accelerator as part of the selected migration task. The user can however re-run the load to reload the items if required. This action will not delete any items that were not originally loaded by Proventeq Migration Accelerator.

6.1.6 - Erase

Clicking on the “Erase” button deletes all of the discovered items related to the selected Migration Task from the database. Any data loaded to the target will remain as is however the application will no-longer know whether it had loaded them. It's advisable to perform a “Reset” to rollback the loaded items from the target before clicking on the “Erase” button, alternatively if an “Erase” operation has already been done the has already been done the items can be manually deleted from the target.

Start erase of selected task


Erase items


6.1.7 - History

A ‘History’ button is available on each area for Discovery and Processing. Clicking on this button brings up a screen that list all of the actions that were performed on that migration task along with date the action was performed and the outcome of that particular action.



Was this article helpful?
1 out of 1 found this helpful