Informatica licence cost after the Salesforce acquisition

Salesforce's announcement of the close says that "The close of the acquisition brings Informatica’s rich data catalog, integration, governance, quality and privacy, metadata management, and Master Data Management (MDM) services to the Salesforce platform." That sentence is about capability, and it is easy to read it as a promise of a combined licence. It is not one. Informatica and Data 360 were bought on different paper, are measured in different units and are priced on different pages. The practical question for a buyer is how each is licensed today, and what happens to your bill if both are in the architecture. The services side of an Informatica project is covered on the Informatica implementation cost page. This page is only about the licence.

#Two licences, two meters

The fastest way to see the difference is to put the units next to each other. Informatica's consumption pricing page and Salesforce's Data 360 pricing page were both read on 13 October 2026.

The Data 360 name itself is recent. Salesforce's help page says "As of October 14, 2025, Data Cloud has been rebranded to Data 360." so older proposals and older blog posts will call the same product Data Cloud, and any price you find under that name needs its date checked.

#How the Informatica licence works

Informatica describes its model in a few plain sentences. Processing Units give a customer access to all the eligible cloud services listed in its Cloud and Product Description Schedule, and the same page adds that "They can also access all Informatica master data management on a per-domain records basis." So there are two metering ideas under one contract: a general pool of units that any eligible service can draw on, and master data management sized by the records in each domain you manage.

The pool is measured per scaler. Informatica says that "IPU consumption is calculated per scaler, based on the scaler's usage including Secure Agent, CDI-e, Data Mass Ingestion volume and more." The scalers are defined in a Measurement Guide, and that document, not the marketing page, is what turns a pipeline design into a unit count. If you are comparing a proposal against a pilot, ask which version of the Measurement Guide the quote assumes, because a scaler definition can change how many units the same workload burns.

Informatica does not publish a rate per unit. Its page offers a way to get a sample price range based on your use case, which is a quote route and not a rate card. That puts Informatica in the same position as most enterprise data products: the price is a negotiated function of how many units you commit to, for how long, and on what terms.

One feature of the model deserves attention before you sign. The page says new eligible services are expected to be included in the platform and automatically activated for customers once released. That is convenient, and it is also an exposure. Ask what activation means for metering. A service switched on and left alone should not consume anything, but you want that written down. The same page says that "The Intelligent Data Management Cloud administrator can control which user has access to each service, monitor usage via a dashboard, and set consumption threshold alerts to ensure cost containment." Use all three controls from the first day, and name the person who owns them.

#Where the two licences overlap

A project that buys both products is where licence cost goes wrong, because several jobs can be done in either place and each place has a different meter.

Take matching and unification. In Informatica, master data management is sized by records per domain. In Data 360, unification is one of the metered actions on the pricing page. If a design matches customers in both, you pay for the same outcome twice, and the two results may disagree. The licence decision is therefore an architecture decision: choose which system owns the matched record and make the other consume it.

Take ingestion. Data 360's page lists batch ingestion as free and charges for what you do with the data afterwards, including preparing it, unifying it, building segments, querying it and sharing it. That changes the economics of cleansing upstream. Cleansing in Informatica spends units but can shrink the number of records Data 360 later unifies, segments and queries. Cleansing in Data 360 costs credits instead. Neither is automatically cheaper. The answer depends on volumes, and you can only know them by measuring a representative load.

Take zero copy. Salesforce lists zero copy sharing as a metered action in Data 360, so federation is not free just because nothing is copied. If an Informatica pipeline already lands the same data in a warehouse that Data 360 reads through zero copy, you are paying for movement and for access.

The Data 360 pricing page frames the choice this way: "Choose Credit-based pricing for a flexible, dynamic model that scales alongside your specific consumption, or Profile-based pricing for a predictable, flat-rate model designed for control." Credits suit uncertain usage and profiles suit a predictable one, so the right choice depends on how stable your profile count is. The same question of predictability applies to Informatica, where a steady, well-understood workload suits a larger committed pool and an exploratory one suits a smaller pool you can top up.

#Contract and renewal mechanics to settle

An IPU contract has the structure of a prepaid pool. Informatica's own wording about paying for what you need now and scaling for the future says as much, but the pricing page does not publish the commercial terms, so each of the following is a question for your order form.

