Meridio Source

The File and Folder settings are used to configure structure hierarchy of items that will be loaded to the target.

You can proceed with the default settings from this window or import a structured mapping CSV file.

Create a new Structured Hierarchy using Import Mappings

Structured Mapping or Import Mappings is an extensive feature used to create a new hierarchy on target which may or may not follow the source hierarchy. Here you can load child items/folders at an entirely different new location specified by you. Also, if child items structure mapping is not present / given by you then they will inherit the mapping of the parent.

This feature is not mandatory for migrating content from source to target. In this case, you can map Source Container to a Document Library or folder directly.

To import a Structure mapping CSV, you need to create a comma delimited CSV file with following columns as header:

1. SourcePathId - Source Path Value will be DocID
2. SourcePathType - Blank
3. SourcePath – Source URI Path/Blank
4. SourceTaxanomy - Blank
5. TargetPathId - Blank
6. TargetPathType - Blank
7. TargetPath - Blank
8. TargetSite – Site Name (System Name or Name in URL)
9. TargetSiteSettings – Blank
10. TargetLibrary – Library Name (System Name or Name in URL)
11. TargetLibrarySettings – Blank
12. TargetFolder – Path of the folder hierarchy under which item will be
13. TargetFolderSettings - Blank
14. TargetPathMetadata - Blank
15. TargetTaxonomy - Blank
16. TaxonomyMappingType - Blank
17. PathMappingType - Blank
18. MappingSettings – Specify either “Create” or “Merge” for source item loading option

PMA supports different type of structure mapping to facilitate your requirements, such as maintaining source hierarchy or to recreate target hierarchy.

1. Based on URI (Default Settings)
2. Based on DocID
3. Based on Metadata Expressions

You can select the structure mapping type from drop-down menu: 

Below is a sample Structure Mapping:

Please find sample structure mapping files at this location:

[Installation directory] \Proventeq\Proventeq Migration Accelerator\SampleFiles

Create file with Unique  Name

In the source system, we could have documents with a duplicate name within the same container (E.g. Folder). So, while migrating such documents, PMA supports a feature to create unique document name by appending auto incremental numbers to their names.

In order to use this feature, you need to select an option ‘Create a new file with unique name’ in the File and Folder Settings tab.

E.g. If we have a total of 3 files with the same name as “XYZ.pdf” then PMA will create unique names for them like below:

• XYZ.pdf
• XYZ (1).pdf
• XYZ (2).pdf

Fileshare Source

The File and Folder settings are used to configure structure hierarchy of items that will be loaded to the target.

You can proceed with the default settings from this window or import a structured mapping CSV file.

Create a new Structured Hierarchy using Import Mappings

Structured Mapping or Import Mappings is an extensive feature used to create a new hierarchy on the target which may or may not follow the source hierarchy. Here you can load child items/folders at an entirely different new location specified by you. Also, if child items structure mapping is not present / given by you then they will inherit the mapping of the parent.

This feature is not mandatory for migrating content from source to target. In this case, you can map a Source Container to a Document Library or folder directly.

To import a Structure mapping CSV, you need to create a comma delimited CSV file with the following columns as header:

1. SourcePathId - Source Path Value will be DocID
2. SourcePathType - Blank
3. SourcePath – Source URI Path/Blank
4. SourceTaxanomy - Blank
5. TargetPathId - Blank
6. TargetPathType - Blank
7. TargetPath - Blank
8. TargetSite – Site Name (System Name or Name in URL)
9. TargetSiteSettings – Blank
10. TargetLibrary – Library Name (System Name or Name in URL)
11. TargetLibrarySettings – Blank
12. TargetFolder – Path of the folder hierarchy under which item will be
13. TargetFolderSettings - Blank
14. TargetPathMetadata - Blank
15. TargetTaxonomy - Blank
16. TaxonomyMappingType - Blank
17. PathMappingType - Blank
18. MappingSettings – Specify either “Create” or “Merge” for source item loading option

PMA supports different type of structure mapping to facilitate your requirements, such as maintaining source hierarchy or to recreate a target hierarchy.

1. Based on URI (Default Settings)
2. Based on DocID
3. Based on Metadata Expressions

You can select the structure mapping type from the drop-down menu based on your requirements.

Below is a sample Structure Mapping:

Please find a sample structure mapping files in the following location:

[Installation directory] \Proventeq\Proventeq Migration Accelerator\SampleFiles

Duplicate File Handling

In Source system, there could be multiple documents with same name in the same folder.
Such documents can be handled by selecting one of the options in File & Folder Settings:-

Discard Files with Duplicate names

Such Items will be marked as failed and will not be migrated

Creating New File with Unique Names

PMA will create a unique document name by appending auto incremental numbers as a file
name suffix.

E.g If we have total 3 files with same name as “XYZ.pdf” then PMA will create unique names for them like below:

• XYZ.pdf
• XYZ (1).pdf
• XYZ (2).pdf

Container Creation Handling

Migration Accelerator allows container creation at modern site level. For this there is a
default provisioning in migration accelerator to assign a template for creating containers in
target.

Note: The site template name in site template details is set to “BLANKINTERNET#0” by
default for existing task. One needs to change it to “STS#3” to allow container creation
in target for SharePoint Online modern site.

Oracle UCM Source

Recreate Source Hierarchy

The File and Folder settings are used to configure structure hierarchy of items that will be loaded to the target.
You can proceed with the default settings from this window or import a structured mapping CSV file.

Create a new Structured Hierarchy using Import Mappings

Structured Mapping or Import Mappings is an extensive feature used to create a new hierarchy on the target which may or may not follow the source hierarchy. Here you can load child items/folders at an entirely different new location specified by you. Also, if child items structure mapping is not present / given by you, then they will inherit the mapping of the parent.

This feature is not mandatory for migrating content from source to target. In this case, you can map the Source Container to a Document Library or folder directly.

To import a Structure mapping CSV, you need to create a comma delimited CSV file with following columns as header:

1. SourcePathId – Source content or collection Id in Oracle UCM. For site it will be Site Id or Name E.g. Proventeq. For file content it will be Content ID E.g. PROV_032903 and for folder/collection it will be a Collection ID E.g. 609002818. For Content Type it will be fixed value -11111, since it is a virtual root considered for migrating all documents of that content type.
2. SourcePathType - Blank
3. SourcePath – Blank
4. SourceTaxanomy - Blank
5. TargetPathId - Blank
6. TargetPathType - Blank
7. TargetPath - Blank
8. TargetSite – Site Name (displayed in URL)
9. TargetSiteSettings – Blank
10. TargetLibrary – Display Name (displayed on UI)
11. TargetLibrarySettings – Blank
12. TargetFolder – Path of the folder hierarchy under which item will be
13. TargetFolderSettings - Blank
14. TargetPathMetadata - Blank
15. TargetTaxonomy - Blank
16. TaxonomyMappingType - Blank
17. PathMappingType - Blank
18. MappingSettings – Specify either “Create” or “Merge” for source item loading option.
19. CreateHierarchyIfNotExists –
    1. Set to “TRUE” to create the specified TargetSite/TargetLibrary/TargetFolder on target if they do not exist
    2. Set to “FALSE” so that item will fail if specified path does not exist

Below is a sample Structure Mapping:

Note that it is mandatory to select document library in “Content Type Mapping Settings” for relevant content mapping. Ideally, we should select the document library name as “Based on Structure Mappings”, if we have specified the library name in structure mapping file for relevant documents. Otherwise, you can select the specific document library in the target site collection for relevant content mapping and then you can skip to mention the same in the structure mapping file for relevant documents.