On 18 November 2025 Salesforce closed its acquisition of Informatica. On 27 March 2026 SAP announced its acquisition of Reltio and completed it on 7 May. Within six months, the two largest independent master data management platforms moved under the roofs of application platform vendors.
If your team is compiling a shortlist of MDM solutions right now, this is not trade-press trivia. It changes the question you need to answer before signing anything.
What actually happened
The Salesforce announcement is explicit about direction: Informatica’s master data management capabilities are to feed the Salesforce platform, with a single data pipeline running from MDM into Data 360, where it grounds Agentforce agents (Salesforce press release, 18 November 2025).
SAP makes a similar argument from the other side of the table. Reltio is to prepare data from SAP and non-SAP sources for AI use cases as part of SAP Business Data Cloud (news.sap.com, 27 March 2026 and 7 May 2026). SAP states that SAP Master Data Governance stays and continues to be developed, that the two products are complementary, and that the Reltio portfolio remains available standalone.
In the Gartner Magic Quadrant for Master Data Management Solutions published on 6 April 2026, the Leaders quadrant included Salesforce (Informatica), Reltio, Profisee, Semarchy and Stibo Systems. Two of those names are now parts of larger organisms.
Why this is an architecture decision, not a procurement one
An acquisition does not break a product. Reltio did not stop working in May, Informatica MDM did not vanish in November, and neither vendor has announced the end of anything. That deserves stating plainly before anyone starts worrying.
The issue lies elsewhere. A product roadmap owned by an application platform vendor tends, over time, to answer that platform’s needs first. This is our assessment rather than anyone’s announcement, but it rests on how this market has behaved after previous acquisitions. Investment follows the owner’s interest.
For an organisation standing entirely on one ecosystem, that is good news. Integration gets deeper and the path gets simpler.
The difficulty starts in mixed landscapes, which is what we see most often in practice: SAP at the core, an industry-specific system that arrived with an acquired subsidiary, a cloud warehouse, and a handful of applications with no intention of disappearing. In that setting, “who owns my MDM vendor” stops being a question about branding and becomes a question about whose requirements get served first in the release two years from now.
MDG and MDM are not the same thing
This question comes up in every conversation, and the naming actively misleads.
Master data management (MDM) is a category. It answers how you turn many records describing the same customer, the same material or the same employee into one trustworthy record, and how you keep it consistent across systems. The category covers consolidation, matching, deduplication, quality rules and distribution back to source systems.
SAP Master Data Governance (MDG) is one specific SAP product within that category, tightly bound to the SAP landscape. Its name emphasises governance: change requests, approval paths, validation rules and audit trail. MDG is strongest where the data is born and lives inside SAP.
The practical distinction: MDM is the problem, MDG is one answer to it. A very good answer when the landscape is SAP-centric and the organisation is ready for the process discipline MDG imposes. A weaker one when half the data originates elsewhere.
One more term deserves clarifying, because it appears in these conversations more than any other. A golden record is not a product or a module. It is an outcome: one record accepted as authoritative, with change history and provenance for every field. You can reach it in MDG, in Reltio, in an independent platform or in ours. You cannot buy it in a box, because it emerges from rules somebody inside the organisation has to settle.
Three questions worth asking before you choose
Where is your master data actually born? If the answer is “in SAP and only in SAP”, the SAP path is the natural one. If the answer contains the word “and”, examine how the candidate treats systems outside its owner’s family. Not in the marketing material, but on your own data.
What happens when the platform strategy changes? Groups acquire companies, and acquired companies bring their own systems. A master data solution has to outlive the current application map, because migrating a data model costs more than migrating an application.
Who inside the organisation settles the disputed rules? The most common cause of failure in master data programmes is not technology. Gartner estimated in December 2021 that more than 75 % of MDM programmes would fail to meet business expectations through 2025, pointing at scope and organisation rather than tool selection. If nobody holds the mandate to decide which version of a customer name prevails, no platform will supply it.
When our approach is the wrong one
We build SNOK MDM as a golden record layer above source systems, without replacing the ERP, with a single-domain pilot in four to eight weeks. So it is worth saying plainly when that is not the right choice.
It is not, when an organisation stands entirely on one ecosystem and is strategically moving further into it. The native tool will win on integration, and we will say so ourselves while running the project on SAP MDG.
It is not, at tens of millions of records with real-time matching requirements. That is the territory of platforms that spent years building exactly that mechanism.
And it is not, where nobody on the client side has time to own the data. An implementation without that role produces a clean master file that gets dirty again within a quarter.
“Master data is the spine. If it is dirty, the best AI model will produce rubbish faster and in greater volume. We start with the clean-up, not with algorithms.” — Kacper Wojciechowski, Team Leader Custom Development / AI, SNOK
What to do this quarter
If your organisation runs Informatica MDM or Reltio, there is no reason for sudden moves. There is a good reason to add a risk-register entry about dependence on the new owner’s roadmap, and to revisit it at the next renewal.
If the choice is still ahead of you, change the order of operations. Measure first: how many duplicates actually sit in one domain, and what they cost per year. Draw up the vendor shortlist after that. The reverse order tends to produce a platform chosen to match a demo rather than a problem.
We covered the longer view in our essay on master data after twenty years, and the scope of our work in this area is described on the Master Data Management page.
If you would like to size the problem on your own data before any purchasing decision, get in touch - measuring duplicates in a single domain takes a few days and requires no changes to your systems.