Salesforce closed its eight billion dollar acquisition of Informatica in November 2025, ahead of the original schedule, and has spent the months since actively folding the data management vendor into Data 360, the rebranded successor to Data Cloud. For organisations running Salesforce alongside MuleSoft or Tableau, or evaluating any of the three, understanding how Informatica now fits commercially is no longer a future consideration. The integration is live and shaping product and pricing decisions today.
Why Salesforce Wanted Informatica Specifically
The strategic logic behind the deal centred on a gap that MuleSoft alone did not close. Independent analysis of the acquisition described Informatica as bringing enterprise-grade metadata management, cataloguing, data quality, and governance to complement Salesforce’s existing application-layer strength through its CRM heritage and MuleSoft integration capabilities, positioning Salesforce to compete more directly as the model layer underneath AI agents becomes increasingly commoditised and competitive differentiation shifts toward the ability to act on diverse enterprise data with precision and context.
That framing matters because it tells you where Salesforce’s investment priority sits now that the deal has closed. This was not primarily a cost synergy acquisition aimed at trimming overlapping functionality. It was aimed at giving Agentforce a genuinely trustworthy data foundation, which means Informatica’s roadmap is now shaped by how well it serves that agentic AI mission rather than continuing purely along its pre-acquisition independent path.
It is also worth noting this was Salesforce’s fourth major data and integration acquisition in under a decade, following MuleSoft in 2018, Tableau in 2019, and Slack in 2021. Each of those earlier acquisitions followed a broadly similar pattern: a period of relative independence immediately after closing, followed by progressively deeper integration into the core platform’s commercial structure over the following eighteen to twenty-four months. There is little reason to expect Informatica’s trajectory to look meaningfully different.
How Informatica Now Fits Into Data 360
Salesforce has been explicit about the division of labour between its newly combined data assets. MuleSoft remains the platform’s go-to tool for real-time integration and API-led connectivity, while Informatica’s role centres on deep data preparation, transformation, and governance, with Data 360 becoming the unified AI-ready data hub powered behind the scenes by Informatica’s more mature data engine handling batch and streaming ingestion, master data management for unifying customer identities, and governance, quality, and compliance through Informatica’s lineage and catalog tools.
That division of labour is genuinely useful for evaluating where new spend is actually justified. An organisation with mature MuleSoft integration already handling real-time connectivity well does not necessarily need to expand that investment simply because Informatica is now available. The commercial opportunity, and the corresponding new cost, sits specifically in the data governance and master data management layer Informatica adds on top.
What Salesforce Says Customers Actually Get
Salesforce’s own product leadership has been direct about the practical problem this combination solves. Informatica’s chief product officer has framed the core issue as AI being unable to see the full picture when context is scattered, stale, or inconsistent across an organisation’s systems, positioning the combined Data 360 and Informatica stack specifically as the fix for that fragmentation when enterprise customers connect their external data to Agentforce workflows.
For organisations whose Agentforce deployments are underperforming specifically because agents lack reliable context about customer or operational data, this combination is worth evaluating seriously. For organisations whose Agentforce challenges are more about adoption, workflow design, or change management than data quality, adding Informatica licensing is unlikely to address the actual bottleneck, regardless of how compelling the platform story sounds.
The Commercial Question Worth Asking Directly
Independent coverage of the acquisition close has flagged the central question that remains only partially answered even now that integration work is underway: how deeply and how quickly Informatica’s capabilities actually get folded into a unified commercial offering versus continuing to exist as a separately licensed product sitting alongside Data 360. SalesforceBen’s coverage of the closing noted that the deal completed ahead of schedule specifically because Salesforce wanted to accelerate exactly this kind of integration work, positioning Informatica’s contribution to Data Cloud’s functionality as a customer data platform around ensuring data from across the organisation is not just unified but clear, trusted, and actionable.
Any organisation currently negotiating a Data 360 or MuleSoft renewal should ask directly whether Informatica capability is being bundled into that agreement, priced as a genuinely separate line item, or offered as an optional add-on with its own distinct commercial terms. The answer materially affects the total cost picture, and it is not yet consistent enough across the market to assume a default structure without confirming it explicitly.
What Existing Informatica Customers Should Do Now
Organisations that were running Informatica independently before the acquisition, entirely separate from any Salesforce relationship, face a distinct set of questions. Confirming how existing Informatica contracts transition under Salesforce ownership, whether pricing structures change at the next renewal, and whether continuing as an Informatica customer without a broader Salesforce relationship remains a viable long-term path are all reasonable questions to raise directly with the account team managing that relationship, rather than assuming continuity of terms by default.
This is particularly relevant given Salesforce’s clear strategic intent to position Informatica as a component of a broader agentic AI platform story rather than a standalone data management product. Organisations with no other Salesforce footprint should watch closely for signs that Informatica’s roadmap and pricing are increasingly optimised for customers running the full Salesforce stack rather than continuing to serve standalone Informatica customers equally well.
Modelling the Combined Total Cost Honestly
For organisations already running MuleSoft and now evaluating whether to add Informatica capability, or Data 360 and evaluating the same question, the honest total cost model needs to include more than the headline Informatica subscription figure. Integration work connecting Informatica’s governance and cataloguing capability into existing MuleSoft flows and Data 360 pipelines is unlikely to be a zero-effort exercise, regardless of how tightly Salesforce ultimately integrates the two products at the platform level.
Budgeting realistically for that integration effort, rather than assuming a newly acquired product slots in automatically because it now carries the same corporate parent as the rest of the stack, avoids the kind of underestimated first-year cost that has become a recurring pattern across large enterprise software acquisitions generally, not something unique to this particular deal.
Conclusion
Salesforce’s acquisition of Informatica has moved well past the announcement phase and into active integration, with Data 360 positioned as the unified hub and Informatica supplying the governance and master data management depth MuleSoft alone never provided. The commercial structure underneath that integration is still evolving, which means organisations negotiating any Data 360, MuleSoft, or Informatica relationship right now have a genuine opportunity to shape favourable terms before the bundled pricing model fully solidifies.
Confirming exactly how Informatica capability is priced relative to existing Data 360 and MuleSoft agreements, and evaluating honestly whether an Agentforce deployment’s actual bottleneck is data quality or something else entirely, are the two most useful steps before committing further budget to this expanding part of the Salesforce platform.
