Informatica and Data 360: two jobs, two owners

A data owner switches Data 360 off on a Friday because a steering slide says Informatica replaces it. The slide has one box, two logos, and a line that calls the MDM match a golden record. On Monday an activation that depended on the unified profile does not run. A seller cannot see the orders that profile had gathered. Someone, following the golden-record line, deletes the account the match had only linked, and keeps the one that looked more complete. The deleted account held the open opportunity. The match had not chosen a winner. A person with a slide had. The opportunity is gone, the activation is quiet, and the acquisition has been asked to do two things it does not say.

Salesforce completed the Informatica acquisition on 18 November 2025. Data Cloud had already been renamed Data 360 on 14 October 2025. Those are two dates and two products. The later date does not retire the earlier product. The match does not delete the loser, because a match is not a golden record, and identity resolution is not one either.

#What the close actually brought

The press release states the scope in one sentence, which you should keep whole: "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." Read the list inside it and stop. Catalog. Integration. Governance. Quality. Privacy. Metadata. Master data management. Those are services named at the close. The sentence does not say Data 360 is withdrawn. It does not say a match overwrites a record. It does not say identity resolution has become a single winning customer. If a proposal adds those verbs, it has left the source.

Use the words the sentence uses when you brief a steering group. Catalog is a list of what data you have and where it lives. Integration, in this sentence, is part of Informatica's offer. It is not a quiet rename of some other integration product you already run. Governance is who may do what with a data set. Quality is whether the values are fit to use. Privacy is the constraint on that use. Metadata is the description that lets the next person find the set. Master data management is how you relate records that claim to be the same real thing. Each of those can be a line on a quote. None of them is a permission to switch another product off.

Write one owner per line. A catalog without an owner becomes a slide. A quality rule without an owner becomes a score nobody acts on. An MDM match without an owner becomes a delete, which is what happened to the opportunity. The owner is a person in the organisation who can refuse a merge. A committee is not an owner. A model is not an owner.

#Data 360 was renamed, and it was not replaced

The rename has its own sentence, and it is only a rename: "As of October 14, 2025, Data Cloud has been rebranded to Data 360." On 14 October 2025, Data Cloud became Data 360. That was before the Informatica close. Update diagrams that still say Data Cloud. Do not update them by erasing Data 360 and writing Informatica in the same box. Informatica does not replace Data 360. A pipeline that ingests, harmonises, and activates can still be the Data 360 job. A catalog of sources can be the Informatica job. If you cannot say which is which, you are not ready to buy either implementation.

People will try to collapse them because both are "data". Collapse is how Monday's activation died. The profile the activation read was a Data 360 output. Turning the product off to honour a new logo removed the output. The catalog, had it been switched on, would have described sources. It would not have answered the activation by itself. Buy the description if you need a description. Keep the pipeline if a person is waiting on it. Write both sentences before anyone disables a job.

Do not describe the rename as a migration of Data 360 into Informatica. A rename changes a label. An acquisition adds a set of services. Neither event is a field map from one product into the other. If you need a map, it is a project of its own, with a source object, a target, a key, and a test. It is not included in the date.

#A match is not a golden record

Master data management can tell you that two records might be the same customer. That is a proposal. A person accepts it, refuses it, or asks for a better key. Acceptance can link the records so a reader can see both. It does not require you to delete one, and it does not require you to copy every field from one onto the other. Survivorship, if you use that word at all, is a rule you write and a person you name. It is not a property of the acquisition.

Identity resolution is not a golden record. Do not let a workshop say that it is, whether the speaker is talking about Data 360 or about Informatica. A unified profile can help a reader. It is not a licence to drop the source rows, and it does not pick a winning value by magic. If two systems disagree on an email, the disagreement stays until someone owns it. Deleting the account that held the opportunity was a choice a slide encouraged. The source material does not encourage it. Put the prohibition in the statement of work in plain words: no delete, and no overwrite, without a named person and a tested rule.

The same prohibition covers a "merge duplicate accounts" job sold as part of the implementation. Merging is a business rule. It needs the key, the fields a human must review, and a way to undo. A confidence score you invent in the room is not the rule. This page will not invent a threshold, a percentage, or a match rate. If the product you own shows a score, read the document for that score. Do not type one into the quote because the workshop wanted a number.

