You can modernize the MDM Hub objects, such as lookup tables, business entities, user roles, users, match rule sets, survivorship configurations, source systems, hierarchies, and relationships, and migrate them to MDM SaaS.
Data models
Data models define the basic structure of your master data. You can modernize the base object columns or business entity fields in the MDM Hub data models.
You can modernize the following MDM Hub objects associated with data model into MDM SaaS:
•Business entities. Modernizes the business entities and their fields or base object columns that you manually or automatically map. If a similar business entity exists in MDM SaaS, you can manually map the fields. If a similar business entity doesn't exist in MDM SaaS, you can create a new business entity in MDM SaaS.
•Reference data. Modernizes the lookup tables and their attributes in the MDM Hub based on the reference data mapping file. The modernization process maps the lookup tables with the corresponding code lists in Reference 360. For more information about reference data mapping file, see Reference data mapping file.
•Source systems. Modernizes the source systems based on the source system details available in the change list XML file.
Match rule sets
In the MDM Hub, match rule sets define the rules used to identify duplicate records. The match rule sets defined for the mapped fields in a data model mapping file are modernized and applied to the corresponding fields in MDM SaaS as Directed AI match rules.
If the mapped fields are used in match rule sets in the MDM Hub, you might find the corresponding Directed AI match rules in MDM SaaS after modernization.
Before you modernize the match rule sets, ensure that you understand the differences between match functionalities in the MDM Hub and MDM SaaS.
The modernized match models appear in draft state in MDM SaaS. Ensure that you review the match models before publishing them.If a match rule uses the Geocode field type as the candidate selection criteria, you might find multiple Geocode fields added in the candidate selection criteria of the match model after modernization. If multiple fields are used to generate match keys in the MDM Hub, the modernization process includes only the first field in the candidate selection criteria after modernization.The modernization process changes the preferred key width used in a fuzzy match rule from the MDM Hub to the standard key generation level.
The following table compares the match functionalities in the MDM Hub and MDM SaaS:
Functionality
MDM Hub
MDM SaaS
Candidate Selection
Match Column
Candidate Selection Criteria
Match Strategy
Exact
Fuzzy
Exact
Fuzzy
Merge Strategy
Automated
Manual
Automated
Manual
Skip
Threshold-based
Match Algorithm
Match Purpose
Match Criteria
Match Level
Conservative
Typical
Loose
Conservative
Typical
Loose
Merge Threshold
Not available
Available
Fuzzy Match Key Type
Not available
Available
Segment Matching
Available
Available
Null Matching
Available
Available
Candidate Filtering
Filtering based on SQL queries
Available through candidate selection criteria
Match Subtype
Available
Not available
Non-Equal Matching
Available
Not available
Hierarchies and relationships
Hierarchies define the parent-child relationships between records. For example, you can consider a relationship between employer and employee records as a parent-child relationship.
Non-hierarchical relationships are called as network relationships in MDM Hub and relationship graph in MDM SaaS. For example, you can consider the relationship between two family members as a non-hierarchical relationship. You can modernize hierarchies and relationships in the MDM Hub.
Note: After you delete a modernized hierarchy in MDM SaaS and create another hierarchy with the same name, ensure that you use a unique identifier value for the new hierarchy.
User accounts and user roles
Before you modernize user roles and users, ensure that you understand the basic principles behind modernizing these objects.
You can also modernize user accounts configured with single sign-on (SSO) in the MDM Hub. Additionally, you can't modernize user groups in the MDM Hub. By default, user roles in the MDM Hub that are mapped to custom user roles in MDM SaaS are assigned create, read, and update privileges on MDM SaaS business entities after modernization.
The modernization process uses the user role details from the MDM Hub configuration in the following ways:
•If you map a user role from the MDM Hub to a custom user role in MDM SaaS, the custom user role is updated with the privileges from the user role in the MDM Hub.
•If you map a user role from the MDM Hub to a predefined user role in MDM SaaS, the predefined user role isn't updated with the privileges from the user roles in the MDM Hub. You can't modify the privileges of predefined user roles in MDM SaaS.
•The MDM Hub users assigned to the user roles that you mapped are modernized to MDM SaaS. The users assigned to unmapped user roles aren't modernized.
The following table summarizes the modernization process for user roles in the MDM Hub:
MDM Hub User Roles
User Role in MDM SaaS
User Privileges in MDM SaaS
User roles in change list file.
The modernization process creates custom user roles in MDM SaaS based on the resource privileges of MDM Hub fields mapped in the data model mapping file.
The modernization process assigns the same privileges as the MDM Hub user role to the modernized custom user roles in MDM SaaS for the attributes. Also, it assigns create, read, update, and delete privileges for the business entities.
Note: You can review and modify the privileges after modernization.
User roles mapped to custom MDM SaaS user roles in the user role mapping file.
The modernization process creates custom user roles in MDM SaaS.
The modernization process updates the privileges of MDM SaaS user roles based on the privileges of mapped MDM Hub user roles. After modernization, you can review and modify the privileges as needed.
User roles mapped to predefined MDM SaaS user roles in the user role mapping file.
The modernization process maps the MDM Hub user roles to predefined user roles in MDM SaaS.
The modernization process retains the privileges of predefined user roles in MDM SaaS. You can't modify the privileges of predefined user roles in MDM SaaS.
User roles in the user account details file.
Based on the user account details file of the MDM Hub, the modernization process creates users and assigns them to the modernized user roles. The users who belong to the user roles that aren't modernized are ignored.
The modernization process assigns the privileges based on the user roles.