migration-center 4.0 Insights – Transform
The Analyze and Organize steps in migration-center 4.0 are pretty much the same as in migration-center 3, except for the new user interface, of course. In today’s post, I will show you the new Transform step. There you will see some fundamental changes in the way we handle objects and their transformation rules.
One major change in migration-center 4.0 is that we now handle all relevant source objects like documents, folders, relations etc., as distinct objects. Thus, if you scan an OpenText Documentum source repository, your scan run can contain different types of objects, e. g. documents, folders, relations, and audit trails, as you can see in the screenshot below.
After you have created your migration set, you can start working on the transformations. First, you have to choose the mapping between the source and the target object types. Since a migration set can now contain more than one source object type, you have to do this for each source object type in the migration set.
And this is how the new transformation view looks like.
We have removed the need for explicit associations between target attributes and transformation rules because in mc4 you define the transformation rules directly on the target attributes. A practical side effect of this is that there is no explicit validation step either. Transformation and validation are done in one single operation.
Back to the transformation rules. To create your custom transformation rules, add the desired custom target object type in the object types list on the left first.
Now you can select an attribute in the tree and start adding transformation functions in the main area.
mc4 supports the same transformation functions as mc3. But the handling of the transformation functions is much easier. For example, you can now use common Windows functionality like drag and drop and copy and paste in order to arrange your functions.
The Source, Processed, and Error Objects tabs allow you to quickly look at the source objects and the results of your transformations.
In the next and final post of this series I will describe the import step of the migration process.