Quality and privacy sit beside the match, not under it. A match that links a record you are not allowed to use has not become allowed. A match that links a blank email to a good email has not made the blank one good. Write the quality rule and the privacy rule as their own lines, with their own owners. A single "data cleanup" line will hide both, and it will hide the delete.

#What the bill is made of

Implementation cost means the parts of the bill. There is no dollar figure here, and there is no claim about how much of your estate the catalog will cover. Coverage is a list you write.

The catalog line names the sources you will describe first, not every system anyone has heard of. Each source has an owner and a classification. A source without an owner will be connected because a demo needed it. Integration, as a line, names the movements you actually want: which system, which object, which key. It does not say "replace the integration platform". If you already run a different integration product, keep it on its own quote until you have a reason to move a named flow. That neighbouring decision is MuleSoft, which is not this acquisition.

Governance names who may certify a data set and who may not. Quality names the defects you will detect, and what happens when one is found: block, warn, or repair under a rule. Privacy names the fields that must not flow into a place a seller can browse. Metadata names who writes the description a new analyst can trust. MDM names the match you will propose, the person who accepts it, and the explicit ban on deleting the losing row.

Data 360, if it stays, is a separate line: the pipeline, the person who waits on it, and the test that it still runs after Informatica work begins. If that line is missing, the Friday switch-off will happen again, because the plan never said to leave it on. Cutover is not a cutover off Data 360. Hypercare is the week after, with both owners checking their own job. Training is the next person who can refuse a merge.

#The week Data 360 was switched off

Monday the activation is empty. Tuesday the seller notices the opportunity is missing and blames the new MDM tool. Wednesday someone restores from a backup, which brings the account back and also brings the old duplicates, because the restore was not a merge rule either. Thursday the steering group asks for a golden record again, using the phrase the slide taught them. Friday you are explaining two products that were never the same, to a room that has already deleted a record.

That week is the cost of a bad sentence. The repair is to turn the Data 360 job back on if you still need it, to stop deletes, and to write the match as a proposal. Do not add another tool in the same week. You are not short of logos. You are short of an owner for a disagreement.

#The test a buyer should use

Searches ask for the best Informatica Salesforce integration agency, for a consultant to hire, and for an implementation partner. Use a test on your sources.

Ask which job is the catalog, and which job is the Data 360 pipeline. A partner who says Informatica replaces Data 360 has failed before the workshop starts. Ask who owns a match when two systems disagree, and what that person is forbidden to do. The forbidden act is deleting or overwriting without a written rule. A partner who calls identity resolution a golden record, or who calls an MDM match one, has failed. Ask them to leave any match rate they cannot show in your product off the quote.

Ask for the source list with owners, not a platform diagram. Ask which existing integration flows are out of scope. A partner who bundles every flow into the new logo is selling a rewrite you did not request. Hiring a consultant is this refusal, said clearly. A ranking of firms will not notice that your opportunity was deleted.

Do not accept a best-agency claim, including one aimed at the firm publishing this page. Compare two firms on whether they keep Data 360 and Informatica as separate sentences. If they cannot, do not sign.

#What you settle before anyone merges a row

Write the two product sentences. Write the sources in the first catalog, each with an owner. Write the match as a proposal. Write the name of the person who may accept it. Write that identity resolution is not a golden record, in the statement of work, so a later slide cannot smuggle the phrase back in. Turn deletes off for matched records until that person has a tested undo.

Then run one disagreement on purpose. Two emails, one customer, an open opportunity on the record someone might have dropped. Show that both records remain, and that the activation still runs. If the only way the demo looks tidy is a delete, the demo is the incident. Stop it.

The quote is ready when a new owner can see which product describes the data, which product serves the waiting activation, and who may accept a match. If the page still says the products have merged, send it back. The close on 18 November 2025 brought a list of services. It did not retire the rename of 14 October 2025, and it did not pick a winning row.

#The other searches

The project quote is on informatica implementation cost. That page does not print a figure. Who bought the company is on what happened to informatica. The connector is on integrating informatica with Salesforce. Whether to move is on should I migrate from informatica. The customer fee is on informatica licence cost. Who to hire is on hiring for informatica. This page does not rank an agency.