10.1 General Settings

Follow

General Settings contains settings controlling behaviour of migration jobs.  Such as how to manage Embedded Links, handline characters that are valid in the Source but invalid in the Target etc. 

 

Picture119.png

 

NOTE: Above is a subset of all settings. Prior to the migration processing you should review all of the settings available to ensure they are correct. 

Job Name: This was set during the initial job creation and can be changed here.

Update Embedded Links can be used to re-establish hyperlinks in well-known Source file contents with the new location of linked files in Target container while performing the migration. This feature is not mandatory for migrating content from Source to Target.

 

NOTE: Enabling this feature will make the migration significantly slower and requires Microsoft Office to be installed on the PMA server.

 

NOTE: When using this feature, it’s essential to take a two pass approach to the migration.  When in the migration phase, first execute up to Step 3-Transform ONLY.  This will generate the necessary information about the location items will be migrated to.  After this has been executed for all items, then Step 4 – Load can be executed and in doing so, this feature will replace the links within document types specified above with the new target information generated during step 3.    The reason why Step £ must be performed is to ensure that the target URL for all embedded items is known, before any migration which may refer to them takes place

 

The document types supported are: -

File Type Extensions
Word
  • .doc .docx
PowerPoint
  • .ppt .pptx
Excel
  • .xls .xlsx
Other .pdf .rtf

 

NOTE: Embedded links in encrypted/password protected items cannot be processed

 

Migrate items with Broken Embedded Links  

A document may contain a link to another item where the target URL is not/cannot be determined.  For example, referring to another document that has been deleted in the source or potentially not captured during the Discovery process.  Such links are termed Broken Links.  This setting controls whether items should be migrated even if it refers to an item where the Embedded link will no longer function in the target.  The default behavior is that such items would not be migrated.

Invalid Characters

Replace Invalid Characters: Targets often have different character limitations than the source so it may be necessary to replace such characters during migration to ensure the item is successfully migrated.  The Pre-Check feature will identify items containing invalid characters.

The default list of invalid characters is suitable for migrations to SharePoint Online.

Picture120.png

Replace with allows you to specify the character to replace any of the invalid characters specified. You can specify no replacement character, if required in which case the character(s) are removed.

Example An invalid filename like Help ? information.txt becomes  Help _ information.txt

File Handling

 

Picture121.png

 

Migrate Duplicate Files: If selected(default) then if an item with the same exists in the migration job, then during migration, a unique document name will be created by appending an auto incrementing number as a file name suffix.  If unselected, any duplicate items will not be migrated.

For example, 3 files with same name as Proventeq User Guide.pdf migrated to the same folder will be migrated with names of

  • Proventeq User Guide.pdf
  • Proventeq User Guide (1).pdf
  • Proventeq User Guide (2).pdf

Advanced General Settings

 

Picture122.png

 

Discovery

By default, after a discovery has begun, it’s not possible to edit the discovery filter.  This is because doing so could create inconsistent results.  For example having no filter and then adding a filter after initial discovery does not remove existing discovered items.  In some scenarios it can be useful to edit the filter, for example to correct a wrong filter value.  By selecting this option, it allows the Discovery filter to be edited even after discovery has started.

Load

By default, the processing stage ‘Step 4 – Migrate to Target’ cannot be selected in the Processing Screen if the “Update Embedded Links” option has been selected and not ALL items have been first processed up to the ‘Step 3 – Transform – Create Item Manifest’ step.  Selecting this option allows the ‘Step 4’ option to become available even if all items have not been transformed.  Note the consequences of selecting this option means that items will be migrated but may contain embedded links which have not been updated (because transform has not occurred for all items) and so will not point to the new location of migrated items.

 

 

 

 

 

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

Comments