Data 360
Informatica is part of Salesforce now: what it changes for your Data 360 plan
Salesforce closed the $8B Informatica deal in November 2025, and by May 2026 it was 'Informatica from Salesforce.' The pitch is a trusted data foundation for agents. The practical question is narrower: does it change what you build in Data 360 this quarter? Mostly no, and this is the part that does.
Salesforce closed its acquisition of Informatica on November 18, 2025. The deal was signed the previous May at $25 a share, about $8 billion in equity value. By May 2026 the product line had a new name, “Informatica from Salesforce,” pitched as the trusted data layer under Agentforce.
If you run Data 360, you are now told that what you bought grew a data catalog, a governance suite, a data-quality engine, and a real master data management product overnight. Most of that is roadmap.
The decision in front of you is smaller than the announcement. For almost every org, Informatica changes nothing about what you build in Data 360 this quarter. You keep going.
The one thing worth doing now is deciding whether the MDM and governance gap you were already going to hit gets filled with Informatica or with something you buy today. That call has a longer lead time than a data stream.
What Salesforce actually bought
Informatica’s platform is IDMC, the Intelligent Data Management Cloud. It bundles several products, and five of them matter to a Salesforce shop.
Data integration is the ETL and ingestion engine. Data quality is the profiling, cleansing, and standardization rules. Data governance and cataloging is a metadata catalog with lineage and business glossaries. Master data management is the golden-record engine for products, accounts, suppliers, and finance data. CLAIRE is Informatica’s AI layer sitting across all of it.
Data 360 already does some of this, and does it well. It ingests, unifies profiles through identity resolution, runs transforms, and tracks lineage natively. The overlap is real, and it drives most of the confusion.
Here is the clean way to separate them. Data 360 links your records into a unified profile so you can activate and ground an agent. MDM masters your records into a governed golden record you can defend to an auditor. Those are different jobs.
I wrote the full split between Data 360 and MDM before this deal closed, and the acquisition collapses none of it. Salesforce owning an MDM product does not turn the unified profile into a golden record. It means the golden record now has a first-party option.
What is shipping, and what is a slide
Be precise about state, because “Informatica from Salesforce” spans products at very different maturity.
Available now: the MDM Extension for Databricks, which publishes trusted golden records from Informatica MDM into a Databricks lakehouse through the Databricks Marketplace. CLAIRE in Slack, which lets someone invoke data discovery, quality, and governance actions from a Slack prompt. And Informatica’s own stack, GA for years, still running as its own platform with its own console.
In preview or on the roadmap: Headless IDMC, the API-first version meant to embed inside Salesforce surfaces, was in private preview with GA targeted around mid-2026. The Data 360 Connector and Scanner promise real-time, bidirectional flow between enterprise systems and Data 360 with end-to-end lineage. They are the connective tissue the whole story depends on, and the newest pieces of it.
Treat any capability described as “unified metadata for Agentforce” or “a single MDM pipeline on Data 360” as a direction, not a switch you flip in Setup this week. Verify the current status against your instance’s release notes before it goes in a plan, because these dates move.
You are buying two things, and confusing them will wreck a project scope. One is a mature standalone platform you can use today the way any Informatica customer does. The other is a promise that it gets woven into Data 360 over the next several releases.
Why Salesforce paid $8 billion for plumbing
The reason is grounding, and it is the same reason your agents underperform in production. Salesforce’s own 2026 research put a number on it: most data leaders say governance has not kept pace with their AI ambitions, and a meaningful share of organizational data is considered untrustworthy by the people who own it.
Marc Benioff’s framing at the close was blunt.
Data and context is the true fuel of Agentforce, and without clean, connected, trusted data there is no intelligence, only hallucination.
That matches what teams see. An agent demos beautifully on curated data, then meets your real Account object, with its four records for one company, its stale addresses, and its custom fields nobody can define.
The model is fine. The data under it is not. This failure mode sits behind most stalled pilots, which is why data quality is the real AI-readiness work, not model selection.
Informatica is Salesforce’s platform-level answer. MDM gives you one defensible version of “who is this supplier” instead of four. The catalog and lineage let you trace an agent’s answer back to a source. Quality rules catch the bad record before it grounds a wrong response.
None of that is glamorous, and all of it decides whether an agent can be trusted.
Where it overlaps what you already have
Before you assume you need any of it, map the overlap against Data 360’s native features. You may already own the capability.
Lineage is the clearest case. Data 360 tracks lineage natively across streams, transforms, and data model objects, and that is usually enough to answer “where did this field come from.” Informatica adds catalog-grade lineage across systems Data 360 never touched, which matters when the answer lives in an on-prem warehouse three hops away.
I covered where the native tracking stops in the piece on lineage in Data 360. Most orgs do not need cross-system catalog lineage until an auditor asks a question the native view can’t answer.
Identity resolution is the trickier overlap. Data 360’s match and reconciliation rules link records into a unified profile, and if you have tuned those rules to not over-merge, you have a working unification layer.
MDM does something adjacent but distinct. It survivorship-merges into a mastered record with a governed lifecycle, stewardship, and the ability to push the golden record back to source systems.
If your only consumer is activation and agent grounding inside Salesforce, the unified profile is often enough. If finance, your ERP, and three other systems all have to agree on one master record, that is MDM’s job, and Data 360 was never going to do it.
Ingestion overlaps too. Data 360 has connectors, zero-copy federation, and the Ingestion API. Informatica’s integration engine is heavier and reaches systems Salesforce’s connectors don’t. If your zero-copy setup already federates the warehouse you care about, a second pipeline tool adds nothing but cost.
The two decisions worth making now
Both of these have longer lead times than a typical Data 360 configuration, which is why they deserve a decision before the integration finishes.
First, the MDM decision. If you have a real master-data problem, meaning multiple systems that disagree on the same customer, product, or supplier and it is blocking an agent or your reporting, you need MDM now, not in a future release. The only question is whether you wait for the Salesforce-native path or buy a mastering solution today.
My bias is to solve the business problem with whatever is GA and design so the golden record feeds Data 360 as a source. If you have no mastering problem, do not stand up a project to acquire an MDM tool because your vendor now sells one.
Second, the governance decision. Governance is the part you cannot retrofit cheaply once agents are live. Decide now who owns data definitions, how a field earns the right to ground an agent, and how you prove an answer’s provenance. Native Data 360 lineage and disciplined ownership get you a long way before any Informatica catalog arrives. The tooling makes it easier; it does not make the decisions for you. That is the same discipline behind governing agent access to Data 360, and it does not wait for a product.
What I’d tell a team this quarter
Keep building. The acquisition changes none of your data streams, transforms, identity rules, or activations, and there is no reason to pause a Data 360 rollout waiting for Informatica to land inside it. Use the standalone Informatica platform today if you have a problem it solves. Design toward the woven-in Data 360 experience as a direction, not a dependency you block on.
The real value of the deal, for you, is the stake Salesforce put in the ground: the data foundation is the product, not an afterthought under the agent. That was always true. Now the roadmap agrees. Spend the waiting period getting your definitions, ownership, and quality rules in order. Those decide whether your agents ground on trusted data, and no acquisition does that work for you.
Understanding the basics
Did Salesforce complete the Informatica acquisition?
Yes. Salesforce signed the agreement in May 2025 at $25 per share, roughly $8 billion in equity value, and completed the acquisition on November 18, 2025. By May 2026 the products were marketed as “Informatica from Salesforce,” with integration into Data 360, Agentforce, MuleSoft, and Slack described as a multi-release roadmap rather than one launch.
Does Informatica replace Data 360?
No. Data 360 stays the ingestion, unification, and activation layer inside Salesforce. Informatica adds master data management, a cross-system catalog and governance suite, and a heavier integration engine. They overlap on lineage and ingestion, but MDM’s governed golden record and Data 360’s unified profile do different jobs, and owning one does not remove the need for the other.
Do I need to buy MDM now that Salesforce owns Informatica?
Only if you have a master-data problem: multiple systems that disagree on the same customer, product, or supplier record, and it is blocking reporting or agent grounding. If your only consumer is activation and grounding inside Salesforce, Data 360’s unified profile is often enough. Don’t start an MDM project just because the capability now lives in the family.
What is CLAIRE in the Salesforce context?
CLAIRE is Informatica’s AI engine that powers data discovery, quality, cataloging, and governance across the IDMC platform. In the Salesforce era it has started surfacing in new places, including a CLAIRE-in-Slack experience for invoking data actions conversationally. It is distinct from Agentforce and from the Atlas reasoning engine. Think of it as the intelligence layer over the data-management tools, not the customer-facing agent.
Deciding whether your master-data and governance gaps need a tool today or can wait for the native path, and getting Data 360 grounded on data your agents can trust? That’s the work we do. Getting the foundation right is what separates an agent that helps from one that hallucinates.
