You can stratgize the modernization of the MDM Hub objects.
You can migrate the MDM Hub objects to MDM SaaS without changing their configurations, upgrade and enhance them to align with MDM SaaS features, or reimplement the objects in MDM SaaS. You can also use a combination of these strategies.
Use the following strategies to modernize MDM Hub objects:
•Reimplement. Recreate the MDM Hub objects in MDM SaaS. This approach may require more time and effort.
•Upgrade and enhance. Upgrade and enhance the MDM Hub objects to optimize them according to MDM SaaS.
•Migrate. Migrate the MDM Hub objects to MDM SaaS as is. To migrate the objects, you can use Business 360 Console or third-party migration tools.
You can choose the modernization strategy based on your business needs and on-premises MDM configuration. You can use Business 360 Console or third-party tools for migrating the MDM Hub objects to MDM SaaS. You can contact Informatica Global Customer support or third-party partners to follow reimplementation or modernization strategies.
Modernization strategy for data models
You can reimplement, upgrade, or migrate your data model objects, such as business entities.
If you use predefined business entities in your on-premises MDM, reimplement the corresponding predefined entities in MDM SaaS instead of migrating or upgrading them. If you use custom business entities, reimplement or migrate based on your business needs.
Modernization strategy for match rule sets
You can configure declarative rules in match rule sets for matching records in the MDM Hub. You can migrate these declarative rules from the MDM Hub to MDM SaaS using Business 360 Console or third-party migration tools.
You can configure Directed AI match rules, Adaptive AI match rules, or both for matching records in MDM SaaS.
Modernization strategy for survivorship rules and trust settings
You can migrate survivorship rules and trust settings from the MDM Hub to MDM SaaS. 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 field in the MDM Hub to MDM SaaS.
In the MDM Hub, you can configure survivorship rules for each field. However, in MDM SaaS smart fields and field groups are a single unit for which you can configure survivorship rules at the field group level.
Modernization strategy for validation rules
You can reimplement validation rules from the MDM Hub as data quality rules in MDM SaaS. Use Business 360 Console for creating basic rules and Cloud Data Quality for creating advanced rules.
Modernization strategy for user accounts and user roles
You can modernize user accounts and roles from the MDM Hub to MDM SaaS using the migration strategy.
Modernization strategy for data standardization and enrichment
To validate, cleanse, transform, standardize, and enrich data, MDM Hub uses Informatica Data Quality rules while MDM SaaS uses Cloud Data Quality. You can use the reimplementation strategy for standardizing and enriching data from the MDM Hub.
Modernization strategy for 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 and the mapping between staging and landing tables are handled internally without user intervention.
Modernization strategy for Business Entity Services
You can use Business Entity Services APIs to access external applications in the MDM Hub. To access these external applications, MDM Hub uses Enterprise JavaBeans, REST, or SOAP APIs. However, MDM SaaS uses only REST APIs for accessing external applications. You can use the Cloud Application Integration and reimplement the MDM Hub Business Entity Services APIs in MDM SaaS.
Additionally, the authorization and authentication process differs between the MDM Hub and MDM SaaS APIs. For more information about using REST APIs in MDM SaaS, see Business 360 REST API.
Modernization strategy for Service Integration Framework
You can use the Service Integration Framework APIs to access external applications in the MDM Hub. However, MDM SaaS doesn’t support Service Integration Framework APIs. You can use Business Entity Services in MDM SaaS to access external applications.
To access external applications through Business Entity Services, contact Informatica Global Customer Support.
Modernization strategy for subject area-based data models
Effective with MDM Hub version 10.4, subject area-based data models are deprecated. To modernize subject area-based data models, upgrade to 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 reimplementation, upgrade, or migration strategy. If the data model includes customizations, you can't modernize it to MDM SaaS because MDM SaaS doesn’t support customizations.