Add two points that are particular to the acquisition. Informatica's site now carries the line "Informatica from Salesforce", so ask whether your next renewal stays on Informatica paper or moves to Salesforce paper, and what changes if it does. Ask also whether Salesforce intends to offer a combined commercial construct, such as credits that can be spent on both products. Do not assume one exists. If a salesperson says it does, ask to see it in the contract, with the exchange rate between units and credits written down.

#What the Data 360 list prices mean in practice

Because Data 360 is the one side of this pairing with published numbers, it is worth turning them into arithmetic, so you can test any proposal against them. These are list prices read on 13 October 2026, before any negotiation, and they are an illustration, not a quote.

If you choose the per-profile route and hold 500,000 unified profiles, the Profiles plan at USD 240 per 1,000 profiles a year comes to USD 120,000 a year, and Enterprise Profiles at USD 420 comes to USD 210,000 a year. The difference buys more included actions and a higher allowance of Flex Credits per profile, which the pricing page gives as one credit per profile on the first plan and two on the second, plus data masking and ad audience add-ons on the second. If you choose Flex Credits, USD 500 buys 100,000 credits, so a million credits is USD 5,000. What a credit buys depends on the rate card, which sets how many credits each action costs, and you should read that card for the actions in your design before you trust any total.

None of this tells you which model suits you. It tells you how to check a salesperson's number. If a proposal quotes a figure for a given profile count that is far from the arithmetic above, ask why, and make them name the add-ons, the term discount or the different plan that explains it.

#Three traps in consumption licences

The first trap is the pilot that runs light. A proof of concept on sample data burns a fraction of what the production load will, so a pool sized from the pilot is too small. Scale the observed burn by the real volume and the real schedule, not the demo's.

The second is domain creep in master data. A domain is a business area such as customer, product or supplier, and the pricing page counts master data on a per-domain records basis. If the contract does not define a domain precisely, a later argument about whether a new data set is a new domain becomes an argument about price. Write the definitions into the order form, along with the record counts you are licensed for.

The third is the renewal that quietly changes the unit. A rename or a repackaging after an acquisition is a natural moment for a discount to reset or a service to move between bundles. Ask for the unit price, the pool size and the list of included services to be compared line by line against your current agreement.

#How to size an Informatica pool

Do not size the pool from a slide. Size it from measured consumption. Start by listing the pipelines, the scalers they will use and the volumes they move, and list the master data domains with an honest record count for each. Then run a representative workload on a pilot allocation and read the usage dashboard the page says is available. Multiply the observed burn by your expected growth, add a headroom margin you can defend, and commit to that, not to the larger number that makes the discount tier look better.

Set threshold alerts at stages, not at the end, so the first alert arrives with enough time to act. Review actual burn against forecast every month, since the page describes usage tracking as a FinOps activity. Put the same discipline on the services you do not use yet. A pool bought to cover planned future services is a commitment to spend on things that do not exist, and the auto-activation model means you can add them later when the need is real.

Finally, decide up front which system does each job. A one-page responsibility table, saying where matching happens, where cleansing happens and what Data 360 consumes, will do more for your licence cost than any negotiation.

#How to compare two offers

You may be comparing an Informatica quote with another integration platform, or an Informatica quote with a plan to do the work inside Data 360. Put them on one grid. Compare the unit, what the unit buys, how you can see the burn, what happens at the limit, how master data is counted and how the term and exit work. A cheaper unit price on a platform that burns more units for your workload is not cheaper. Ask each vendor to price the same pilot workload and compare the totals, not the headline units.

Include the people cost in the comparison too, even though it is not a licence line. A consumption model rewards teams that watch usage, so someone has to own the dashboard, the alerts and the monthly review. If nobody will, a flat commitment with generous headroom may suit you better than a tight pool that triggers overage rates, and that is a legitimate reason to pay a little more for the same capacity.

#Where the other questions sit

The services fee and the question of who owns which attribute belong on the Informatica and Data 360 page. Who bought the company belongs on what happened to Informatica. The rule about not overwriting a good value belongs on integrating Informatica with Salesforce, and the question of whether to move belongs on should I migrate from Informatica.