Seven paths from the hubs and habits enterprises run master data on today: SAP MDG, on-premises Informatica MDM, IBM InfoSphere MDM, Microsoft Master Data Services, TIBCO EBX, Oracle's E-Business Suite data hubs and DRM, and spreadsheets beside the ERP.
SAP ECC mainstream maintenance for enhancement packages 6 to 8 ends on December 31, 2027, with extended maintenance to December 31, 2030 at a surcharge.
The path →Salesforce completed its acquisition of Informatica on November 18, 2025.
The path →InfoSphere MDM 11.5 reached end of support on April 30, 2023.
The path →Master Data Services is removed in SQL Server 2025 and supported on SQL Server 2022 and earlier, so the database platform's next upgrade ends the free hub..
The path →EBX moved from Orchestra Networks to TIBCO in 2018 and, on March 26, 2026, into the autonomous Cloud Software Group unit ON EBX.
The path →Oracle keeps Premier Support for E-Business Suite through at least 2037, so there is no forced date.
The path →Most enterprises run master data on ERP screens and spreadsheets.
The path →| Event | Date | Source |
|---|---|---|
| SAP Master Data Governance | SAP ECC mainstream maintenance for enhancement packages 6 to 8 ends on December 31, 2027, with extended maintenance to December 31, 2030 at a surcharge; MDG on ECC moves with it, and MDG cloud edition is positioned by SAP as complementary, so the S/4HANA move is also an MDG re-platform decision. | Rimini Street: no extension to ECC 2027 deadline, updated Aug 14 2025; SAP Community MDG FAQ, checked Sep 17 2026 |
| Informatica Multidomain MDM (on-premises) | 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. | Salesforce completes acquisition of Informatica, Nov 18 2025; Informatica MDM modernization deck, Feb 18 2025 |
| IBM InfoSphere MDM | InfoSphere MDM 11.5 reached end of support on April 30, 2023; 11.6 runs on a five-plus-three support policy; IBM renamed its cloud-native Match 360 to IBM Master Data Management v5.3 on December 10, 2025 and calls it the next stage of the portfolio. | IBM support: end of support for InfoSphere MDM 11.5, Apr 27 2022; IBM announcement: from Match 360 to IBM MDM, Dec 10 2025 |
| Microsoft SQL Server Master Data Services | Master Data Services is removed in SQL Server 2025 and supported on SQL Server 2022 and earlier, so the database platform's next upgrade ends the free hub. | Microsoft Learn: Master Data Services overview, checked Sep 17 2026 |
| TIBCO EBX (ON EBX) | EBX moved from Orchestra Networks to TIBCO in 2018 and, on March 26, 2026, into the autonomous Cloud Software Group unit ON EBX; reviewers report instability after the version 6 upgrade and a third-party benchmark reports renewals above prior terms (unconfirmed). | Business Wire: EBX is now part of ON EBX, Mar 26 2026; PeerSpot reviews of TIBCO EBX (review site), Jun 2025 |
| Oracle E-Business Suite data hubs and DRM | Oracle keeps Premier Support for E-Business Suite through at least 2037, so there is no forced date; the pull is the move to Fusion, where customer data sits in CX, product data in SCM and hierarchies in Enterprise Data Management, each priced by its own metric. | Oracle Premier Support for E-Business Suite, checked Sep 17 2026; Oracle Fusion metric descriptions, Aug 26 2026 |
| Spreadsheets and ERP-only master data | Most enterprises run master data on ERP screens and spreadsheets: the ERP validates its own fields, the spreadsheet holds the mappings, hierarchies and the list of who owns what, and a second ERP or a CRM brings a second copy. There is no vendor date; the trigger is the next merger, planning project or audit finding. | Gartner press release: lack of AI-ready data puts AI projects at risk, Feb 26 2025 |
No. Versions, merges and decisions load into the audit trail with their dates and people, and point-in-time reads cover them.
The first domain follows the four-week plan on the first-domain page; a hub with several domains moves one domain at a time, consumers behind a router.
Yes; the side-by-side run is the normal pattern, and the old hub is retired when the last consumer has moved.
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.
