Modernize On-Premises Objects > Modernization process > MDM Hub objects in the modernization process
  

MDM Hub objects in the modernization process

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:

Match rule sets

In the MDM Hub, match rule contain the rules that 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.
If a source system is configured as a distinct source in the MDM Hub, the match process doesn't match records within the same source system. However, records from a distinct source system match with records from other source systems. When base object tables or business entities in the mapped files have distinct source systems configured, the modernization process migrates them to MDM SaaS.
The modernized match models appear as drafts in MDM SaaS. Review the drafts before publishing them.
When you review the draft match models after modernization, you might observe the following changes:
Before you modernize the match rule sets, ensure that you understand the differences between match functionalities in the MDM Hub and MDM SaaS.
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
Based on SQL queries
Available through candidate selection criteria
Match Subtype
Available
Not available
Non-Equal Matching
Available
Not available
Distinct Source Systems
Available
Available

Supported Populations

You can modernize business entities that use different populations in their match model configurations.
The following table describes the populations supported by match model configurations during modernization:
Population
Description
Arabic
Contains the Arabic Standard script for the Arabia population.
Arabic_m
Contains a mix of Arabic, Romanized Arabic, English, and Arabicized English scripts for the Arabia population.
Arabic_r
Contains the Arabic Romanized Standard script for the Arabia population.
Argentina
Contains the Argentina Standard script for the Argentina population.
Australia
Contains the Australia Standard script for the Australia population.
Belgium
Contains the Belgium Standard script for the Belgium population.
Brasil
Contains the Brasil Standard script for the Brasil population.
Bulgaria_c
Contains the Bulgarian Cyrillic Standard script for the Bulgaria population.
Bulgaria_r
Contains the Bulgarian Romanised script for the Bulgaria population.
Canada
Contains the Canada Standard script for the Canada population.
Chile
Contains the Chile Standard script for the Chile population.
Chinese
Contains the Chinese Standard script for the Chinese population.
Chinese_i
Contains the Traditional Chinese Standard script for the Chinese population.
Chinese_r
Contains the Chinese Romanised Standard script for the Chinese population.
Chinese_s
Contains the Simplified Chinese Standard script for the Chinese population.
Chinese_t
Contains the Traditional Chinese Standard script for the Chinese population.
Colombia
Contains the Colombia Standard script for the Colombia population.
Croatia
Contains the Croatia Standard script for the Croatia population.
Czech
Contains the Czech Standard script for the Czech population.
Denmark
Contains the Denmark Standard script for the Denmark population.
Estonia
Contains the Estonia Standard script for the Estonia population.
Finland
Contains the Finland Standard script for the Finland population.
France
Contains the France Standard script for the France population.
Gaelic
Contains the Gaelic Standard script for the Gaelic population.
Germany
Contains the Germany Standard script for the Germany population.
Greek
Contains the Greek Standard script for the Greek population.
Greek_l
Contains the Greek Mixed Standard script for the Greek population.
Hebrew
Contains the Hebrew Standard script for the Hebrew population.
Hk_r
Contains the Hong Kong Romanized Standard script for the Hong Kong population.
Hungary
Contains the Hungary Standard script for the Hungary population.
India
Contains the India Standard script for the India population.
Indo_chin_r
Contains the Indo-China Standard Standard script for the Indo-China population.
Indonesia
Contains the Indonesia Standard script for the Indonesia population.
International
Contains the International Latin-1 Standard script.
Ireland
Contains the Ireland Standard script for the Ireland population.
Italy
Contains the Italy Standard script for the Italy population.
Japan
Contains the Japan Standard script for the Japan population.
Japan_r
Contains the Japanese Romanized Standard script for the Japan population.
Kazakhstan
Contains the Kazakhstan Standard script for the Kazakhstan population.
Korean
Contains the Korean Standard script for the Korean population.
Korean_r
Contains the Korean Romanized Standard script for the Korean population.
Luxembourg
Contains the Luxembourg Standard script for the Luxembourg population.
Malaysia
Contains the Malaysia Standard script for the Malaysia population.
Malta
Contains the Malta Standard script for the Malta population.
Mexico
Contains the Mexico Standard script for the Mexico population.
Netherlands
Contains the Netherlands Standard script for the Netherlands population.
New Zealand
Contains the New Zealand Standard script for the New Zealand population.
Norway
Contains the Norway Standard script for the Norway population.
Peru
Contains the Peru Standard script for the Peru population.
Philippines
Contains the Philippines Standard script for the Philippines population.
Poland
Contains the Poland Standard script for the Poland population.
Portugal
Contains the Portugal Standard script for the Portugal population.
Puerto_rico
Contains the Puerto Rico Standard script for the Puerto Rico population.
Romania
Contains the Romania Standard script for the Romania population.
Russia
Contains the Russia Standard script for the Russia population.
Singapore
Contains the Singapore Standard script for the Singapore population.
Slovakia
Contains the Slovakia Standard script for the Slovakia population.
South_africa
Contains the South Africa Standard script for the South Africa population.
Spain
Contains the Spain Standard script for the Spain population.
Sweden
Contains the Sweden Standard script for the Sweden population.
Switzerland
Contains the Switzerland Standard script for the Switzerland population.
Taiwan_r
Contains the Taiwan Romanised Standard script for the Taiwan population.
Thai
Contains the Thai Standard script for the Thailand population.
Thai_r
Contains the Thai Romanised Standard script for the Thailand population.
Turkey
Contains the Turkey Standard script for the Turkey population.
Uk
Contains the UK Standard script for the UK population.
Usa
Contains the USA Standard script for the USA population.
Vietnam_r
Contains the Vietnamese Romanized Standard script for the Vietnam population.

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:
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.