11.1. Migration Steps

Follow

Select the Migration option on the Migration Dashboard to display the migration steps.

 

Picture123.png

 

Picture124.png

 

Migration is actually a set of 4 sequential steps that need to be executed for each item.  Using the slider control you can select how many steps to execute.  This allows you to review the output of that step for the processed items, before continuing.

The output generated from a step remains with that item and is not re-generated even if that step is executed again. This means if step 2 (Classify) has assigned content type or step 3(Transform) has built the Item Manifest they will remain with that item, even if subsequent changes elsewhere have been made to migration settings (e.g. Structure mapping, content and security mappings).  It also means metadata captured in Step 1 is unchanged, even if such data is altered in the source system.

If steps 1 to 3 are run and the resulting output is not correct, then use ‘Undo’ option to delete this data. The ‘Undo’ option is only available once any step has been executed.

Use the Item Details screen to display the details of items in the Items List to view the output from these steps.

Step Verification
1 Items list shows source metadata content.  Ensure this is complete and correct.
2 On the Item details review the Source Content type
3 On item details, review target metadata properties. Target URL etc.
4 Review item in target location, content, metadata properties, access permissions if relevant.

To start processing, select the step by using the slider or clicking on the card and then select the Start Process option.

Migration Run Settings

  • Include previously failed Items Option

If selected, items that previously failed will be resubmitted for processing along with any items still awaiting migration.

  • Maximum number of items

Select number of items to be processed. 

  • Maximum number of threads

Defines how many items are processed concurrently.  The optimal value for this setting depends on various factors including the number of documents going into each site collection.  A higher number of threads gives better performance when you have fewer site collections with lots of documents in folders.

 

NOTE Processing can take several hours or more, depending on the amount of data and selected processing step.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

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

Comments