HowTo: create and configure Attachment content type mapping in Hummingbird to SharePoint Migration

Follow

Please refer below steps to create an Attachment custom content type and map it to DocumentSet content type. We have do this custom content type mapping because Migration Accelerator will migrate Hummingbird attachments in a DocumentSet along with its primary document.

  1. Create a custom content type named “Attachment” as shown below and by using given PS Script.
    Please Refer to the section “5.5.4 Custom Content Type (Source Classification)” in the user guide to understand the steps how to create a custom content type classification.

    attachment-content-type-1.png

    PowerShell Script:

    If($MigrationItem.SI.EntityType -eq "Attachment")

    {

    return $True

    }

    else

    {

    return $False

    }

  2. Create a content type mapping for Attachments -> DocumentSet as shown below:

    attachment-content-type-2.png

    • Refer below screenshot for “Title” field mapping by using Metadata based mapping.

      attachment-content-type-2a.png
    • Refer below screenshots for “Created” and “Modified” fields function mapping by using an existing function “Get-SourceItemValue”.

      attachment-content-type-2b.png

      attachment-content-type-2c.png
    • Refer below screenshot for DocumentSet’s “FileLeafRef” metadata field by using script mapping.

      attachment-content-type-2d.png

      PowerShell Script:

      return 'Attachment_' + $MigrationItem.SI.ItemName

  3. Click on “Close” button to save “Attachment -> DocumentSet” content type mapping.

 

 

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

Comments