Modernize On-Premises Objects > Modernize on-premises objects > Modernization strategies for on-premises objects
  

Modernization strategies for on-premises objects

You can choose a modernization strategy based on your business needs and on-premises MDM configuration.
Use the following strategies to modernize the MDM Hub objects:
If you choose either the migration or reimplementation strategy, use the same strategy consistently for all remaining objects. However, you can use the reimplementation strategy for objects that aren't supported by the modernization process.
The following table describes the modernization strategy for each object that the modernization process supports:
Supported MDM Hub Object
Description
Data models
Use the migration strategy to modernize data model objects, such as business entities.
Match Rule Sets
Use the migration strategy to modernize the data model objects.
The modernization process migrates the match rule sets based on the mapped fields in the business entities.
Survivorship Rules and Trust Settings
Use the migration strategy to modernize the survivorship rules and trust settings.
When you use Business 360 Console to migrate the survivorship rules and trust settings, the modernization process automatically migrates the rules and settings associated with each business entity field in the MDM Hub to MDM SaaS.
User Accounts and User Roles
Use the migration strategy to modernize user accounts and roles from the MDM Hub to MDM SaaS.
The following table describes the modernization strategies for unsupported MDM Hub objects:
Unsupported MDM Hub Object
Description
Data Standardization, Enrichment, and Validation
Use the reimplementation strategy for standardization, enrichment, and validation.
Use the Enrichment Validation and Orchestrator to validate, cleanse, transform, standardize, and enrich data in MDM SaaS by creating objective groups, objectives, and rule associations.
Siperian Mapping
In the MDM Hub, Siperian mapping manages the mapping between landing and staging tables. In MDM SaaS, the ingress process loads data from external applications to MDM SaaS and the mapping between staging and landing tables is handled internally without user intervention.
You can ingress data from the MDM Hub to MDM SaaS without reimplementing Siperian Mappings.
Service Integration Framework
MDM Hub uses the Service Integration Framework APIs to invoke the MDM Hub operations from external applications in real time. However, MDM SaaS doesn’t support Service Integration Framework APIs. You can use Business Entity Services in MDM SaaS to access external applications.
Use Cloud Application Integration and MDM SaaS APIs to perform MDM operations from external applications in real time.
Additionally, the authorization and authentication process differs between the MDM Hub and MDM SaaS APIs. For more information about MDM SaaS REST APIs, see Business 360 REST API.
Subject Area-Based Data Models
To modernize subject area-based data models, upgrade to the MDM Hub version 10.5 and migrate subject area-based data models to business entity-based data models.
You can then modernize these data models using the reimplementation strategy.