Salesforce completed its acquisition of Informatica on November 18, 2025; the on-premises Multidomain MDM line sits beside a cloud service with a modernisation programme, and Informatica's own migration guidance notes that history data stays behind in a move from the on-premises hub to the SaaS service and parks in a lake.
| Informatica MDM | Lima master data |
|---|---|
| Base object | domain in the catalogue |
| Xref table | cross-reference, kept as a join |
| Match rule set and thresholds | match rules with two thresholds |
| Trust and validation rules | survivorship per field; column and row rules |
| Hierarchy Manager | versioned hierarchies |
| IDD subject area | grids and forms in the golden view |
| SIF services | REST, SOAP and SQL data services |
| HIST tables and merge history | the append-only audit trail, loaded with history |
A high-tech company with three base objects (customer, product, supplier) and 2.4 million xref rows kept the on-premises hub running while Lima read the same sources in place. After eight weeks the two golden sets agreed on 99.3% of records; the differences were reviewed as proposals. The history tables loaded into Lima's audit trail with their dates, so the merge history was searchable after the cut-over.
They move behind a router one at a time: SOAP consumers get a generated WSDL, SQL readers get views with the same names, API consumers get REST with the same shapes.
Yes, read-only, for as long as your retention policy needs; its history is already searchable in Lima.
The inventory: the count of domains, sources, rules, hierarchies and consumers, written before the work starts.
Bring two systems that hold the same customers, suppliers or materials. In one working day we connect them, run the match on live rows, review the queue with your steward and publish the first golden view with its API.