Informatica's MDM SaaS runs on the Intelligent Data Management Cloud with 360 applications for customer, product, supplier, finance and reference data.
Every Informatica cell carries its source number; the sources are listed at the foot of the page.
| Question | Informatica | Lima master data |
|---|---|---|
| Where the master data lives | Business entities, hierarchies and relationships are stored in the IDMC MDM service after ingress jobs or REST loads; egress jobs and business events publish golden records to warehouses and applications [1][2]. Salesforce positions Informatica as the 'Trust & Understanding' layer under Data 360 [3]. | Golden records are governed views over the sources, read in place through the federated engine, and materialised only where latency needs it, in your lake, under the same keys. The transactions sit in the same bed, so a merged customer and its orders change together. |
| Reaching SAP, Oracle and the lakes | Reads and writes go through IDMC connectors and the Secure Agent; the modernisation page moves on-premises customers to the cloud service [4]. Reviewers report that SAP and rare-system connectors carry separate licences [5]. | SAP S/4HANA and ECC through released read interfaces and change capture; Oracle Fusion through REST and BI Cloud Connector extracts, E-Business Suite through JDBC and open interfaces; Snowflake, Databricks and Fabric read in place; Salesforce, ServiceNow and Workday through their APIs. Write-back through BAPIs, IDocs, REST and web services, acknowledged and logged. |
| Golden record: matching and survivorship | Declarative exact and fuzzy rules plus an ML match model trained by labelling pairs; merge paths automatic, manual queue or threshold; cell-level survivorship with source ranking, recency and decay; unmerge of up to ten source records per request [2][6]. The MDM hub page markets 'AI-driven match and merge with rule recommendations and full explainability' [7]. | Strong keys first (VAT ID, DUNS, GTIN, manufacturer part number), then standardised attribute and address matching, with a language model for the hard pairs; two thresholds per rule (review, merge); survivorship per field by source rank, recency, verification and steward override; unmerge restores the sources; every value keeps its source, rule and time. |
| Hierarchies and reference data | Balanced, unbalanced, ragged and recursive hierarchies, with multiple hierarchies for the same entity; Reference 360 manages code lists, crosswalks and alternate hierarchies with versions [8][9]. | Levels and several hierarchies per entity, kept as versions with validity dates and validated against the facts they aggregate; reference data and crosswalks kept as small domains with the same history, rules and security. |
| Rules, security and audit | Field validations (length, range, patterns, dates), address and e-mail verification, and reusable data-quality rule specifications; record-level and attribute-level data access rules with conditional filters; a history page per record and an anonymise-history API [6][10]. | Column, row and business rules in one language, evaluated on save and on demand, including rules over aggregates and across tables; twelve security layers for read, write and delete; an append-only audit trail with point-in-time reads and logged reads of sensitive columns. |
| APIs and data services | REST business-entity APIs with PATCH, search, search-match (scores 0 to 100, HTTP 429 rate limiting), related entities (up to 10,000), job and export APIs, and business events; 'Headless MDM (APIs and MCP servers)' on the product page [6][7]. | REST, SOAP, SQL (JDBC and ODBC), events and an agent endpoint over one policy engine; the golden-record lookup answers with the record, the cross-reference and live related facts; page sizes and rate limits published per endpoint. |
| Analytics: pivots, measures, transactions | Dashboards cover hub metrics such as match analysis and usage; custom dashboards through Application Composer; analytics on transactions happens after egress to a warehouse [11]. | Pivots on any hierarchy level with time on the columns and measures in the cells; calculated measures; data entry with disaggregation by weights, equal shares or a time profile; drill-down from a cell to the transactions and to the source row; charts beside grids; natural-language and SQL querying. |
| Pricing unit and trial | Informatica Processing Units plus 'per-domain records' for MDM; the AWS Marketplace lists Multidomain MDM Cloud Edition at $699,000 per year for up to 3 million unconsolidated records; 30-day trials exist for twelve IDMC services and none for MDM [12][13][14]. | Platform capacity tiers (32C to 128C); domains, records, attributes and users included; the price is written before the work starts; a guided first domain on your data in one day; the showcase estate for demonstrations; a self-service sandbox tier is a decision pending (see the review notes). |
| Analyst placements 2025–26 | Gartner Magic Quadrant for MDM Solutions, April 6, 2026: Leader, 'highest in Ability to Execute'; Forrester Wave MDM Q2 2025: Leader with the highest Current Offering score [15][16]. | Analyst evaluation is the purpose of this page set; placements to date: none. The platform pages are organised on Gartner's eight mandatory features and four implementation styles so a briefing lands in the right market. |
Choose Informatica when the estate already runs on IDMC for integration, quality and cataloguing, when a Salesforce-led roadmap suits the customer domain, and when a hub copy with egress to the warehouse is the intended architecture. Seven Leader placements and the deepest connector catalogue are real advantages for a buyer standardising on one data-management vendor [15].
Lima suits the enterprise whose master data should be governed on the rows in place across SAP, Oracle, the CRM and the lakes, with the transactions in the same bed: the golden record and its orders in one query, rules over totals, pivots on golden dimensions with data entry and disaggregation, drill-downs to the source row, and a headless lookup that answers with live related facts. Twelve security layers and an append-only audit trail apply to every door, and the price is written before the work starts.
The domain catalogue shows thirty domains with, for each, the objects read in place in SAP S/4HANA, Oracle Fusion, Salesforce, Workday, ServiceNow, Snowflake and Databricks and the interface used for the write-back.
Facts change; re-check the sources at each review and re-date the page.
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.