BARC Perspective – SAP Acquires Reltio

SAP has agreed to acquire Reltio, a cloud-native MDM platform with $185M in annual recurring revenue, to address a structural gap in its AI strategy. The deal, expected to close Q2 or Q3 2026, makes Reltio a core capability within SAP Business Data Cloud.

For SAP customers, the key questions are if this acquisition helps their data & AI priorities and architecture. For the broader market, this signals that context engineering has moved from concept to capital allocation.

What happened?

• SAP agreed to acquire Reltio, a cloud-native master data management (MDM) and context intelligence platform, announced March 2026. Deal terms were not disclosed.
• Reltio ended FY26 (January 31) with $185M ARR, 40% year-over-year bookings growth, material positive cash flow, and 200+ large enterprise customers. Essentially, Reltio showed multiple signs of being IPO-ready in a financial market that is not really favourable for SaaS-company IPOs right now.
• Reltio will become a core capability within SAP Business Data Cloud (BDC), while remaining available as a standalone offering, especially for non-SAP customers. Transaction close expected Q2 or Q3 2026, subject to regulatory approvals.

What is Master Data? Master data is the basic, long-term relevant business information of a company that is used consistently across different systems, applications and business processes. It forms the backbone of operational and analytical processes and ensures a uniform view of central business objects. In contrast to transactional data, which changes frequently, master data is relatively stable and serves as a reference for all data-related activities. Typical master data objects include customers, products, employees, suppliers, locations and accounts. The quality and consistency of master data is crucial for the efficiency of business processes, the accuracy of reports and analyses and compliance requirements. Effective master data management is therefore essential to ensure data integrity and provide the basis for sound business decisions.

Master Data Management: Master Data Management (MDM) encompasses the processes, data governance, policies, standards, and tools that consistently define and manage an organization’s critical master data. Its objective is to ensure a unified definition and usage of identical data. Concepts for achieving this include centralized, decentralized, and federated approaches, with exchange facilitated through a Master Data Management system that contains a reference to the existing master data.
For AI, MDM will develop further than unifying datasets to golden records: MDM will be a important piece in the puzzle of helping AI models to make sense of information that is scattered over many source systems to create a coherent, accurate picture of the reality.

Why is it important?

• SAP’s AI strategy had a visible gap. BDC, Joule, and Joule Agents require unified, governed master data across SAP and non-SAP systems. The context layer was the missing piece, SAP has already been working on the last year. MDM is an important part of this piece and SAP wins a lot of ground with this step. Without such a context layer, AI working across fragmented enterprise data produces results that cannot be trusted.
• BARC survey data shows that SAP customers are behind in terms of AI adoption: Only 3% of SAP Datasphere users deploy it for AI/ML workloads, against 57% for Snowflake and 50% for Databricks. Note: SAP BDC launched in February 2025 and is not yet reflected in this survey data, because most of our respondents had not yet migrated from Datasphere to BDC when they took part in the survey.
• SAP customers already work on MDM. The acquistion now complemented or (or might even replace) SAP’s own MDM capabilities provided with SAP Master Data Governance (MDG). SAP MDG has lost some of SAP’s attention over the last years. Now, the topic of MDM is given a more strategic focus and momentum within the SAP Ecosystem again.
• The impact extends beyond analytics into operations. Reltio improves data quality not just for analytical AI and data analytics workloads, but for the operational and transactional layer: Core business processes like procurement workflows, supplier management, and transactional agents running in production in the ERP system. This is where data errors are most costly and where entity resolution and golden records deliver immediate, measurable business value.
• One risk worth monitoring: as SAP progressively owns the process layer, semantic layer, master data layer, and AI orchestration layer simultaneously, switching costs could rise well beyond application migration alone. Organizations should assess whether this deepening integration serves their long-term flexibility, or gradually makes it harder to route SAP data to competing platforms.

What is Context Engineering? Context engineering is the systematic design of the data foundation that AI agents work from containing structured and unstructured data alike, metadata and properietary knowledge.

