Partition Fields Discussion

Hopp requires all root Business Objects to have a Partition Field (which is why you cannot delete it). When data is actually being migrated in the Hopp Runtime environment, Hopp will use this field to partition the data by the value in this field.

It is then possible to decide which users have access to view the data for a given partition. While members of the migration team typically will have access to view the data for all partitions, it is possible to limit the access of external users (users from the business being migrated).

This comes in particularly handy if a migration project is migrating more than one business. For instance, if several Banks are migrating from one Banking System Provider to another in one migration project. Using this partition mechanism, Hopp will enable you to control that users involved in the migration from one bank will not be able to see the migrated data from the other bank(s).

Partitions Explanation

In some (rare) cases, more than one business may be migrated as part of the same project. That is to be kept separate but use the same mapping logic, flow and some common data. This typically occurs when different business units or legal entities are part of the same migration into the same target system(s).

An example could be multiple separate organizations that need to be migrated at the same time to the same target system using the same Target Map. In this case, all the businesses are exported from the current systems together and migrated by Hopp in one single project with different parts.

Each separate business being migrated in the same Project in this way is called a Partition.

(A side note: Even though two businesses can be said to be involved in a merger migration because one business is merged into the other, a merger only involves one partition).

Nevertheless, it is paramount that the entire migration setup can handle them when they do occur. For instance, the Hopp migration solution separates the data and Events concerning each partition and has authorization mechanisms in place to control that business users from one Partition (Organization A) cannot view data from another Partition (Organization B).