📄️ Transformation (1a. Multiple Parents)
In some systems, such as Documentum, one RECORD can exist in multiple locations. If the target system does not support this, this flow can be used to split up records with multiple parents into individual records. The original record will remain at the location specified in source.parentIds[0] and migration.flags.originalParentIds will contain the original value of source.parentIds. For the other locations a RECORD is created with source.link referencing the original record.
📄️ Transformation (1b. Structure Mapping)
Warning: this flow will overwrite the target field when flow variable resetTarget has been set to true! Before running this flow, make sure the source.ancestors have been calculated. Check in the documentation of the source accelerator if it already calculates the ancestors. If not, use the Calculate Ancestors accelerator.
📄️ Transformation (1c. Exclude Content)
After setting the scope of the migration, additional rules for excluding content are configured here. As an example, this flow excludes configured content types as well as folders and their children based on configured identifiers.
📄️ Transformation (1d. Update Migration Flags)
Now that the full migration scope has been set, this flow will retrieve all excluded CONTAINER and RECORD objects and set migration.migrate to false for their non-current versions. Furthermore, all their related BINARY and AUDITLOG objects are also excluded.
📄️ Transformation (2. Transform Binaries)
In many systems, such as SharePoint Online, each RECORD object should have a BINARY associated with it. Furthermore, missing or zero-byte files can causes issues.
📄️ Transformation (3a. Metadata Mapping)
Warning: this flow will overwrite the target.contentType and target.properties fields.
📄️ Transformation (3b. Principal Mapping)
Warning: this flow will overwrite the systemName and displayName of target.created.principal and target.lastModified.principal for containers and records!
📄️ Transformation (3c. Permission Mapping)
Warning: this flow will overwrite the target.principals and target.permissions fields for ACL's!
📄️ Transformation (4a. Replace Invalid Characters)
This flow replaces target system specific invalid characters found in the target.name.systemName field of RECORD and CONTAINER documents. This is useful for ensuring that the target system does not encounter any incompatible characters that would cause issues in the load stage of the migration. The flow does update the target.hierarchies of the object, but not for its children.
📄️ Transformation (4b. Deduplicate Names)
This flow deduplicates the target.name.systemName for RECORD and CONTAINER documents within each container.
📄️ Transformation (4c. Long Name & Path Restructuring)
In certain systems there are limitations on the maximum number of characters an object name and/or path can have.