What’s interesting about it?

• The open architecture question is unresolved. SAP did a massive investment in the past year to deliver on the openness of Business Data Cloud. Reltio’s value is built on connecting data from various SAP and non-SAP systems. In the most probable scenario, SAP would use this technology to make migrating to BDC easier, but also to actively support their customers’ multi-platform strategies. In the worst case scenario, SAP could use this to build a SAP-bound master data layer that locks their customers SAP data in.
• Reltio’s value extends beyond BDC. While the deal positions Reltio as a core BDC and AI capability, its impact is equally significant for the broader operational ERP suite: S/4HANA, SuccessFactors, Ariba, and other transactional systems where master data quality directly affects process outcomes. Customers should evaluate Reltio not only as an AI data layer but as an operational data foundation across the full SAP landscape.
• Independent MDM vendors face a narrowing window. For Ataccama, Profisee, and others, the competitive logic has shifted. They may focus even more on Snowflake and Databricks customers in Ataccama’s case, and on Microsoft-centric customers in Profisee’s. Interestingly, this deal partially mirrors the strategic rationale behind Salesforce’s pursuit of Informatica that has been completed just two months ago.
• Integration of unstructured data. Reltio comes with capabilities to integrate unstructured data. This might open the world for SAP to integrate documents like PDF, DOCX and more with structured data in BDC and provide it there as enriched context to agents.

Implications for customers

• SAP customers: Reltio addresses a real, long-standing gap. Watch three things:
  
  • Can Reltio solve the challenge you are currently in? That might be a migration from BW to BDC. That might be setting up a multi-platform strategy or even the question how to leverage SAP and non-SAP data combined for Agentic AI.
  • How SAP prices Reltio (standalone vs. bundled).
  • Whether the platform retains genuine openness to non-SAP data sources. MDM value depends on covering the full data landscape, not just the SAP footprint. One migration mechanism worth understanding: data that is logically integrated through Reltio does not need to be physically migrated first! It remains accessible across systems in place. Virtual integration through Reltio makes the next migration step feasible without a full cutover, reducing the complexity and risk of moving to BDC or S/4HANA progressively.
• Existing Reltio customers (non-SAP): SAP has committed to maintaining Reltio as a standalone offering. Short-term continuity is secured. Track feature prioritization, performance and stability over the first 12 months post-close. Secure written commitments on roadmap continuity.
• One grounding point for both: Getting MDM done is more about the process, than the technology. Reltio can improve data quality for analytics and AI. It does not replace clean processes, clear data ownership, or disciplined stewardship in ERP, CRM, and operational systems.

Analyst quotes

• This acquisition is a strategic one. SAP is buying a critical piece for the data foundation to back up its AI promises towards customers and shareholders.
  — Florian Bigelmaier, Analyst, BARC
• Reltio’s relevance is not limited to the analytics and AI pipeline. The platform improves master data quality where it originates: in operational ERP, CRM, and procurement workflows. That is where data errors are most expensive, and where the real enterprise impact begins.
  — Timm Grosser, Senior Analyst, BARC
• This acquisition will result in improvements for SAP on the side of operational processes, SAP’s main business, but also in the data and AI world.
  — Dr. Carsten Bange, Founder & CEO, BARC

BARC’s view

The SAP-Reltio deal makes the clearest argument yet that context engineering has been accepted as a necessary practice to scale Agentic AI. SAP is acquiring the layer that determines whether its entire AI portfolio delivers. Additionally, it acquires software that could simplify migrations to SAP BDC. For customers that use several SAP and non-SAP applications, it may also ease the pain of stitching records (e.g., of customers, suppliers, …) together.

The outcome for customers depends on execution: Whether Reltio’s multi-vendor, open-architecture positioning survives integration, and which direction SAP takes in developing this strategic solution. Organizations that have not yet mapped their master data strategy to their AI ambitions should treat this as the signal to start.