This is the fourth post of my series Insights into the development of migration-center 4. In the last post I showed you how to configure and run a scanner in order to read all the desired files and their metadata from the source system. In today's post I will show you how to organize your scan runs into so called migration sets. All further processing in the migration-center, i.e. transformation, validation, and import, will be based on a migration set. So the definition of a migration set is an important step in the whole migration workflow.
When you press the Organize icon in the main navigation bar, the client shows you the list of existing migration sets. You can use the icons in the command bar above the list to create, edit, copy, or delete a migration set.
A migration set defines the source and target platforms for your migration, as you can see in the screenshot below.
After you have chosen the platforms, you can define which files will be included in the migration set by selecting the appropriate scan runs from the list of available scan runs (a scan run is available if it matches the selected source platform and contains at least one file that is not assigned to another migration set):
And that is all you need in order to proceed with the next step in our migration workflow, the transformation of the source into the target object types.
As a migration-center user you might wonder where to filter and exclude source objects from the migration set. This is currently not possible at this stage of the development, but we will of course include this functionality in the final release of MC 4.0. So stay tuned and don't miss the next post where I will describe the completely redesigned transformation step.